Hi, Mirek!
This is certainly an interesting attempt to make better code navigation.
In my opinion previous version had one good ability to switch between native and alphabet sorting. Personally I've used alphabet sorting because generally it was much easier to find one from alphabetically sorted routines.

I also would like to discuss the way items are visualized.

Mirek, it is certainly an era of widescreen PCs now, and it would be good to support widescreen features where possible. So if description of item is better fit into one line, it is better be so. In my opinion, you had an elegant visualization before:
<type> <namespace>::<item>
If you wanted to make it more elegant, you could make it something like this:
<namespace_semitransparent::><item>
(one column of semi-transparent drawn namespaces and next column of item names). And no horizontal lines.
If you need visualization, I'll make it.
This is how in my opinion it could be done better.

besides the width problem (and I have 1600 screen on notebook and 1920 on desktop), the other problem is that it is IMO good to see the name as first thing on the line.

mirek wrote on Thu, 31 July 2014 17:32

besides the width problem (and I have 1600 screen on notebook and 1920 on desktop), the other problem is that it is IMO good to see the name as first thing on the line.

Of course it is better! And I have a solution for you: you need to add return type and/or namespace ONLY in case of disambiguation, if you have items with similar signatures. In all other cases all you need is name of item, which will be draw first in line while fitting into single line.

One minor change: putting ':' in front of class name makes navigotor require full match.

So the list of options is now:

line number
'CAT' lists all elements where class name or member name contains 'CAT' (case ignored)
'STRING:CAT' lists all elements where class name contains 'STRING' and member name contains 'CAT' (case ignored) (so that includes e.g. StringBuffer::Cat)
':STRING:CAT' lists all elements where class name is equal 'STRING' and member name contains 'CAT' (case ignored) (does not include StringBuffer::)

EDIT (moved from other thread): The ability to switch between declaration and definition would be good.

Mirek, it would be nice to also get the jumping between declaration and definition when repeatedly clicking on the function/method name like it was implemented with the old version.

At the moment, when clicking on the function/method it only jumps to the declaration/definition currently present in the edited file (usually declaration if .h file is shown and definition in case of a .cpp file).

Regards
Matthias

I think that new navigator should appear in a new window as previous one. For example now I press ctrl-g and I type something and press cursor down and up to navigate through functions and editor cursor is moving instead. This is annoying. Very annoying I would remove navigator from splitview (problem with longer names) and put it only in a popup dialog. It was a way more convenient for me.

unodgs wrote on Wed, 13 August 2014 12:50

I think that new navigator should appear in a new window as previous one. For example now I press ctrl-g and I type something and press cursor down and up to navigate through functions and editor cursor is moving instead. This is annoying. Very annoying I would remove navigator from splitview (problem with longer names) and put it only in a popup dialog. It was a way more convenient for me.

OK, we can do that too - when Navigator is off, Ctrl+G could make dialog.

Overall, I thank for feedback, I have now some hopefully nice ideas I want to try...