[Skip to # list below for questions]
First and foremost, I have been using C::B as my work editor of choice for over a year now, and have recommended it to others as well. I work in embedded development, and my project includes hundreds of files and a whole mess of preprocessor definitions to support our various product versions. All I have to do is #define one of these values in an included header file, and the code completion preprocessor parser handles this beautifully project-wide.
What I find lacking is the option I am teased with called "Gray out Inactive Preprocessor Code" in the general editor settings. I've seen a few mentions of this when searching the forums, but no real response or concern following them. I'll get to it:
1) Inactive preprocessor code is straight-up black, not gray. This makes it much less obvious for those of us who use black as a default text color, thus sort of defeating the purpose of the feature.
2) The feature does not work across multiple files within a project. I have tested this with the simplest single .cpp + .hpp file project. Defining the macro in the header file will still result in code being grayed out in the .cpp file. It has to be defined specifically in the same file I am looking at.
In my opinion these issues make the feature useless in any real project scenario, and makes me wonder why it is included in a default installation of C::B... It's unfortunate because I would really benefit from it if it was a little more robust. Perhaps it could be tied into the preprocessor parsing capability of code completion. As you can guess, I have no C::B development experience so I have no idea what kind of an undertaking this would be.
Mostly I am just curious if this is on anyone's radar, as it has been this way for quite some time now. I am currently using a nightly build from a couple weeks ago.
`Zach