Another Scripting Question
briany at qldlearning.com
Sun May 16 23:35:49 CDT 2004
You may want to drop the "last line" reference altogether, and just say:
put "xxx"&return after fld "MessageWatcher"
IIRC, "the last line" may try to be smart and find the non-empty line
before your return, rather than the technically empty data after it.
> on mouseUp
> put "mouseUp" && return after the last line of cd fld
> end mouseUp
> on mouseStillDown
> put "mouseStillDown" && return after the last line of cd fld
> end mouseStillDown
> on mouseEnter
> put "mouseEnter" && return after the last line of cd fld
> end mouseEnter
> on mouseLeave
> put "mouseLeave" && return after the last line of cd fld
> end mouseLeave
> The problem is that the first of the four messages prints in the first
> line of the field. Great -- this is not a problem. The problem is
> that the second prints on the same line as the first ("the problem"),
> all subsequent messages print on their own line.
> Any ideas on this one? The above script is for a single button that
> user is encouraged to use with the four event types scripted (and
> suggested in the presentation).
More information about the use-livecode