Not sure I understand but if what you want is the equivalent of manually answering "yes" to the dialog box that pops up for each #define then you can modify the code in seldisp.e like this.
The defines I'm working with control conditional compilation.
Since there are so many (over 1000 actually), it makes the code impossible to follow.
I'm trying to find an automated or semi-automated solution for the Firmware engineers here, to take the original source,
process it by removing the conditional compiles (which have been satisfied by a list of #defines), and produce a view of the source code
without all of the preprocessor directives.
Slick Edit is the only tool I've heard of that will even come close to doing it.
But having to answer yes/no, true false for 100's of lines in each file isn't helping.
I would also like to understand how to preprocess the conditional compile statements (#if #else, etc)
for ALL the files in the project.
Currently, my solution is
run a program I've written to go through each .C file, and write a list of definitions such as
TURBO_MODE TRUE
BLINK_LED FALSE
to a file.
I then open this file, copy and paste this list of defines into the List Box under the SelectiveDisplay/Settings/Defines dialog.
This will then "preprocess" the conditional compile steps out of the source code (visually).
If I could find where the string of defines is stored in the project files, it might help, but it is not stored in any of the project files I've scanned, nor in any file under Program Files/SlickEdit, nor in the registry.
Yet, when I start another Slick Edit session, the defines which were previously entered in the Settings/Defines dialog are persistant.