Peter,
I have been developing CBT that does all of the same stuff, with the
exception of the voice-overs. At first, each animation ran without stopping,
but then (with Scott & Kevin's patient help) I learned how to break the
animations up into small chunks using the "send" command, which allowed me
to catch a user keypress (I use the Esc key) to stop the demo. This also
requires keeping track of the messages that are being sent, so you can
cancel the pending messages when the user presses Esc.
I was tempted to post some of the code, but when I looked at it, it seemed
awfully spaghetti-like, with a lot of interconnecting handlers, and I
thought you might be better off trying to implement these strategies within
the context of your own existing code rather than trying to ape mine. But if
you find yourself stuck, I will be happy to post some samples to help get
you on the right track.
Regards,
Marni
--
Marni Centor
Summit Systems
22 Cortlandt St.
New York, NY 10007
(212) 896-3466
> -----Original Message-----
> From: Peter Reid [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, November 18, 1999 7:14 PM
> To: [EMAIL PROTECTED]
> Subject: Aborting Animations
>
>
> I've been developing a CBT package that includes animated
> demonstrations of the use of some software. The animations have been
> programmed to include the following elements:
>
> - automated mouse movement
> - automated text input
> - automated button clicking
> - automated field scrolling
> - voice-overs
> - appearing and disappearing elements, etc.
>
> The whole idea is to give the impression of an unseen human guiding
> the user through various processes.
>
> A key feature is the ability for the user to abort a given animated
> demo. I tried doing this by encapsulating each animated demo in a
> 'try' statement and telling the user that they could Ctrl+dot to
> abort a sequence part way through. However, whenever the user aborts
> during the playback of a voice-over segment an error dialog appears.
> This also happens during non-sound parts of the animation but in a
> less predictable fashion.
>
> In the end the only way I could get round the problem was to resort
> to the "deprecated" approach of setting the 'lockErrorDialogs' and
> handling the 'errorDialogs' message. This worked fine and allows
> immediate termination of sound segments as well as all the other
> elements.
>
> Any ideas why the 'try' method didn't work, especially with sound?
> Also, can anyone suggest a more appropriate or elegant approach?
>
> Best regards
>
> Peter
> --------------------------------------------------------
> Peter Reid
> Reid-IT Limited, Loughborough, Leics., UK
> Tel: +44 (0)1509 268843 Fax: +44 (0)1509 264986
> E-mail: [EMAIL PROTECTED]
> Web: http://www.reidit.co.uk
>
----------------------------------------------------------------------------
--------------------
The views and opinions expressed in this email message are the sender's
own, and do not necessarily represent the views and opinions of Summit
Systems Inc.
