| 1 |
NAME |
| 2 |
|
| 3 |
Tickit::Async - use Tickit with IO::Async |
| 4 |
|
| 5 |
SYNOPSIS |
| 6 |
|
| 7 |
use IO::Async; |
| 8 |
use Tickit::Async; |
| 9 |
|
| 10 |
my $tickit = Tickit::Async->new; |
| 11 |
|
| 12 |
# Create some widgets |
| 13 |
# ... |
| 14 |
|
| 15 |
$tickit->set_root_widget( $rootwidget ); |
| 16 |
|
| 17 |
my $loop = IO::Async::Loop->new; |
| 18 |
$loop->add( $tickit ); |
| 19 |
|
| 20 |
$tickit->run; |
| 21 |
|
| 22 |
DESCRIPTION |
| 23 |
|
| 24 |
This class allows a Tickit user interface to run alongside other |
| 25 |
IO::Async-driven code, using IO::Async as a source of IO events. |
| 26 |
|
| 27 |
As a shortcut convenience, a containing IO::Async::Loop will be |
| 28 |
constructed using the default magic constructor the first time it is |
| 29 |
needed, if the object is not already a member of a loop. This will |
| 30 |
allow a Tickit::Async object to be used without being aware it is not a |
| 31 |
simple Tickit object. |
| 32 |
|
| 33 |
To avoid accidentally creating multiple loops, callers should be |
| 34 |
careful to add the Tickit::Async object to the main application's loop |
| 35 |
if one already exists as soon as possible after construction. |
| 36 |
|
| 37 |
AUTHOR |
| 38 |
|
| 39 |
Paul Evans <[email protected]> |
| 40 |
|