Possible bug

[sgranado]

I am on SE2008.  When I do a click on an entry in the drop down in the references toolbar/tab, it appends () before it begins the tag search.  This always results in a Tag not found error.  I do not think its correct o append the () since the drop down includes the (...) that are important to the tag.

Hope my explanation makes sense.

[Graeme]

I don't see this behaviour.  If an entry in the drop down list doesn't have parentheses already, they get added, but if they're already there, they don't get added.  Have you got the latest hotfixes  - revision 26.  There was a bug related to the references drop down list that was fixed but it might not be your problem.  If it's not, maybe you could post a screenshot that shows the extra parentheses or describe how to reproduce.  (also what O.S are you on)

Graeme

[sgranado]

I have attached a picture.  Hopefully it clarifies.

I am on XP.

[Graeme]

I don't get this behaviour.  If I explicitly type sprintf(proto)() in the search box, slick throws away the spurious trailing parentheses and does the correct search.  If I type sprintfx(proto)() in the search box, slick says "Tag 'sprintfx(proto)' not found" i.e. it's thrown away the extra parentheses.

Does find references work for you at all?  e.g. if you hit Ctrl+/ (push-ref) does it find references to the symbol the cursor is on?

Did you install the latest hotfixes, making sure to install the latest "required" hotfix before the cumulative hotfix?

There's some things you could try...

1: Try rebuilding the tag files involved - the project/workspce tag file and the C/C++ library file.

or

2: Try a brand new config directory.  Create a new empty folder called e.g. c:\temp\slick_config.  When you invoke slick, add -sc c:\temp\slick_config to the command line that invokes slick.  Slick should create a new config folder named 13.0.0 in the slick_config folder.  You'll need to click yes when slick prompts you to create tag files for C/C++.  Without doing any other customisation, open the project you were on and try the sprintf find references problem.  If the problem is gone you might want to consider continuing with the brand new config folder.  You could try importing some of your config from you old config folder  - especially key bindings - use "export/import" in the key bindings dialog.  There's some other files that would be safe to copy over.  If you copy vusrdefs.e over, after loading it (type its name inclusing full path on the cmd line an dpress return) you should immediately check if the find references problem has come back.

or
3: In tagrefs.e line 484, you'll see this line

Code: [Select]

      if (find_refs(search_string,1)==0) {

You could insert a debug line immediately before this

Code: [Select]

      say('Refs debug :' :+ search_string);
The say command creates a debug window and shows the message  - see what it thinks search_string is.

Graeme

[chrisant]

@sgranado:  a hotfix was released a few weeks ago to address the extra () that got added.  It sounds like you probably need to get the latest hotfixes.  Be sure to get the required hotfix first, and then get the cumulative hotfix.