Little Bugs on code navigation

[Pich]

Hi,

I hope you don't hate me for this new post. I've found another little bug ( maybe ) on code navigation function.

If you have:

x = func(a,b,c)

if you CTRL+LEFT CLICK or CTRL+ALT+LEFT CLICK you can go to declaration or definition.
But if you write ( I',ve found some code written in this way ... ):

x=func(a,b,c)

You notice the equal sign is near the function name ( without any space separating the function name from the equal sign )and you can't navigate.

------------------------------------------------------------------------------------------

Another issue is on code navigation with respect to files. If you have:

#include "prototype.h"

but on the disk the file is saved as Prototype.h, you cannot open that file, because of the different case.
On linux system this is mandatory cause linux file system is case sensitive. On windows system ( windows xp in my case ) the file system is case insensitive and you should open the file even if the name has a different case.

Sorry for all my posts, I hope I can help you developing a better product.

Pich

[eranif]

x = func(a,b,c)

if you CTRL+LEFT CLICK or CTRL+ALT+LEFT CLICK you can go to declaration or definition.
But if you write ( I',ve found some code written in this way ... ):

x=func(a,b,c)

You notice the equal sign is near the function name ( without any space separating the function name from the equal sign )and you can't navigate.

There is an bug opened for this in the tracker already

On linux system this is mandatory cause linux file system is case sensitive. On windows system ( windows xp in my case ) the file system is case insensitive and you should open the file even if the name has a different case

Please submit a bug report for this at sourceforge

Eran

[Pich]

Done here:

http://sourceforge.net/tracker/?func=de ... tid=979960