Maybe it's related: Plain demoqt built in -mt will also behave strangely, f.e. second window is slowly or not catching any events. I've reported this twice in the past.
Brgds, Viktor On 2010 Jan 22, at 16:59, Pritpal Bedi wrote: > > Hi Marcos > > > Marcos Gambeta wrote: >> >> See this example: >> >> [begincode] >> #include "xbp.ch" >> #include "appevent.ch" >> >> PROCEDURE Main () >> >> LOCAL oDlg >> ... >> >> . Compile the example with the parameter -mt. >> . Run and open two or three windows using the menu. >> . Close the main window. >> . GPF. >> >> Sometimes the example don´t close all windows opened (one or two windows >> remain open). >> >> I am not a Xbase++ developer and my code can be wrong. Any help will be >> apreciated. >> > > I will test above code shortly. > > A rule in MT: > The dialogs in another threads have to be destroyed by > the program code and only then destroy the main window. I was unable > to cover this problem. > > I will see what can be done in this context. > > BTW : did you find that other dialogs were behving properly ? > I have many changelog notices to describe this issue with MT and > multi dialogs. > > Regards > Pritpal Bedi > -- > View this message in context: > http://old.nabble.com/-hbxbp--Working-with-2-or-more-windows-tp27273253p27275462.html > Sent from the Harbour - Dev mailing list archive at Nabble.com. > > _______________________________________________ > Harbour mailing list (attachment size limit: 40KB) > Harbour@harbour-project.org > http://lists.harbour-project.org/mailman/listinfo/harbour _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
