Re: [perl-win32-gui-users] Avoid the appearance of a "frozen"

Thread safe or not, unlike a Win32::GUI object, a $dbh object can't be shared among more threads. Does anyone know why? Because of DBI, of DBD::mysql, or because a database connection can't be shared among more threads, or something else? Octavian - Original Message - From: "Charles Al

Re: [perl-win32-gui-users] Avoid the appearance of a "frozen"

To clarify my earlier comment: DBI is considered threadsafe but some of the DBD's are not. Here's more info: http://search.cpan.org/~timb/DBI/DBI.pm#Threads_and_Thread_Safety As far determining which modules are or are not threadsafe, read the perldocs! Thanks, Charles Alderman - Origin

Re: [perl-win32-gui-users] Taking action after the call to Win32::GUI::Dialog()

hello i refer to the "rpnoble" question: In the Draw.pl example, all program action takes place in the timer event. Is there a way to trigger a default program action without using the timer event once the program has called Win32::GUI::Dialog()? In all of my win32::GUI programs, I use a menu

Re: [perl-win32-gui-users] Avoid the appearance of a "frozen"

Thanks for all the great responses! I changed my code so that each GUI handle is managed only by the thread that created it. This works perfect--and has eliminated all the crasing I was seeing! As a follow-up question, how do you know *for sure* which modules are not thread-safe? For example, I wo