If that is your only worry, then Shockwave is fine for what you want
to do. You should read up on objects and the actorList and the "on
stepFrame" handler, or behaviors and checking for events in the "on
exitFrame" handler. Both of these approaches can be used to simulate
multi-threading and allow the program to remain interactive while
doing things "in the background". You can think of each object or
behavior as a seperate thread that gets time at every frame event
("go to the frame") and you can check on what's going on in the
object or behavior in the respective stepFrame or exitFrame handler.
With objects, you need to explicitly put them into "the actorList".
Then on each frame event, all objects in the actorList get called
back in their "on stepFrame" handler. Behaviors are much simpler -
if you just have an "on exitFrame" handler, it will be called on each
frame event.
Good luck,
Irv
At 1:45 PM -0500 2/4/02, Jason Gruhl wrote:
>Hello List:
>I am trying to decide whether or not to use Shockwave for a web app
>that I am writing. My one concern is shockwaves ability to do
>multi-threaded sort of tasks. Basically what I envision is a user who
>interacts with the application while the application is constantly
>talking to a server and updating data which is displayed on the
>screen. What do you think about shockwave compared to say a java
>applet.
>
--
Lingo / Director / Shockwave development for all occasions.
(Home-made Lingo cooked up fresh every day just for you.)
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/lingo-l.cgi To post messages to the list, email
[EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for
learning and helping with programming Lingo. Thanks!]
