On Friday, November 22, 2002, at 02:20 AM, Jan Schenkel wrote:
I recommend Jan's approach.First of all, let's redo the repeat loop and make it a 'send' loop.
And would add this.
If doSlideThing is called from a button mouseUp, you need a way to keep from starting a second slide show running on top of and interfering with the first. It can also keep the first from being able to be stopped.
The simplest way might be this:
on startSlideThing
endSlideThing
doSlideThing
end startSlideThing
...and don't call doSlideThing from anywhere else.
You can also use a busy flag which can have advantages in preventing a stagger when stopping and immediately starting a slide show.
If cards can be changed, consider what you want to happen. You may want to endSlideThing. If not, the field should be card qualified or be me. (In the latter case, put the three slideThing handlers in the field and send to the field; your field becomes a slide show object.)
(And to add to the confusion... You might consider keeping the slide show on all the time and simply switch out the word list, using a blank list to keep it from flashing.)
Dar Scott
_______________________________________________
use-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/use-revolution
