Multiple syntax controls, different color schemes?

I need to have more than one syntax editor control on a form, with independent syntax coloring. I assumed that the SetSyntaxAndColorScheme call would allow me to do this for each on an individual basis, but it looks as if the syntax controls store the coloring logic globally. This means that whatever was the last call to SetSyntaxAndColorScheme affects all syntax editor controls.

 

Is this what is supposed to happen? It makes the control rather restrictive if that is the case.

I think it is the LexConfigurationManager which is using the static s_ptrLexConfigurationManager_Default. This gets updated any time you alter the scheme in any CXTPSyntaxCtrl. What we need is to have each CXTPSyntaxEditCtrl keep their own CXTPSyntaxEditConfigurationManager rather than have a global one.

 

I seem to have some success with the following for each different CXTPSyntaxEditCtrl:

CXTPSyntaxEditConfigurationManagerPtr myManagerPtr = new CXTPSyntaxEditConfigurationManager();

mySyntaxEditCtrl.GetEditBuffer()->SetLexConfigurationManager(myManagerPtr);

 

Does this look right?

Hi Mark. Thanks, but I strongly prefer controls to be encapsulated. For example, if I set the font for a particular static text control I don't want the font for all static text controls in my application to change. Similarly, I would prefer to have syntax edit controls that are individually configurable and whose state does not depend on how a control elsewhere has been modified. However, I think that the existing code allows for this without any special build, just by maintaing a separate CXTPSyntaxEditConfiguration member as I've indicated above--presumably this is why this mechanism has been included anyway. This seems preferable to building a private version of the CodeJock library. Testing what I have done at the moment (I currently am using 4 slightly differently configured syntax editor controls in an application) that mechanism seems to be working fine so far (no crashes or memory leaks yet ).

I just wanted to second this.  We have a program that uses the syntax edit as pop-up sub-windows to edit macros and scripts within our program.  Each instance will have a different set of variable names that we want highlighted, so each needs its own space.  We could solve it by creating bogus file extensions, but that seems like a kludge.  The fix robin_l mentions does indeed work for us, though it has the side-effect of making launching the syntax editors slower because the code ends up loading the scripts twice (then not using any of the loaded scripts once we introduce our dynamic runtime one).