The learning curve is the burning curve

Jan Schenkel janschenkel at yahoo.com
Fri Jul 12 00:43:01 EDT 2002


Hi John,

The mouseUp handler triggers the very first
updateCLock. After that, updateCLock calls itself
repeatedly afterwards until you remove it from the
pendingMessages or RR quits (whichever comes first)

You can also manually fire the updateClock from the
message box, or from another script such as your
card's openCard handler.

The system doesn't know about the updateCLock event
itself, so it doesn't know it's supposed to call it.

Hope this cleared things up a bit,

Jan Schenkel.

"As we grow older, we grow both wiser and more foolish
at the same time."  (De Rochefoucald)

--- John <john at oneChip.com> wrote:
> 
> On Wednesday, July 10, 2002, at 10:42 AM, Ken Ray
> wrote:
> 
> > Ro,
> >
> > Here's a simple "send" script that puts the
> current time into a field:
> >
> > (I made this the script of a button, but you can
> change it to anything 
> > you
> > like):
> >
> > on mouseUp
> >   send updateClock to me in 10 milliseconds
> > end mouseUp
> >
> > on updateClock
> >   put the long time into field 1
> >   send updateClock to me in 500 milliseconds
> > end updateClock
> 
>     It seems that this would work with only
> "updateClock" in the mouseUp 
> handler (it does when I try it).  I can't figure out
> why the mousUp 
> handler is shown as it is.  Is it necessary for some
> reason?
> 
> Thanks,
> John
> 
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
>
http://lists.runrev.com/mailman/listinfo/use-revolution


__________________________________________________
Do You Yahoo!?
Sign up for SBC Yahoo! Dial - First Month Free
http://sbc.yahoo.com



More information about the Use-livecode mailing list