processEvents() and threads

**wysota** · 20th February 2009, 09:05

Isn't placing processEvents() calls inside the calculation process also changing the way the calculations are done? I'm not sure why injecting processEvents() is fine and dividing the code into 10 methods is not.

**talk2amulya** · 20th February 2009, 09:13

no, injecting processEvents() is NOT fine..thats why i m finding an alternate solution..the management is adamant at making no changes to the "calculation" function..and now the torch has been passed..i have been taken off the issue and sm QT guru would be looking after the issue..i m really looking forward to his stance on this

thank you all for your time!

**seneca** · 20th February 2009, 09:16

This may seem a elaborate solution just to get marketing happy, but how about spawning a mini-app in a second process just displaying the splash?

**talk2amulya** · 20th February 2009, 09:26

wow, now thats smth that may catch their attention cuz they DO NOT wanna change ANTH in the calculation function...who knows..but thanks man, that might be a good thing to remember as solving a problem..just spawn another process

**seneca** · 20th February 2009, 09:45

This is something I was seriously considering for long running print jobs, because for no apparent reason Qt does not allow to print a text document outside the main thread. However there is hope that at least this design flaw might get fixed somewhen:

http://labs.trolltech.com/blogs/2007...-and-printing/