Gtk2::Builder3pm
Wrapper for gtkbuilder
Hierarchy
Glib::Object+----Gtk2::Builder
Methods
builder = Gtk2::Builder->new
integer = $builder->add_from_file ($filename)
- •
-
$filename(localized file name)
May croak with a Glib::Error in $@ on failure.
integer = $builder->add_from_string ($buffer)
- •
-
$buffer(string)
May croak with a Glib::Error in $@ on failure.
integer = $builder->add_objects_from_string ($buffer, $first_object_id, ...)
•
|
|
|---|---|
•
|
|
•
|
... (list) |
Since: gtk+ 2.14
$builder->connect_signals ($user_data)
$builder->connect_signals ($user_data, $package)
$builder->connect_signals ($user_data, %handlers)
There are four ways to let Gtk2::Builder do the signal connecting work for you:
- "$builder->connect_signals ($user_data)"
-
When invoked like this, Gtk2::Builder will connect signals to functions in the calling package. The callback names are specified in the UI description.
- "$builder->connect_signals ($user_data, $package)"
-
When invoked like this, Gtk2::Builder will connect signals to functions in the package $package.
- "$builder->connect_signals ($user_data, $object)"
-
When invoked like this, Gtk2::Builder will connect signals to method calls against the object
$object.
- "$builder->connect_signals ($user_data, %handlers)"
-
When invoked like this, %handlers is used as a mapping from handler names to code references.
$builder->connect_signals_full ($func, $user_data=undef)
•
|
|
|---|---|
•
|
|
object = $builder->get_object ($name)
- •
-
$name(string)
list = $builder->get_objects
string or undef = $builder->get_translation_domain
$builder->set_translation_domain ($domain)
- •
-
$domain(string or undef)
Properties
- 'translation-domain' (string : default undef : readable / writable / private)
-
The translation domain used by gettext
Releases
5 releases since Debian 5.0 (Lenny); the text changed 4 times.