Clangd preprocessor define issue - opacity stops working after toggling Configure

[Michael12]

Hello,

I'm having an issue for a few latest versions of clangd. I was hoping this issue would be resolved in newest update of VS Code extension - clangd v1.0.5., but still with no success. 

Issue: I'm using two Configurations in CMake -> Configure. Configurations are defined in CMakePresets.json like this:

I'm using define as this:

 

I'm switching configuration via CMake->Configure->Select Configure Preset.

Now, switching Configuration on clangd v1.0.2 will highlight/fade non-used define correctly. Switching to clangd version v1.0.4, it's no longer working correctly.

I have set the setting on v1.0.4 as such:

Opacity is 0.5. If I change the Configuration, the Opacity no longer works on the code segment:

But, if I go to settings and just enter the value 0.5, it starts working again, untill the next Configure change.

This issue in not on v1.0.2, only at v1.0.4 and v1.0.5.

[Cartu38 OpenDev]

@Michael12 
What happens if after preset selection update you're closing & opening back your .c file ? Is opacity applied in sync. expectation ?

[Cartu38 OpenDev]

@Michael12 
I'm able to face the same starting 1.0.4. File closure or switch between 2 editor tabs is applying proper rendering refresh.

[Michael12]

Yes! You're right. Switching tabs or closing and reopening the file will refresh the opacity. It's still little inconvenient. Is it possible to fix it in future? Thanks for help.

[Kouthair]

Hello @Michael12 ,

I was able to recreate the same behavior, and I have forwarded your request to our development team to look further into it. (Internal ticket ID: 0062377)

I will let you know if there are any updates on this matter.
As previously discussed, switching tabs does set the correct opacity.

PS: Ticket ID: 0062377 is an internal tracking number and is not accessible or usable by customers.