Re: [Valgrind-valkyrie-dev] sugesstions...

[Cerion Armour-B. <ce...@ke...>]

Thanks for the feedback Anton.

We're busy now fixing some bugs and supporting the latest valgrind release...

1. Fixed
2. I don't really understand why this is necessary: do you move your sources 
after building?
3i. ?! I can't reproduce this - can you send me the logfile pls?
3ii. Well spotted :-) I'll add it to the todo list
3iii. I don't understand what you mean, can you clarify?
4. I've added more options for the configure script - adding the functionality 
in the valkyrie options is too much work for now: maybe in the future :-)

Regards,
Cerion

On Tuesday 03 Jun 2008, Anton Dudarenko wrote:
> Your tool is simply excellent, but I would like to notice something in its
> behaviour and to suggest improving it.
>
> 1. To include horizontal scrolling for a LOG window. Otherwise it is
> impossible to see the full text of the memory check`s messages of an error.
>
> 2. To include possibility to open on double click a file even if it is
> certain by you as inaccessible. The obvious decision - simply to display a
> inquiry window with the text "On the given way a file it is not accessible
> - whether YOU wish to specify its place independently?" And if the user has
> specified it - to use the received way further and as consequence - already
> at once to open an editor window with the specified file on the specified
> line at double click...
>
> 3. To "cure" behaviour of buttons 'Open|Close errors' and 'Open|Close the
> selected item'. In the current version they work not correctly.
> 
> 3i. The first 
> command opens a tree only for SysCallParam and UnInitCondition nodes. The
> others remain folded.
> 
> 3ii. And it remains turned ON (the button visually is 
> pressed) even if I have folded after that all nodes by means of "arrow key"
> buttons on the keyboard.
>
> 3iii.
> The second command to become accessible to the chosen tree node of an error 
> messages only if this node has been preliminary opened and will fold again
> by mouse or by means of "arrow key" buttons on the keyboard.
>
> 4. In a window of program properties at a field of editor choice well to
> provide auto filling of a command line for 2-4 widespread editors
>
> gvim +%n
>
> vi +%n
>
> vimx +%n
>
> kate --line %n
>
> etc....
>
> And for the KATE editor it is necessary on one to reduce number of a line
> on which it will be necessary to move in the opened editor. It is an error
> of this editor itself that at the jump from a command line for the line 5,
> for example, actually it passes on 6.