This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Go To Definition is a game of luck

Hello,

the usage of the "Go To Definition" function is one of the most important function of the IDE for me. Working with software I`m using this function hundreds of times per day. In the past (up to 5.24.2) this was working without any problems. Today (5.35.0) I have have so much problems with this function. In 50% of all cases it works fine as usual. In the other 50% I`m always getting this enervating "No browse info for symbol in this context".
- yes, I enabled the creation of the browse information in the options
- yes, I rebuild the complete code
- yes, the header file with the searched information is included (open document and ctrl-f-search will find)
- yes, I hoped that with 5.35 the problem would be silently fixed ... but it does not
I can not imagine that such a great IDE like uvision has so elementary bugs ... the mistake must be on my side. Where is my fault ?
Please help !

friendly regards
Recently

Parents
  • I was wrong in linking Editor with F2. Thank you for the detailed explanation.


    You confirmed my findings. I noticed that input from keyboard is often ignored for few seconds when in editor. I looked what uVision is doing and there is a clang thread often taking as much as 10% of the CPU - without compiling code or using editor. Is it possible to turn off that dynamic syntax checking/browse info generation ? Would be great to have this option.

Reply
  • I was wrong in linking Editor with F2. Thank you for the detailed explanation.


    You confirmed my findings. I noticed that input from keyboard is often ignored for few seconds when in editor. I looked what uVision is doing and there is a clang thread often taking as much as 10% of the CPU - without compiling code or using editor. Is it possible to turn off that dynamic syntax checking/browse info generation ? Would be great to have this option.

Children
  • You can turn off the generation of browse info via the option "Options for Target - Output - Browse Information" in uVision

    You can also turn off the dynamic syntax checking via "Configuration - Text Completion - Dynamic Syntax Checking" in uVision

  • At the time I reported the issue, the "effect" had a 50% probability. In the meantime, our project has grown and the search almost doesn't work at all. Sometimes you see what you're looking for a few lines up, but the search isn't able to find it. Unfortunately I was not allowed to provide the code, so I hope that others have the same problem and that it will be solved soon. Since I personally need this functionality very often, I find working with uvision extremely uncomfortable and can only advise against using it.

  • There might be some correlation with the project size. It crossed my mind. Difficult to judge. We have no clue what is priority for them. I would guess it is well known issue but there is just not enough resources to sort it out. It is a trade off. You might expect this with free version but when you spend several thousand you migh say it is shocking
    Depressing ? Definitelly. Is it depressing enough I spend time to integrate toolchain with other robust IDE ? No.

  • have you tried the latest MDK v5.37? Is there improvement with your project using the latest MDK v5.37?