>
> I'm not very familiar with threads so I might be way off here, but seems
> to me that in FxMixer, we go through all of the channels in a recursive
> function just to add them on the job queue - and we do this every
> period. Additionally it seems (I could be wrong as I'm not sure how the
> queue works) that this puts the channels in the exact opposite order
> than what they should be processed in.
I haven't reviewed the code you are speaking about, but assuming these are
adjacent nested threads, they would get fired virtually simultaneously when
queued by the same parent so ordering is usually the least of anyones
worries.
Threads generally run off on their own and eventually die based on their
natural lifecycle, so if it appears they're being added too-often, that
design is likely to be intentional.
-Tres
------------------------------------------------------------------------------
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
_______________________________________________
LMMS-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lmms-devel
