-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Semantic highlighting isn't working with CreateWindow macros #11416
Comments
You appear to not be getting semantic highlighting for those macros in the CreateWindow call. Is IntelliSense working at that point or has it crashed? Do you see a "semantic token type" when viewing the token/scopes for the CreateWindow call? Are you able to provide a simple repro? We could also try to see if can repro it ourselves based on the screenshot info... |
@sean-mcmanus any update on this? btw I've seen the exact same issue with Visual Studio, and it was fixed |
@billgan1024 we share this code with Visual Studio, so that fix should flow into our extension the next time we take a merge. It won't be in 1.19 though because we're stabilizing for release. I expect it will be in 1.20.0. We could do a pre-release not long after 1.19 releases to stable. |
@billgan1024 This is fixed in our 1.20.x pre-release channel. |
When using macros defined in other files, sometimes the tokens/scopes are incorrect for macros inside the macro call.
For example:
CW_USEDEFAULT
is a windows macro but for some reason it is white instead of blue since it doesn't haveentity.name.function.preprocessor.cpp
as the foreground.However, when I define my own macros, the macros are now blue which seems to be correct:
So this highlighting is inconsistent.
Originally posted by @billgan1024 in #11248 (comment)
The text was updated successfully, but these errors were encountered: