Judy,
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.
HTH, Brian
on mouseUp
put "mouseUp" && return after the last line of cd fld "MessageWatcher"
end mouseUp
on mouseStillDown put "mouseStillDown" && return after the last line of cd fld "MessageWatcher" end mouseStillDown
on mouseEnter put "mouseEnter" && return after the last line of cd fld "MessageWatcher" end mouseEnter
on mouseLeave put "mouseLeave" && return after the last line of cd fld "MessageWatcher" 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"), but
all subsequent messages print on their own line.
Any ideas on this one? The above script is for a single button that the
user is encouraged to use with the four event types scripted (and
suggested in the presentation).
_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
