Quote: Originally Posted by frodobaggins
I would assume they broke the app into sections as a "cheap" form of multithreading.
Yes, it is implemented in a wrapper .exe so it runs in it's own process. WMP as an in-process control / object slows down everything in the main app because the vb runtime does not create or properly marshall separate threads for controls and classes (even though it's supposed to). Doing an activex exe wrapper allows us to do things in separate threads without using the createthread api. If you've ever done this in vb you know it's not exactly pretty. The ActiveX exe allows us to pass objects, arrays, structures, whatever we want back and forth between the two applications, which is a huge advantage over threading something using CreateThread. Also, it is safe to run in the VB IDE, which by itself is not threadsafe.
We'd love to know of more elegant ways to do this - if anyone has suggestions.
__________________
'01 Chevy Xtreme Stepside
(pics)
FIC K7MNF-64 / Athlon 3200 | 256 DDR | 120 GB 7.2k WD
WinXP Pro | MediaEngine | 12.1 VGA TFT Touch|Creative CIMR-100
350w Vector | 320w mATX PS | Hellroaring BIC95150 |
ButterflySDC