Can Build->Select Configuration drive Selective Display

[Wanderer]

This thread -- http://community.slickedit.com/index.php?topic=276.0 -- suggested a new feature.  (Maybe it can already be done.)

It would be handy to be able to select a configuration (Build->Set Active Configuration) and have a certain set of tokens get defined for Selective Display.  Perhaps there is a _proj... or _project... handler that could be used.

It looks like _prjconfig_xxx might work.  The next challenge is setting the tokens for Selective Display, and then activating it.

[hs2]

You may tweak your project setup using the 'Open command' feature.
http://community.slickedit.com/index.php?topic=259.0
I'm going to make use of it to switch my C-Compiler tagfile setup for my Windows- and my embedded projects.

HS2

[dunkers]

switch my C-Compiler tagfile setup for my Windows- and my embedded projects

Am I missing something here? To change tag files (I have several embedded compilers along with Borland and Microsoft windows one) in the project properties I use the Compile/Link tab to specify the compiler.

I had missed that but support very kindly put me straight when I whinged about my sticky VC++ tag file...

[Wanderer]

You may tweak your project setup using the 'Open command' feature.
http://community.slickedit.com/index.php?topic=259.0
I'm going to make use of it to switch my C-Compiler tagfile setup for my Windows- and my embedded projects.

HS2

I'm not sure that will do what I want.  According to the on-line help:
Commands can be entered for projects that are executed when the project is activated. This information is stored per project, not per configuration.

I'd like per-configuration settings.  It is unclear from the Help as to what sorts of commands you can use, and where they are applied.
I'd like to do something like this:
preprocess XVTWS=1 MTFWS=7 XOLWS=5 WINWS=1 WIN32 MACWS=0 XmVersion=1 XVT_TEXTEDIT

Unfortunately, typing that in to the Open command window just sent SlickEdit on a long trip south...

[hs2]

@Wanderer:

Similar things happened to me when adding some stuff to the 'Open' commands.
@see http://community.slickedit.com/index.php?topic=264.msg1006#msg1006
Maybe commenting (as I did) the ref'd paragraph helps.

@dunkers:
Is it that simple ... I completely ignored that b/c mostly I roll my own build env.
It's a bit confusing that all avail. tagfiles are always visible in the tagfile list...
However, thanks a lot !
HS2