Running modules with the threaded option Thread last updated on 2003-11-15 22:53:56

Posted by member 7991 on 2003-11-15 10:58:51

Is there any disadvantage to running EVERY module in a theme threaded. Of course, some modules don't work well when threaded. But, if after testing and removing the option from those modules which have issues when threaded, could this lead to less obvious problems/instability?

Posted by member 111 on 2003-11-15 13:00:38 link

Threaded means that nobody can predict order of modules loading, and that is the main disadvatage.
1) it will be much better if desktop module would be loaded before other modules
2) some special modules as zorder.dll or grdTransparent required to be loaded BEFORE of AFTER other interface modules to take effect

Posted by member 99 on 2003-11-15 22:40:46 link

With NetLoadModule, even threaded modules load in order.

RabidVWM doesn't work perfectly threaded, but it's hard to tell. Everything works fine except for drag&switch/dropping things dragged from other applications. It's very difficult to find every little incompatibility like this.

Posted by member 7223 on 2003-11-15 22:53:56 link

If my current theme use modules that doesn't have (big) memory leak and are not litestep'frozing'able; then, does running modules threaded still make sense ?