But how would you do multiple calls against the same thing?
{
.signal_connect( :delete{ Gtk2.main_quit } );
.set_title( "Test" );
.border_width( 15 );
.add( .signal_connect( :clicked{ Gtk2.main_quit } ) on Gtk2::Butto
+n.new( "Quit" ) );
.show_all;
} on Gtk2::Window.new( "toplevel" );
There is a simple analogon in Perl5:
my $window = map {
$_->signal_connect( delete_event => sub { Gtk2->main_quit } );
$_->set_title( "Test" );
$_->set_border_width( 15 );
$_->add( map {
$_->signal_connect( clicked => sub { Gtk2->main_quit } );
$_;
} Gtk2::Button->new( "Quit" ) );
$_->show_all();
$_;
} Gtk2::Window->new( "toplevel" );
Meh. It puts things in the wrong order IMO.
Makeshifts last the longest.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|