#if 0 inactive code

[joecar]

I can't get #if 0 code slabs to color as inactive code... what did I miss...?

Thanks.

[Dennis]

Do you have the feature disabled?  Document > C/C++ Options... > Color Coding > Language > |x| Color Inactive...

Have you changed your color scheme?  Double-check that the inactive code colors have a background that you can clearly see.  Tools > Options > Appearance > Colors > Comments > Inactive*

Are you looking for this to work in a language that does not have built-in C-Preprocessing support?  What language are we dealing with here?

If none of the above are the problem, could you post some sample code?

[joecar]

C code.

I have not changed to color scheme.

See attached pics.

[Dennis]

Only thing I can guess is that your code is actually in ANSI-C mode, so you might want to check those options.

Also, if you have changed to color coding in any manner so that #if is not detected as a preprocessing directive, that would break things too.

I would suggest trying this with is shiny new configuration to make sure the problem is not in your configuration.

Code: [Select]

vs +new -sc /tmp/shinynewconfig

[Graeme]

I can't get #if 0 code slabs to color as inactive code... what did I miss...?

Thanks.

In the Document menu -> select mode(...)    - what mode is shown.
Did you install a new version just before the problem started?
Does the problem appear in more than one file?
With slick closed, try deleting vslick.sta.

[joecar]

Document->Select Mode (C/C++)

I did change the color for block matching highlighting.

Problem appears for all open C/C++ files.

[joecar]

I deleted vslick.sta and inactive coloring still does not go.

[joecar]

Code: [Select]

vs +new -sc /tmp/shinynewconfig

Doing this, inactive color shows up ok.

[Dennis]

That would mean the issue is in your configuration, either colors, or color coding.  I'll take a look at your user.cfg.xml if you attach it and see where the problem is.

[joecar]

See attached, thanks.

[Dennis]

Uncheck Document > C/C++ Options... > Color Coding > Langauge > Preprocessing keywords can appear anywhere

This has an undesirable interaction with inactive code regions coloring.  Should not be a problem because C++ preprocessing can't just be anywhere, it has to be the first non-blank character.

I'll check into the interaction, because it should not break the normal case for coloring inactive code, but that fix would have to go in the next release, not hot-fixable.

[joecar]

Ok, I unchecked that and inactive coloring on #if 0 is fixed.

Thanks, appreciate all your help.

[Dennis]

Just for curiosity's sake, was there a particular reason you had enabled that option?

[joecar]

I'm not sure why/how that got checked in the first place.