although the topic is a bit old, i'd like to add the following command;
for a project that involves many cpu-intensive tasks, mainly in
graphics manipulation/-analysing, after alot of testing i finally
ended-up splitting-up different tasks between two seperate projectors
that communicate
Hi,
Easy question for the Gurus ;o)
If I have a number Timeouts running at the same and they all access say
the same List.
Does director run them off a single thread or might it possibly use
multiple threads to run them?
Im talking mutual exclusion or critical sections here. Can both my
On 20 Dec 2005, at 16:27, Alan Skinner wrote:
Hi,
Easy question for the Gurus ;o)
If I have a number Timeouts running at the same and they all access
say
the same List.
Does director run them off a single thread or might it possibly use
multiple threads to run them?
Im talking mutual
At 3:27 PM + 12/20/05, Alan Skinner wrote:
Does director run them off a single thread or might it possibly use
multiple threads to run them?
Just a hunch, but I think timeout objects are serviced sequentially.
--
Cole
[To remove yourself from this list, or to change to digest mode, go
If my memory serves me correctly timeouts are actually called in reverse
order that they are in the timeout list. This makes sense in that if one
of the processes called by the timeout has the timeout forget itself then
it would be removed from the list and this would screw up the current
Just to confirm that my memory was working correctly I tossed this little
test together.
Create a parent script, called parent
--parent
property pId
on new me, aId
pId = aId
return me
end
on prepareFrame me
put prepareFrame, pId, _system.milliseconds
end
on timedEvent me
put
Hi Alan,
The only time I've found events to be not safely sequenced is when using certain xtras that trigger
handlers based on external events. For example: baDropFile can trigger a dropFile event in the
middle of another handler's execution. I think baMouseWheel also does this, though I'm
another place where Dirctor is multithreaded is with the net
operations
getNetThing, etc.
the multi-user stuff, of course
Are you sure ?
I know they are asynchronous but multi threaded ?
Bart Pietercil
[To remove yourself from this list, or to change to digest mode, go to
At 11:44 PM +0100 12/20/05, you wrote:
another place where Dirctor is multithreaded is with the net operations
getNetThing, etc.
the multi-user stuff, of course
Are you sure ?
I know they are asynchronous but multi threaded ?
there is a distinction, but for all intents purposes, these
