R2D2-
Look up a couple posts. The next version already has that issue corrected by matching the macros with a macro list, which is tied with my version compatibility setting so only macros that are valid for the version your on will highlight. Also I think it will be o.k. to have anything following a $ be a variable because I dont highlight things inside quotes. Therefor

$ThisWillHighlight = QUOTE But $4.23 this will not ENDQUOTE

Or a better example would be:
? QUOTE The value of $ThisIsntColored is ENDQUOTE + $ThisIs

I think it will work pretty well this way and any variable you put in will highlight.

MCA - kdyer
I'm always open to suggestions but the reason I have them all in uppercase when you do an insert is because I used the 3.61 and 4.21 Kixtart manuals for all my syntax and I tried to follow it to the letter. Its all in uppercase in the manual so mine is too. If I did play with it I probably would go with mixed case (I blieve thats the term for it) for commands and functions with macros still in uppercase. Programming wise it would be easy to do one and not the other the way the color routine is written. Might be a addition, but its really a nice thing to have and not a issue per se.

As before if anyone has any comments, suggestions, or the like please let me know. I do have a comment though..maybe if the forums don't like your post (the last time I typed all this it said HTML wasnt allowed) it should just show you it again and let you edit it and repost. When I hit the back button my text was all gone. I think Ill select all and copy before this reply....

Allan.
_________________________
Kixtarter - KiXtart Script Editor
http://www.AllanDynes.com/