in reply to Tkx and WIN32::FileOP

The problem is that the FileOp dialogs enter their own event loops, which means that Tk's event loop doesn't get serviced until the dialog completes. One way to prevent that would be to run the dialog in a thread and use DoOneEvent() in a loop until the dialog completes.

Where you currently do:

my $filename = OpenGialog( ... );

You need to use something like this, though you'll need to look up the details yourself:

use threads; use threads::shared; ... my $filename :shared; async { $filename = OpenDialog( ... ); }->detach; DoOneEvent( 1 ) until $filename; ## use $filename

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.

Replies are listed 'Best First'.
Re^2: Tkx and WIN32::FileOP
by conversecorollary (Novice) on May 27, 2011 at 23:23 UTC
    Ah, I knew I was missing something here and it was some sort of interaction between the 2. Do you have any opinion about wxWidgets?
      Do you have any opinion about wxWidgets?

      No. I've never used them.


      Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
      "Science is about questioning the status quo. Questioning authority".
      In the absence of evidence, opinion is indistinguishable from prejudice.
        Thank you for the insight abouit the event loops..