Sorry for this repost, I'm close to contacting OP Support about my
problem, but thought I would give it another try asking if anybody
can recognize any of the symptoms I have with breakpoints.

Here once again the list of oddities:

1. Seems that when the debugger suspends at a certain breakpoint, say
at line 100, it actually has stopped somewhere further down the
document, about +/- 15 lines further down. I can tell from watching
the variables being declared as shown in the variables window.

2. Breakpoints apparently can't be set anywhere inside a lassoscript-
file...? It works for me only when I set a breakpoint on a line with
ie. the start of an if- or select-statement, a line with an include
or library and a few other sorts of code. Is that intended so?

3. Breakpoints disappear when I shut down eclipse. That is, the blue
dots in the margin of the lassoscript files indicating the position
os the breakpoints are still there, but they are gone from the
breakpoints window and they don't trigger in a debug session. If I
set them again they do, however. Is this intended?

4. I seem to remember in the "early days" of LSfE that when I started
a debug session, an arrow in the margin of the document would show to
which point the session had arrived, that is, the session would start
with suspending the process with this arrow at line 1 of the
document. Also, I think LSfE used to force focus to the position of
this arrow, if necessary by opening documents like include files
where you choose to "go into". This I don't see anymore.

5. Apparently you can't add new breakpoints further down the document
when suspended in the middle of a debug session...? This is ok, of
course, could be a feature however...?


/nikolaj


--
------------------------------
Lasso Support: http://support.omnipilot.com/
Search the list archives:
http://www.listsearch.com/lassostudiotalk.lasso
Manage your list subscription:
http://www.listsearch.com/lassostudiotalk.lasso?manage