On Feb 8, 2010, at 7:23 AM, Koen Deforche wrote:

> Hey Daniel,
>>> Although this fix seems to have partially fixed the problem, I am seeing an 
>>> issue that I did not notice before.  Now, when I create a modal WDialog and 
>>> call the dialog's exec() I get a boost::lock_error exception thrown:
> We had not considered this, and indeed, this the exec() method
> starting the recurse eventloop is a problem, as it does not consider
> that it may be running from a different thread than the thread that
> was handling the incoming event.
> I fear the fix will not be trivial. Is it possible to use the
> non-exec() method of invoking the dialog as a workaround ?

Do you mean to make the dialog non-modal?  Or is there some other way to 
execute a modal dialog other than using exec()?  I would not be able to make 
the dialog non-modal, that would not work for my application.  If there is some 
other way to execute a modal dialog, could you tell me how to do it?  


Daniel Ginsburg / email: daniel.ginsb...@childrens.harvard.edu
Principal Software Architect
Fetal-Neonatal Neuroimaging and Development Science Center
Children's Hospital Boston
300 Longwood Avenue
Boston, MA 02115
Phone: 857-218-5140

The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
witty-interest mailing list

Reply via email to