Rechercher une page de manuel
POE::Loop::Tk.3pm
Langue: en
Version: 2010-05-14 (ubuntu - 24/10/10)
Section: 3 (Bibliothèques de fonctions)
return ``Tk needs a DISPLAY (set one today, okay?)'' unless (
(defined $ENV{DISPLAY} and length $ENV{DISPLAY}) or $^O eq ``MSWin32''
);
my $test_name = shift;
if ($test_name eq ``k_signals_rerun'' and $^O eq ``MSWin32'') {
return ``This test crashes Perl when run with Tk on $^O'';
}
return ``Tk tests require the Tk module'' if do { eval ``use Tk''; $@ };
my $m = eval { Tk::MainWindow->new() };
if ($@) {
my $why = $@;
$why =~ s/ at .*//;
return ``Tk couldn't be initialized: $why'';
}
return; }
NAME
POE::Loop::Tk - a bridge that allows POE to be driven by TkSYNOPSIS
See POE::Loop.DESCRIPTION
POE::Loop::Tk implements the interface documented in POE::Loop. Therefore it has no documentation of its own. Please see POE::Loop for more details.POE::Loop::Tk is one of two versions of the Tk event loop bridge. The other, POE::Loop::TkActiveState accommodates behavior differences in ActiveState's build of Tk. Both versions share common code in POE::Loop::TkCommon. POE::Loop::Tk dynamically selects the appropriate bridge code based on the runtime environment.
SEE ALSO
POE, POE::Loop, Tk, POE::Loop::TkCommon, POE::Loop::PerlSignals.AUTHORS & LICENSING
Please see POE for more information about authors, contributors, and POE's licensing.Contenus ©2006-2024 Benjamin Poulain
Design ©2006-2024 Maxime Vantorre