Author Topic: Code Navigation with project-specific tag files  (Read 802 times)

Jmathew

  • Community Member
  • Posts: 10
  • Hero Points: 0
Code Navigation with project-specific tag files
« on: March 02, 2017, 08:57:10 pm »
Hello everyone,
I have created 2 projects in a workspace and set them to "project-specific tag file". Under Tools->Tag files i see 2 project tag files, each listing the correct source files.
When i press CTRL+. i get a prompt because there are variables in both projects with the same name. I found an option "prioritize navigation to symbols in the currect project" which avoids the prompt but apparently always jumps to the marked active projects definition.
Isn't there an option to always jump to the defintion of the project  the open file belongs to?
Basically i wish code navigation and tagging would always be project-restricted. I would very much appreciate that. thank you.

Graeme

  • Senior Community Member
  • Posts: 1978
  • Hero Points: 226
Re: Code Navigation with project-specific tag files
« Reply #1 on: March 03, 2017, 10:57:38 am »
You could write a macro that switched the active project every time you switched to  a buffer.  Don't know what the performance would be like.  Would that help?

Jmathew

  • Community Member
  • Posts: 10
  • Hero Points: 0
Re: Code Navigation with project-specific tag files
« Reply #2 on: March 03, 2017, 09:16:29 pm »
Good idea. That would probably partly help. But I also get autocomplete and symbol highlighting from the wrong project. So i fear it's not that simple to solve this with a macro. I was hoping that there's a setting (I didn't see) to completly seperate projects. But it looks like project tagging is not intended to do what i imagined it would do...

Graeme

  • Senior Community Member
  • Posts: 1978
  • Hero Points: 226
Re: Code Navigation with project-specific tag files
« Reply #3 on: March 03, 2017, 10:22:49 pm »
If you switched the active project, wouldn't auto complete find the right one?  What do you mean by symbol highlighting?

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 3941
  • Hero Points: 256
Re: Code Navigation with project-specific tag files
« Reply #4 on: March 03, 2017, 10:47:24 pm »
You could create two separate workspaces. Only one can be open at a time. No way you get tags from a project not in the workspace. The downside is that you want to switch workspaces before editing files in the other project (use the project menu history -- it's easy and quick). Also, you can't use SlickEdit project dependency build stuff but I doubt that matters to you.

Jmathew

  • Community Member
  • Posts: 10
  • Hero Points: 0
Re: Code Navigation with project-specific tag files
« Reply #5 on: March 04, 2017, 02:22:50 pm »
No autocomplete suggests symbols from both projects and if i chose a symbol from the wrong project it gets bold (highlighted). creating seperate workspaces is what we have been doing. I just recently found out that slickedit supports project tagging, now. It doesn't do what i thought it would, though. Maybe slickedit will have that feature in the future  ;) Thanks for your replies