[Done] Color Highlighting for SYSTEM VARIABLES in MS Editor

jpuziano · Post by **jpuziano** » Fri Feb 03, 2006 5:28 pm

Hi Support,

Would it be possible to provide color highlighting for all SYSTEM VARIABLES in the Macro Scheduler editor? Perhaps a new color not presently used?

That way, if a SYSTEM VARIABLE was used by mistake, users would see they're dealing with a SYSTEM VARIABLE and use something else.

This might prevent situations like in the following post...
http://www.mjtnet.com/usergroup/viewtopic.php?t=2584

Post by **Marcus Tettmar** » Fri Feb 03, 2006 5:47 pm

Good idea!

jpuziano · Post by **jpuziano** » Sat Sep 27, 2008 6:37 am

Hi Marcus,

Will color highlighting for SYSTEM VARIABLES be supported in the improved editor for the upcoming version 11 of Macro Scheduler?

jpuziano · Post by **jpuziano** » Tue Dec 02, 2008 11:14 pm

Hi Marcus,

While playing with the 11 betas, I was happy to see that you added color highlighting for SYSTEM VARIABLES... they were showing up dark red which was great. But now after installing the official 11 release... they're back to plain black.

I don't see an option to turn color highlighting on or off anywhere... how do I get the color highlighting back?

jpuziano · Post by **jpuziano** » Wed Dec 03, 2008 7:44 am

Hi Marcus,

OK, answered my own question, I entered the following in version 11 and this is how it looked:

Let>_DUMP_VARS=0
Let>_WRITE_LOG_FILE=0

Both are valid system variables... but only the first is getting the special highlighting... so I assume that the problem is that this (and perhaps other) new system variables have not been added to the list of system variables that the syntax highlighter looks for... please update.

Thanks and take care

Post by **Marcus Tettmar** » Wed Dec 03, 2008 9:38 am

I'll get that fixed in the first maintenance release.

kpassaur · Post by **kpassaur** » Wed Dec 03, 2008 1:51 pm

I just installed the offical update and have had some issues.

Half way through viewing an existing script the colors all became black and when I tried to edit it "End>" was inserted for what ever reason I don't know. Since it was an existing working script, I compiled it, (have not tested it yet - and won't bother) and it placed the header information in for the next compile (fantastic).

I opened another script and the same thing with the colors (I count on the colors) so I rebooted thinking that may fix it.) Same thing so I said forget it I will wait until someone else has the issues and reports it.

Well, I did a restore (the install did not create a restore point) so I used yesterdays, no big deal.

I went to open the script and it will not open in version 10 anymore. So I had to restore the script from my backup.

Post by **Marcus Tettmar** » Wed Dec 03, 2008 2:00 pm

Please please please please please read the release notes. If you edit a script in v11 you will NOT be able to open it in v10. This is stated in the release notes and has been the case since the beta was announced.

As for the colors, not sure what is happening there, but if you manage to find a pattern to reproduce please let me know.

JRL · Post by **JRL** » Wed Dec 03, 2008 3:26 pm

kpassaur wrote:I went to open the script and it will not open in version 10 anymore. So I had to restore the script from my backup.

If there is an absolute requirement to edit a script from the version 11 editor using the version 10 editor. Here is a way to do it. I'm not recommending this but I've done it and it worked for me. Be sure you back up the script before you try this.

- Open Windows Explorer
- Right click on the script file
- pick "Open With" then "NotePad" from the menu (or browse to notepad)
- Press CTRL+A (select all) then CTRL+C (copy)
- Close notepad
- Open the script in the version 10 editor
- You will see a few odd characters if this is a version 11 edited script
- Press CTRL+A (select all) then CTRL+V (paste)

Post by **Marcus Tettmar** » Wed Dec 03, 2008 3:31 pm

JRL wrote:
kpassaur wrote:I went to open the script and it will not open in version 10 anymore. So I had to restore the script from my backup.
If there is an absolute requirement to edit a script from the version 11 editor using the version 10 editor. Here is a way to do it. I'm not recommending this but I've done it and it worked for me. Be sure you back up the script before you try this.

- Open Windows Explorer
- Right click on the script file
- pick "Open With" then "NotePad" from the menu (or browse to notepad)
- Press CTRL+A (select all) then CTRL+C (copy)
- Close notepad
- Open the script in the version 10 editor
- You will see a few odd characters if this is a version 11 edited script
- Press CTRL+A (select all) then CTRL+V (paste)

Now do you want the quick way? Whilst in the v11 editor select File/Save As, and in "Save as Type" select "ANSI Script Files". Then the file will be compatible with v10 and earlier.

Post by **Marcus Tettmar** » Wed Dec 03, 2008 3:37 pm

That assumes you have v11 running of course. Otherwise, JRL's solution will also work.

The difference is just that v11 saves .scp files with Unicode encoding. v10 expects ANSI encoding.

Notepad gives you an encoding option when you save and autodetects the encoding when you open a file. So another way should just be to open the file in Notepad and then save it again, selecting ANSI encoding as you do so.

kpassaur · Post by **kpassaur** » Wed Dec 03, 2008 4:55 pm

Thanks for the tips to save a version 10 script.

I installed ver 11 on another PC and have the same issue with colors or should I say Commands being recognized. It is not on all scripts but on some of them (actually most of them that I tried).

I did notice (this maybe just me) that the ones that had Dialog Boxes were the ones that had issues. However, the colors change to all black at no specific command line.

It is really puzzling, if anyone wants to try one I will post it and they can see what they get.

Post by **Marcus Tettmar** » Wed Dec 03, 2008 5:01 pm

Please could you send me one of the scripts that causes problems. I haven't seen this issue myself having tested with all kinds of scripts of various sizes, but perhaps there is something in your script file. Might make sense if you send the .scp file as an attachment to my email address.

jpuziano · Post by **jpuziano** » Wed Dec 03, 2008 8:58 pm

mtettmar wrote:I'll get that fixed in the first maintenance release.

Thanks Marcus... I'll look for it then.

jpuziano · Post by **jpuziano** » Thu Dec 04, 2008 7:04 am

Per Macro Scheduler History page at http://www.mjtnet.com/mswhatsnew.htm

Version 11.0.26 03/12/2008

Fixed: Syntax highlighting being halted by "dialog" keyword
Fixed: _WRITE_LOG_FILE missing from syntax highlighter

Now works fine... thanks for the quick fix (same day!).

[Done] Color Highlighting for SYSTEM VARIABLES in MS Editor

[Done] Color Highlighting for SYSTEM VARIABLES in MS Editor

Color in editor and automatically entering End>

Version 11 and colors