strange things

about the scripts...

� the first of these is a message The Script is too long ... which occurs within a if .. then {} loop. The commands within the brackets are not executed, but after the closing bracket, there is business as usual. How many command are allowed within such brackets and why is there a limitation ? ?
� getnumber-commands with an input of 5 or 6 parameters work only if I write the whole command into one line .If there is any carriage return in this line it will miss anything which comes afterwards. This forces lines with more than 200 characters. It only occurs in Worksheet scripts which are executed upon loading of ASCII data. If I use buttons in a graph window everything is fine with carriage returns. getnumber
(bla1) par1
(bla2) par2
(bigblabla); <- by the way you cannot put much text in that. Surely not enough

for the most stupid user who will work with these scripts.
� If ..then sequences sometimes seem to work only if the opening bracket is in the same line as the if, sometimes not. What's the reason for this ?
� If I want to exit a script before the whole sequence is run through, e.g. for a test purpose, how to stop it ? break without options does not seem to work. Deliberately set errors now do not terminate program execution.
� getyesno(blabla)variable(window title) worked well in V4.0, version 4.1 prefers to get (blabla) variable (window ..) with spaces in between. Why this ?

There is some confusion about the Script Window and how it works.

Basically it is a text window that can act as input to the LabTalk
command interpreter. This capability can be turned on and off with
the Edit:Script Execution menu option. When on, and you type a line
of text and then press Enter, the line is interpreted as LabTalk
script. At that point, a semicolon gets appended to the line to
indicate it has been interpreted. If you type the semicolon at the
end of the line and then press Enter, it does not get interpreted.
If you highlight a block of text (including those semicolons) and
press Enter, the whole block is sent to the interpreter. If you
need a script command to spread out over multiple lines, just turn
execution off, type the lines, then turn it back on and do a
highlight&Enter.
Try to think of the Script Window as a handy tool rather than a
full-blown IDE environment.

The LabTalk interpreter has a limited internal buffer that can hold
about 1000 tokens - which means about 1000 characters. This size
limit applies to script between brackets { } or a highlighted block
of script in the Script Window. This can certainly be a 'hassle'
when you get on a coding roll, but has a side benefit of making you
code in manageable blocks.

Interrupting a script depends heavily on what your script is doing.
Sometimes simply pressing the escape key stops a script. Sometimes
you can make a button that executes a BREAK 1 command, and sometimes
you can execute a BREAK 1 command in the Script Window. At other
times there is nothing you can do but wait.