-
Notifications
You must be signed in to change notification settings - Fork 319
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request]: ability to resolve structure global structure members on mouse-hover (VSC-1584) #1420
Comments
Unfortunately this a Language extension feature and our extension doesn't implement this yet. In our documentation we suggest users either Microsoft C/C++ extension or Clang extension for language support. It might be best to post a feature request in their respective GitHub repositories. |
Thanks @brianignacio5 , I've mentioned it in the Microsoft C/C++ extension repo. We can close this if preferred. |
Some follow up questions about your use case @bryghtlabs-richard
I just want to know since a user replied to you in the cpptools repository that is related to debugging, but it is my understanding that hover definitions are handled by the language extension so I'm not sure how is related to debugging. |
@brianignacio5 , here's my launch.json:
It happens when I'm debugging. I think showing the type would be reasonable when hovering when not in debugging. |
This issue has been marked as |
Is your feature request related to a problem? Please describe.
Yes - when I hover the mouse over a structure's member, it shows me the type(which is nice), but often I actually want to see the data inside the structure.
Example structure definition in header:
Example usage site:
Hovering on moveStatus.AIFrom shows:
Describe the solution you'd like
I'd like ESP-IDF VSCode to display the structure member variable's value instead, or in addition to, the type. Ideally, the same way that ESP-IDF VSCode displays structure member variables values when allocated on the stack.
Describe alternatives you've considered
I can add each global variable to the watch window, but it's quite time consuming.
The text was updated successfully, but these errors were encountered: