as for onenterframe (as with other 'major' events), I usually bubble that
event, as to give me more control of which object(usually a movieclip)
listens and which one doesn't, without altering the object itself. Has
little to do with threading, but I'm not sure if simulating threading in
actionscri
You can always write some kind of wrapper, so you don't have to mess
around with empty
movieclips, and onEnterFrame, etc.
function caluculateStuff()
{
// set up any data needed for calculation
// ...
TaskManager.forloop(loopFunction, 1, 10, finalFunction);
function loopFunction(var i
Hahaha,
Okay your point is well taken. Especially since I am currently working on
fixing a multi-threaded Java socket application at the moment.
Multi-threaded programing isn't a walk in the park, that's for sure. But,
with that said, depending on how Scott implements his MovieClip approach it
m
define its
Update method, add it to array, and in on enter frame loop through that
array and for each element call Update
^^
sounds like a job for
AsBroadCaster!
hooray
On 12/7/05, A.Cicak <[EMAIL PROTECTED]> wrote:
>
> Believe me multithreding is lot harder to debug, read and maintain in mo
Believe me multithreding is lot harder to debug, read and maintain in most
cases assuming that onEnterFrame is not made
in way that you put 20 loops all in one function (onEnterFrame) . You could
make object (MultiLoop) which has method Update, some private counters, etc.
and for each problemati
5 matches
Mail list logo
