Hello Xavier,
> Hi gals and guys,
>
> Here's a little troublesome script...
>
> This is in a button, when pressed, the button hilites itself non-stop
> forever (the type command I presume) instead of typing the text in the field
> as expected.
>
> Ctrl C doesn't work (yeah, im stuck doing windows). Closing the stack is the
> only thing that does... I suppose there's a good reason (probably the
> traversal...) but I can't spend too much time on this...
>
> Question is: Is it normal behavior? It sure is unexpected...
I don't know what's going on in your button,
but it doesn't sound very healthy ;-)
Anyway, here we go, just add these 2 lines:
> on mouseUp
> put fld "HistoryChanges" into HC -- ;)
> put "<"& the short date &">" into todaysdate
> put line 3 of HC into lastDateEntry
> if lastDateEntry is not todaysdate then
select before line 3 of fld "HistoryChanges" ##!!!
> type todaysdate & return & return #### !!! before line 3 ...
> else
select before line 4 of fld "HistoryChanges" ##!!!
> type return before line 4 of fld "HistoryChanges"
> end if
> end mouseUp
You have to tell MC first where to type...
You can vary the speed of the typing, too.
"the typingrate" is the delay in milliseconds
between the simulated keystrokes!!!
It may range from 0 to 65535, which
should fit into most needs :-D
Isn't MC wonderful ?!!!!
Hope this helps.
Regards
Klaus Major
P.S. If your are not for the animation-effect,
the "put"-command is a lot more effective.
Archives: http://www.mail-archive.com/[email protected]/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
