Just off the top of my head - not sure if this is the best way to do
this - but what about having your repeat loop in an "on idle" message
in the card script. The loop should test to see if it should be
scrolling the field by looking at the value of a custom property
(e.g., of the field) which is in turn set by the Start & Stop
buttons. Something like (untested & off the cuff):
on idle
if the doScroll of fld MyField is 1 then
get the scroll of fld MyField
set the scroll of fld MyField to (it + incrememt)
end if
end idle
In this case the Start button would set the doScroll of fld MyField
to 1 and the Stop button would set it to anything else. Of course
you'd have to deal with the case where you were at the bottom of the
field.
You may need to play with a delay in the scrolling so your users
don't get dizzy...
Regards,
Dave Tremmel
>I've seen this before, but could not find it in the archives...
>
>Suppose I want a stack with one field and two buttons, named "Start" and
>"Stop." When I click "Start", I want the field to auto-scroll and keep
>scrolling, until I click the "Stop" button. Obviously a simple repeat loop
>in the Start button won't work. Anyone done this?
>
>:)
>Richard MacLemale
>Instructional Technology Specialist
>James W. Mitchell High School
>
>
>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.
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.
