Resolved by DJ Sures!
DJ, please do not see this as a criticism, I remain one the biggest fans of your great work!
Now I am doing extensive script writing for the ALTAIR robots, there are a couple of issues that really slow down my EZ_Builder code writing productivity.
The one that really gets me is the EZ-Script Function suggestion box (that I never use) that appears over your code making it hard to see the nearby lines and some times the window seems to lock in position and this takes a few key presses just to get rid of the box. I know this may be useful for some people but for me to say it is annoying is an understatement! Is there a way to turn this off, if not could I please ask that the option is given?
Another thing I noticed is that sometimes you cannot label a code line out (which is helpful when debugging) even with a "#" place in front of the code line it still gets parsed - it usually throws up a syntax error here is an example
"syntax error on line 67,Unknown command # $LIGHT=setbits(0,0,0,0,0,0,$bit7,$bit6)"
If I take the hash symbol away then it works again?
Thanks for anything you can do here.
Tony
Looking into it
Good point Alan, though it would be good to get this fixed and I have seen this occur when there is only one comment tag on a line.
Tony
If I may comment on this issue since we're talking about debugging and labeling out code, it would be nice to have a symbol (or symbol pair) to label out groups of lines. For example, while '#' disables a single line, a pair such as '(#' could begin the labeling out of a group of lines and the opposite '#)' would signify the end. Of course any not normally used symbol would work as well. It would also be good if this pair could be used on a line by itself and still be valid. For example:
(# Labeling out all the lines including this one Line 1 Line 2 Line 3 #)
Would be the same as this:
(# Labeling out all the lines including this one Line 1 Line 2 Line 3 #)
Such a thing would allow for easy labeling out or enabling of entire code sections. Being able to have the symbols on separate lines helps in visually identifying the start and end points.
An alternative method would be that when the interpreter running the script finds a '#' symbol on a line by itself, it skips all subsequent lines until it finds another '#' on a line by itself:
Labeling out all the lines including this one Line 1 Line 2 Line 3
Whatever method was used would need to ignore lines regardless of content, including lines that have a '#' symbol already in them.
I realize this sort of thing is easier said than done. My apologies if I have simply repeated a point made in the past, but I could not find such a discussion by searching the old posts.
@wsb00001
I agree that this is a great idea. I know I use this in c# and in SQL a lot. It would be a nice feature to add into scripting in ARC.
Toymaker,
I am able to reproduce the bug when i do this
I am not able to reproduce the bug any other way. You had mentioned that there are other scenarios in which a similar bug had been evident. Can you help me by providing an example code line that is different than the above which triggers this similar style bug in commenting?
DJ, over the last months, the single line hash problem only happened a couple of times and I never logged what the particular lines contained as I sort of accepted the problem. I will now though record the line details if it happens again for you. The bigger problem was the 2 hash per line event that caused problems every time and I am grateful for your prompt fix for this.
Tony