msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2024-07-04 07:49+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Put one translator per line, in the form NAME <EMAIL>, YEAR1, YEAR2
msgctxt "_"
msgid "translator-credits"
msgstr ""

#. (itstool) path: info/title
#: C/index-in.docbook:45
msgid "Programming with <application>gtkmm</application> 4"
msgstr ""

#. (itstool) path: authorgroup/author
#: C/index-in.docbook:47
msgid "<personname><firstname>Murray</firstname><surname>Cumming</surname></personname>"
msgstr ""

#. (itstool) path: authorgroup/author
#: C/index-in.docbook:50
msgid "<personname><firstname>Bernhard</firstname><surname>Rieder</surname></personname> <contrib>Chapter on \"Timeouts\".</contrib>"
msgstr ""

#. (itstool) path: authorgroup/author
#: C/index-in.docbook:54
msgid "<personname><firstname>Jonathon</firstname><surname>Jongsma</surname></personname> <contrib>Chapter on \"Drawing with Cairo\".</contrib> <contrib>Chapter on \"Working with gtkmm's Source Code\".</contrib> <contrib>Chapter on \"Recent Files\".</contrib>"
msgstr ""

#. (itstool) path: authorgroup/author
#: C/index-in.docbook:60
msgid "<personname><firstname>Ole</firstname><surname>Laursen</surname></personname> <contrib>Parts of chapter on \"Internationalization\".</contrib>"
msgstr ""

#. (itstool) path: authorgroup/author
#: C/index-in.docbook:64
msgid "<personname><firstname>Marko</firstname><surname>Anastasov</surname></personname> <contrib>Chapter on \"Printing\".</contrib> <contrib>Parts of chapter on \"Internationalization\".</contrib>"
msgstr ""

#. (itstool) path: authorgroup/author
#: C/index-in.docbook:69
msgid "<personname><firstname>Daniel</firstname><surname>Elstner</surname></personname> <contrib>Section \"Build Structure\" of chapter on \"Wrapping C Libraries with gmmproc\".</contrib>"
msgstr ""

#. (itstool) path: authorgroup/author
#: C/index-in.docbook:73
msgid "<personname><firstname>Chris</firstname><surname>Vine</surname></personname> <contrib>Chapter on \"Multi-threaded programs\".</contrib>"
msgstr ""

#. (itstool) path: authorgroup/author
#: C/index-in.docbook:77
msgid "<personname><firstname>David</firstname><surname>King</surname></personname> <contrib>Section on Gtk::Grid.</contrib>"
msgstr ""

#. (itstool) path: authorgroup/author
#: C/index-in.docbook:81
msgid "<personname><firstname>Pedro</firstname><surname>Ferreira</surname></personname> <contrib>Chapter on \"Keyboard Events\".</contrib>"
msgstr ""

#. (itstool) path: authorgroup/author
#: C/index-in.docbook:85
msgid "<personname><firstname>Kjell</firstname><surname>Ahlstedt</surname></personname> <contrib>Update from gtkmm 3 to gtkmm 4.</contrib> <contrib>Chapter on \"Building applications\".</contrib> <contrib>Chapter on \"The DropDown Widget\".</contrib> <contrib>Chapter on \"ListView, GridView, ColumnView\".</contrib>"
msgstr ""

#. (itstool) path: authorgroup/author
#: C/index-in.docbook:92
msgid "<personname><firstname>Daniel</firstname><surname>Boles</surname></personname> <contrib>Notes on need to remove widgets in non-managed wrappers from parents to dispose, other tweaks.</contrib>"
msgstr ""

#. (itstool) path: abstract/para
#: C/index-in.docbook:100
msgid "This book explains key concepts of the <application>gtkmm</application> C++ API for creating user interfaces. It also introduces the main user interface elements (\"widgets\")."
msgstr ""

#. (itstool) path: info/copyright
#: C/index-in.docbook:103
msgid "<year>2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010</year> <holder>Murray Cumming</holder>"
msgstr ""

#. (itstool) path: legalnotice/para
#: C/index-in.docbook:109
msgid "Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. You may obtain a copy of the GNU Free Documentation License from the Free Software Foundation by visiting their Web site or by writing to: Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA."
msgstr ""

#. (itstool) path: chapter/title
#: C/index-in.docbook:120
msgid "Introduction"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:123
msgid "This book"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:125
msgid "This book explains key concepts of the <application>gtkmm</application> C++ API for creating user interfaces. It also introduces the main user interface elements (\"widgets\"). Although it mentions classes, constructors, and methods, it does not go into great detail. Therefore, for full API information you should follow the links into the reference documentation."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:127
msgid "This book assumes a good understanding of C++, and how to create C++ programs."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:129
msgid "We would very much like to hear of any problems you have learning <application>gtkmm</application> with this document, and would appreciate input regarding improvements. Please see the <link linkend=\"chapter-contributing\">Contributing</link> section for further information."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:137
msgid "gtkmm"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:139
msgid "<application>gtkmm</application> is a C++ wrapper for <link xlink:href=\"http://www.gtk.org/\">GTK</link>, a library used to create graphical user interfaces. It is licensed using the LGPL license, so you can develop open software, free software, or even commercial non-free software using <application>gtkmm</application> without purchasing licenses."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:147
msgid "<application>gtkmm</application> was originally named gtk-- because GTK was originally named GTK+ and had a + in the name. However, as -- is not easily indexed by search engines, the package generally went by the name <application>gtkmm</application>, and that's what we stuck with."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:152
msgid "Why use <application>gtkmm</application> instead of GTK?"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:154
msgid "<application>gtkmm</application> allows you to write code using normal C++ techniques such as encapsulation, derivation, and polymorphism. As a C++ programmer you probably already realize that this leads to clearer and better organized code."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:155
msgid "<application>gtkmm</application> is more type-safe, so the compiler can detect errors that would only be detected at run time when using C. This use of specific types also makes the API clearer because you can see what types should be used just by looking at a method's declaration."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:156
msgid "Inheritance can be used to derive new widgets. The derivation of new widgets in GTK C code is so complicated and error prone that almost no C coders do it. As a C++ developer you know that derivation is an essential Object Orientated technique."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:157
msgid "Member instances can be used, simplifying memory management. All GTK C widgets are dealt with by use of pointers. As a C++ coder you know that pointers should be avoided where possible."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:158
msgid "<application>gtkmm</application> involves less code compared to GTK, which uses prefixed function names and lots of cast macros."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:162
msgid "<application>gtkmm</application> compared to Qt"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:164
msgid "Trolltech's Qt is the closest competition to <application>gtkmm</application>, so it deserves discussion."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:166
msgid "<application>gtkmm</application> developers tend to prefer <application>gtkmm</application> to Qt because <application>gtkmm</application> does things in a more C++ way. Qt originates from a time when C++ and the standard library were not standardized or well supported by compilers. It therefore duplicates a lot of stuff that is now in the standard library, such as containers and type information. Most significantly, Trolltech modified the C++ language to provide signals, so that Qt classes cannot be used easily with non-Qt classes. <application>gtkmm</application> was able to use standard C++ to provide signals without changing the C++ language. See the <link xlink:href=\"https://wiki.gnome.org/Projects/gtkmm/FAQ\">FAQ</link> for more detailed differences."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:171
msgid "<application>gtkmm</application> is a wrapper"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:173
msgid "<application>gtkmm</application> is not a native C++ toolkit, but a C++ wrapper of a C toolkit. This separation of interface and implementation has advantages. The <application>gtkmm</application> developers spend most of their time talking about how <application>gtkmm</application> can present the clearest API, without awkward compromises due to obscure technical details. We contribute a little to the underlying GTK code base, but so do the C coders, and the Perl coders and the Python coders, etc. Therefore GTK benefits from a broader user base than language-specific toolkits - there are more implementers, more developers, more testers, and more users."
msgstr ""

#. (itstool) path: chapter/title
#: C/index-in.docbook:181
msgid "Installation"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:184
msgid "Dependencies"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:186
msgid "Before attempting to install <application>gtkmm</application><application>-4.0</application>, you might first need to install these other packages."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:191
msgid "<application>sigc++-3.0</application>"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:192
msgid "<application>gtk4</application>"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:193
msgid "<application>glibmm-2.68</application>"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:194
msgid "<application>cairomm-1.16</application>"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:195
msgid "<application>pangomm-2.48</application>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:197
msgid "These dependencies have their own dependencies, including the following applications and libraries:"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:202
msgid "<application>pkg-config</application>"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:203
msgid "<application>glib-2.0</application>"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:204
msgid "<application>pango</application>"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:205
msgid "<application>cairo</application>"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:206
msgid "<application>gdk-pixbuf-2.0</application>"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:207
msgid "<application>graphene-1.0</application>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:212
msgid "Unix and Linux"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:215
msgid "Prebuilt Packages"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:217
msgid "Recent versions of <application>gtkmm</application> are packaged by nearly every major Linux distribution these days. So, if you use Linux, you can probably get started with <application>gtkmm</application> by installing the package from the official repository for your distribution. Distributions that include <application>gtkmm</application> in their repositories include Debian, Ubuntu, Red Hat, Fedora, Mandriva, Suse, and many others."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:225
msgid "The names of the <application>gtkmm</application> packages vary from distribution to distribution (e.g. <application>libgtkmm-4.0-dev</application> on Debian and Ubuntu or <application>gtkmm4.0-devel</application> on Red Hat and Fedora), so check with your distribution's package management program for the correct package name and install it like you would any other package."
msgstr ""

#. (itstool) path: note/para
#: C/index-in.docbook:233
msgid "The package names will not change when new API/ABI-compatible versions of <application>gtkmm</application> are released. Otherwise they would not be API/ABI-compatible. So don't be surprised, for instance, to find <application>gtkmm</application> 4.8 supplied by Debian's <application>libgtkmm-4.0-dev</application> package."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:243
msgid "Installing From Source"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:245
msgid "If your distribution does not provide a pre-built <application>gtkmm</application> package, or if you want to install a different version than the one provided by your distribution, you can also install <application>gtkmm</application> from source. The source code for <application>gtkmm</application> can be downloaded from <link xlink:href=\"https://download.gnome.org/sources/gtkmm/\"/>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:251
msgid "After you've installed all of the dependencies, download the <application>gtkmm</application> source code, unpack it, and change to the newly created directory. <application>gtkmm</application> can be built with Meson. See the <filename>README</filename> file in the <application>gtkmm</application> version you've downloaded."
msgstr ""

#. (itstool) path: note/para
#: C/index-in.docbook:258
msgid "Remember that on a Unix or Linux operating system, you will probably need to be <literal>root</literal> to install software. The <command>su</command> or <command>sudo</command> command will allow you to enter the <literal>root</literal> password and have <literal>root</literal> status temporarily."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:265
msgid "The <filename>configure</filename> script or <command>meson</command> will check to make sure all of the required dependencies are already installed. If you are missing any dependencies, it will exit and display an error."
msgstr ""

#. (itstool) path: para/screen
#: C/index-in.docbook:276
#, no-wrap
msgid ""
"\n"
"# meson setup --prefix=/usr &lt;builddir&gt; &lt;srcdir&gt;\n"
"# meson configure --prefix=/usr\n"
"# ./configure --prefix=/usr\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:270
msgid "By default, <application>gtkmm</application> if built with Meson or Autotools, will be installed under the <filename>/usr/local</filename> directory. On some systems you may need to install to a different location. For instance, on Red Hat Linux systems you might use the <literal>--prefix</literal> option with configure, like one of: <_:screen-1/>"
msgstr ""

#. (itstool) path: warning/para
#: C/index-in.docbook:283
msgid "You should be very careful when installing to standard system prefixes such as <filename>/usr</filename>. Linux distributions install software packages to <filename>/usr</filename>, so installing a source package to this prefix could corrupt or conflict with software installed using your distribution's package-management system. Ideally, you should use a separate prefix for all software you install from source."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:292
msgid "If you want to help develop <application>gtkmm</application> or experiment with new features, you can also install <application>gtkmm</application> from git. Most users will never need to do this, but if you're interested in helping with <application>gtkmm</application> development, see the <link linkend=\"chapter-working-with-source\">Working with gtkmm's Source Code</link> appendix."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:302
msgid "Microsoft Windows"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:304
msgid "GTK and <application>gtkmm</application> were designed to work well with Microsoft Windows, and the developers encourage its use on the win32 platform. However, Windows has no standard installation system for development libraries. Please see the <link xlink:href=\"https://wiki.gnome.org/Projects/gtkmm/MSWindows\">Windows Installation</link> page or the <link linkend=\"sec-windows-installation\"><application>gtkmm</application> and Win32</link> appendix for Windows-specific installation instructions and notes."
msgstr ""

#. (itstool) path: chapter/title
#: C/index-in.docbook:315
msgid "Basics"
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:317
msgid "This chapter will introduce some of the most important aspects of <application>gtkmm</application> coding. These will be demonstrated with simple working example code. However, this is just a taster, so you need to look at the other chapters for more substantial information."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:320
msgid "Your existing knowledge of C++ will help you with <application>gtkmm</application> as it would with any library. Unless we state otherwise, you can expect <application>gtkmm</application> classes to behave like any other C++ class, and you can expect to use your existing C++ techniques with <application>gtkmm</application> classes."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:325
#: C/index-in.docbook:3940
msgid "Simple Example"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:327
msgid "To begin our introduction to <application>gtkmm</application>, we'll start with the simplest program possible. This program will create an empty 200 x 200 pixel window."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:332
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/base\">Source Code</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:334
msgid "We will now explain each part of the example"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:335
#, no-wrap
msgid ""
"#include &lt;gtkmm.h&gt;"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:336
msgid "All <application>gtkmm</application> programs must include certain <application>gtkmm</application> headers; <literal>gtkmm.h</literal> includes the entire <application>gtkmm</application> kit. This is usually not a good idea, because it includes a megabyte or so of headers, but for simple programs, it suffices."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:343
msgid "The next part of the program:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:344
#, no-wrap
msgid ""
"class MyWindow : public Gtk::Window\n"
"{\n"
"public:\n"
"  MyWindow();\n"
"};\n"
"\n"
"MyWindow::MyWindow()\n"
"{\n"
"  set_title(\"Basic application\");\n"
"  set_default_size(200, 200);\n"
"}"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:355
msgid "defines the <classname>MyWindow</classname> class. Its default constructor sets the window's title and default (initial) size."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:360
msgid "The <function>main()</function> function's first statement:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:361
#, no-wrap
msgid ""
"auto app = Gtk::Application::create(\"org.gtkmm.examples.base\");"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:362
msgid "creates a <classname>Gtk::Application</classname> object, stored in a <classname>Glib::RefPtr</classname> smartpointer. This is needed in all <application>gtkmm</application> applications. The <methodname>create()</methodname> method for this object initializes <application>gtkmm</application>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:367
msgid "The last line creates and shows a window and enters the <application>gtkmm</application> main processing loop, which will finish when the window is closed. Your <function>main()</function> function will then return with an appropriate success or error code. The <parameter>argc</parameter> and <parameter>argv</parameter> arguments, passed to your application on the command line, can be checked when <methodname>make_window_and_run()</methodname> is called, but this simple application does not use those arguments."
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:373
#, no-wrap
msgid ""
"return app-&gt;make_window_and_run&lt;MyWindow&gt;(argc, argv);"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:375
msgid "After putting the source code in <literal>simple.cc</literal> you can compile the above program with <application>gcc</application> using:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:379
#, no-wrap
msgid ""
"g++ simple.cc -o simple `pkg-config --cflags --libs gtkmm-4.0` -std=c++17"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:380
msgid "Note that you must surround the <literal>pkg-config</literal> invocation with backquotes. Backquotes cause the shell to execute the command inside them, and to use the command's output as part of the command line. Note also that <literal>simple.cc</literal> must come before the <literal>pkg-config</literal> invocation on the command line. <literal>-std=c++17</literal> is necessary only if your compiler is not C++17 compliant by default."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:391
msgid "Headers and Linking"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:393
msgid "Although we have shown the compilation command for the simple example, you really should use the <link xlink:href=\"https://mesonbuild.com/\">Meson build system</link>. The examples used in this book are included in the <application>gtkmm-documentation</application> package, with appropriate build files, so we won't show the build commands in future. The <filename>README</filename> file in <application>gtkmm-documentation</application> describes how to build the examples."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:401
msgid "To simplify compilation, we use <literal>pkg-config</literal>, which is present in all (properly installed) <application>gtkmm</application> installations. This program 'knows' what compiler switches are needed to compile programs that use <application>gtkmm</application>. The <literal>--cflags</literal> option causes <literal>pkg-config</literal> to output a list of include directories for the compiler to look in; the <literal>--libs</literal> option requests the list of libraries for the compiler to link with and the directories to find them in. Try running it from your shell-prompt to see the results on your system."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:411
msgid "However, this is even simpler when using the <function>dependency()</function> function in a <filename>meson.build</filename> file with Meson. For instance:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:415
#, no-wrap
msgid ""
"gtkmm_dep = dependency('gtkmm-4.0', version: '&gt;= 4.6.0')"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:416
msgid "This checks for the presence of gtkmm and defines <literal>gtkmm_dep</literal> for use in your <filename>meson.build</filename> files. For instance:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:420
#, no-wrap
msgid ""
"exe_file = executable('my_program', 'my_source1.cc', 'my_source2.cc',\n"
"  dependencies: gtkmm_dep,\n"
"  win_subsystem: 'windows',\n"
")"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:424
msgid "gtkmm-4.0 is the name of the current stable API. There are older APIs called gtkmm-2.4 and gtkmm-3.0 which install in parallel when they are available. There are several versions of gtkmm-2.4, such as gtkmm 2.10 and there are several versions of the gtkmm-3.0 API. Note that the API name does not change for every version because that would be an incompatible API and ABI break. There might be a future gtkmm-5.0 API which would install in parallel with gtkmm-4.0 without affecting existing applications."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:431
msgid "If you start by experimenting with a small application that you plan to use just for yourself, it's easier to start with a <filename>meson.build</filename> similar to the <filename>meson.build</filename> files in the <link linkend=\"chapter-building-applications\">Building applications</link> chapter."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:436
msgid "If you use the older Autotools build system, see also the GNU site. It has more information about <link xlink:href=\"https://www.gnu.org/software/autoconf/\">autoconf</link> and <link xlink:href=\"https://www.gnu.org/software/automake/\">automake</link>. There are also some books describing Autotools: \"GNU Autoconf, Automake, and Libtool\" by Gary Vaughan et al. and \"Autotools, A Practitioner's Guide to GNU Autoconf, Automake, and Libtool\" by John Calcote."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:447
#: C/index-in.docbook:6571
msgid "Widgets"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:449
msgid "<application>gtkmm</application> applications consist of windows containing widgets, such as buttons and text boxes. In some other systems, widgets are called \"controls\". For each widget in your application's windows, there is a C++ object in your application's code. So you just need to call a method of the widget's class to affect the visible widget."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:450
msgid "Widgets are arranged inside container widgets such as frames and notebooks, in a hierarchy of widgets within widgets. Some of these container widgets, such as <classname>Gtk::Grid</classname>, are not visible - they exist only to arrange other widgets. Here is some example code that adds 2 <classname>Gtk::Button</classname> widgets to a <classname>Gtk::Box</classname> container widget:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:452
#, no-wrap
msgid ""
"m_box.append(m_Button1);\n"
"m_box.append(m_Button2);"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:454
msgid "and here is how to add the <classname>Gtk::Box</classname>, containing those buttons, to a <classname>Gtk::Frame</classname>, which has a visible frame and title:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:456
#, no-wrap
msgid ""
"m_frame.set_child(m_box);"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:457
msgid "Most of the chapters in this book deal with specific widgets. See the <link linkend=\"chapter-container-widgets\">Container Widgets</link> section for more details about adding widgets to container widgets."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:461
msgid "Although you can specify the layout and appearance of windows and widgets with C++ code, you will probably find it more convenient to design your user interfaces with <filename class=\"extension\">.ui</filename> XML files and load them at runtime with <classname>Gtk::Builder</classname>. See the <link linkend=\"chapter-builder\">Gtk::Builder</link> chapter."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:467
msgid "Although <application>gtkmm</application> widget instances have lifetimes and scopes just like those of other C++ classes, <application>gtkmm</application> has an optional time-saving feature that you will see in some of the examples. The <function>Gtk::make_managed()</function> allows you to create a new widget and state that it will become owned by the container into which you place it. This allows you to create the widget, add it to the container and not be concerned about deleting it, since that will occur when the parent container (which may itself be managed) is deleted. You can learn more about <application>gtkmm</application> memory management techniques in the <link linkend=\"chapter-memory\">Memory Management chapter</link>."
msgstr ""

#. (itstool) path: section/title
#. (itstool) path: appendix/title
#: C/index-in.docbook:481
#: C/index-in.docbook:5379
#: C/index-in.docbook:5622
#: C/index-in.docbook:8879
msgid "Signals"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:483
msgid "<application>gtkmm</application>, like most GUI toolkits, is <emphasis>event-driven</emphasis>. When an event occurs, such as the press of a mouse button, the appropriate signal will be <emphasis>emitted</emphasis> by the Widget that was pressed. Each Widget has a different set of signals that it can emit. To make a button click result in an action, we set up a <emphasis>signal handler</emphasis> to catch the button's \"clicked\" signal."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:490
msgid "<application>gtkmm</application> uses the libsigc++ library to implement signals. Here is an example line of code that connects a Gtk::Button's \"clicked\" signal with a signal handler called \"on_button_clicked\":"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:492
#, no-wrap
msgid ""
"m_button1.signal_clicked().connect( sigc::mem_fun(*this,\n"
"  &amp;HelloWorld::on_button_clicked) );"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:495
msgid "For more detailed information about signals, see the <link linkend=\"chapter-signals\">appendix</link>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:496
msgid "For information about implementing your own signals rather than just connecting to the existing <application>gtkmm</application> signals, see the <link linkend=\"chapter-custom-signals\">appendix</link>."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:502
msgid "Glib::ustring"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:504
msgid "You might be surprised to learn that <application>gtkmm</application> doesn't use <classname>std::string</classname> in its interfaces. Instead it uses <classname>Glib::ustring</classname>, which is so similar and unobtrusive that you could actually pretend that each <classname>Glib::ustring</classname> is a <classname>std::string</classname> and ignore the rest of this section. But read on if you want to use languages other than English in your application."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:505
msgid "std::string uses 8 bits per character, but 8 bits aren't enough to encode languages such as Arabic, Chinese, and Japanese. Although the encodings for these languages have been specified by the <link xlink:href=\"http://www.unicode.org/\">Unicode Consortium</link>, the C and C++ languages do not yet provide any standardized Unicode support for UTF-8 encoding. GTK and GNOME chose to implement Unicode using UTF-8, and that's what is wrapped by Glib::ustring. It provides almost exactly the same interface as std::string, along with automatic conversions to and from std::string."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:510
msgid "One of the benefits of UTF-8 is that you don't need to use it unless you want to, so you don't need to retrofit all of your code at once. <classname>std::string</classname> will still work for 7-bit ASCII strings. But when you try to localize your application for languages like Chinese, for instance, you will start to see strange errors, and possible crashes. Then all you need to do is start using <classname>Glib::ustring</classname> instead."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:511
msgid "Note that UTF-8 isn't compatible with 8-bit encodings like ISO-8859-1. For instance, German umlauts are not in the ASCII range and need more than 1 byte in the UTF-8 encoding. If your code contains 8-bit string literals, you have to convert them to UTF-8 (e.g. the Bavarian greeting \"Grüß Gott\" would be \"Gr\\xC3\\xBC\\xC3\\x9F Gott\")."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:512
msgid "You should avoid C-style pointer arithmetic, and functions such as strlen(). In UTF-8, each character might need anywhere from 1 to 6 bytes, so it's not possible to assume that the next byte is another character. <classname>Glib::ustring</classname> worries about the details of this for you so you can use methods such as Glib::ustring::substr() while still thinking in terms of characters instead of bytes."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:514
msgid "Unlike the Windows UCS-2 Unicode solution, this does not require any special compiler options to process string literals, and it does not result in Unicode executables and libraries which are incompatible with ASCII ones."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:516
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/glibmm/classGlib_1_1ustring.html\">Reference</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:518
msgid "See the <link linkend=\"chapter-internationalization\">Internationalization</link> section for information about providing the UTF-8 string literals."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:523
msgid "Mixing C and C++ APIs"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:525
msgid "You can use C APIs which do not yet have convenient C++ interfaces. It is generally not a problem to use C APIs from C++, and <application>gtkmm</application> helps by providing access to the underlying C object, and providing an easy way to create a C++ wrapper object from a C object, provided that the C API is also based on the <classname>GObject</classname> system."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:531
msgid "To use a <application>gtkmm</application> instance with a C function that requires a C <classname>GObject</classname> instance, use the C++ instance’s <function>gobj()</function> function to obtain a pointer to the underlying C instance. For example:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:536
#, no-wrap
msgid ""
"\n"
"Gtk::Button button(\"example\");\n"
"gtk_button_do_something_that_gtkmm_cannot(button.gobj());\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:541
msgid "To obtain a <application>gtkmm</application> instance from a C <classname>GObject</classname> instance, use one of the many overloaded <function>Glib::wrap()</function> functions. The C instance’s reference count is not incremented, unless you set the optional <parameter>take_copy</parameter> argument to <literal>true</literal>. For example:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:547
#, no-wrap
msgid ""
"\n"
"GtkButton* cbutton = get_a_button();\n"
"Gtk::Button* button = Glib::wrap(cbutton);\n"
"button-&gt;set_label(\"Now I speak C++ too!\");\n"
""
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:554
msgid "it's a widget or other class that inherits from <classname>Gtk::Object</classname>, and"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:555
msgid "the C instance has a floating reference when the wrapper is created, and"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:556
msgid "<function>Gtk::manage()</function> has not been called on it (which includes if it was created with <function>Gtk::make_managed()</function>), or"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:557
msgid "<function>Gtk::manage()</function> was called on it, but it was never added to a parent."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:552
msgid "The C++ wrapper shall be explicitly deleted if <_:itemizedlist-1/> <function>Glib::wrap()</function> binds the C and C++ instances to each other. Don't delete the C++ instance before you want the C instance to die."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:562
msgid "In all other cases the C++ instance is automatically deleted when the last reference to the C instance is dropped. This includes all <function>Glib::wrap()</function> overloads that return a <classname>Glib::RefPtr</classname>."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:569
msgid "Hello World in <application>gtkmm</application>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:571
msgid "We've now learned enough to look at a real example. In accordance with an ancient tradition of computer science, we now introduce Hello World, a la <application>gtkmm</application>:"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:576
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/helloworld\">Source Code</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:578
msgid "Try to compile and run it before going on. You should see something like this:"
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:583
msgid "Hello World"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:585
msgctxt "_"
msgid "external ref='figures/helloworld.png' md5='02f7e986e608661d5a1524ac5f0c0b2e'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:589
msgid "Pretty thrilling, eh? Let's examine the code. First, the <classname>HelloWorld</classname> class:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:594
#, no-wrap
msgid ""
"class HelloWorld : public Gtk::Window\n"
"{\n"
"public:\n"
"  HelloWorld();\n"
"  ~HelloWorld() override;\n"
"\n"
"protected:\n"
"  //Signal handlers:\n"
"  void on_button_clicked();\n"
"\n"
"  //Member widgets:\n"
"  Gtk::Button m_button;\n"
"};"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:608
msgid "This class implements the \"Hello World\" window. It's derived from <classname>Gtk::Window</classname>, and has a single <classname>Gtk::Button</classname> as a member. We've chosen to use the constructor to do all of the initialization work for the window, including setting up the signals. Here it is, with the comments omitted:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:617
#, no-wrap
msgid ""
"HelloWorld::HelloWorld()\n"
": m_button(\"Hello World\")\n"
"{\n"
"  m_button.set_margin(10);\n"
"  m_button.signal_clicked().connect(sigc::mem_fun(*this,\n"
"    &amp;HelloWorld::on_button_clicked));\n"
"  set_child(m_button);\n"
"}"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:626
msgid "Notice that we've used an initializer statement to give the <literal>m_button</literal> object the label \"Hello World\"."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:631
msgid "Next we call the Button's <methodname>set_margin()</methodname> method. This sets the amount of space around the button."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:636
msgid "We then hook up a signal handler to <literal>m_button</literal>'s <literal>clicked</literal> signal. This prints our friendly greeting to <literal>stdout</literal>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:641
msgid "Next, we use the Window's <methodname>set_child()</methodname> method to put <literal>m_button</literal> in the Window. The <methodname>set_child()</methodname> method places the Widget in the Window."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:647
msgid "Now let's look at our program's <function>main()</function> function. Here it is, without comments:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:652
#, no-wrap
msgid ""
"int main(int argc, char* argv[])\n"
"{\n"
"  auto app = Gtk::Application::create(\"org.gtkmm.example\");\n"
"  return app-&gt;make_window_and_run&lt;HelloWorld&gt;(argc, argv);\n"
"}"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:658
msgid "First we instantiate an object stored in a <classname>Glib::RefPtr</classname> smartpointer called <literal>app</literal>. This is of type <classname>Gtk::Application</classname>. Every <application>gtkmm</application> program must have one of these."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:663
msgid "Next we call <methodname>make_window_and_run()</methodname> which creates an object of our <classname>HelloWorld</classname> class, shows that Window and starts the <application>gtkmm</application> <emphasis>event loop</emphasis>. During the event loop <application>gtkmm</application> idles, waiting for actions from the user, and responding appropriately. When the user closes the Window, <methodname>make_window_and_run()</methodname> will return, causing our <function>main()</function> function to return. The application will then finish."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:672
msgid "Like the simple example we showed earlier, this Hello World program does not use the command-line parameters."
msgstr ""

#. (itstool) path: chapter/title
#: C/index-in.docbook:681
msgid "Changes in <application>gtkmm</application> 3"
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:683
msgid "<application>gtkmm</application>-3.0 is an old version of the <application>gtkmm</application> API that installs in parallel with the still older <application>gtkmm</application>-2.4 API and the new <application>gtkmm</application>-4.0 API. The last version of the <application>gtkmm</application>-2.4 API was <application>gtkmm</application> 2.24. <application>gtkmm</application> 3 has no major fundamental differences to <application>gtkmm</application> 2 but does make several small changes that were not possible while maintaining binary compatibility. If you never used the <application>gtkmm</application>-2.4 API then you can safely ignore this chapter."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:685
msgid "<application>gtkmm</application> 3's library is called <literal>libgtkmm-3.0</literal> rather than <literal>libgtkmm-2.4</literal> and installs its headers in a similarly-versioned directory, so your pkg-config check should ask for <literal>gtkmm-3.0</literal> rather than <literal>gtkmm-2.4</literal>."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:687
msgid "<application>gtkmm</application> 3 added some new classes:"
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:690
msgid "<classname>Gtk::AppChooser</classname>, <classname>Gtk::AppChooserButton</classname>, <classname>Gtk::AppChooserDialog</classname> allow the user to select an installed application to open a particular type of content."
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:691
msgid "<classname>Gtk::Grid</classname> is a new container widget that will eventually replace <classname>Gtk::Box</classname> and <classname>Gtk::Table</classname>. It arranges its children according to properties of those children rather than its own layout details."
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:692
msgid "<classname>Gtk::Switch</classname> displays On/Off states more explicitly than <classname>Gtk::CheckButton</classname>. It may be useful, for instance, when allowing users to activate hardware."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:695
msgid "<application>gtkmm</application> 3 also made several small changes to the API, which you will probably encounter when porting code that used <application>gtkmm</application>-2.4. Here is a short list:"
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:700
msgid "<classname>Gtk::CellLayout</classname>, used by <classname>Gtk::IconView</classname>, <classname>Gtk::TreeView::Column</classname> and <classname>Gtk::ComboBox</classname>, now has a <classname>Gtk::CellArea</classname> which can be used to specify more details of how the <classname>CellRenderer</classname>s are arranged and aligned."
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:702
msgid "Gtk::ComboBox now derives from CellLayout, allowing easier layout and alignment of its <classname>Gtk::CellRenderer</classname>s."
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:704
msgid "<classname>Gtk::Adjustment</classname> and <classname>IconSet</classname> and <classname>Gdk::Cursor</classname> are now used via <classname>Glib::RefPtr</classname>."
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:706
msgid "<classname>Gtk::Box</classname>, <classname>Gtk::ButtonBox</classname>, <classname>Gtk::IconView</classname>, <classname>Gtk::Paned</classname>, <classname>Gtk::ProgressBar</classname>, <classname>Gtk::ScaleButton</classname>, <classname>Gtk::Scrollbar</classname> and <classname>Gtk::Separator</classname> now derive from <classname>Gtk::Orientable</classname>, allowing their orientation (vertical or horizontal) to be specified without requiring the use of a derived class such as <classname>Gtk::HBox</classname>."
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:709
msgid "<classname>Gtk::IconView</classname>, <classname>Gtk::TextView</classname>, <classname>Gtk::TreeView</classname> and other widgets derive from Scrollable instead of having their own methods such as <methodname>get_vadjustment()</methodname> and instead of having their own set_scroll_adjustments signal."
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:711
msgid "<classname>Gtk::Style</classname> and <classname>Gtk::Rc</classname> were removed, replaced by <classname>Gtk::StyleContext</classname>, and <classname>Gtk::StyleProvider</classname>s, such as <classname>Gtk::CssProvider</classname>."
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:713
msgid "Widget::on_expose_event() was replaced by Widget::on_draw(), which assumes that cairomm is used for drawing, via the provided <classname>Cairo::Context</classname> and does not require you to call <methodname>Cairo::Context::clip()</methodname>."
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:715
msgid "<classname>Gdk::RGBA</classname> replaces <classname>Color</classname>, adding an alpha component for opacity. <classname>Colormap</classname> was removed, along with its awkward use to allocate colors."
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:717
msgid "<classname>Gdk::Pixmap</classname> and <classname>Gdk::Bitmap</classname> were removed in favor of <classname>Gdk::Pixbuf</classname>."
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:719
msgid "<classname>Gdk::Drawable</classname> was removed, with its methods moving into <classname>Gdk::Window</classname>."
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:721
msgid "We now use std::vector in several methods instead of the intermediate *Handle types to make the API clearer."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:726
msgid "All deprecated API was removed in <application>gtkmm</application> 3.0, though there have been new deprecations in later <application>gtkmm</application> 3.x versions."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:728
msgid "As a first step to porting your source code to <application>gtkmm</application>-3.0 you should probably ensure that your application builds with the deprecated <application>gtkmm</application>-2.4 API disabled, by defining macro such as GTKMM_DISABLE_DEPRECATED. There are some autotools macros that can help with this by defining them optionally at build time. See the <link xlink:href=\"https://wiki.gnome.org/Projects/gtkmm/PortingToGtkmm3\">gtkmm 3 porting wiki page</link> for more details."
msgstr ""

#. (itstool) path: chapter/title
#: C/index-in.docbook:733
msgid "Changes in <application>gtkmm</application>-4.0 and <application>glibmm-2.68</application>"
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:735
msgid "<application>gtkmm</application>-4.0 is a new version of the <application>gtkmm</application> API that installs in parallel with the older <application>gtkmm</application>-2.4 and <application>gtkmm</application>-3.0 APIs. The last version of the <application>gtkmm</application>-3.0 API is <application>gtkmm</application> 3.24. <application>gtkmm</application> 4 has no major fundamental differences to <application>gtkmm</application> 3 but does make several changes (both small and large ones) that were not possible while maintaining binary compatibility. If you never used the <application>gtkmm</application>-3.0 API then you can safely ignore this chapter."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:743
msgid "<application>gtkmm</application> 4's library is called <literal>libgtkmm-4.0</literal> rather than <literal>libgtkmm-3.0</literal> and installs its headers in a similarly-versioned directory, so your <application>pkg-config</application> check should ask for <literal>gtkmm-4.0</literal> rather than <literal>gtkmm-3.0</literal>."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:749
msgid "<application>gtkmm</application>-4.0 is used in combination with <application>glibmm-2.68</application>, which sets the global locale for your program. The older <application>glibmm-2.4</application> does not do that, and <application>gtkmm</application>-3.0 does it only to some extent. What this means is briefly that if your <application>gtkmm</application>-3.0 program contains a call to <function>std::locale::global(std::locale(\"\"))</function>, you can probably remove it. If you don't want <application>glibmm</application> or <application>gtkmm</application> to set the global locale for you, you should add a call to <function>Glib::set_init_to_users_preferred_locale(false)</function> before any call to <function>Glib::init()</function> or <methodname>Gtk::Application::create()</methodname>. See the <application>glibmm</application> <link xlink:href=\"https://gnome.pages.gitlab.gnome.org/glibmm/namespaceGlib.html\"> reference</link>."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:761
msgid "There are lots and lots of differences between <application>gtkmm</application>-3.0 and <application>gtkmm</application>-4.0. The following lists are not complete."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:764
msgid "There are some important behavioural changes, to which you must adapt when migrating:"
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:767
msgid "Whereas in <application>gtkmm</application>-3.0, destruction of a non-managed C++ widget wrapper caused the wrapped GtkWidget to be destroyed, changes in GTK4 mean that in <application>gtkmm</application>-4.0 this canʼt always be the case. GTK4 has no uniform way to remove a widget from a parent, as GTK3 did with <methodname>Gtk::Container::remove()</methodname>, so <application>gtkmm</application>-4.0 canʼt do the removal for you as <application>gtkmm</application>-3.0 did. Hence, if a non-managed C++ widget instance is destructed while the widget is a child of another, <application>gtkmm</application>-4.0 wonʼt remove it from the parent, the parent retains a ref that stops the child being disposed, and the GtkWidget stays alive. The end result is that to destroy a non-managed widget with its C++ wrapper you must first remove it from its parent (however that parent allows) so the C++ wrapperʼs dtor can drop the final reference."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:780
msgid "Some new classes were added in <application>gtkmm</application> 4 and <application>glibmm</application> 2.68:"
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:782
msgid "<classname>Glib::ExtraClassInit</classname> and <classname>Gtk::Snapshot</classname>: These classes are needed only for writing custom widgets. See the <link linkend=\"sec-custom-widgets\">Custom Widgets</link> section."
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:785
msgid "<classname>Gtk::EventControllerKey</classname>, <classname>Gtk::EventControllerMotion</classname>, <classname>Gtk::EventControllerScroll</classname> and <classname>Gtk::GestureStylus</classname>"
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:788
msgid "<classname>Gdk::Paintable</classname>, <classname>Gdk::Texture</classname>, <classname>Gtk::Picture</classname> and <classname>Gtk::WidgetPaintable</classname>"
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:791
msgid "<classname>Gdk::Window</classname> has been renamed to <classname>Gdk::Surface</classname>. (<classname>Gtk::Window</classname> keeps its name.)"
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:793
msgid "<classname>Gdk::DrawContext</classname> and <classname>Gdk::CairoContext</classname> are new. <classname>Gdk::DrawingContext</classname> has been removed."
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:795
msgid "<classname>Gtk::Clipboard</classname> has been replaced by the new <classname>Gdk::Clipboard</classname>."
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:797
msgid "<classname>Gdk::DragContext</classname> has been split into <classname>Gdk::Drag</classname> and <classname>Gdk::Drop</classname>."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:801
msgid "There have also been several changes to the API, which you will probably encounter when porting code that used <application>gtkmm</application>-3.0 and <application>glibmm</application>-2.4. Here is a short list:"
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:805
msgid "A C++17 compiler is required."
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:806
msgid "<classname>Gtk::Button</classname>, <classname>Gtk::ToolButton</classname>, <classname>Gtk::MenuItem</classname> and <classname>Gtk::Switch</classname> implement the <classname>Gtk::Actionable</classname> interface instead of the removed <classname>Gtk::Activatable</classname> interface."
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:810
msgid "<classname>Gtk::FontButton</classname> implements the <classname>Gtk::FontChooser</classname> interface."
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:811
msgid "<classname>Gtk::Widget</classname>: The <methodname>get_preferred_*_vfunc()</methodname>s have been replaced by <methodname>measure_vfunc()</methodname>. This change only affects custom widgets."
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:814
msgid "<classname>sigc::slot</classname>s use the <classname>sigc::slot&lt;R(Args...)&gt;</classname> syntax. Example: <classname>sigc::slot&lt;void(int, int)&gt;</classname> instead of <classname>sigc::slot&lt;void, int, int&gt;</classname>."
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:816
msgid "<classname>Gtk::DrawingArea</classname> uses a draw function instead of the draw signal."
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:817
msgid "<classname>Glib::ArrayHandle</classname>, <classname>Glib::StringArrayHandle</classname>, <classname>Glib::ListHandle</classname> and <classname>Glib::SListHandle</classname> have been removed. They were used in <application>glibmm</application>-2.4, but not used in <application>gtkmm</application>-3.0. If you've ever used these classes, replace them with a standard C++ container, such as <classname>std::vector</classname>."
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:821
msgid "<classname>Gtk::Container</classname> has been removed."
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:822
msgid "<methodname>Gtk::Widget::show_all()</methodname> has been removed. The default value of <methodname>Gtk::Widget::property_visible()</methodname> has been changed from <literal>false</literal> to <literal>true</literal>."
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:825
msgid "All event signals have been removed from <classname>Gtk::Widget</classname>. In most cases you can use one of the subclasses of <classname>Gtk::EventController</classname> as a replacement. For instance, use <classname>Gtk::GestureMultiPress</classname> instead of <methodname>signal_button_press_event()</methodname> and <methodname>signal_button_release_event()</methodname>, and <classname>Gtk::EventControllerKey</classname> instead of <methodname>signal_key_press_event()</methodname> and <methodname>signal_key_release_event()</methodname>."
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:832
msgid "<classname>Glib::RefPtr</classname> is an alias for <classname>std::shared_ptr</classname>. If you make your own <classname>Glib::ObjectBase</classname>-derived classes with <methodname>create()</methodname> methods that return a <classname>Glib::RefPtr</classname>, you must use <methodname>Glib::make_refptr_for_instance()</methodname> in your <methodname>create()</methodname> methods."
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:837
msgid "<methodname>Gtk::Box::pack_start()</methodname> and <methodname>Gtk::Box::pack_end()</methodname> have been removed. Use the new <classname>Gtk::Box</classname> methods <methodname>append()</methodname>, <methodname>prepend()</methodname>, <methodname>insert_child_after()</methodname> and <methodname>insert_child_at_start()</methodname>."
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:842
msgid "<classname>Gtk::ButtonBox</classname> has been removed."
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:843
msgid "<classname>Gtk::RadioButton</classname> and <classname>Gtk::RadioButtonGroup</classname> have been removed. Use <classname>Gtk::CheckButton</classname> or <classname>Gtk::ToggleButton</classname> with <methodname>set_group()</methodname>."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:848
msgid "All deprecated API was removed in <application>gtkmm</application> 4.0 and <application>glibmm</application> 2.68, though there will be new deprecations in future versions."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:851
msgid "As a first step to porting your source code to <application>gtkmm</application>-4.0 you should probably ensure that your application builds with the deprecated <application>gtkmm</application>-3.0 and <application>glibmm-2.4</application> API disabled, by defining the macros GTKMM_DISABLE_DEPRECATED, GDKMM_DISABLE_DEPRECATED, GLIBMM_DISABLE_DEPRECATED and GIOMM_DISABLE_DEPRECATED. There are some autotools macros that can help with this by defining them optionally at build time. See the <link xlink:href=\"https://wiki.gnome.org/Projects/gtkmm/PortingToGtkmm3\">Porting from gtkmm-2.4 to gtkmm-3.0</link> wiki page for more details."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:858
msgid "See also <link xlink:href=\"https://docs.gtk.org/gtk4/migrating-3to4.html\"> Migrating from GTK 3.x to GTK 4</link>."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:862
msgid "Deprecations in <application>gtkmm</application> 4.10"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:863
msgid "Many classes are deprecated since <application>gtkmm</application> 4.10. They can still be used in <application>gtkmm</application>4 applications, provided GTKMM_DISABLE_DEPRECATED and GDKMM_DISABLE_DEPRECATED are not defined. There are also many new classes in <application>gtkmm</application> 4.10, which replace some of the deprecated classes. Some example programs in this tutorial use classes deprecated since <application>gtkmm</application> 4.10. Some other programs use classes available since <application>gtkmm</application> 4.10."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:869
msgid "Deprecated classes: AppChooser, AppChooserButton, AppChooserDialog, AppChooserWidget, CellArea, CellAreaBox, CellAreaContext, CellLayout, CellRenderer, CellRendererAccel, CellRendererCombo, CellRendererPixbuf, CellRendererProgress, CellRendererSpin, CellRendererSpinner, CellRendererText, CellRendererToggle, CellView, ComboBox, ComboBoxText, EntryCompletion, IconView, ListStore, ListViewText, StyleContext, TreeDragDest, TreeDragSource, TreeIter and other classes in treeiter.h, TreeModel, TreeModelFilter, TreeModelSort, TreePath, TreeRowReference, TreeSelection, TreeSortable, TreeStore, TreeView, TreeViewColumn, namespace CellRenderer_Generation, namespace TreeView_Private, ColorButton, ColorChooser, ColorChooserDialog, FileChooser, FileChooserDialog, FileChooserNative, FileChooserWidget, FontButton, FontChooser, FontChooserDialog, FontChooserWidget, MessageDialog, TreeModelColumn, TreeModelColumnRecord, InfoBar, Assistant, AssistantPage, LockButton, Statusbar, VolumeButton."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:887
msgid "New classes and enums: AlertDialog, ColorDialog, ColorDialogButton, ColumnViewSorter, FileDialog, FontDialog, FontDialogButton, FileLauncher, UriLauncher, ATContext, enums DialogError, FontLevel, Collation."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:892
msgid "In most cases there are replacements for the deprecated classes. See the reference documentation."
msgstr ""

#. (itstool) path: chapter/title
#: C/index-in.docbook:900
msgid "Buttons"
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:902
msgid "<application>gtkmm</application> provides four basic types of buttons:"
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:909
msgid "Push buttons"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:911
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1Button.html\"><classname>Gtk::Button</classname></link>. Standard buttons, usually marked with a label or picture. Pushing one triggers an action. See the <link linkend=\"sec-pushbuttons\">Button</link> section."
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:918
msgid "Toggle buttons"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:920
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1ToggleButton.html\"><classname>Gtk::ToggleButton</classname></link>. Unlike a normal Button, which springs back up, a ToggleButton stays down until you press it again. It might be useful as an on/off switch. See the <link linkend=\"sec-toggle-buttons\">ToggleButton</link> section."
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:928
msgid "Check buttons"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:930
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1CheckButton.html\"><classname>Gtk::CheckButton</classname></link>. These act like ToggleButtons, but show their state in small squares, with their label at the side. They should be used in most situations which require an on/off setting. See the <link linkend=\"sec-checkbuttons\">CheckButton</link> section."
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:940
msgid "Radio buttons"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:942
msgid "Named after the station selectors on old car radios, these buttons are used in groups for options which are mutually exclusive. Pressing one causes all the others in its group to turn off. They are similar to ToggleButtons or CheckButtons (a small widget with a label at the side), but usually look different. There is no separate radio button class. Check buttons and toggle buttons can act as radio buttons. See the <link linkend=\"sec-radio-buttons\">Radio Button</link> section."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:956
msgid "Note that, due to GTK's theming system, the appearance of these widgets will vary. In the case of check buttons and radio buttons, they may vary considerably."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:963
msgid "Button"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:965
msgid "There are two ways to create a Button. You can specify a label string in the <classname>Gtk::Button</classname> constructor, or set it later with <methodname>set_label()</methodname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:971
msgid "To define an accelerator key for keyboard navigation, place an underscore before one of the label's characters and specify <literal>true</literal> for the optional <literal>mnemonic</literal> parameter. For instance:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:973
#, no-wrap
msgid ""
"Gtk::Button* pButton = new Gtk::Button(\"_Something\", true);"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:975
msgid "<classname>Gtk::Button</classname> is also a container so you could put any other widget, such as a <classname>Gtk::Image</classname> into it."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:981
msgid "The <classname>Gtk::Button</classname> widget has the <literal>clicked</literal> signal which is emitted when the button is pressed and released."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:986
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1Button.html\">Reference</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:989
#: C/index-in.docbook:1043
#: C/index-in.docbook:1103
#: C/index-in.docbook:1219
#: C/index-in.docbook:1277
#: C/index-in.docbook:1595
#: C/index-in.docbook:1662
#: C/index-in.docbook:1685
#: C/index-in.docbook:1720
#: C/index-in.docbook:1774
#: C/index-in.docbook:1813
#: C/index-in.docbook:1854
#: C/index-in.docbook:1887
#: C/index-in.docbook:2177
#: C/index-in.docbook:2209
#: C/index-in.docbook:2263
#: C/index-in.docbook:2310
#: C/index-in.docbook:2471
#: C/index-in.docbook:2495
#: C/index-in.docbook:2519
#: C/index-in.docbook:2557
#: C/index-in.docbook:2585
#: C/index-in.docbook:2616
#: C/index-in.docbook:4513
#: C/index-in.docbook:4542
#: C/index-in.docbook:4569
#: C/index-in.docbook:4596
#: C/index-in.docbook:4628
#: C/index-in.docbook:4652
#: C/index-in.docbook:4831
#: C/index-in.docbook:4980
#: C/index-in.docbook:5056
#: C/index-in.docbook:5128
#: C/index-in.docbook:5196
#: C/index-in.docbook:5436
#: C/index-in.docbook:6293
#: C/index-in.docbook:6341
#: C/index-in.docbook:6909
#: C/index-in.docbook:7033
#: C/index-in.docbook:7680
#: C/index-in.docbook:7741
#: C/index-in.docbook:7799
#: C/index-in.docbook:8024
#: C/index-in.docbook:9487
msgid "Example"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:991
msgid "This example creates a button with a picture and a label."
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:996
msgid "buttons example"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:998
msgctxt "_"
msgid "external ref='figures/buttons.png' md5='ab288a013ed7d6c0b797f5998961dea9'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1002
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/buttons/button\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:1009
msgid "ToggleButton"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1011
msgid "<classname>ToggleButton</classname>s are like normal <classname>Button</classname>s, but when clicked they remain activated, or pressed, until clicked again."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1013
msgid "To retrieve the state of the <classname>ToggleButton</classname>, you can use the <methodname>get_active()</methodname> method. This returns <literal>true</literal> if the button is \"down\". You can also set the toggle button's state, with <methodname>set_active()</methodname>. Note that, if you do this, and the state actually changes, it causes the \"clicked\" signal to be emitted. This is usually what you want."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1020
msgid "You can use the <methodname>toggled()</methodname> method to toggle the button, rather than forcing it to be up or down: This switches the button's state, and causes the <literal>toggled</literal> signal to be emitted."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1025
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1ToggleButton.html\">Reference</link>"
msgstr ""

#. (itstool) path: section/title
#. (itstool) path: figure/title
#: C/index-in.docbook:1030
#: C/index-in.docbook:1046
msgid "CheckButton"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1032
msgid "<classname>Gtk::CheckButton</classname> inherits directly from <classname>Gtk::Widget</classname>. It is similar to <classname>Gtk::ToggleButton</classname>. The only real difference between the two is <classname>Gtk::CheckButton</classname>'s appearance. You can check and set a check button using the same member methods as for <classname>Gtk::ToggleButton</classname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1040
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1CheckButton.html\">Reference</link>"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:1048
msgctxt "_"
msgid "external ref='figures/checkbutton.png' md5='4d0e8f846ce98aeeada64227dd2f55a7'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1052
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/buttons/checkbutton\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:1058
msgid "Radio Button"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1060
msgid "There is no separate class for radio buttons. Check buttons and toggle buttons act as radio buttons when they form a group. Only one button in a group can be selected at any one time."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:1067
msgid "Groups"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1068
msgid "You create the buttons, and set up their group afterwards. In the following example, we put 3 radio buttons in a group:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:1073
#, no-wrap
msgid ""
"\n"
"auto rb1 = Gtk::make_managed&lt;Gtk::CheckButton&gt;(\"button1\");\n"
"auto rb2 = Gtk::make_managed&lt;Gtk::CheckButton&gt;(\"button2\");\n"
"auto rb3 = Gtk::make_managed&lt;Gtk::CheckButton&gt;(\"button3\");\n"
"rb2-&gt;set_group(*rb1);\n"
"rb3-&gt;set_group(*rb1);\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1081
msgid "We told <application>gtkmm</application> to put all three <classname>CheckButton</classname>s in the same group by using <methodname>set_group()</methodname> to tell the other <classname>CheckButton</classname>s to share group with the first <classname>CheckButton</classname>."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:1091
#: C/index-in.docbook:1556
#: C/index-in.docbook:5307
msgid "Methods"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1092
msgid "<classname>CheckButton</classname>s and <classname>ToggleButton</classname>s are \"off\" when created; this means that when you first make a group of them, they will all be off. Don't forget to turn one of them on using <methodname>set_active()</methodname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1098
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1RadioButton.html\">Reference</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1104
msgid "The following example demonstrates the use of grouped <classname>CheckButton</classname>s:"
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:1110
msgid "RadioButton"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:1112
msgctxt "_"
msgid "external ref='figures/radiobuttons.png' md5='49ad0ed4567104af07b1c6484ffb821e'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1116
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/buttons/radiobutton\">Source Code</link>"
msgstr ""

#. (itstool) path: chapter/title
#. (itstool) path: figure/title
#: C/index-in.docbook:1123
#: C/index-in.docbook:1230
msgid "Range Widgets"
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:1125
msgid "<classname>Gtk::Scale</classname> inherits from <classname>Gtk::Range</classname>. <classname>Gtk::Scrollbar</classname> does not inherit from <classname>Gtk::Range</classname>, but it shares much functionality with <classname>Gtk::Scale</classname>. They both contain a \"trough\" and a \"slider\" (sometimes called a \"thumbwheel\" in other GUI environments). Dragging the slider with the pointer moves it within the trough, while clicking in the trough advances the slider towards the location of the click, either completely, or by a designated amount, depending on which mouse button is used. This should be familiar scrollbar behavior."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:1137
msgid "As will be explained in the <link linkend=\"chapter-adjustment\">Adjustments</link> section, all range widgets are associated with an <classname>Adjustment</classname> object. To change the lower, upper, and current values used by the widget you need to use the methods of its <classname>Adjustment</classname>, which you can get with the <methodname>get_adjustment()</methodname> method. The range widgets' default constructors create an <classname>Adjustment</classname> automatically, or you can specify an existing <classname>Adjustment</classname>, maybe to share it with another widget. See the <link linkend=\"chapter-adjustment\">Adjustments</link> section for further details."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:1151
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1Range.html\">Reference</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:1154
msgid "Scrollbar Widgets"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1156
msgid "These are standard scrollbars. They should be used only to scroll another widget, such as a <classname>Gtk::Entry</classname> or a <classname>Gtk::Viewport</classname>, though it's usually easier to use the <classname>Gtk::ScrolledWindow</classname> widget in most cases."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1163
msgid "The orientation of a <classname>Gtk::Scrollbar</classname> can be either horizontal or vertical."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1168
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1Scrollbar.html\">Reference</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:1173
msgid "Scale Widgets"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1175
msgid "<classname>Gtk::Scale</classname> widgets (or \"sliders\") allow the user to visually select and manipulate a value within a specific range. You might use one, for instance, to adjust the magnification level on a zoomed preview of a picture, or to control the brightness of a colour, or to specify the number of minutes of inactivity before a screensaver takes over the screen."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1184
msgid "As with <classname>Scrollbar</classname>s, the orientation can be either horizontal or vertical. The default constructor creates an <classname>Adjustment</classname> with all of its values set to <literal>0.0</literal>. This isn't useful so you will need to set some <classname>Adjustment</classname> details to get meaningful behavior."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:1193
msgid "Useful methods"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1195
msgid "<classname>Scale</classname> widgets can display their current value as a number next to the trough. By default they show the value, but you can change this with the <methodname>set_draw_value()</methodname> method."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1201
msgid "The value displayed by a scale widget is rounded to one decimal point by default, as is the <literal>value</literal> field in its <classname>Gtk::Adjustment</classname>. You can change this with the <methodname>set_digits()</methodname> method."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1208
msgid "Also, the value can be drawn in different positions relative to the trough, specified by the <methodname>set_value_pos()</methodname> method."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1213
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1Scale.html\">Reference</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1221
msgid "This example displays a window with three range widgets all connected to the same adjustment, along with a couple of controls for adjusting some of the parameters mentioned above and in the section on adjustments, so you can see how they affect the way these widgets work for the user."
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:1232
msgctxt "_"
msgid "external ref='figures/range_widgets.png' md5='8bebdf457c84aa921681a7f44f46f244'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1236
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/range_widgets\">Source Code</link>"
msgstr ""

#. (itstool) path: chapter/title
#: C/index-in.docbook:1243
msgid "Miscellaneous Widgets"
msgstr ""

#. (itstool) path: section/title
#. (itstool) path: figure/title
#: C/index-in.docbook:1246
#: C/index-in.docbook:1287
msgid "Label"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1248
msgid "Labels are the main method of placing non-editable text in windows, for instance to place a title next to an <classname>Entry</classname> widget. You can specify the text in the constructor, or later with the <methodname>set_text()</methodname> or <methodname>set_markup()</methodname> methods."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1255
msgid "The width of the label will be adjusted automatically. You can produce multi-line labels by putting line breaks (\"\\n\") in the label string."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1259
msgid "The label text can be justified using the <methodname>set_justify()</methodname> method. The widget is also capable of word-wrapping, which can be activated with <methodname>set_wrap()</methodname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1265
msgid "Gtk::Label supports some simple formatting, for instance allowing you to make some text bold, colored, or larger. You can do this by providing a string to <methodname>set_markup()</methodname>, using the <link xlink:href=\"https://docs.gtk.org/Pango/pango_markup.html\">Pango Markup syntax</link>. For instance, <code> &lt;b&gt;bold text&lt;/b&gt; and &lt;s&gt;strikethrough text&lt;/s&gt; </code> ."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1274
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1Label.html\">Reference</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1278
msgid "Below is a short example to illustrate these functions. This example makes use of the Frame widget to better demonstrate the label styles. (The Frame widget is explained in the <link linkend=\"sec-frame\">Frame</link> section.) It is possible that the first character in <literal>m_Label_Normal</literal> is shown underlined only when you press the <keycap>Alt</keycap> key."
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:1289
msgctxt "_"
msgid "external ref='figures/label.png' md5='107dd71338becc14c70fbd3a708caa89'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1293
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/label\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#. (itstool) path: figure/title
#: C/index-in.docbook:1300
#: C/index-in.docbook:1356
msgid "Entry"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:1303
msgid "Simple Use"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1305
msgid "Entry widgets allow the user to enter text. You can change the contents with the <methodname>set_text()</methodname> method, and read the current contents with the <methodname>get_text()</methodname> method."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1310
msgid "Occasionally you might want to make an <classname>Entry</classname> widget read-only. This can be done by passing <literal>false</literal> to the <methodname>set_editable()</methodname> method."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1316
msgid "For the input of passwords, passphrases and other information you don't want echoed on the screen, calling <methodname>set_visibility()</methodname> with <literal>false</literal> will cause the text to be hidden."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1322
msgid "You might want to be notified whenever the user types in a text entry widget. <classname>Gtk::Entry</classname> provides two signals, <literal>activate</literal> (since <application>gtkmm</application> 4.8) and <literal>changed</literal>, for this purpose. <literal>activate</literal> is emitted when the user presses the <keycap>Enter</keycap> key in a text-entry widget; <literal>changed</literal> is emitted when the text in the widget changes. You can use these, for instance, to validate or filter the text the user types. Moving the keyboard focus to another widget may also signal that the user has finished entering text. The <literal>leave</literal> signal in a <classname>Gtk::EventControllerFocus</classname> can notify you when that happens. The <link linkend=\"sec-comboboxentry\">ComboBox with an Entry</link> section contains example programs that use these signals."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1336
msgid "If you pass <literal>true</literal> to the <methodname>set_activates_default()</methodname> method, pressing <keycap>Enter</keycap> in the <classname>Gtk::Entry</classname> will activate the default widget for the window containing the <classname>Gtk::Entry</classname>. This is especially useful in dialog boxes. The default widget is usually one of the dialog buttons, which e.g. will close the dialog box. To set a widget as the default widget, use <methodname>Gtk::Window::set_default_widget()</methodname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1345
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1Entry.html\">Reference</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:1348
msgid "Simple Entry Example"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1349
msgid "This example uses <classname>Gtk::Entry</classname>. It also has two <classname>CheckButton</classname>s, with which you can toggle the editable and visible flags."
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:1358
msgctxt "_"
msgid "external ref='figures/entry.png' md5='ae877c1b982f8c6cadebc9867f6d9075'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1362
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/entry/simple\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#. (itstool) path: figure/title
#: C/index-in.docbook:1369
#: C/index-in.docbook:1409
msgid "Entry Completion"
msgstr ""

#. (itstool) path: note/para
#: C/index-in.docbook:1371
msgid "<classname>Gtk::EntryCompletion</classname> is deprecated since <application>gtkmm</application> 4.10. There is no replacement in <application>gtkmm</application>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1375
msgid "An <classname>Entry</classname> widget can offer a drop-down list of pre-existing choices based on the first few characters typed by the user. For instance, a search dialog could suggest text from previous searches."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1380
msgid "To enable this functionality, you must create an <classname>EntryCompletion</classname> object, and provide it to the <classname>Entry</classname> widget via the <methodname>set_completion()</methodname> method."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1385
msgid "The <classname>EntryCompletion</classname> may use a <classname>TreeModel</classname> containing possible entries, specified with <methodname>set_model()</methodname>. You should then call <methodname>set_text_column()</methodname> to specify which of your model columns should be used to match possible text entries."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1391
msgid "Alternatively, if a complete list of possible entries would be too large or too inconvenient to generate, a callback slot may instead be specified with <methodname>set_match_func()</methodname>. This is also useful if you wish to match on a part of the string other than the start."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1397
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1EntryCompletion.html\">Reference</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:1400
msgid "Entry Completion Example"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1401
msgid "This example creates a <classname>Gtk::EntryCompletion</classname> and associates it with a <classname>Gtk::Entry</classname> widget. The completion uses a <classname>Gtk::TreeModel</classname> of possible entries, and some additional actions."
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:1411
msgctxt "_"
msgid "external ref='figures/entry_completion.png' md5='5b9015c5bd9c04c2c51eb1de40ab7534'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1415
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/entry/completion\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:1421
msgid "Entry Icons"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1423
msgid "An <classname>Entry</classname> widget can show an icon at the start or end of the text area. The icon can be specified by methods such as <methodname>set_icon_from_paintable()</methodname> or <methodname>set_icon_from_icon_name()</methodname>. An application can respond to the user pressing the icon by handling the <methodname>signal_icon_press</methodname> signal."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:1431
msgid "Entry Icon Example"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1432
msgid "This example shows a <classname>Gtk::Entry</classname> widget with a named search icon, and prints text to the terminal when the icon is pressed."
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:1438
msgid "Entry with Icon"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:1440
msgctxt "_"
msgid "external ref='figures/entry_icon.png' md5='fb1db5f1b82bb2849d352170ada89191'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1444
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/entry/icon\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:1450
msgid "Entry Progress"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1452
msgid "An <classname>Entry</classname> widget can show a progress bar inside the text area, under the entered text. The progress bar will be shown if the <methodname>set_progress_fraction()</methodname> or <methodname>set_progress_pulse_step()</methodname> methods are called."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:1458
msgid "Entry Progress Example"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1459
msgid "This example shows a <classname>Gtk::Entry</classname> widget with a progress bar."
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:1465
msgid "Entry with Progress Bar"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:1467
msgctxt "_"
msgid "external ref='figures/entry_progress.png' md5='07a446c645744d0ab3516112271cf4e3'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1471
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/entry/progress\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#. (itstool) path: figure/title
#: C/index-in.docbook:1479
#: C/index-in.docbook:1602
msgid "SpinButton"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1481
msgid "A <classname>SpinButton</classname> allows the user to select a value from a range of numeric values. It has an <classname>Entry</classname> widget with increment and decrement buttons at the side. Clicking the buttons causes the value to 'spin' up and down across the range of possible values. The <classname>Entry</classname> widget may also be used to enter a value directly."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1489
msgid "The value can have an adjustable number of decimal places, and the step size is configurable. <classname>SpinButton</classname>s have an 'auto-repeat' feature as well: holding down the increment or decrement button can optionally cause the value to change more quickly the longer the button is held down."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:1503
msgid "<literal>value</literal>: value for the Spin Button"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:1509
msgid "<literal>lower</literal>: lower range value"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:1515
msgid "<literal>upper</literal>: upper range value"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:1520
msgid "<literal>step_increment</literal>: value to increment/decrement when pressing mouse button 1"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:1527
msgid "<literal>page_increment</literal>: value to increment/decrement when pressing mouse button 2"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:1534
msgid "<literal>page_size</literal>: unused"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1496
msgid "<classname>SpinButton</classname>s use an <link linkend=\"chapter-adjustment\">Adjustment</link> object to hold information about the range of values. These Adjustment attributes are used by the Spin Button like so: <_:itemizedlist-1/>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1542
msgid "Additionally, mouse button 3 can be used to jump directly to the <literal>upper</literal> or <literal>lower</literal> values."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1547
msgid "The <classname>SpinButton</classname> can create a default <classname>Adjustment</classname>, which you can access via the <methodname>get_adjustment()</methodname> method, or you can specify an existing <classname>Adjustment</classname> in the constructor."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1558
msgid "The number of decimal places can be altered using the <methodname>set_digits()</methodname> method."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1563
msgid "You can set the spinbutton's value using the <methodname>set_value()</methodname> method, and retrieve it with <methodname>get_value()</methodname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1568
msgid "The <methodname>spin()</methodname> method 'spins' the <classname>SpinButton</classname>, as if its increment or decrement button had been clicked. You need to specify a <classname>Gtk::SpinType</classname> to specify the direction or new position."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1575
msgid "To prevent the user from typing non-numeric characters into the entry box, pass <literal>true</literal> to the <methodname>set_numeric()</methodname> method."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1580
msgid "To make the <classname>SpinButton</classname> 'wrap' between its upper and lower bounds, use the <methodname>set_wrap()</methodname> method."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1585
msgid "To force it to snap to the nearest <literal>step_increment</literal>, use <methodname>set_snap_to_ticks()</methodname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1590
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1SpinButton.html\">Reference</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1597
msgid "Here's an example of a <classname>SpinButton</classname> in action:"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:1604
msgctxt "_"
msgid "external ref='figures/spinbutton.png' md5='2157244b231fea5619793aa8ba25d4d8'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1608
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/spinbutton\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#. (itstool) path: figure/title
#: C/index-in.docbook:1615
#: C/index-in.docbook:1665
msgid "ProgressBar"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1617
msgid "Progress bars are used to show the status of an ongoing operation. For instance, a <classname>ProgressBar</classname> can show how much of a task has been completed."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1623
msgid "To change the value shown, use the <methodname>set_fraction()</methodname> method, passing a <type>double</type> between 0.0 and 1.0 to provide the new fraction."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1628
msgid "A <classname>ProgressBar</classname> is horizontal and left-to-right by default, but you can change it to a vertical progress bar by using the <methodname>set_orientation()</methodname> method."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1634
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1ProgressBar.html\">Reference</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:1637
msgid "Activity Mode"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1639
msgid "Besides indicating the amount of progress that has occurred, the progress bar can also be used to indicate that there is some activity; this is done by placing the progress bar in <emphasis>activity mode</emphasis>. In this mode, the progress bar displays a small rectangle which moves back and forth. Activity mode is useful in situations where the progress of an operation cannot be calculated as a value range (e.g., receiving a file of unknown length)."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1649
msgid "To do this, you need to call the <methodname>pulse()</methodname> method at regular intervals. You can also choose the step size, with the <methodname>set_pulse_step()</methodname> method."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1655
msgid "The progress bar can also display a configurable text string next to the bar, using the <methodname>set_text()</methodname> method."
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:1667
msgctxt "_"
msgid "external ref='figures/progressbar.png' md5='c7dcbf44476378ef1d0c601f619c7918'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1671
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/progressbar\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#. (itstool) path: figure/title
#: C/index-in.docbook:1677
#: C/index-in.docbook:1692
msgid "InfoBar"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1679
msgid "An <classname>InfoBar</classname> may show small items of information or ask brief questions. Unlike a <classname>Dialog</classname>, it appears at the top of the current window instead of opening a new window. Its API is very similar to the <link linkend=\"chapter-dialogs\">Gtk::Dialog</link> API."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1682
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1InfoBar.html\">Reference</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1687
msgid "The <classname>InfoBar</classname> widget is deprecated since <application>gtkmm</application> 4.10. The example shows an info bar consisting of a <classname>Box</classname> with a <classname>Label</classname> and a <classname>Button</classname>."
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:1694
msgctxt "_"
msgid "external ref='figures/infobar.png' md5='4da1d3d7d3011221c3a1d896436b1931'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1698
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/infobar\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:1705
msgid "Tooltips"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1707
msgid "Tooltips are the little information windows that pop up when you leave your pointer over a widget for a few seconds. Use <methodname>set_tooltip_text()</methodname> to set a text string as a tooltip on any <classname>Widget</classname>. <classname>Gtk::Tooltip</classname> is used for more advanced tooltip usage, such as showing an image as well as text."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1716
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1Widget.html\">Widget Reference</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1717
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1Tooltip.html\">Tooltip Reference</link>"
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:1723
msgid "Tooltip"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:1725
msgctxt "_"
msgid "external ref='figures/tooltip.png' md5='85a18bdc5b7301f2d4d4a1886176a38c'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1729
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/tooltips\">Source Code</link>"
msgstr ""

#. (itstool) path: chapter/title
#: C/index-in.docbook:1736
msgid "Container Widgets"
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:1738
msgid "Container widgets, like other widgets, derive from <classname>Gtk::Widget</classname>. Some container widgets, such as <classname>Gtk::Grid</classname> can hold many child widgets, so these typically have more complex interfaces. Others, such as <classname>Gtk::Frame</classname> contain only one child widget."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:1746
msgid "Single-item Containers"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1748
msgid "Most single-item container widgets have <methodname>set_child()</methodname> and <methodname>unset_child()</methodname> methods for the child widget. <classname>Gtk::Button</classname> and <classname>Gtk::Window</classname> are technically single-item containers, but we have discussed them already elsewhere."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1755
msgid "We also discuss the <classname>Gtk::Paned</classname> widget, which allows you to divide a window into two separate \"panes\". This widget actually contains two child widgets, but the number is fixed so it seems appropriate."
msgstr ""

#. (itstool) path: section/title
#. (itstool) path: figure/title
#: C/index-in.docbook:1762
#: C/index-in.docbook:1777
msgid "Frame"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1764
msgid "Frames can enclose one or a group of widgets within a box, optionally with a title. For instance, you might place a group of <classname>ToggleButton</classname>s or <classname>CheckButton</classname>s in a <classname>Frame</classname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1771
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1Frame.html\">Reference</link>"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:1779
msgctxt "_"
msgid "external ref='figures/frame.png' md5='e7b49b5f57afa5c0d4c487c187f1be55'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1783
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/frame\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#. (itstool) path: figure/title
#: C/index-in.docbook:1789
#: C/index-in.docbook:1816
msgid "Paned"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1791
msgid "Panes divide a widget into two halves, separated by a moveable divider. The two halves (panes) can be oriented either horizontally (side by side) or vertically (one above the other)."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1797
msgid "Unlike the other widgets in this section, pane widgets contain not one but two child widgets, one in each pane. Therefore, you should use <methodname>set_start_child()</methodname> and <methodname>set_end_child()</methodname> instead of a <methodname>set_child()</methodname> method."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1804
msgid "You can adjust the position of the divider using the <methodname>set_position()</methodname> method, and you will probably need to do so."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1810
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1Paned.html\">Reference</link>"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:1818
msgctxt "_"
msgid "external ref='figures/paned.png' md5='874e9d11227d6d10d2ab7cb0b04de32d'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1822
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/paned\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#. (itstool) path: figure/title
#: C/index-in.docbook:1828
#: C/index-in.docbook:1861
msgid "ScrolledWindow"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1830
msgid "<classname>ScrolledWindow</classname> widgets create a scrollable area. You can insert any type of widget into a <classname>ScrolledWindow</classname>, and it will be accessible regardless of its size by using the scrollbars. Note that <classname>ScrolledWindow</classname> is not a <classname>Gtk::Window</classname> despite the slightly misleading name."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1839
msgid "Scrolled windows have <emphasis>scrollbar policies</emphasis> which determine whether the <classname>Scrollbar</classname>s will be displayed. The policies can be set with the <methodname>set_policy()</methodname> method. The policy may be for instance <literal>Gtk::PolicyType::AUTOMATIC</literal> or <literal>Gtk::PolicyType::ALWAYS</literal>. <literal>Gtk::PolicyType::AUTOMATIC</literal> will cause the scrolled window to display the scrollbar only if the contained widget is larger than the visible area. <literal>Gtk::PolicyType::ALWAYS</literal> will cause the scrollbar to be displayed always."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1851
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1ScrolledWindow.html\">Reference</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1856
msgid "Here is a simple example that packs 100 toggle buttons into a ScrolledWindow. Try resizing the window to see the scrollbars react."
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:1863
msgctxt "_"
msgid "external ref='figures/scrolledwindow.png' md5='b99f195d17b39197af733087e0e69def'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1867
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/scrolledwindow\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#. (itstool) path: figure/title
#: C/index-in.docbook:1873
#: C/index-in.docbook:1896
msgid "AspectFrame"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1875
msgid "The <classname>AspectFrame</classname> widget looks like a <classname>Frame</classname> widget, but it also enforces the <emphasis>aspect ratio</emphasis> (the ratio of the width to the height) of the child widget, adding extra space if necessary. For instance, this would allow you to display a photograph without allowing the user to distort it horizontally or vertically while resizing."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1884
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1AspectFrame.html\">Reference</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1889
msgid "The following program uses a <classname>Gtk::AspectFrame</classname> to present a drawing area whose aspect ratio will always be 2:1, no matter how the user resizes the top-level window."
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:1898
msgctxt "_"
msgid "external ref='figures/aspectframe.png' md5='9d8aac9521789ed27036a97a22fedece'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1902
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/aspectframe\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:1908
msgid "Other Single-item Containers"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1910
msgid "There are other single-item containers. See the reference documentation for a complete list. Here are links to some example programs that show containers, which are not mentioned elsewhere in this tutorial."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1916
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/expander\">Source Code, Expander</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1917
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/popover\">Source Code, Popover</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:1924
msgid "Multiple-item Containers"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1926
msgid "Multiple-item container widgets have other methods than <methodname>set_child()</methodname> and <methodname>unset_child()</methodname>. Different containers can have different methods for adding and removing child widgets. For instance, <classname>Gtk::Box</classname> has <methodname>append()</methodname> and <methodname>remove()</methodname> as well as other methods. The <methodname>remove()</methodname> method for multiple-item containers takes an argument, specifying which widget to remove."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:1936
msgid "Packing"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1938
msgid "You've probably noticed that <application>gtkmm</application> windows seem \"elastic\" - they can usually be stretched in many different ways. This is due to the <emphasis>widget packing</emphasis> system."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1943
msgid "Many GUI toolkits require you to precisely place widgets in a window, using absolute positioning, often using a visual editor. This leads to several problems:"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:1950
msgid "The widgets don't rearrange themselves when the window is resized. Some widgets are hidden when the window is made smaller, and lots of useless space appears when the window is made larger."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:1954
msgid "It's impossible to predict the amount of space necessary for text after it has been translated to other languages, or displayed in a different font. On Unix it is also impossible to anticipate the effects of every theme and window manager."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:1958
msgid "Changing the layout of a window \"on the fly\", to make some extra widgets appear, for instance, is complex. It requires tedious recalculation of every widget's position."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1964
msgid "<application>gtkmm</application> uses the packing system to solve these problems. Rather than specifying the position and size of each widget in the window, you can arrange your widgets in rows, columns, and/or grids. <application>gtkmm</application> can size your window automatically, based on the sizes of the widgets it contains. And the sizes of the widgets are, in turn, determined by the amount of text they contain, or the minimum and maximum sizes that you specify, and/or how you have requested that the available space should be shared between sets of widgets. You can perfect your layout by specifying margins and centering values for each of your widgets. <application>gtkmm</application> then uses all this information to resize and reposition everything sensibly and smoothly when the user manipulates the window."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1973
msgid "<application>gtkmm</application> arranges widgets hierarchically, using <emphasis>containers</emphasis>. A container widget contains other widgets. Most <application>gtkmm</application> widgets are containers. Windows, Notebook tabs, and Buttons are all container widgets. There are two flavors of containers: single-child containers and multiple-child containers. Most container widgets in <application>gtkmm</application> are single-child containers, including <classname>Gtk::Window</classname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:1982
msgid "Yes, that's correct: a Window can contain at most one widget. How, then, can we use a window for anything useful? By placing a multiple-child container in the window. The most useful container widgets are <classname>Gtk::Grid</classname> and <classname>Gtk::Box</classname>."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:1993
msgid "<classname>Gtk::Grid</classname> arranges its child widgets in rows and columns. Use <methodname>attach()</methodname> and <methodname>attach_next_to()</methodname> to insert child widgets."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:2001
msgid "<classname>Gtk::Box</classname> arranges its child widgets vertically or horizontally. Use <methodname>append()</methodname> to insert child widgets."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2009
msgid "There are several other containers, which we will also discuss."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2013
msgid "If you've never used a packing toolkit before, it can take some getting used to. You'll probably find, however, that you don't need to rely on visual form editors quite as much as you might with other toolkits."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:2023
msgid "An improved Hello World"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2025
msgid "Let's take a look at a slightly improved <literal>helloworld</literal>, showing what we've learnt."
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:2030
msgid "Hello World 2"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:2032
msgctxt "_"
msgid "external ref='figures/helloworld2.png' md5='b16c41a2b1206bb0a5a3e1e488e198f8'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2036
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/helloworld2\">Source Code</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2038
msgid "After building and running this program, try resizing the window to see the behavior. Also, try playing with <methodname>set_expand()</methodname>, <methodname>set_hexpand()</methodname>, <methodname>set_vexpand()</methodname>, <methodname>set_halign()</methodname> and <methodname>set_valign()</methodname> while reading the <link linkend=\"sec-boxes\">Boxes</link> section."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:2049
msgid "Boxes"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2051
msgid "Most packing uses boxes as in the above example. These are invisible containers into which we can pack our widgets. When packing widgets into a horizontal box, the objects are inserted horizontally from left to right. In a vertical box, widgets are packed from top to bottom. You may use any combination of boxes inside or beside other boxes to create the desired effect."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:2061
msgid "Adding widgets"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:2063
msgid "Per-child packing options"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2064
msgid "The <methodname>append()</methodname> method places widgets inside these containers. It will start at the top and work its way down in a <classname>Box</classname> with vertical orientation, or pack left to right in a <classname>Box</classname> with horizontal orientation. If it's inconvenient to add widgets in this order, use <methodname>insert_child_after()</methodname> or <methodname>insert_child_at_start()</methodname>. We will use <methodname>append()</methodname> in our examples."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2074
msgid "There are several options governing how widgets are to be packed, and this can be confusing at first. You can modify the packing by using <methodname>set_expand()</methodname>, <methodname>set_hexpand()</methodname>, <methodname>set_vexpand()</methodname>, <methodname>set_halign()</methodname>, <methodname>set_valign()</methodname> and/or <methodname>set_margin()</methodname> on the child widgets. If you have difficulties, then it is sometimes a good idea to play with the <application>Cambalache</application> GUI designer to see what is possible. You can then use the <classname>Gtk::Builder</classname> API to load your GUI at runtime."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2085
msgid "There are basically five different styles, as shown in this picture:"
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:2091
msgid "Box Packing 1"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:2093
msgctxt "_"
msgid "external ref='figures/box_packing1.png' md5='dedb723a5ca690ed542d09361fc8ad4a'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2097
msgid "Each line contains one horizontal <classname>Box</classname> with several buttons. Each of the buttons on a line is packed into the <classname>Box</classname> with the same arguments to the <methodname>set_hexpand()</methodname>, <methodname>set_halign()</methodname>, <methodname>set_margin_start()</methodname> and <methodname>set_margin_end()</methodname> methods."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2106
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1Box.html\">Reference</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:2111
msgid "Per-container packing options"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2112
msgid "Here's the constructor for the <classname>Box</classname> widget, and methods that set per-container packing options:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:2115
#, no-wrap
msgid ""
"Gtk::Box(Gtk::Orientation orientation = Gtk::Orientation::HORIZONTAL, int spacing = 0);\n"
"void set_orientation(Gtk::Orientation orientation);\n"
"void set_spacing(int spacing);\n"
"void set_homogeneous(bool homogeneous = true);"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2119
msgid "Passing <literal>true</literal> to <methodname>set_homogeneous()</methodname> will cause all of the contained widgets to be the same size. <parameter>spacing</parameter> is a (minimum) number of pixels to leave between each widget."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2125
msgid "What's the difference between spacing (set when the box is created) and margins (set separately for each child widget)? Spacing is added between objects, and margins are added on one or more sides of a widget. The following figure should make it clearer. The shown margins are the left and right margins of each button in the row."
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:2134
msgid "Box Packing 2"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:2136
msgctxt "_"
msgid "external ref='figures/box_packing2.png' md5='48e64123d27cc8e66137c8a2edf9589f'"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:2144
msgid "Gtk::Application and command-line options"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2146
msgid "The following example program requires a command-line option. The source code shows two ways of handling command-line options in combination with <classname>Gtk::Application</classname>."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:2152
msgid "Handle the options in <function>main()</function> and hide them from <classname>Gtk::Application</classname> by setting <literal>argc = 1</literal> in the call to <methodname>Gtk::Application::run()</methodname>."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:2158
msgid "Give all command-line options to <methodname>Gtk::Application::run()</methodname> and add the flag <literal>Gio::Application::Flags::HANDLES_COMMAND_LINE</literal> to <methodname>Gtk::Application::create()</methodname>. Connect a signal handler to the <literal>command_line</literal> signal, and handle the command-line options in the signal handler."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:2165
msgid "You must set the optional parameter <literal>after = false</literal> in the call to <literal>signal_command_line().connect()</literal>, because your signal handler must be called before the default signal handler. You must also call <methodname>Gio::Application::activate()</methodname> in the signal handler, unless you want your application to exit without showing its main window. (<classname>Gio::Application</classname> is a base class of <classname>Gtk::Application</classname>.)"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2179
msgid "Here is the source code for the example that produced the screenshots above. When you run this example, provide a number between 1 and 3 as a command-line option, to see different packing options in use."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2182
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/box\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#. (itstool) path: figure/title
#: C/index-in.docbook:2188
#: C/index-in.docbook:2218
msgid "Grid"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2190
msgid "A <classname>Grid</classname> dynamically lays out child widgets in rows and columns. The dimensions of the grid do not need to be specified in the constructor."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2195
msgid "Child widgets can span multiple rows or columns, using <methodname>attach()</methodname>, or added next to an existing widget inside the grid with <methodname>attach_next_to()</methodname>. Individual rows and columns of the grid can be set to have uniform height or width with <methodname>set_row_homogeneous()</methodname> and <methodname>set_column_homogeneous()</methodname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2202
msgid "You can set the <emphasis>margin</emphasis> and <emphasis>expand</emphasis> properties of the child <classname>Widget</classname>s to control their spacing and their behavior when the Grid is resized."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2206
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1Grid.html\">Reference</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2210
msgid "This example creates a window with three buttons in a grid. The first two buttons are in the upper row, from left to right. A third button is attached underneath the first button, in a new lower row, spanning two columns."
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:2220
msgctxt "_"
msgid "external ref='figures/grid.png' md5='18031e926d6082207f18de1b08cd85ae'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2224
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/grid\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#. (itstool) path: figure/title
#: C/index-in.docbook:2230
#: C/index-in.docbook:2266
msgid "Notebook"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2232
msgid "A <classname>Notebook</classname> has a set of stacked <literal>pages</literal>, each of which contains widgets. Labelled <literal>tabs</literal> allow the user to select the pages. <classname>Notebook</classname>s allow several sets of widgets to be placed in a small space, by only showing one page at a time. For instance, they are often used in preferences dialogs."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2241
msgid "Use the <methodname>append_page()</methodname>, <methodname>prepend_page()</methodname> and <methodname>insert_page()</methodname> methods to add tabbed pages to the <literal>Notebook</literal>, supplying the child widget and the name for the tab."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2248
msgid "To discover the currently visible page, use the <methodname>get_current_page()</methodname> method. This returns the page number, and then calling <methodname>get_nth_page()</methodname> with that number will give you a pointer to the actual child widget."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2255
msgid "To programmatically change the selected page, use the <methodname>set_current_page()</methodname> method."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2260
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1Notebook.html\">Reference</link>"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:2268
msgctxt "_"
msgid "external ref='figures/notebook.png' md5='b46c25388d4c250b0ab737f71f82d81b'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2272
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/notebook/\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#. (itstool) path: figure/title
#: C/index-in.docbook:2279
#: C/index-in.docbook:2313
msgid "Assistant"
msgstr ""

#. (itstool) path: note/para
#: C/index-in.docbook:2281
msgid "<classname>Gtk::Assistant</classname> is deprecated since <application>gtkmm</application> 4.10. There is no replacement in <application>gtkmm</application>. libadwaita (a C library) has replacement parts (like AdwCarousel). In some cases, a <classname>Gtk::Notebook</classname> might be an acceptable replacement."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2287
msgid "An <classname>Assistant</classname> splits a complex operation into steps. Each step is a page, containing a header, a child widget and an action area. The Assistant's action area has navigation buttons which update automatically depending on the type of the page, set with <methodname>set_page_type()</methodname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2291
msgid "Use the <methodname>append_page()</methodname>, <methodname>prepend_page</methodname> and <methodname>insert_page()</methodname> methods to add pages to the <classname>Assistant</classname>, supplying the child widget for each page."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2295
msgid "To determine the currently-visible page, use the <methodname>get_current_page()</methodname> method, and pass the result to <methodname>get_nth_page()</methodname>, which returns a pointer to the actual widget. To programmatically change the current page, use the <methodname>set_current_page()</methodname> method."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2299
msgid "To set the title of a page, use the <methodname>set_page_title()</methodname> method."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2303
msgid "To add widgets to the action area, use the <methodname>add_action_widget()</methodname> method. They will be packed alongside the default buttons. Use the <methodname>remove_action_widget()</methodname> method to remove widgets."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2307
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1Assistant.html\">Reference</link>"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:2315
msgctxt "_"
msgid "external ref='figures/assistant.png' md5='14f588bf7a1dde5e329e5478efe3ae3f'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2319
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/assistant/\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:2326
msgid "Other Multi-item Containers"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2328
msgid "There are other multi-item containers. See the reference documentation for a complete list. Here are links to some example programs that show containers, which are not mentioned elsewhere in this tutorial."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2334
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/actionbar\">Source Code, ActionBar</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2335
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/listbox_flowbox/flowbox\">Source Code, FlowBox</link>"
msgstr ""

#. (itstool) path: chapter/title
#: C/index-in.docbook:2342
msgid "ListView, GridView, ColumnView"
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:2344
msgid "Lists are intended to be used whenever developers want to display many objects in roughly the same way. They are perfectly fine to be used for very short lists of only 2 or 3 items, but generally scale fine to thousands of items."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:2350
msgid "Lists are meant to be used with changing data, both with the items themselves changing as well as the list adding and removing items. Of course, they work just as well with static data."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:2356
msgid "The <link xlink:href=\"https://docs.gtk.org/gtk4/section-list-widget.html\">List Widget Overview</link> chapter in the GTK documentation contains more information about list widgets."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:2361
msgid "Some examples are shown in this chapter. There are more examples in the <link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/listmodelviews/\">listmodelviews directory</link> in <application>gtkmm-documentation</application>'s examples."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:2367
msgid "The Data Model"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2369
msgid "The data model is a class that implements the <classname>Gio::ListModel</classname> interface. Examples of such classes are <classname>Gio::ListStore</classname> (not to be confused with the deprecated <classname>Gtk::ListStore</classname>), <classname>Gtk:StringList</classname>, <classname>Gtk:DirectoryList</classname> and <classname>Pango::FontMap</classname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2377
msgid "The elements in a model are called <emphasis>items</emphasis>. All items are instances of a subclass of <classname>Glib::Object</classname>. For instance, you might have a <classname>ColumnView</classname> with one integer and one text column, like so:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:2383
#: C/index-in.docbook:3385
#, no-wrap
msgid ""
"class ModelColumns : public Glib::Object\n"
"{\n"
"public:\n"
"  int m_col_id;\n"
"  Glib::ustring m_col_name;\n"
"\n"
"  static Glib::RefPtr&lt;ModelColumns&gt; create(\n"
"    int col_id, const Glib::ustring&amp; col_name)\n"
"  {\n"
"    return Glib::make_refptr_for_instance&lt;ModelColumns&gt;(\n"
"      new ModelColumns(col_id, col_name));\n"
"  }\n"
"\n"
"protected:\n"
"  ModelColumns(int col_id, const Glib::ustring&amp; col_name)\n"
"  : m_col_id(col_id), m_col_name(col_name)\n"
"  {}\n"
"};\n"
"\n"
"Glib::RefPtr&lt;Gio::ListStore&lt;ModelColumns&gt;&gt; m_ListStore;\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2405
msgid "Every item in a model has a position which is the unsigned integer that describes where in the model the item is located. The first item in a model is at position 0. The position of an item can of course change as other items are added to or removed from the model."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2411
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/glibmm/classGio_1_1ListStore.html\">Gio::ListStore Reference</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2412
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1StringList.html\">StringList Reference</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2413
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1DirectoryList.html\">DirectoryList Reference</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:2417
msgid "The Selection Model"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2419
msgid "The selection model is a class that implements the <classname>Gtk::SelectionModel</classname> interface. You can choose between <classname>NoSelection</classname>, <classname>SingleSelection</classname> and <classname>MultiSelection</classname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2424
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1NoSelection.html\">NoSelection Reference</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2425
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1SingleSelection.html\">SingleSelection Reference</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2426
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1MultiSelection.html\">MultiSelection Reference</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:2430
msgid "The Factory"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2432
msgid "Data from the data model is added to the view by a factory, which is a subclass of <classname>ListItemFactory</classname>. There is only one such subclass in <application>gtkmm</application>, <classname>SignalListItemFactory</classname>. Data from the model is added to the view with signal handlers connected to a <classname>SignalListItemFactory</classname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2438
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1SignalListItemFactory.html\">SignalListItemFactory Reference</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:2442
#: C/index-in.docbook:2813
#: C/index-in.docbook:3866
msgid "The View"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2444
msgid "The View is the widget that displays the model data and allows the user to interact with it. The View can show all of the model's columns, or just some, and it can show them in various ways."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2450
msgid "An important requirement for views (especially views of long lists) is that they need to know which items are not visible so they can be recycled. Views achieve that by implementing the <classname>Scrollable</classname> interface and expecting to be placed directly into a <classname>ScrolledWindow</classname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2457
msgid "There are different view widgets to choose from."
msgstr ""

#. (itstool) path: section/title
#. (itstool) path: figure/title
#: C/index-in.docbook:2462
#: C/index-in.docbook:2474
msgid "ListView"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2464
msgid "The <classname>ListView</classname> shows a 1-dimensional list with one column."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2468
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1ListView.html\">Reference</link>"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:2476
msgctxt "_"
msgid "external ref='figures/listmodel_listview.png' md5='5e49d159f43fdc5242998713bdedafc8'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2480
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/listmodelviews/list_listview\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#. (itstool) path: figure/title
#: C/index-in.docbook:2486
#: C/index-in.docbook:2498
msgid "GridView"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2488
msgid "The <classname>GridView</classname> shows a 2-dimensional grid."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2492
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1GridView.html\">Reference</link>"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:2500
msgctxt "_"
msgid "external ref='figures/listmodel_gridview.png' md5='0d87e962deacc452f32513f0d5e07e04'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2504
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/listmodelviews/gridview\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#. (itstool) path: figure/title
#: C/index-in.docbook:2510
#: C/index-in.docbook:2522
msgid "ColumnView"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2512
msgid "The <classname>ColumnView</classname> shows a 1-dimensional list with one or more columns."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2516
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1ColumnView.html\">Reference</link>"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:2524
msgctxt "_"
msgid "external ref='figures/listmodel_columnview.png' md5='fd8445f1904773397a7252bf843e2c38'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2528
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/listmodelviews/list_columnview\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:2535
#: C/index-in.docbook:3133
msgid "Sorting"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2537
msgid "The list can be sorted by wrapping it in a <classname>SortListModel</classname>. There are two ways to do this."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:2542
msgid "In a <classname>ColumnView</classname>, get the <classname>ColumnViewSorter</classname> from the <classname>ColumnView</classname> and set it to the <classname>SortListModel</classname>. Set a <classname>Sorter</classname> to each <classname>ColumnViewColumn</classname>. Then the user of your app can sort the items by clicking on a column heading."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:2547
msgid "In any view, set a <classname>Sorter</classname> such as a <classname>StringSorter</classname> or a <classname>NumericSorter</classname> to the <classname>SortListModel</classname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2552
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1SortListModel.html\">SortListModel Reference</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2553
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1StringSorter.html\">StringSorter Reference</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2554
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1NumericSorter.html\">NumericSorter Reference</link>"
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:2560
msgid "SortListModel"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:2562
msgctxt "_"
msgid "external ref='figures/listmodel_sort.png' md5='9f6ee5fc4c2f03172fefc8027d97063e'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2566
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/listmodelviews/sort\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:2572
msgid "Filtering"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2574
msgid "The list can be filtered by wrapping it in a <classname>FilterListModel</classname>. Set a <classname>Filter</classname> such as a <classname>StringFilter</classname> or a <classname>BoolFilter</classname> to the <classname>FilterListModel</classname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2580
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1FilterListModel.html\">FilterListModel Reference</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2581
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1StringFilter.html\">StringFilter Reference</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2582
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1BoolFilter.html\">BoolFilter Reference</link>"
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:2588
msgid "FilterListModel"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:2590
msgctxt "_"
msgid "external ref='figures/listmodel_filter.png' md5='b1407e88c99b90c2ad7698ce30a46a1e'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2594
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/listmodelviews/filter\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:2600
msgid "Displaying Trees"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2602
msgid "While the deprecated <classname>TreeView</classname> provided built-in support for trees, the list widgets, and in particular <classname>Gio::ListModel</classname>, do not. However, <application>gtkmm</application> provides functionality to make trees look and behave like lists for the people who still want to display lists. This is achieved by using the <classname>TreeListModel</classname> to flatten a tree into a list. The <classname>TreeExpander</classname> widget can then be used inside a listitem to allow users to expand and collapse rows."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2612
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1TreeListModel.html\">TreeListModel Reference</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2613
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1TreeExpander.html\">TreeExpander Reference</link>"
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:2619
msgid "TreeListModel"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:2621
msgctxt "_"
msgid "external ref='figures/listmodel_tree.png' md5='656307ee78c8fd9ac379f2a0d01b8a81'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2625
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/listmodelviews/tree_columnview\">Source Code</link>"
msgstr ""

#. (itstool) path: chapter/title
#: C/index-in.docbook:2633
msgid "The TreeView widget"
msgstr ""

#. (itstool) path: note/para
#: C/index-in.docbook:2635
msgid "<classname>Gtk::TreeView</classname> is deprecated since <application>gtkmm</application> 4.10. In new code, use <classname>Gtk::ListView</classname> for lists and <classname>Gtk::ColumnView</classname> for tabular lists."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:2640
msgid "The <classname>Gtk::TreeView</classname> widget can contain lists or trees of data, in columns."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:2646
msgid "The Model"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2648
msgid "Each <classname>Gtk::TreeView</classname> has an associated <classname>Gtk::TreeModel</classname>, which contains the data displayed by the <classname>TreeView</classname>. Each <classname>Gtk::TreeModel</classname> can be used by more than one <classname>Gtk::TreeView</classname>. For instance, this allows the same underlying data to be displayed and edited in 2 different ways at the same time. Or the 2 Views might display different columns from the same Model data, in the same way that 2 SQL queries (or \"views\") might show different fields from the same database table."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2658
msgid "Although you can theoretically implement your own Model, you will normally use either the <classname>ListStore</classname> or <classname>TreeStore</classname> model classes."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2664
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1TreeModel.html\">Reference</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:2667
msgid "ListStore, for rows"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2669
msgid "The <classname>ListStore</classname> contains simple rows of data, and each row has no children."
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:2675
#: C/index-in.docbook:3256
msgid "TreeView - ListStore"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:2677
#: C/index-in.docbook:3258
msgctxt "_"
msgid "external ref='figures/treeview_list.png' md5='60e5e4ecb284d0cdc53373fe0ec858ee'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2681
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1ListStore.html\">Reference</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:2686
msgid "TreeStore, for a hierarchy"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2688
msgid "The <classname>TreeStore</classname> contains rows of data, and each row may have child rows."
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:2694
#: C/index-in.docbook:3276
msgid "TreeView - TreeStore"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:2696
#: C/index-in.docbook:3278
msgctxt "_"
msgid "external ref='figures/treeview_tree.png' md5='2270025659b23ebfc0e38d8b629289ef'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2700
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1TreeStore.html\">Reference</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:2705
msgid "Model Columns"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2707
msgid "The <classname>TreeModelColumnRecord</classname> class is used to keep track of the columns and their data types. You add <classname>TreeModelColumn</classname> instances to the <classname>ColumnRecord</classname> and then use those <classname>TreeModelColumn</classname>s when getting and setting the data in model rows. You will probably find it convenient to derive a new <classname>TreeModelColumnRecord</classname> which has your <classname>TreeModelColumn</classname> instances as member data."
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:2718
#, no-wrap
msgid ""
"class ModelColumns : public Gtk::TreeModelColumnRecord\n"
"{\n"
"public:\n"
"\n"
"  ModelColumns()\n"
"    { add(m_col_text); add(m_col_number); }\n"
"\n"
"  Gtk::TreeModelColumn&lt;Glib::ustring&gt; m_col_text;\n"
"  Gtk::TreeModelColumn&lt;int&gt; m_col_number;\n"
"};\n"
"\n"
"ModelColumns m_Columns;"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2731
msgid "You specify the <classname>ColumnRecord</classname> when creating the Model, like so:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:2735
#, no-wrap
msgid ""
"Glib::RefPtr&lt;Gtk::ListStore&gt; refListStore =\n"
"    Gtk::ListStore::create(m_Columns);"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2737
msgid "As a <classname>TreeModelColumnRecord</classname> describes structure, not data, it can be shared among multiple models, and this is preferable for efficiency. However, the instance (such as <varname>m_Columns</varname> here) should usually not be static, because it often needs to be instantiated after <application>glibmm</application> has been initialized. The best solution is to make it a lazily instantiated singleton, so that it will be constructed on-demand, whenever the first model accesses it."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:2749
msgid "Adding Rows"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2751
msgid "Add rows to the model with the <methodname>append()</methodname>, <methodname>prepend()</methodname>, or <methodname>insert()</methodname> methods."
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:2755
#, no-wrap
msgid ""
"auto iter = m_refListStore-&gt;append();"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2756
msgid "You can dereference the iterator to get the Row:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:2758
#, no-wrap
msgid ""
"auto row = *iter;"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:2760
msgid "Adding child rows"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2761
msgid "<classname>Gtk::TreeStore</classname> models can have child items. Add them with the <methodname>append()</methodname>, <methodname>prepend()</methodname>, or <methodname>insert()</methodname> methods, like so:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:2766
#, no-wrap
msgid ""
"auto iter_child =\n"
"    m_refTreeStore-&gt;append(row.children());"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:2773
msgid "Setting values"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2775
msgid "You can use the <methodname>operator[]</methodname> overload to set the data for a particular column in the row, specifying the <classname>TreeModelColumn</classname> used to create the model."
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:2780
#, no-wrap
msgid ""
"row[m_Columns.m_col_text] = \"sometext\";"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:2784
msgid "Getting values"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2786
msgid "You can use the <methodname>operator[]</methodname> overload to get the data in a particular column in a row, specifying the <classname>TreeModelColumn</classname> used to create the model."
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:2791
#, no-wrap
msgid ""
"auto strText = row[m_Columns.m_col_text];\n"
"auto number = row[m_Columns.m_col_number];"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2793
msgid "The compiler will complain if you use an inappropriate type. For instance, this would generate a compiler error:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:2797
#, no-wrap
msgid ""
"//compiler error - no conversion from ustring to int.\n"
"int number = row[m_Columns.m_col_text];"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:2802
msgid "\"Hidden\" Columns"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2804
msgid "You might want to associate extra data with each row. If so, just add it as a Model column, but don't add it to the View."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2815
msgid "The View is the actual widget (<classname>Gtk::TreeView</classname>) that displays the model (<classname>Gtk::TreeModel</classname>) data and allows the user to interact with it. The View can show all of the model's columns, or just some, and it can show them in various ways."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2822
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1TreeView.html\">Reference</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:2825
msgid "Using a Model"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2827
msgid "You can specify a <classname>Gtk::TreeModel</classname> when constructing the <classname>Gtk::TreeView</classname>, or you can use the <methodname>set_model()</methodname> method, like so:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:2832
#, no-wrap
msgid ""
"m_TreeView.set_model(m_refListStore);"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:2836
msgid "Adding View Columns"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2838
msgid "You can use the <methodname>append_column()</methodname> method to tell the View that it should display certain Model columns, in a certain order, with a certain column title."
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:2843
#, no-wrap
msgid ""
"m_TreeView.append_column(\"Messages\", m_Columns.m_col_text);"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2844
msgid "When using this simple <methodname>append_column()</methodname> overload, the <classname>TreeView</classname> will display the model data with an appropriate <classname>CellRenderer</classname>. For instance, strings and numbers are shown in a simple <classname>Gtk::Entry</classname> widget, and booleans are shown in a <classname>Gtk::CheckButton</classname>. This is usually what you need. For other column types you must either connect a callback that converts your type into a string representation, with <methodname>TreeViewColumn::set_cell_data_func()</methodname>, or derive a custom <classname>CellRenderer</classname>. Note that (unsigned) short is not supported by default - You could use (unsigned) int or (unsigned) long as the column type instead."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:2860
msgid "More than one Model Column per View Column"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2862
msgid "To render more than one model column in a view column, you need to create the <classname>TreeView::Column</classname> widget manually, and use <methodname>pack_start()</methodname> to add the model columns to it."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2868
msgid "Then use <methodname>append_column()</methodname> to add the view Column to the View. Notice that <methodname>Gtk::TreeView::append_column()</methodname> is overloaded to accept either a prebuilt <classname>Gtk::TreeView::Column</classname> widget, or just the <classname>TreeModelColumn</classname> from which it generates an appropriate <classname>Gtk::TreeView::Column</classname> widget."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2875
msgid "Here is some example code, which has a pixbuf icon and a text name in the same column:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:2878
#, no-wrap
msgid ""
"\n"
"auto pColumn = Gtk::make_managed&lt;Gtk::TreeView::Column&gt;(\"Icon Name\");\n"
"\n"
"// m_columns.icon and m_columns.iconname are columns in the model.\n"
"// pColumn is the column in the TreeView:\n"
"pColumn-&gt;pack_start(m_columns.icon, /* expand= */ false);\n"
"pColumn-&gt;pack_start(m_columns.iconname);\n"
"\n"
"m_TreeView.append_column(*pColumn);"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:2890
msgid "Specifying CellRenderer details"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2892
msgid "The default <classname>CellRenderer</classname>s and their default behavior will normally suffice, but you might occasionally need finer control. For instance, this example code from <filename>gtkmm/demos/gtk-demo/example_treeview_treestore.cc</filename>, appends a <classname>Gtk::CellRenderer</classname> widget and instructs it to render the data from various model columns through various aspects of its appearance."
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:2900
#, no-wrap
msgid ""
"auto cols_count = m_TreeView.append_column_editable(\"Alex\", m_columns.alex);\n"
"auto pColumn = m_TreeView.get_column(cols_count-1);\n"
"if(pColumn)\n"
"{\n"
"  auto pRenderer = static_cast&lt;Gtk::CellRendererToggle*&gt;(pColumn-&gt;get_first_cell());\n"
"  pColumn-&gt;add_attribute(pRenderer-&gt;property_visible(), m_columns.visible);\n"
"  pColumn-&gt;add_attribute(pRenderer-&gt;property_activatable(), m_columns.world);"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2908
msgid "You can also connect to <classname>CellRenderer</classname> signals to detect user actions. For instance:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:2912
#, no-wrap
msgid ""
"\n"
"auto pRenderer = Gtk::make_managed&lt;Gtk::CellRendererToggle&gt;();\n"
"pRenderer-&gt;signal_toggled().connect(\n"
"    sigc::bind( sigc::mem_fun(*this,\n"
"        &amp;Example_TreeView_TreeStore::on_cell_toggled), m_columns.dave)\n"
");"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:2921
#: C/index-in.docbook:3287
msgid "Editable Cells"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:2924
msgid "Automatically-stored editable cells."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2926
msgid "Cells in a <classname>TreeView</classname> can be edited in-place by the user. To allow this, use the <classname>Gtk::TreeView</classname> <methodname>insert_column_editable()</methodname> and <methodname>append_column_editable()</methodname> methods instead of <methodname>insert_column()</methodname> and <methodname>append_column()</methodname>. When these cells are edited the new values will be stored immediately in the Model. Note that these methods are templates which can only be instantiated for simple column types such as <classname>Glib::ustring</classname>, int, and long."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:2940
msgid "Implementing custom logic for editable cells."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2942
msgid "However, you might not want the new values to be stored immediately. For instance, maybe you want to restrict the input to certain characters or ranges of values."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2947
msgid "To achieve this, you should use the normal <classname>Gtk::TreeView</classname> <methodname>insert_column()</methodname> and <methodname>append_column()</methodname> methods, then use <methodname>get_column_cell_renderer()</methodname> to get the <classname>Gtk::CellRenderer</classname> used by that column."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2953
msgid "You should then cast that <classname>Gtk::CellRenderer*</classname> to the specific <classname>CellRenderer</classname> that you expect, so you can use specific API."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2957
msgid "For instance, for a CellRendererText, you would set the cell's <emphasis>editable</emphasis> property to true, like so:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:2960
#, no-wrap
msgid ""
"cell-&gt;property_editable() = true;"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2961
msgid "For a CellRendererToggle, you would set the <emphasis>activatable</emphasis> property instead."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2965
msgid "You can then connect to the appropriate \"edited\" signal. For instance, connect to <methodname>Gtk::CellRendererText::signal_edited()</methodname>, or <methodname>Gtk::CellRendererToggle::signal_toggled()</methodname>. If the column contains more than one <classname>CellRenderer</classname> then you will need to use <methodname>Gtk::TreeView::get_column()</methodname> and then call <methodname>get_cells()</methodname> on that view Column."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2973
msgid "In your signal handler, you should examine the new value and then store it in the Model if that is appropriate for your application."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:2982
msgid "Iterating over Model Rows"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2984
msgid "<classname>Gtk::TreeModel</classname> provides a C++ Standard Library-style container of its children, via the <methodname>children()</methodname> method. You can use the familiar <methodname>begin()</methodname> and <methodname>end()</methodname> methods iterator incrementing, like so:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:2990
#, no-wrap
msgid ""
"\n"
"auto children = refModel-&gt;children();\n"
"for (auto iter = children.begin(), end = children.end(); iter != end; ++iter)\n"
"{\n"
"  auto row = *iter;\n"
"  //Do something with the row - see above for set/get.\n"
"}"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:2997
msgid "If you always want to iterate across the entire range, much more succinct syntax is possible using C++'s range-based <literal>for</literal> loop:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:3001
#, no-wrap
msgid ""
"\n"
"for (auto row: refModel-&gt;children())\n"
"{\n"
"  //Do something with the row - see above for set/get.\n"
"}"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:3008
msgid "Row children"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3010
msgid "When using a <classname>Gtk::TreeStore</classname>, the rows can have child rows, which can have their own children in turn. Use <methodname>Gtk::TreeModel::Row::children()</methodname> to get the container of child <classname>Row</classname>s:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:3015
#, no-wrap
msgid ""
"Gtk::TreeModel::Children children = row.children();"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:3021
msgid "The Selection"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3023
msgid "To find out what rows the user has selected, get the <classname>Gtk::TreeView::Selection</classname> object from the <classname>TreeView</classname>, like so:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:3028
#, no-wrap
msgid ""
"auto refTreeSelection = m_TreeView.get_selection();"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:3031
msgid "Single or multiple selection"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3033
msgid "By default, only single rows can be selected, but you can allow multiple selection by setting the mode, like so:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:3037
#, no-wrap
msgid ""
"refTreeSelection-&gt;set_mode(Gtk::SelectionMode::MULTIPLE);"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:3041
msgid "The selected rows"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3043
msgid "For single-selection, you can just call <methodname>get_selected()</methodname>, like so:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:3047
#, no-wrap
msgid ""
"auto iter = refTreeSelection-&gt;get_selected();\n"
"if(iter) //If anything is selected\n"
"{\n"
"  auto row = *iter;\n"
"  //Do something with the row.\n"
"}"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3054
msgid "For multiple-selection, you need to call <methodname>get_selected_rows()</methodname> or define a callback, and give it to <methodname>selected_foreach()</methodname>, <methodname>selected_foreach_path()</methodname>, or <methodname>selected_foreach_iter()</methodname>, like so:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:3061
#, no-wrap
msgid ""
"refTreeSelection-&gt;selected_foreach_iter(\n"
"    sigc::mem_fun(*this, &amp;TheClass::selected_row_callback) );\n"
"\n"
"void TheClass::selected_row_callback(\n"
"    const Gtk::TreeModel::const_iterator&amp; iter)\n"
"{\n"
"  auto row = *iter;\n"
"  //Do something with the row.\n"
"}"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:3074
msgid "The \"changed\" signal"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3076
msgid "To respond to the user clicking on a row or range of rows, connect to the signal like so:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:3080
#, no-wrap
msgid ""
"refTreeSelection-&gt;signal_changed().connect(\n"
"    sigc::mem_fun(*this, &amp;Example_IconTheme::on_selection_changed)\n"
");"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:3086
msgid "Preventing row selection"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3088
msgid "Maybe the user should not be able to select every item in your list or tree. For instance, in the gtk-demo, you can select a demo to see the source code, but it doesn't make any sense to select a demo category."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3093
msgid "To control which rows can be selected, use the <methodname>set_select_function()</methodname> method, providing a <classname>sigc::slot</classname> callback. For instance:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:3098
#, no-wrap
msgid ""
"m_refTreeSelection-&gt;set_select_function( sigc::mem_fun(*this,\n"
"    &amp;DemoWindow::select_function) );"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3100
msgid "and then"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:3103
#, no-wrap
msgid ""
"bool DemoWindow::select_function(\n"
"    const Glib::RefPtr&lt;Gtk::TreeModel&gt;&amp; model,\n"
"    const Gtk::TreeModel::Path&amp; path, bool)\n"
"{\n"
"  const auto iter = model-&gt;get_iter(path);\n"
"  return iter-&gt;children().empty(); // only allow leaf nodes to be selected\n"
"}"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:3113
msgid "Changing the selection"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3115
msgid "To change the selection, specify a <classname>Gtk::TreeModel::iterator</classname> or <classname>Gtk::TreeModel::Row</classname>, like so:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:3120
#, no-wrap
msgid ""
"auto row = m_refModel-&gt;children()[5]; //The sixth row.\n"
"if(row)\n"
"  refTreeSelection-&gt;select(row.get_iter());"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3123
msgid "or"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:3126
#, no-wrap
msgid ""
"auto iter = m_refModel-&gt;children().begin()\n"
"if(iter)\n"
"  refTreeSelection-&gt;select(iter);"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3135
msgid "The standard tree models (<classname>TreeStore</classname> and <classname>ListStore</classname>) derive from <classname>TreeSortable</classname>, so they offer sorting functionality. For instance, call <methodname>set_sort_column()</methodname>, to sort the model by the specified column. Or supply a callback function to <methodname>set_sort_func()</methodname> to implement a more complicated sorting algorithm."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3139
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1TreeSortable.html\">TreeSortable Reference</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:3142
msgid "Sorting by clicking on columns"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3144
msgid "So that a user can click on a <classname>TreeView</classname>'s column header to sort the <classname>TreeView</classname>'s contents, call <methodname>Gtk::TreeView::Column::set_sort_column()</methodname>, supplying the model column on which model should be sorted when the header is clicked. For instance:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:3147
#, no-wrap
msgid ""
"auto pColumn = treeview.get_column(0);\n"
"if(pColumn)\n"
"  pColumn-&gt;set_sort_column(m_columns.m_col_id);"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:3153
msgid "Independently sorted views of the same model"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3155
msgid "The <classname>TreeView</classname> already allows you to show the same <classname>TreeModel</classname> in two <classname>TreeView</classname> widgets. If you need one of these TreeViews to sort the model differently than the other then you should use a <classname>TreeModelSort</classname> instead of just, for instance, <methodname>Gtk::TreeViewColumn::set_sort_column()</methodname>. <classname>TreeModelSort</classname> is a model that contains another model, presenting a sorted version of that model. For instance, you might add a sorted version of a model to a <classname>TreeView</classname> like so:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:3163
#, no-wrap
msgid ""
"auto sorted_model = Gtk::TreeModelSort::create(model);\n"
"sorted_model-&gt;set_sort_column(columns.m_col_name, Gtk::SortType::ASCENDING);\n"
"treeview.set_model(sorted_model);"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3167
msgid "Note, however, that the TreeView will provide iterators to the sorted model. You must convert them to iterators to the underlying child model in order to perform actions on that model. For instance:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:3169
#, no-wrap
msgid ""
"void ExampleWindow::on_button_delete()\n"
"{\n"
"  auto refTreeSelection = m_treeview.get_selection();\n"
"  if(refTreeSelection)\n"
"  {\n"
"    auto sorted_iter = m_refTreeSelection-&gt;get_selected();\n"
"    if(sorted_iter)\n"
"    {\n"
"      auto iter = m_refModelSort-&gt;convert_iter_to_child_iter(sorted_iter);\n"
"      m_refModel-&gt;erase(iter);\n"
"    }\n"
"  }\n"
"}"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3183
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1TreeModelSort.html\">TreeModelSort Reference</link>"
msgstr ""

#. (itstool) path: section/title
#. (itstool) path: chapter/title
#. (itstool) path: figure/title
#: C/index-in.docbook:3189
#: C/index-in.docbook:3307
#: C/index-in.docbook:5283
#: C/index-in.docbook:5441
msgid "Drag and Drop"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3191
msgid "<classname>Gtk::TreeView</classname> already implements simple drag-and-drop when used with the <classname>Gtk::ListStore</classname> or <classname>Gtk::TreeStore</classname> models (since gtk 4.8). If necessary, it also allows you to implement more complex behavior when items are dragged and dropped, using the normal <link linkend=\"chapter-draganddrop\">Drag and Drop</link> API."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:3200
msgid "Reorderable rows"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3202
msgid "If you call <methodname>Gtk::TreeView::set_reorderable()</methodname> then your TreeView's items can be moved within the treeview itself. This is demonstrated in the <classname>TreeStore</classname> example."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3207
msgid "However, this does not allow you any control of which items can be dragged, and where they can be dropped. If you need that extra control then you might create a derived <literal>Gtk::TreeModel</literal> from <literal>Gtk::TreeStore</literal> or <literal>Gtk::ListStore</literal> and override the <literal>Gtk::TreeDragSource::row_draggable_vfunc()</literal> and <literal>Gtk::TreeDragDest::row_drop_possible_vfunc()</literal> virtual methods. You can examine the <literal>Gtk::TreeModel::Path</literal>s provided and allow or disallow dragging or dropping by returning <literal>true</literal> or <literal>false</literal>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3214
msgid "This is demonstrated in the drag_and_drop example."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:3220
#: C/index-in.docbook:3330
msgid "Popup Context Menu"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3222
msgid "Lots of people need to implement right-click context menus for <classname>TreeView</classname>s so we will explain how to do that here to save you some time. It's much the same as a normal context menu, as described in the <link linkend=\"sec-menus-popup\">menus chapter</link>. You use a <classname>Gtk::GestureClick</classname> to detect the mouse click."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3229
msgid "This is demonstrated in the Popup Context Menu example. In that example a derived <classname>TreeView</classname> is used, but that's not necessary."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:3236
#: C/index-in.docbook:3937
#: C/index-in.docbook:4235
#: C/index-in.docbook:5557
#: C/index-in.docbook:5956
msgid "Examples"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3238
msgid "Some <classname>TreeView</classname> examples are shown here. There are more examples in the <link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/treeview/\">treeview directory</link> in <application>gtkmm-documentation</application>'s examples."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3242
msgid "If neither <classname>ListStore</classname> nor <classname>TreeStore</classname> is suitable for your application, look at the <link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/treeview/custom_treemodel\">custom TreeModel</link> example. It shows how you can make your own implementation of the <classname>TreeModel</classname> interface."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:3249
msgid "ListStore"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3250
msgid "This example has a <classname>Gtk::TreeView</classname> widget, with a <classname>Gtk::ListStore</classname> model."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3262
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/treeview/list/\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:3267
msgid "TreeStore"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3269
msgid "This example is very similar to the <classname>ListStore</classname> example, but uses a <classname>Gtk::TreeStore</classname> model instead, and adds children to the rows."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3282
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/treeview/tree/\">Source Code</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3289
msgid "This example is identical to the <classname>ListStore</classname> example, but it uses <methodname>TreeView::append_column_editable()</methodname> instead of <methodname>TreeView::append_column()</methodname>."
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:3296
msgid "TreeView - Editable Cells"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:3298
msgctxt "_"
msgid "external ref='figures/treeview_editablecells.png' md5='b4c81c776d192afdc3685fd4a8ef178c'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3302
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/treeview/editable_cells/\">Source Code</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3309
msgid "This example is much like the <classname>TreeStore</classname> example, but has 2 extra columns to indicate whether the row can be dragged, and whether it can receive drag-and-dropped rows. It uses a derived <classname>Gtk::TreeStore</classname> which overrides the virtual functions as described in the <link linkend=\"sec-treeview-draganddrop\">TreeView Drag and Drop</link> section."
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:3319
msgid "TreeView - Drag And Drop"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:3321
msgctxt "_"
msgid "external ref='figures/treeview_draganddrop.png' md5='fb5de06eb865e9bd312f0b020e8f631d'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3325
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/treeview/drag_and_drop/\">Source Code</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3332
msgid "This example is much like the <classname>ListStore</classname> example, but derives a custom <classname>TreeView</classname> to encapsulate the tree model code and popup menu code in our derived class. See the <link linkend=\"sec-treeview-contextmenu\">TreeView Popup Context Menu</link> section."
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:3340
msgid "TreeView - Popup Context Menu"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:3342
msgctxt "_"
msgid "external ref='figures/treeview_popup.png' md5='29c7b04f9f865c6ae8214cbb1724b05f'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3346
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/treeview/popup/\">Source Code</link>"
msgstr ""

#. (itstool) path: chapter/title
#: C/index-in.docbook:3353
msgid "The DropDown Widget"
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:3355
msgid "The <classname>DropDown</classname> widget is an alternative to the deprecated <classname>ComboBox</classname>. It uses list models instead of tree models, and the content is displayed using widgets instead of cell renderers."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:3360
msgid "The <classname>DropDown</classname> widget offers a list of choices in a dropdown menu. If appropriate, it can show extra information about each item, such as text, a picture, or a check button. The <classname>DropDown</classname> widget can optionally have an <classname>Entry</classname> in the dropdown menu, allowing the user to search in a long list."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:3367
msgid "The list is provided via a <classname>Gio::ListModel</classname>, and data from this model is added to the <classname>DropDown</classname>'s view with signal handlers connected to a <classname>SignalListItemFactory</classname>. This provides flexibility, but the <classname>StringList</classname> class provides a simpler text-based specialization in case that flexibility is not required."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:3374
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1DropDown.html\">Reference</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:3377
#: C/index-in.docbook:3552
msgid "The model"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3379
msgid "The model for a <classname>DropDown</classname> can be defined and filled exactly as for a <classname>ListView</classname> or a <classname>ColumnView</classname>. It must be a subclass of <classname>Glib::Object</classname>. For instance, you might have a <classname>DropDown</classname> with one integer and one text column, like so:"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3407
msgid "After appending rows to this model, you should provide the model to the <classname>DropDown</classname> with the <methodname>set_model()</methodname> method. Unless you use the <classname>StringList</classname> model, you also need to set a <classname>ListItemFactory</classname> with <methodname>set_factory()</methodname>. If you want the items in the dropdown menu to look different from the item in the <classname>DropDown</classname> widget, you also need to set a separate <classname>ListItemFactory</classname> with <methodname>set_list_factory()</methodname>."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:3418
msgid "The selected item"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3420
msgid "To discover what item, if any, the user has selected from the <classname>DropDown</classname>, call <methodname>DropDown::get_selected()</methodname>. This returns an <type>unsigned int</type> that you can use to get the selected data from the model. For instance, you might read an integer ID value from the model, even though you have chosen only to show the human-readable description in the <classname>DropDown</classname>. For instance:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:3427
#, no-wrap
msgid ""
"unsigned int sel = m_DropDown.get_selected();\n"
"if (sel != GTK_INVALID_LIST_POSITION)\n"
"{\n"
"  // Get the data for the selected row, using our knowledge of the list model:\n"
"  auto id = m_ListStore-&gt;get_item(sel).m_col_id;\n"
"  set_some_id_chosen(id); // Your own function.\n"
"}\n"
"else\n"
"  set_nothing_chosen(); // Your own function.\n"
""
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:3440
#: C/index-in.docbook:3591
#: C/index-in.docbook:3652
msgid "Responding to changes"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3442
msgid "You might need to react to every change of selection in the <classname>DropDown</classname>, for instance to update other widgets. To do so, you should connect to <methodname>property_selected().signal_changed()</methodname>. For instance:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:3446
#, no-wrap
msgid ""
"m_DropDown.property_selected().signal_changed().connect(\n"
"  sigc::mem_fun(*this, &amp;ExampleWindow::on_dropdown_changed));\n"
""
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:3452
msgid "Simple String Example"
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:3455
msgid "Simple DropDown"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:3457
msgctxt "_"
msgid "external ref='figures/dropdown_string.png' md5='b1689605c645e1ada3040f6df3335c56'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3461
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/dropdown/string\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:3465
msgid "Examples with a Search Entry"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3467
msgid "The dropdown menu may contain an <classname>Entry</classname> that allows to search for items in the list. Call <methodname>set_enable_search()</methodname> and <methodname>set_expression()</methodname>. For instance:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:3471
#, no-wrap
msgid ""
"m_DropDown.set_enable_search(true);\n"
"auto expression = Gtk::ClosureExpression&lt;Glib::ustring&gt;::create(\n"
"  sigc::mem_fun(*this, &amp;ExampleWindow::get_col_name));\n"
"m_DropDown.set_expression(expression);\n"
"\n"
"//-------\n"
"Glib::ustring ExampleWindow::get_col_name(const Glib::RefPtr&lt;Glib::ObjectBase&gt;&amp; item)\n"
"{\n"
"  const auto col = std::dynamic_pointer_cast&lt;ModelColumns&gt;(item);\n"
"  return col ? col-&gt;m_col_name : \"\";\n"
"}\n"
""
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:3485
msgid "String Example"
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:3488
msgid "Search String"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:3490
msgctxt "_"
msgid "external ref='figures/dropdown_search_string.png' md5='e130e644e7cfb13a5b90ab1372b17503'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3494
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/dropdown/search_string\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:3498
msgid "Font Example"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3500
msgid "This example uses a <classname>Pango::FontMap</classname> as its model. This is possible because <classname>Pango::FontMap</classname> implements the <classname>Gio::ListModel</classname> interface. Of course you can use a <classname>FontDialogButton</classname> instead."
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:3507
#: C/index-in.docbook:3526
msgid "Search Font"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:3509
msgctxt "_"
msgid "external ref='figures/dropdown_search_font.png' md5='1733e29c88c19dc6c4cbd1114446ac18'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3513
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/dropdown/search_font\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:3518
msgid "Complex Example"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3520
msgid "This is a more complex example with two <classname>SignalListItemFactory</classname> objects and their signal handlers. This example would be simpler without the checkmark in the dropdown menu."
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:3528
msgctxt "_"
msgid "external ref='figures/dropdown_complex.png' md5='2167fb44e42653aa7fd855604c4c1e65'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3532
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/dropdown/complex\">Source Code</link>"
msgstr ""

#. (itstool) path: chapter/title
#: C/index-in.docbook:3537
msgid "Combo Boxes"
msgstr ""

#. (itstool) path: note/para
#: C/index-in.docbook:3539
msgid "<classname>Gtk::ComboBox</classname> and <classname>Gtk::ComboBoxText</classname> are deprecated since <application>gtkmm</application> 4.10. Use <classname>Gtk::DropDown</classname> in new code."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:3543
msgid "The <classname>ComboBox</classname> widget offers a list (or tree) of choices in a dropdown menu. If appropriate, it can show extra information about each item, such as text, a picture, a check button, or a progress bar. The <classname>ComboBox</classname> widget usually restricts the user to the available choices, but it can optionally have an <classname>Entry</classname>, allowing the user to enter arbitrary text if none of the available choices are suitable."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:3546
msgid "The list is provided via a <classname>TreeModel</classname>, and columns from this model are added to the ComboBox's view with the <methodname>ComboBox::pack_start()</methodname> method. This provides flexibility and compile-time type-safety, but the <classname>ComboBoxText</classname> class provides a simpler text-based specialization in case that flexibility is not required."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:3549
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1ComboBox.html\">Reference</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3554
msgid "The model for a ComboBox can be defined and filled exactly as for a <classname>TreeView</classname>. For instance, you might derive a ComboBox class with one integer and one text column, like so:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:3556
#, no-wrap
msgid ""
"class ModelColumns : public Gtk::TreeModel::ColumnRecord\n"
"{\n"
"public:\n"
"  ModelColumns()\n"
"  { add(m_col_id); add(m_col_name); }\n"
"\n"
"  Gtk::TreeModelColumn&lt;int&gt; m_col_id;\n"
"  Gtk::TreeModelColumn&lt;Glib::ustring&gt; m_col_name;\n"
"};\n"
"\n"
"ModelColumns m_columns;"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3568
msgid "After appending rows to this model, you should provide the model to the <classname>ComboBox</classname> with the <methodname>set_model()</methodname> method. Then use the <methodname>pack_start()</methodname> or <methodname>pack_end()</methodname> methods to specify what columns will be displayed in the ComboBox. As with the TreeView you may either use the default cell renderer by passing the <classname>TreeModelColumn</classname> to the pack methods, or you may instantiate a specific <classname>CellRenderer</classname> and specify a particular mapping with either <methodname>add_attribute()</methodname> or <methodname>set_cell_data_func()</methodname>. Note that these methods are in the <classname>CellLayout</classname> base class."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:3572
msgid "The chosen item"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3574
msgid "To discover what item, if any, the user has chosen from the ComboBox, call <methodname>ComboBox::get_active()</methodname>. This returns a <classname>TreeModel::iterator</classname> that you can dereference to a <classname>Row</classname> in order to read the values in your columns. For instance, you might read an integer ID value from the model, even though you have chosen only to show the human-readable description in the ComboBox. For instance:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:3576
#, no-wrap
msgid ""
"Gtk::TreeModel::iterator iter = m_Combo.get_active();\n"
"if(iter)\n"
"{\n"
"  auto row = *iter;\n"
"\n"
"  //Get the data for the selected row, using our knowledge\n"
"  //of the tree model:\n"
"  auto id = row[m_Columns.m_col_id];\n"
"  set_something_id_chosen(id); //Your own function.\n"
"}\n"
"else\n"
"  set_nothing_chosen(); //Your own function."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3593
msgid "You might need to react to every change of selection in the ComboBox, for instance to update other widgets. To do so, you should handle the <literal>changed</literal> signal. For instance:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:3596
#, no-wrap
msgid ""
"m_combo.signal_changed().connect( sigc::mem_fun(*this,\n"
"      &amp;ExampleWindow::on_combo_changed) );"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:3601
#: C/index-in.docbook:3687
msgid "Full Example"
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:3604
msgid "ComboBox"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:3606
msgctxt "_"
msgid "external ref='figures/combobox_complex.png' md5='ec96e29fe85caef072868284443e413e'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3610
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/combobox/complex\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:3615
#: C/index-in.docbook:3701
msgid "Simple Text Example"
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:3618
msgid "ComboBoxText"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:3620
msgctxt "_"
msgid "external ref='figures/combobox_text.png' md5='f8278861eaa5cdc1d165b577fc41ccf4'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3624
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/combobox/text\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:3629
msgid "ComboBox with an Entry"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3631
msgid "A <classname>ComboBox</classname> may contain an <classname>Entry</classname> widget for entering of arbitrary text, by specifying <literal>true</literal> for the constructor's <literal>has_entry</literal> parameter."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:3634
msgid "The text column"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3636
msgid "So that the <classname>Entry</classname> can interact with the drop-down list of choices, you must specify which of your model columns is the text column, with <methodname>set_entry_text_column()</methodname>. For instance:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:3638
#, no-wrap
msgid ""
"m_combo.set_entry_text_column(m_columns.m_col_name);"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3639
msgid "When you select a choice from the drop-down menu, the value from this column will be placed in the <classname>Entry</classname>."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:3645
msgid "The entry"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3647
msgid "Because the user may enter arbitrary text, an active model row isn't enough to tell us what text the user has entered. Therefore, you should retrieve the <classname>Entry</classname> widget with the <methodname>ComboBox::get_entry()</methodname> method and call <methodname>get_text()</methodname> on that."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3654
msgid "When the user enters arbitrary text, it may not be enough to connect to the <literal>changed</literal> signal, which is emitted for every typed character. It is not emitted when the user presses the <keycap>Enter</keycap> key. Pressing the <keycap>Enter</keycap> key or moving the keyboard focus to another widget may signal that the user has finished entering text. To be notified of these events, connect to the <classname>Entry</classname>'s <literal>activate</literal> signal (available since <application>gtkmm</application> 4.8), and add a <classname>Gtk::EventControllerFocus</classname> and connect to its <literal>leave</literal> signal, like so"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:3664
#, no-wrap
msgid ""
"auto entry = m_Combo.get_entry();\n"
"if (entry)\n"
"{\n"
"  // Alternatively you can connect to m_Combo.signal_changed().\n"
"  entry-&gt;signal_changed().connect(sigc::mem_fun(*this,\n"
"    &amp;ExampleWindow::on_entry_changed));\n"
"  entry-&gt;signal_activate().connect(sigc::mem_fun(*this,\n"
"    &amp;ExampleWindow::on_entry_activate));\n"
"  // The Entry shall receive focus-leave events.\n"
"  auto controller = Gtk::EventControllerFocus::create();\n"
"  m_ConnectionFocusLeave = controller-&gt;signal_leave().connect(\n"
"    sigc::mem_fun(*this, &amp;ExampleWindow::on_entry_focus_leave));\n"
"  entry-&gt;add_controller(controller);\n"
"}"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3678
msgid "The <literal>changed</literal> signals of <classname>ComboBox</classname> and <classname>Entry</classname> are both emitted for every change. It doesn't matter which one you connect to. But the <classname>EventControllerFocus</classname> must be added to the <classname>Entry</classname>."
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:3690
msgid "ComboBox with Entry"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:3692
msgctxt "_"
msgid "external ref='figures/comboboxentry_complex.png' md5='09bd46bc2fb93193ed4f9cf910ede733'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3696
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/combobox/entry_complex\">Source Code</link>"
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:3704
msgid "ComboBoxText with Entry"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:3706
msgctxt "_"
msgid "external ref='figures/comboboxentry_text.png' md5='164e857e073b574d6176927c8247ad96'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3710
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/combobox/entry_text\">Source Code</link>"
msgstr ""

#. (itstool) path: chapter/title
#. (itstool) path: figure/title
#: C/index-in.docbook:3718
#: C/index-in.docbook:3943
msgid "TextView"
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:3720
msgid "The <classname>TextView</classname> widget can be used to display and edit large amounts of formatted text. Like the <classname>TreeView</classname>, it has a model/view design. In this case the <classname>TextBuffer</classname> is the model."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:3728
msgid "The Buffer"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3730
msgid "<classname>Gtk::TextBuffer</classname> is a model containing the data for the <classname>Gtk::TextView</classname>, like the <classname>Gtk::TreeModel</classname> used by <classname>Gtk::TreeView</classname>. This allows two or more <classname>Gtk::TextView</classname>s to share the same <classname>TextBuffer</classname>, and allows those TextBuffers to be displayed slightly differently. Or you could maintain several <classname>Gtk::TextBuffer</classname>s and choose to display each one at different times in the same <classname>Gtk::TextView</classname> widget."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3740
msgid "The <classname>TextView</classname> creates its own default <classname>TextBuffer</classname>, which you can access via the <methodname>get_buffer()</methodname> method."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3746
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1TextBuffer.html\">Reference</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:3749
msgid "Iterators"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3751
msgid "A <classname>Gtk::TextBuffer::iterator</classname> and a <classname>Gtk::TextBuffer::const_iterator</classname> represent a position between two characters in the text buffer. Whenever the buffer is modified in a way that affects the number of characters in the buffer, all outstanding iterators become invalid. Because of this, iterators can't be used to preserve positions across buffer modifications. To preserve a position, use <classname>Gtk::TextBuffer::Mark</classname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3758
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1TextIter.html\">Reference</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:3762
msgid "Tags and Formatting"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:3765
msgid "Tags"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3767
msgid "To specify that some text in the buffer should have specific formatting, you must define a tag to hold that formatting information, and then apply that tag to the region of text. For instance, to define the tag and its properties:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:3770
#, no-wrap
msgid ""
"auto refTagMatch = Gtk::TextBuffer::Tag::create();\n"
"refTagMatch-&gt;property_background() = \"orange\";"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3772
msgid "You can specify a name for the <classname>Tag</classname> when using the <methodname>create()</methodname> method, but it is not necessary."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3777
msgid "The <classname>Tag</classname> class has many other properties."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3781
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1TextTag.html\">Reference</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:3786
msgid "TagTable"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3788
msgid "Each <classname>Gtk::TextBuffer</classname> uses a <classname>Gtk::TextBuffer::TagTable</classname>, which contains the <classname>Tag</classname>s for that buffer. 2 or more <classname>TextBuffer</classname>s may share the same <classname>TagTable</classname>. When you create <classname>Tag</classname>s you should add them to the <classname>TagTable</classname>. For instance:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:3796
#, no-wrap
msgid ""
"auto refTagTable = Gtk::TextBuffer::TagTable::create();\n"
"refTagTable-&gt;add(refTagMatch);\n"
"//Hopefully a future version of <application>gtkmm</application> will have a set_tag_table() method,\n"
"//for use after creation of the buffer.\n"
"auto refBuffer = Gtk::TextBuffer::create(refTagTable);"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3802
msgid "You can also use <methodname>get_tag_table()</methodname> to get, and maybe modify, the <classname>TextBuffer</classname>'s default <classname>TagTable</classname> instead of creating one explicitly."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3808
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1TextTagTable.html\">Reference</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:3813
msgid "Applying Tags"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3815
msgid "If you have created a <classname>Tag</classname> and added it to the <classname>TagTable</classname>, you may apply that tag to part of the <classname>TextBuffer</classname> so that some of the text is displayed with that formatting. You define the start and end of the range of text by specifying <classname>Gtk::TextBuffer::iterator</classname>s. For instance:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:3822
#, no-wrap
msgid ""
"refBuffer-&gt;apply_tag(refTagMatch, iterRangeStart, iterRangeStop);"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3823
msgid "Or you could specify the tag when first inserting the text:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:3826
#, no-wrap
msgid ""
"refBuffer-&gt;insert_with_tag(iter, \"Some text\", refTagMatch);"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3828
msgid "You can apply more than one <classname>Tag</classname> to the same text, by using <methodname>apply_tag()</methodname> more than once, or by using <methodname>insert_with_tags()</methodname>. The <classname>Tag</classname>s might specify different values for the same properties, but you can resolve these conflicts by using <methodname>Tag::set_priority()</methodname>."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:3840
msgid "Marks"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3842
msgid "<classname>TextBuffer</classname> iterators are generally invalidated when the text changes, but you can use a <classname>Gtk::TextBuffer::Mark</classname> to remember a position in these situations. For instance,"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:3847
#, no-wrap
msgid ""
"auto refMark = refBuffer-&gt;create_mark(iter);"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3849
msgid "You can then use the <methodname>get_iter()</methodname> method later to create an iterator for the <classname>Mark</classname>'s new position."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3854
msgid "There are two built-in <classname>Mark</classname>s - <literal>insert</literal> and <literal>selection_bound</literal>, which you can access with <classname>TextBuffer</classname>'s <methodname>get_insert()</methodname> and <methodname>get_selection_bound()</methodname> methods."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3861
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1TextMark.html\">Reference</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3868
msgid "As mentioned above, each <classname>TextView</classname> has a <classname>TextBuffer</classname>, and one or more <classname>TextView</classname>s can share the same <classname>TextBuffer</classname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3875
msgid "Like the <classname>TreeView</classname>, you should probably put your <classname>TextView</classname> inside a <classname>ScrolledWindow</classname> to allow the user to see and move around the whole text area with scrollbars."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3882
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1TextView.html\">Reference</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:3885
msgid "Default formatting"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3887
msgid "<classname>TextView</classname> has various methods which allow you to change the presentation of the buffer for this particular view. Some of these may be overridden by the <classname>Gtk::TextTag</classname>s in the buffer, if they specify the same things. For instance, <methodname>set_left_margin()</methodname>, <methodname>set_right_margin()</methodname>, <methodname>set_indent()</methodname>, etc."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:3898
msgid "Scrolling"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3900
msgid "<classname>Gtk::TextView</classname> has various <methodname>scroll_to()</methodname> methods. These allow you to ensure that a particular part of the text buffer is visible. For instance, your application's Find feature might use <methodname>Gtk::TextView::scroll_to()</methodname> to show the found text."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:3915
msgid "Widgets and ChildAnchors"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3917
msgid "You can embed widgets, such as <classname>Gtk::Button</classname>s, in the text. Each such child widget needs a <classname>ChildAnchor</classname>. ChildAnchors are associated with <classname>iterator</classname>s. For instance, to create a child anchor at a particular position, use <methodname>Gtk::TextBuffer::create_child_anchor()</methodname>:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:3924
#, no-wrap
msgid ""
"auto refAnchor = refBuffer-&gt;create_child_anchor(iter);"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3926
msgid "Then, to add a widget at that position, use <methodname>Gtk::TextView::add_child_at_anchor()</methodname>:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:3930
#, no-wrap
msgid ""
"m_TextView.add_child_at_anchor(m_Button, refAnchor);"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3932
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1TextChildAnchor.html\">Reference</link>"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:3945
msgctxt "_"
msgid "external ref='figures/textview.png' md5='451e30f66cc32c4231bb6bc442cf0d2f'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3949
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/textview/\">Source Code</link>"
msgstr ""

#. (itstool) path: chapter/title
#: C/index-in.docbook:3956
msgid "Menus and Toolbars"
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:3958
msgid "There are specific APIs for menus and toolbars, but you should usually deal with them together, creating <classname>Gio::SimpleAction</classname>s that you can refer to in both menus and toolbars. In this way you can handle activation of the action instead of responding to the menu and toolbar items separately. And you can enable or disable both the menu and toolbar item via the action. <classname>Gtk::Builder</classname> can create menus and toolbars."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:3966
msgid "This involves the use of the <classname>Gio::SimpleActionGroup</classname>, <classname>Gio::SimpleAction</classname> and <classname>Gtk::Builder</classname> classes, all of which should be instantiated via their <methodname>create()</methodname> methods, which return <classname>RefPtr</classname>s."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:3974
msgid "Actions"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3976
msgid "First create the <classname>Gio::SimpleAction</classname>s and add them to a <classname>Gio::SimpleActionGroup</classname>, with <methodname>Gio::ActionMap::add_action()</methodname>. (<classname>Gio::ActionMap</classname> is a base class of <classname>Gio::SimpleActionGroup</classname>.) Then add the action group to your window with <methodname>Gtk::Widget::insert_action_group()</methodname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3984
msgid "The arguments to <methodname>add_action()</methodname> specify the action's name, which is used in the menu items and toolbar buttons. You can also specify a signal handler when calling <methodname>add_action()</methodname>. This signal handler will be called when the action is activated via either a menu item or a toolbar button."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:3992
#: C/index-in.docbook:4119
msgid "For instance:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:3994
#, no-wrap
msgid ""
"\n"
"m_refActionGroup = Gio::SimpleActionGroup::create();\n"
"\n"
"m_refActionGroup-&gt;add_action(\"new\", sigc::mem_fun(*this, &amp;ExampleWindow::on_action_file_new));\n"
"m_refActionGroup-&gt;add_action(\"open\", sigc::mem_fun(*this, &amp;ExampleWindow::on_action_file_open));\n"
"m_refActionGroup-&gt;add_action(\"quit\", sigc::mem_fun(*this, &amp;ExampleWindow::on_action_file_quit));\n"
"\n"
"insert_action_group(\"example\", m_refActionGroup);\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4004
msgid "If you use an <classname>Gtk::ApplicationWindow</classname>, you don't have to create your own action group. <classname>Gio::ActionGroup</classname> and <classname>Gio::ActionMap</classname> are base classes of <classname>Gtk::ApplicationWindow</classname>."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:4015
msgid "Menubar and Toolbar"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4017
msgid "Next you should create a <classname>Gtk::Builder</classname>. At this point is also a good idea to tell the application to respond to keyboard shortcuts, by using <methodname>Gtk::Application::set_accel_for_action()</methodname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4023
#: C/index-in.docbook:5735
#: C/index-in.docbook:5800
#: C/index-in.docbook:11493
msgid "For instance,"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:4025
#, no-wrap
msgid ""
"\n"
"m_refBuilder = Gtk::Builder::create();\n"
"\n"
"app-&gt;set_accel_for_action(\"example.new\", \"&lt;Primary&gt;n\");\n"
"app-&gt;set_accel_for_action(\"example.quit\", \"&lt;Primary&gt;q\");\n"
"app-&gt;set_accel_for_action(\"example.copy\", \"&lt;Primary&gt;c\");\n"
"app-&gt;set_accel_for_action(\"example.paste\", \"&lt;Primary&gt;v\");\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4044
msgid "Then, you can define the actual visible layout of the menus and toolbars, and add the UI layout to the <classname>Builder</classname>. This \"ui string\" uses an XML format, in which you should mention the names of the actions that you have already created. For instance:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:4050
#, no-wrap
msgid ""
"\n"
"Glib::ustring ui_info =\n"
"  \"&lt;interface&gt;\"\n"
"  \"  &lt;menu id='menubar'&gt;\"\n"
"  \"    &lt;submenu&gt;\"\n"
"  \"      &lt;attribute name='label' translatable='yes'&gt;_File&lt;/attribute&gt;\"\n"
"  \"      &lt;section&gt;\"\n"
"  \"        &lt;item&gt;\"\n"
"  \"          &lt;attribute name='label' translatable='yes'&gt;_New&lt;/attribute&gt;\"\n"
"  \"          &lt;attribute name='action'&gt;example.new&lt;/attribute&gt;\"\n"
"  \"        &lt;/item&gt;\"\n"
"  \"      &lt;/section&gt;\"\n"
"  \"      &lt;section&gt;\"\n"
"  \"        &lt;item&gt;\"\n"
"  \"          &lt;attribute name='label' translatable='yes'&gt;_Quit&lt;/attribute&gt;\"\n"
"  \"          &lt;attribute name='action'&gt;example.quit&lt;/attribute&gt;\"\n"
"  \"        &lt;/item&gt;\"\n"
"  \"      &lt;/section&gt;\"\n"
"  \"    &lt;/submenu&gt;\"\n"
"  \"    &lt;submenu&gt;\"\n"
"  \"      &lt;attribute name='label' translatable='yes'&gt;_Edit&lt;/attribute&gt;\"\n"
"  \"      &lt;item&gt;\"\n"
"  \"        &lt;attribute name='label' translatable='yes'&gt;_Copy&lt;/attribute&gt;\"\n"
"  \"        &lt;attribute name='action'&gt;example.copy&lt;/attribute&gt;\"\n"
"  \"      &lt;/item&gt;\"\n"
"  \"      &lt;item&gt;\"\n"
"  \"        &lt;attribute name='label' translatable='yes'&gt;_Paste&lt;/attribute&gt;\"\n"
"  \"        &lt;attribute name='action'&gt;example.paste&lt;/attribute&gt;\"\n"
"  \"      &lt;/item&gt;\"\n"
"  \"    &lt;/submenu&gt;\"\n"
"  \"  &lt;/menu&gt;\"\n"
"  \"&lt;/interface&gt;\";\n"
"\n"
"m_refBuilder-&gt;add_from_string(ui_info);\n"
"m_refBuilder-&gt;add_from_resource(\"/toolbar/toolbar.ui\");\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4087
msgid "This is where we specify the names of the menu items as they will be seen by users in the menu. Therefore, this is where you should make strings translatable, by adding <literal>translatable='yes'</literal>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4091
msgid "To instantiate a <classname>Gtk::PopoverMenuBar</classname> and toolbar (a horizontal <classname>Gtk::Box</classname>) which you can actually show, you should use the <methodname>Builder::get_object()</methodname> and <methodname>Builder::get_widget()</methodname> methods, and then add the widgets to a container. For instance:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:4098
#, no-wrap
msgid ""
"\n"
"auto gmenu = m_refBuilder-&gt;get_object&lt;Gio::Menu&gt;(\"menubar\");\n"
"auto pMenuBar = Gtk::make_managed&lt;Gtk::PopoverMenuBar&gt;(gmenu);\n"
"m_Box.append(*pMenuBar);\n"
"\n"
"auto toolbar = m_refBuilder-&gt;get_widget&lt;Gtk::Box&gt;(\"toolbar\");\n"
"m_Box.append(*toolbar);\n"
""
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:4111
msgid "Popup Menus"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4112
msgid "<classname>Menu</classname>s are normally just added to a window, but they can also be displayed temporarily as the result of a mouse button click. For instance, a context menu might be displayed when the user clicks their right mouse button."
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:4121
#, no-wrap
msgid ""
"\n"
"Glib::ustring ui_info =\n"
"  \"&lt;interface&gt;\"\n"
"  \"  &lt;menu id='menu-examplepopup'&gt;\"\n"
"  \"    &lt;section&gt;\"\n"
"  \"      &lt;item&gt;\"\n"
"  \"        &lt;attribute name='label' translatable='yes'&gt;Edit&lt;/attribute&gt;\"\n"
"  \"        &lt;attribute name='action'&gt;examplepopup.edit&lt;/attribute&gt;\"\n"
"  \"      &lt;/item&gt;\"\n"
"  \"      &lt;item&gt;\"\n"
"  \"        &lt;attribute name='label' translatable='yes'&gt;Process&lt;/attribute&gt;\"\n"
"  \"        &lt;attribute name='action'&gt;examplepopup.process&lt;/attribute&gt;\"\n"
"  \"      &lt;/item&gt;\"\n"
"  \"      &lt;item&gt;\"\n"
"  \"        &lt;attribute name='label' translatable='yes'&gt;Remove&lt;/attribute&gt;\"\n"
"  \"        &lt;attribute name='action'&gt;examplepopup.remove&lt;/attribute&gt;\"\n"
"  \"      &lt;/item&gt;\"\n"
"  \"    &lt;/section&gt;\"\n"
"  \"  &lt;/menu&gt;\"\n"
"  \"&lt;/interface&gt;\";\n"
"\n"
"m_refBuilder-&gt;add_from_string(ui_info);\n"
"\n"
"auto gmenu = m_refBuilder-&gt;get_object&lt;Gio::Menu&gt;(\"menu-examplepopup\");\n"
"m_MenuPopup.set_menu_model(gmenu);\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4148
msgid "To show the popup menu, use a <classname>Gtk::GestureClick</classname> and connect to its <literal>pressed</literal> signal. In the signal handler, use <classname>Gtk::PopoverMenu</classname>'s <methodname>popup()</methodname> method. For instance:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:4154
#, no-wrap
msgid ""
"\n"
"void ExampleWindow::on_label_pressed(int /* n_press */, double x, double y)\n"
"{\n"
"  const Gdk::Rectangle rect(x, y, 1, 1);\n"
"  m_MenuPopup.set_pointing_to(rect);\n"
"  m_MenuPopup.popup();\n"
"}"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:4165
msgid "Gio::Resource and glib-compile-resources"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4167
msgid "Applications and libraries often contain binary or textual data that is really part of the application, rather than user data. For instance <classname>Gtk::Builder</classname> <filename class=\"extension\">.ui</filename> files, splashscreen images, <classname>Gio::Menu</classname> markup xml, CSS files, icons, etc. These are often shipped as files in <filename class=\"directory\">$datadir/appname</filename>, or manually included as literal strings in the code."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4175
msgid "The <classname>Gio::Resource</classname> API and the <application>glib-compile-resources</application> program provide a convenient and efficient alternative to this, which has some nice properties. You maintain the files as normal files, so it's easy to edit them, but during the build the files are combined into a binary bundle that is linked into the executable. This means that loading the resource files is efficient (as they are already in memory, shared with other instances) and simple (no need to check for things like I/O errors or locate the files in the filesystem). It also makes it easier to create relocatable applications."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4187
msgid "Resource bundles are created by the <application>glib-compile-resources</application> program which takes an xml file that describes the bundle, and a set of files that the xml references. These are combined into a binary resource bundle."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4192
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/glibmm/classGio_1_1Resource.html\">Gio::Resource Reference</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4193
msgid "An example:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:4194
#, no-wrap
msgid ""
"\n"
"&lt;?xml version=\"1.0\" encoding=\"UTF-8\"?&gt;\n"
"&lt;gresources&gt;\n"
"  &lt;gresource prefix=\"/toolbar\"&gt;\n"
"    &lt;file preprocess=\"xml-stripblanks\"&gt;toolbar.ui&lt;/file&gt;\n"
"    &lt;file&gt;rain.png&lt;/file&gt;\n"
"  &lt;/gresource&gt;\n"
"&lt;/gresources&gt;\n"
""
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:4205
msgid "<filename>/toolbar/toolbar.ui</filename>"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:4206
msgid "<filename>/toolbar/rain.png</filename>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4203
msgid "This will create a resource bundle with the files <_:itemizedlist-1/>"
msgstr ""

#. (itstool) path: para/screen
#: C/index-in.docbook:4214
#, no-wrap
msgid ""
"$ glib-compile-resources --target=resources.c --generate-source toolbar.gresource.xml"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4209
msgid "You can then use <application>glib-compile-resources</application> to compile the xml to a binary bundle that you can load with <methodname>Gio::Resource::create_from_file()</methodname>. However, it's more common to use the <parameter class=\"command\">--generate-source</parameter> argument to create a C source file to link directly into your application. E.g. <_:screen-1/>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4216
msgid "Once a <classname>Gio::Resource</classname> has been created and registered all the data in it can be accessed globally in the process by using API calls like <methodname>Gio::Resource::open_stream_from_global_resources()</methodname> to stream the data or <methodname>Gio::Resource::lookup_data_in_global_resources()</methodname> to get a direct pointer to the data. You can also use URIs like <uri>resource:///toolbar/rain.png</uri> with <classname>Gio::File</classname> to access the resource data."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4224
msgid "Often you don't need a <classname>Gio::Resource</classname> instance, because resource data can be loaded with methods such as <methodname>Gdk::Pixbuf::create_from_resource()</methodname>, <methodname>Gtk::Builder::add_from_resource()</methodname> and <methodname>Gtk::Image::set_from_resource()</methodname>."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:4238
msgid "Application Menu and Main Menu example"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4239
msgid "This program contains an application menu, a menubar and a toolbar. Classes are derived from <classname>Gtk::Application</classname> and <classname>Gtk::ApplicationWindow</classname>."
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:4246
msgid "App and Main Menu"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:4248
msgctxt "_"
msgid "external ref='figures/main_menu.png' md5='fc670c5887873c4c8ec1e5aa1e032680'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4252
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/menus/main_menu/\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:4257
msgid "Main Menu example"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4258
msgid "This program contains a menubar and a toolbar. A class is derived from <classname>Gtk::Window</classname>."
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:4264
msgid "Main Menu"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:4266
msgctxt "_"
msgid "external ref='figures/menus_and_toolbars.png' md5='cbe894e7603b7c3de488d4c9ff503442'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4270
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/menus_and_toolbars\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:4275
msgid "Popup Menu example"
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:4278
msgid "Popup Menu"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:4280
msgctxt "_"
msgid "external ref='figures/menu_popup.png' md5='bd168ad48b89f488d29e13db9b765168'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4284
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/menus/popup/\">Source Code</link>"
msgstr ""

#. (itstool) path: chapter/title
#: C/index-in.docbook:4291
msgid "Adjustments"
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:4293
msgid "<application>gtkmm</application> has various widgets that can be visually adjusted using the mouse or the keyboard, such as the <classname>Range</classname> widgets (described in the <link linkend=\"chapter-range-widgets\">Range Widgets</link> section). There are also a few widgets that display some adjustable part of a larger area, such as the <classname>Viewport</classname> widget. These widgets have <classname>Gtk::Adjustment</classname> objects that express this common part of their API."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:4303
msgid "So that applications can react to changes, for instance when a user moves a scrollbar, <classname>Gtk::Adjustment</classname> has a <literal>value_changed</literal> signal. You can then use the <methodname>get_value()</methodname> method to discover the new value."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:4311
msgid "Creating an Adjustment"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4313
msgid "The <classname>Gtk::Adjustment</classname> is created by its <methodname>create()</methodname> method which is as follows:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:4318
#, no-wrap
msgid ""
"Glib::RefPtr&lt;Gtk::Adjustment&gt; Gtk::Adjustment::create(\n"
"  double value,\n"
"  double lower,\n"
"  double upper,\n"
"  double step_increment = 1,\n"
"  double page_increment = 10,\n"
"  double page_size = 0);"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4326
msgid "The <parameter>value</parameter> argument is the initial value of the adjustment, usually corresponding to the topmost or leftmost position of an adjustable widget. The <parameter>lower</parameter> and <parameter>upper</parameter> arguments specify the possible range of values which the adjustment can hold. The <parameter>step_increment</parameter> argument specifies the smaller of the two increments by which the user can change the value, while the <parameter>page_increment</parameter> is the larger one. The <parameter>page_size</parameter> argument usually corresponds somehow to the visible area of a panning widget. The <parameter>upper</parameter> argument is used to represent the bottommost or rightmost coordinate in a panning widget's child."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:4345
msgid "Using Adjustments the Easy Way"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4347
msgid "The adjustable widgets can be roughly divided into those which use and require specific units for these values, and those which treat them as arbitrary numbers."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4352
msgid "The group which treats the values as arbitrary numbers includes the <classname>Range</classname> widgets (<classname>Scrollbar</classname> and <classname>Scale</classname>), the <classname>ScaleButton</classname> widget, and the <classname>SpinButton</classname> widget. These widgets are typically \"adjusted\" directly by the user with the mouse or keyboard. They will treat the <parameter>lower</parameter> and <parameter>upper</parameter> values of an adjustment as a range within which the user can manipulate the adjustment's <parameter>value</parameter>. By default, they will only modify the <parameter>value</parameter> of an adjustment."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4364
msgid "The other group includes the <classname>Viewport</classname> widget and the <classname>ScrolledWindow</classname> widget. All of these widgets use pixel values for their adjustments. These are also typically adjusted indirectly using scrollbars. While all widgets which use adjustments can either create their own adjustments or use ones you supply, you'll generally want to let this particular category of widgets create its own adjustments."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4373
msgid "If you share an adjustment object between a Scrollbar and a TextView widget, manipulating the scrollbar will automagically adjust the TextView widget. You can set it up like this:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:4378
#, no-wrap
msgid ""
"// creates its own adjustments\n"
"Gtk::TextView textview;\n"
"// uses the newly-created adjustment for the scrollbar as well\n"
"Gtk::Scrollbar vscrollbar(textview.get_vadjustment(), Gtk::Orientation::VERTICAL);"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:4386
msgid "Adjustment Internals"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4388
msgid "OK, you say, that's nice, but what if I want to create my own handlers to respond when the user adjusts a <classname>Range</classname> widget or a <classname>SpinButton</classname>. To access the value of a <classname>Gtk::Adjustment</classname>, you can use the <methodname>get_value()</methodname> and <methodname>set_value()</methodname> methods:"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4396
msgid "As mentioned earlier, <classname>Gtk::Adjustment</classname> can emit signals. This is, of course, how updates happen automatically when you share an <classname>Adjustment</classname> object between a <classname>Scrollbar</classname> and another adjustable widget; all adjustable widgets connect signal handlers to their adjustment's <literal>value_changed</literal> signal, as can your program."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4405
msgid "So, for example, if you have a <classname>Scale</classname> widget, and you want to change the rotation of a picture whenever its value changes, you would create a signal handler like this:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:4410
#, no-wrap
msgid ""
"void cb_rotate_picture(MyPicture* picture)\n"
"{\n"
"  picture-&gt;set_rotation(adj-&gt;get_value());\n"
"..."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4414
msgid "and connect it to the scale widget's adjustment like this:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:4417
#, no-wrap
msgid ""
"adj-&gt;signal_value_changed().connect(sigc::bind&lt;MyPicture*&gt;(sigc::mem_fun(*this,\n"
"    &amp;cb_rotate_picture), picture));"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4420
msgid "What if a widget reconfigures the <parameter>upper</parameter> or <parameter>lower</parameter> fields of its <classname>Adjustment</classname>, such as when a user adds more text to a text widget? In this case, it emits the <literal>changed</literal> signal."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4427
msgid "<classname>Range</classname> widgets typically connect a handler to this signal, which changes their appearance to reflect the change - for example, the size of the slider in a scrollbar will grow or shrink in inverse proportion to the difference between the <parameter>lower</parameter> and <parameter>upper</parameter> values of its <classname>Adjustment</classname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4436
msgid "You probably won't ever need to attach a handler to this signal, unless you're writing a new type of range widget."
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:4440
#, no-wrap
msgid ""
"adjustment-&gt;signal_changed();"
msgstr ""

#. (itstool) path: chapter/title
#: C/index-in.docbook:4447
msgid "Dialogs"
msgstr ""

#. (itstool) path: note/para
#: C/index-in.docbook:4449
msgid "<classname>Gtk::Dialog</classname> and the classes derived from it, are deprecated since <application>gtkmm</application> 4.10. They can still be used in <application>gtkmm</application>4 applications, provided GTKMM_DISABLE_DEPRECATED and GDKMM_DISABLE_DEPRECATED are not defined. Some of the dialog classes are replaced by classes that are available since <application>gtkmm</application> 4.10."
msgstr ""

#. (itstool) path: note/para
#: C/index-in.docbook:4454
msgid "The examples in this chapter use classes that are available since <application>gtkmm</application> 4.10. Similar examples with the deprecated classes are available in the <link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/gtkmm-4-0/examples/book/dialogs/\"> gtkmm-4-0 branch</link> in the git repository."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:4460
msgid "Dialogs are used as secondary windows, to provide specific information or to ask questions. <classname>Gtk::Dialog</classname> windows contain a few pre-packed widgets to ensure consistency, and a <literal>response</literal> signal which is emitted when the user dismisses the dialog."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:4467
msgid "There are several derived <classname>Dialog</classname> classes which you might find useful. <classname>Gtk::MessageDialog</classname> is used for most simple notifications. But at other times you might need to derive your own dialog class to provide more complex functionality."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:4474
msgid "To pack widgets into a custom dialog, you should pack them into the <classname>Gtk::Box</classname>, available via <methodname>get_content_area()</methodname>. To just add a <classname>Button</classname> to the bottom of the <classname>Dialog</classname>, you could use the <methodname>add_button()</methodname> method."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:4482
msgid "The <literal>response</literal> signal handler receives an <literal>int</literal>. This may be a value from the <type>Gtk::ResponseType</type> if the user closed the dialog by clicking a standard button, or it could be the custom response value that you specified when using <methodname>add_button()</methodname>."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:4489
msgid "To show the dialog, call <methodname>set_visible(true)</methodname>. If the same dialog instance will be shown several times, you must also call <methodname>set_hide_on_close()</methodname>, or else the dialog will be destroyed when it's closed. Connect to the <literal>response</literal> signal, if you want to know which button was pressed. The <literal>response</literal> signal handler is also where you should hide the dialog."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:4498
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1Dialog.html\">Reference</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:4501
msgid "AlertDialog and MessageDialog"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4502
msgid "<classname>MessageDialog</classname> (deprecated since <application>gtkmm</application> 4.10) and <classname>AlertDialog</classname> (available since <application>gtkmm</application> 4.10) are convenience classes, used to create simple, standard message dialogs, with a message and buttons for user response."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4509
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1AlertDialog.html\">AlertDialog Reference</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4510
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1MessageDialog.html\">MessageDialog Reference</link>"
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:4516
msgid "AlertDialog"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:4518
msgctxt "_"
msgid "external ref='figures/dialogs_alertdialog.png' md5='88fa2103ad6d842eeebc68cc8cfd94ef'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4522
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/dialogs/alertdialog\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:4527
msgid "FileDialog and FileChooserDialog"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4528
msgid "The <classname>FileChooserDialog</classname> (deprecated since <application>gtkmm</application> 4.10) and <classname>FileDialog</classname> (available since <application>gtkmm</application> 4.10) are suitable for use with \"Open\" or \"Save\" menu items."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4533
msgid "Most of the useful member methods for <classname>FileChooserDialog</classname> are actually in the <classname>Gtk::FileChooser</classname> base class."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4538
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1FileDialog.html\">FileDialog Reference</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4539
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1FileChooserDialog.html\">FileChooserDialog Reference</link>"
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:4545
msgid "FileDialog"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:4547
msgctxt "_"
msgid "external ref='figures/dialogs_filedialog.png' md5='15ecc452482112428259d0dcd8d0394a'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4551
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/dialogs/filedialog\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:4556
msgid "ColorDialog and ColorChooserDialog"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4557
msgid "The <classname>ColorChooserDialog</classname> (deprecated since <application>gtkmm</application> 4.10) and <classname>ColorDialog</classname> (available since <application>gtkmm</application> 4.10) allow the user to choose a color. The <classname>ColorButton</classname> (deprecated since <application>gtkmm</application> 4.10) and <classname>ColorDialogButton</classname> (available since <application>gtkmm</application> 4.10) open a color selection dialog when it is clicked."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4565
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1ColorDialog.html\">ColorDialog Reference</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4566
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1ColorChooserDialog.html\">ColorChooserDialog Reference</link>"
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:4572
msgid "ColorDialog"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:4574
msgctxt "_"
msgid "external ref='figures/dialogs_colordialog.png' md5='029761e82cf06d3cbeaac2b7ccd70e57'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4578
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/dialogs/colordialog\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:4583
msgid "FontDialog and FontChooserDialog"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4584
msgid "The <classname>FontChooserDialog</classname> (deprecated since <application>gtkmm</application> 4.10) and <classname>FontDialog</classname> (available since <application>gtkmm</application> 4.10) allow the user to choose a font. The <classname>FontButton</classname> (deprecated since <application>gtkmm</application> 4.10) and <classname>FontDialogButton</classname> (available since <application>gtkmm</application> 4.10) open a font chooser dialog when it is clicked."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4592
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1FontDialog.html\">FontDialog Reference</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4593
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1FontChooserDialog.html\">FontChooserDialog Reference</link>"
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:4599
msgid "FontDialog"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:4601
msgctxt "_"
msgid "external ref='figures/dialogs_fontdialog.png' md5='e35e05429468fa8823416b8a0deff342'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4605
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/dialogs/fontdialog\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:4610
msgid "Non-modal AboutDialog"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4611
msgid "The <classname>AboutDialog</classname> offers a simple way to display information about a program, like its logo, name, copyright, website and license."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4615
msgid "Most dialogs in this chapter are modal, that is, they freeze the rest of the application while they are shown. It's also possible to create a non-modal dialog, which does not freeze other windows in the application. The following example shows a non-modal <classname>AboutDialog</classname>. This is perhaps not the kind of dialog you would normally make non-modal, but non-modal dialogs can be useful in other cases. E.g. <application>gedit</application>'s search-and-replace dialog is non-modal."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4625
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1AboutDialog.html\">Reference</link>"
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:4631
msgid "AboutDialog"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:4633
msgctxt "_"
msgid "external ref='figures/dialogs_about.png' md5='1b70a95ad73fce53bb5a2fbd3df69c5c'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4637
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/dialogs/aboutdialog\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:4642
msgid "Custom Dialog"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4643
msgid "When none of the predefined dialog classes suit your needs, you can make your own dialog by deriving a class from <classname>Window</classname> and fill it with the widgets you need."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4649
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1Window.html\">Window Reference</link>"
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:4655
msgid "Window Dialog"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:4657
msgctxt "_"
msgid "external ref='figures/dialogs_windowdialog.png' md5='53deb18153f6903fe45d015fc06ccef3'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4661
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/dialogs/windowdialog\">Source Code</link>"
msgstr ""

#. (itstool) path: chapter/title
#: C/index-in.docbook:4668
msgid "The DrawingArea Widget"
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:4669
msgid "The <classname>DrawingArea</classname> widget is a blank window that gives you the freedom to create any graphic you desire. Along with that freedom comes the responsibility to draw on the widget. When a widget is first shown, or when it is covered and then uncovered again it needs to redraw itself. Most widgets have code to do this, but the <classname>DrawingArea</classname> does not, allowing you to write your own draw function to determine how the contents of the widget will be drawn. This is done by setting a draw function with a call to the <methodname>set_draw_func()</methodname> member function."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:4681
msgid "GTK uses the <link xlink:href=\"http://cairographics.org\">Cairo</link> drawing API. With <application>gtkmm</application>, you may use the <link xlink:href=\"http://www.cairographics.org/cairomm/\">cairomm</link> C++ API for cairo."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:4686
msgid "You can draw very sophisticated shapes using Cairo, but the methods to do so are quite basic. Cairo provides methods for drawing straight lines, curved lines, and arcs (including circles). These basic shapes can be combined to create more complex shapes and paths which can be filled with solid colors, gradients, patterns, and other things. In addition, Cairo can perform complex transformations, do compositing of images, and render antialiased text."
msgstr ""

#. (itstool) path: note/title
#: C/index-in.docbook:4696
msgid "Cairo and Pango"
msgstr ""

#. (itstool) path: note/para
#: C/index-in.docbook:4697
msgid "Although Cairo can render text, it's not meant to be a replacement for Pango. Pango is a better choice if you need to perform more advanced text rendering such as wrapping or ellipsizing text. Drawing text with Cairo should only be done if the text is part of a graphic."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:4702
msgid "In this section of the tutorial, we'll cover the basic Cairo drawing model, describe each of the basic drawing elements in some detail (with examples), and then present a simple application that uses Cairo to draw a custom clock widget."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:4710
msgid "The Cairo Drawing Model"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4711
msgid "The basic concept of drawing in Cairo involves defining 'invisible' paths and then stroking or filling them to make them visible."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4715
msgid "To do any drawing in <application>gtkmm</application> with Cairo, you must first get a <classname>Cairo::Context</classname> object. This class holds all of the graphics state parameters that describe how drawing is to be done. This includes information such as line width, color, the surface to draw to, and many other things. This allows the actual drawing functions to take fewer arguments to simplify the interface. Usually, you use the <classname>Cairo::Context</classname> that you get as input data to the draw function that you set with the call to <methodname>set_draw_func()</methodname>. It's also possible to create a <classname>Cairo::Context</classname> by calling the <methodname>Gdk::Surface::create_cairo_context()</methodname> and <methodname>Gdk::CairoContext::cairo_create()</methodname> functions. Since Cairo contexts are reference-counted objects, <methodname>cairo_create()</methodname> returns a <classname>Cairo::RefPtr&lt;Cairo::Context&gt;</classname> object. (Note the difference between <classname>Gdk::CairoContext</classname> and <classname>Cairo::Context</classname>.)"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4732
msgid "The following example shows how to set up a Cairo context with a foreground color of red and a width of 2. Any drawing functions that use this context will use these settings."
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:4737
#, no-wrap
msgid ""
"\n"
"Gtk::DrawingArea myArea;\n"
"auto gdkCairoContext = myArea.get_surface()-&gt;create_cairo_context();\n"
"auto myContext = gdkCairoContext-&gt;cairo_create();\n"
"myContext-&gt;set_source_rgb(1.0, 0.0, 0.0);\n"
"myContext-&gt;set_line_width(2.0);\n"
"    "
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4744
msgid "Each <classname>Cairo::Context</classname> is associated with a particular <classname>Gdk::Surface</classname>, so the first line of the above example creates a <classname>Gtk::DrawingArea</classname> widget and the next two lines use its associated <classname>Gdk::Surface</classname> to create a <classname>Cairo::Context</classname> object. The final two lines change the graphics state of the context."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4752
msgid "There are a number of graphics state variables that can be set for a Cairo context. The most common context attributes are color (using <methodname>set_source_rgb()</methodname> or <methodname>set_source_rgba()</methodname> for translucent colors), line width (using <methodname>set_line_width()</methodname>), line dash pattern (using <methodname>set_dash()</methodname>), line cap style (using <methodname>set_line_cap()</methodname>), and line join style (using <methodname>set_line_join()</methodname>), and font styles (using <methodname>set_font_size()</methodname>, <methodname>set_font_face()</methodname> and others). There are many other settings as well, such as transformation matrices, fill rules, whether to perform antialiasing, and others. For further information, see the <link xlink:href=\"http://www.cairographics.org/cairomm/\">cairomm</link> API documentation."
msgstr ""

#. (itstool) path: tip/para
#: C/index-in.docbook:4784
msgid "It is good practice to put all modifications to the graphics state between <methodname>save()</methodname>/<methodname>restore()</methodname> function calls. For example, if you have a function that takes a <classname>Cairo::Context</classname> reference as an argument, you might implement it as follows:"
msgstr ""

#. (itstool) path: tip/programlisting
#: C/index-in.docbook:4790
#, no-wrap
msgid ""
"void doSomething(const Cairo::RefPtr&lt;Cairo::Context&gt;&amp; context, int x)\n"
"{\n"
"    context-&gt;save();\n"
"    // change graphics state\n"
"    // perform drawing operations\n"
"    context-&gt;restore();\n"
"}"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4767
msgid "The current state of a <classname>Cairo::Context</classname> can be saved to an internal stack of saved states and later be restored to the state it was in when you saved it. To do this, use the <methodname>save()</methodname> method and the <methodname>restore()</methodname> method. This can be useful if you need to temporarily change the line width and color (or any other graphics setting) in order to draw something and then return to the previous settings. In this situation, you could call <methodname>Cairo::Context::save()</methodname>, change the graphics settings, draw the lines, and then call <methodname>Cairo::Context::restore()</methodname> to restore the original graphics state. Multiple calls to <methodname>save()</methodname> and <methodname>restore()</methodname> can be nested; each call to <methodname>restore()</methodname> restores the state from the matching paired <methodname>save()</methodname>. <_:tip-1/>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4799
msgid "The draw function that you set with a call to <methodname>set_draw_func()</methodname> is called with a Cairo context that you shall use for drawing in the <classname>Gtk::DrawingArea</classname> widget. It is not necessary to save and restore this Cairo context in the draw function."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:4807
msgid "Drawing Straight Lines"
msgstr ""

#. (itstool) path: tip/para
#: C/index-in.docbook:4816
msgid "Since the Cairo graphics library was written with support for multiple output targets (the X window system, PNG images, OpenGL, etc), there is a distinction between user-space and device-space coordinates. The mapping between these two coordinate systems defaults to one-to-one so that integer values map roughly to pixels on the screen, but this setting can be adjusted if desired. Sometimes it may be useful to scale the coordinates so that the full width and height of a window both range from 0 to 1 (the 'unit square') or some other mapping that works for your application. This can be done with the <methodname>Cairo::Context::scale()</methodname> function."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4808
msgid "Now that we understand the basics of the Cairo graphics library, we're almost ready to start drawing. We'll start with the simplest of drawing elements: the straight line. But first you need to know a little bit about Cairo's coordinate system. The origin of the Cairo coordinate system is located in the upper-left corner of the window with positive x values to the right and positive y values going down. <_:tip-1/>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4832
msgid "In this example, we'll construct a small but fully functional <application>gtkmm</application> program and draw some lines into the window. The lines are drawn by creating a path and then stroking it. A path is created using the functions <methodname>Cairo::Context::move_to()</methodname> and <methodname>Cairo::Context::line_to()</methodname>. The function <methodname>move_to()</methodname> is similar to the act of lifting your pen off of the paper and placing it somewhere else -- no line is drawn between the point you were at and the point you moved to. To draw a line between two points, use the <methodname>line_to()</methodname> function."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4844
msgid "After you've finished creating your path, you still haven't drawn anything visible yet. To make the path visible, you must use the function <methodname>stroke()</methodname> which will stroke the current path with the line width and style specified in your <classname>Cairo::Context</classname> object. After stroking, the current path will be cleared so that you can start on your next path."
msgstr ""

#. (itstool) path: tip/para
#: C/index-in.docbook:4853
msgid "Many Cairo drawing functions have a <methodname>_preserve()</methodname> variant. Normally drawing functions such as <methodname>clip()</methodname>, <methodname>fill()</methodname>, or <methodname>stroke()</methodname> will clear the current path. If you use the <methodname>_preserve()</methodname> variant, the current path will be retained so that you can use the same path with the next drawing function."
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:4863
#: C/index-in.docbook:4986
msgid "Drawing Area - Lines"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:4865
msgctxt "_"
msgid "external ref='figures/drawingarea_lines.png' md5='3e205f8303890e4eb2ea88487e8633e7'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4869
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/drawingarea/simple\">Source Code</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4871
msgid "This program contains a single class, <classname>MyArea</classname>, which is a subclass of <classname>Gtk::DrawingArea</classname> and contains an <methodname>on_draw()</methodname> member function. This function becomes the draw function by a call to <methodname>set_draw_func()</methodname> in <classname>MyArea</classname>'s constructor. <methodname>on_draw()</methodname> is then called whenever the image in the drawing area needs to be redrawn. It is passed a <classname>Cairo::RefPtr</classname> pointer to a <classname>Cairo::Context</classname> that we use for the drawing. The actual drawing code sets the color we want to use for drawing by using <methodname>set_source_rgb()</methodname> which takes arguments defining the Red, Green, and Blue components of the desired color (valid values are between 0 and 1). After setting the color, we created a new path using the functions <methodname>move_to()</methodname> and <methodname>line_to()</methodname>, and then stroked this path with <methodname>stroke()</methodname>."
msgstr ""

#. (itstool) path: tip/title
#: C/index-in.docbook:4890
msgid "Drawing with relative coordinates"
msgstr ""

#. (itstool) path: tip/para
#: C/index-in.docbook:4891
msgid "In the example above we drew everything using absolute coordinates. You can also draw using relative coordinates. For a straight line, this is done with the function <methodname>Cairo::Context::rel_line_to()</methodname>."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:4898
msgid "Line styles"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4899
msgid "In addition to drawing basic straight lines, there are a number of things that you can customize about a line. You've already seen examples of setting a line's color and width, but there are others as well."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4905
msgid "If you've drawn a series of lines that form a path, you may want them to join together in a certain way. Cairo offers three different ways to join lines together: Miter, Bevel, and Round. These are show below:"
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:4912
msgid "Different join types in Cairo"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:4914
msgctxt "_"
msgid "external ref='figures/cairo_joins.png' md5='1b1e2a28e976039f1e4a0aa523ac40fb'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4917
msgid "The line join style is set using the function <methodname>Cairo::Context::set_line_join()</methodname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4921
msgid "Line ends can have different styles as well. The default style is for the line to start and stop exactly at the destination points of the line. This is called a Butt cap. The other options are Round (uses a round ending, with the center of the circle at the end point) or Square (uses a squared ending, with the center of the square at the end point). This setting is set using the function <methodname>Cairo::Context::set_line_cap()</methodname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4931
msgid "There are other things you can customize as well, including creating dashed lines and other things. For more information, see the Cairo API documentation."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:4939
msgid "Drawing thin lines"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4940
msgid "If you try to draw one pixel wide lines, you may notice that the line sometimes comes up blurred and wider than it ought to be. This happens because Cairo will try to draw from the selected position, to both sides (half to each), so if you're positioned right on the intersection of the pixels, and want a one pixel wide line, Cairo will try to use half of each adjacent pixel, which isn't possible (a pixel is the smallest unit possible). This happens when the width of the line is an odd number of pixels (not just one pixel)."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4950
msgid "The trick is to position in the middle of the pixel where you want the line to be drawn, and thus guaranteeing you get the desired results. See <link xlink:href=\"http://cairographics.org/FAQ/#sharp_lines\">Cairo FAQ</link>."
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:4957
msgid "Drawing Area - Thin Lines"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:4959
msgctxt "_"
msgid "external ref='figures/drawingarea_thin_lines.png' md5='589cbad88ee60c46503e89c4318822a1'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4963
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/drawingarea/thin_lines\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:4968
msgid "Drawing Curved Lines"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4969
msgid "In addition to drawing straight lines Cairo allows you to easily draw curved lines (technically a cubic Bézier spline) using the <methodname>Cairo::Context::curve_to()</methodname> and <methodname>Cairo::Context::rel_curve_to()</methodname> functions. These functions take coordinates for a destination point as well as coordinates for two 'control' points. This is best explained using an example, so let's dive in."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4981
msgid "This simple application draws a curve with Cairo and displays the control points for each end of the curve."
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:4988
msgctxt "_"
msgid "external ref='figures/drawingarea_curve.png' md5='1a9cdaaad2b17b89d8450f949c1ddef5'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4992
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/drawingarea/curve\">Source Code</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4993
msgid "The only difference between this example and the straight line example is in the <methodname>on_draw()</methodname> function, but there are a few new concepts and functions introduced here, so let's examine them briefly."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:4999
msgid "We make a call to <methodname>Cairo::Context::scale()</methodname>, passing in the width and height of the drawing area. This scales the user-space coordinate system such that the width and height of the widget are both equal to 1.0 'units'. There's no particular reason to scale the coordinate system in this case, but sometimes it can make drawing operations easier."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5008
msgid "The call to <methodname>Cairo::Context::curve_to()</methodname> should be fairly self-explanatory. The first pair of coordinates define the control point for the beginning of the curve. The second set of coordinates define the control point for the end of the curve, and the last set of coordinates define the destination point. To make the concept of control points a bit easier to visualize, a line has been drawn from each control point to the end-point on the curve that it is associated with. Note that these control point lines are both translucent. This is achieved with a variant of <methodname>set_source_rgb()</methodname> called <methodname>set_source_rgba()</methodname>. This function takes a fourth argument specifying the alpha value of the color (valid values are between 0 and 1)."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:5027
msgid "Drawing Arcs and Circles"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5028
msgid "With Cairo, the same function is used to draw arcs, circles, or ellipses: <methodname>Cairo::Context::arc()</methodname>. This function takes five arguments. The first two are the coordinates of the center point of the arc, the third argument is the radius of the arc, and the final two arguments define the start and end angle of the arc. All angles are defined in radians, so drawing a circle is the same as drawing an arc from 0 to 2 * M_PI radians. An angle of 0 is in the direction of the positive X axis (in user-space). An angle of M_PI/2 radians (90 degrees) is in the direction of the positive Y axis (in user-space). Angles increase in the direction from the positive X axis toward the positive Y axis. So with the default transformation matrix, angles increase in a clockwise direction. (Remember that the positive Y axis points downwards.)"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5043
msgid "To draw an ellipse, you can scale the current transformation matrix by different amounts in the X and Y directions. For example, to draw an ellipse with center at <varname>x</varname>, <varname>y</varname> and size <varname>width</varname>, <varname>height</varname>:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:5049
#, no-wrap
msgid ""
"context-&gt;save();\n"
"context-&gt;translate(x, y);\n"
"context-&gt;scale(width / 2.0, height / 2.0);\n"
"context-&gt;arc(0.0, 0.0, 1.0, 0.0, 2 * M_PI);\n"
"context-&gt;restore();"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5057
msgid "Here's an example of a simple program that draws an arc, a circle and an ellipse into a drawing area."
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:5062
msgid "Drawing Area - Arcs"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:5064
msgctxt "_"
msgid "external ref='figures/drawingarea_arcs.png' md5='d94b40e33b9fab7ea9e2c870b97fcf0c'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5068
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/drawingarea/arcs\">Source Code</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5070
msgid "There are a couple of things to note about this example code. Again, the only real difference between this example and the previous ones is the <methodname>on_draw()</methodname> function, so we'll limit our focus to that function. In addition, the first part of the function is nearly identical to the previous examples, so we'll skip that portion."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5078
msgid "Note that in this case, we've expressed nearly everything in terms of the height and width of the window, including the width of the lines. Because of this, when you resize the window, everything scales with the window. Also note that there are three drawing sections in the function and each is wrapped with a <methodname>save()</methodname>/<methodname>restore()</methodname> pair so that we're back at a known state after each drawing."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5087
msgid "The section for drawing an arc introduces one new function, <methodname>close_path()</methodname>. This function will in effect draw a straight line from the current point back to the first point in the path. There is a significant difference between calling <methodname>close_path()</methodname> and manually drawing a line back to the starting point, however. If you use <methodname>close_path()</methodname>, the lines will be nicely joined together. If you use <methodname>line_to()</methodname> instead, the lines will end at the same point, but Cairo won't do any special joining."
msgstr ""

#. (itstool) path: note/title
#: C/index-in.docbook:5100
msgid "Drawing counter-clockwise"
msgstr ""

#. (itstool) path: note/para
#: C/index-in.docbook:5101
msgid "The function <methodname>Cairo::Context::arc_negative()</methodname> is exactly the same as <methodname>Cairo::Context::arc()</methodname> but the angles go the opposite direction."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:5113
msgid "Drawing Text"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:5116
msgid "Drawing Text with Pango"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5117
msgid "Text is drawn via Pango Layouts. The easiest way to create a <classname>Pango::Layout</classname> is to use <methodname>Gtk::Widget::create_pango_layout()</methodname>. Once created, the layout can be manipulated in various ways, including changing the text, font, etc. Finally, the layout can be rendered using the <methodname>Pango::Layout::show_in_cairo_context()</methodname> method."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5130
msgid "Here is an example of a program that draws some text, some of it upside-down. The Printing chapter contains another <link linkend=\"sec-printing-examples\">example</link> of drawing text."
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:5136
msgid "Drawing Area - Text"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:5138
msgctxt "_"
msgid "external ref='figures/drawingarea_pango_text.png' md5='07c39668c9dda2ac1f9455caf6e4d16a'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5142
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/drawingarea/pango_text\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:5154
msgid "Drawing Images"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5155
msgid "There is a method for drawing from a <classname>Gdk::Pixbuf</classname> to a <classname>Cairo::Context</classname>. A <classname>Gdk::Pixbuf</classname> buffer is a useful wrapper around a collection of pixels, which can be read from files, and manipulated in various ways."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5162
msgid "Probably the most common way of creating <classname>Gdk::Pixbuf</classname>s is to use <methodname>Gdk::Pixbuf::create_from_file()</methodname> or <methodname>Gdk::Pixbuf::create_from_resource()</methodname>, which can read an image file, such as a png file into a pixbuf ready for rendering."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5170
msgid "The <classname>Gdk::Pixbuf</classname> can be rendered by setting it as the source pattern of the Cairo context with <methodname>Gdk::Cairo::set_source_pixbuf()</methodname>. Then draw the image with either <methodname>Cairo::Context::paint()</methodname> (to draw the whole image), or <methodname>Cairo::Context::rectangle()</methodname> and <methodname>Cairo::Context::fill()</methodname> (to fill the specified rectangle). <methodname>set_source_pixbuf()</methodname> is not a member of <classname>Cairo::Context</classname>. It takes a <classname>Cairo::Context</classname> as its first parameter."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5181
msgid "Here is a small bit of code to tie it all together: (Note that usually you wouldn't load the image every time in the draw signal handler! It's just shown here to keep it all together.)"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:5186
#, no-wrap
msgid ""
"void MyArea::on_draw(const Cairo::RefPtr&lt;Cairo::Context&gt;&amp; cr, int width, int height)\n"
"{\n"
"  auto image = Gdk::Pixbuf::create_from_file(\"myimage.png\");\n"
"  // Draw the image at 110, 90, except for the outermost 10 pixels.\n"
"  Gdk::Cairo::set_source_pixbuf(cr, image, 100, 80);\n"
"  cr-&gt;rectangle(110, 90, image-&gt;get_width()-20, image-&gt;get_height()-20);\n"
"  cr-&gt;fill();\n"
"}"
msgstr ""

#. (itstool) path: para/screen
#: C/index-in.docbook:5203
#, no-wrap
msgid ""
"$ glib-compile-resources --target=resources.c --generate-source image.gresource.xml"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5197
msgid "Here is an example of a simple program that draws an image. The program loads the image from a resource file. See the <link linkend=\"sec-gio-resource\">Gio::Resource and glib-compile-resources</link> section. Use <application>glib-compile-resources</application> to compile the resources into a C source file that can be compiled and linked with the C++ code. E.g. <_:screen-1/>"
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:5206
msgid "Drawing Area - Image"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:5208
msgctxt "_"
msgid "external ref='figures/drawingarea_image.png' md5='4fbb9f465b7b8b209f295c44dd664d5a'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5212
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/drawingarea/image\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:5226
msgid "Example Application: Creating a Clock with Cairo"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5228
msgid "Now that we've covered the basics of drawing with Cairo, let's try to put it all together and create a simple application that actually does something. The following example uses Cairo to create a custom <classname>Clock</classname> widget. The clock has a second hand, a minute hand, and an hour hand, and updates itself every second."
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:5236
msgctxt "_"
msgid "external ref='figures/cairo_clock.png' md5='fceab985fd70bec94b273f78dd481d31'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5238
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/drawingarea/clock\">Source Code</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5239
msgid "As before, almost all of the interesting stuff is done in the draw function <methodname>on_draw()</methodname>. Before we dig into the draw function, notice that the constructor for the <classname>Clock</classname> widget connects a handler function <methodname>on_timeout()</methodname> to a timer with a timeout period of 1000 milliseconds (1 second). This means that <methodname>on_timeout()</methodname> will get called once per second. The sole responsibility of this function is to invalidate the window so that <application>gtkmm</application> will be forced to redraw it."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5250
msgid "Now let's take a look at the code that performs the actual drawing. The first section of <methodname>on_draw()</methodname> should be pretty familiar by now. This example again scales the coordinate system to be a unit square so that it's easier to draw the clock as a percentage of window size so that it will automatically scale when the window size is adjusted. Furthermore, the coordinate system is scaled over and down so that the (0, 0) coordinate is in the very center of the window."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5260
msgid "The function <methodname>Cairo::Context::paint()</methodname> is used here to set the background color of the window. This function takes no arguments and fills the current surface (or the clipped portion of the surface) with the source color currently active. After setting the background color of the window, we draw a circle for the clock outline, fill it with white, and then stroke the outline in black. Notice that both of these actions use the <methodname>_preserve</methodname> variant to preserve the current path, and then this same path is clipped to make sure that our next lines don't go outside the outline of the clock."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5272
msgid "After drawing the outline, we go around the clock and draw ticks for every hour, with a larger tick at 12, 3, 6, and 9. Now we're finally ready to implement the time-keeping functionality of the clock, which simply involves getting the current values for hours, minutes and seconds, and drawing the hands at the correct angles."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:5284
msgid "The <classname>Gtk::DragSource</classname> and <classname>Gtk::DropTarget</classname> event controllers have methods and signals which are used for Drag and Drop."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:5290
msgid "Sources and Targets"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5291
msgid "Things are dragged from <literal>sources</literal> to be dropped on <literal>targets</literal>. Each source and target has information about the data formats that it can send or receive, provided by <classname>Gdk::ContentFormats</classname>. A drop target will only accept a dragged item if they both share a compatible format. Appropriate signals will then be emitted, telling the signal handlers which format was used."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5299
msgid "<classname>Gdk::ContentFormats</classname> objects contain information about available <type>GType</type>s and mime types (media types)."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5309
msgid "<classname>Widget</classname>s can be identified as sources or targets using <classname>Gtk::DragSource</classname> and <classname>Gtk::DropTarget</classname> event controllers."
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:5314
#, no-wrap
msgid ""
"auto source = Gtk::DragSource::create();\n"
"m_source_widget.add_controller(source);"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:5321
msgid "<literal>void set_content(const Glib::RefPtr&lt;Gdk::ContentProvider&gt;&amp; content)</literal>: Sets a content provider on the drag source."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:5327
msgid "<literal>void set_actions(Gdk::DragAction actions)</literal>: Sets the actions on the drag source. For instance <literal>Gdk::DragAction::COPY | Gdk::DragAction::MOVE</literal>."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:5334
msgid "<literal>void set_icon(const Glib::RefPtr&lt;const Gdk::Paintable&gt;&amp; paintable, int hot_x, int hot_y)</literal>: Sets a paintable to use as icon during DND operations."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5317
msgid "Some <classname>DragSource</classname> methods: <_:itemizedlist-1/>"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:5342
#, no-wrap
msgid ""
"auto target = Gtk::DropTarget::create(gtype, actions);\n"
"m_target_widget.add_controller(target);"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:5349
msgid "<literal>void set_gtypes(const std::vector&lt;GType&gt;&amp; types)</literal>: Sets the supported types for this drop target."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:5355
msgid "<literal>void set_actions(Gdk::DragAction actions)</literal>: Sets the actions that this drop target supports."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:5361
msgid "<literal>Glib::ValueBase get_value() const</literal>: Gets the current drop data, as a <classname>Glib::Value</classname>."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:5367
msgid "<literal>void reject()</literal>: Rejects the ongoing drop operation. This function should be used when delaying the decision on whether to accept a drag or not until after reading the data."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5345
msgid "Some <classname>DropTarget</classname> methods: <_:itemizedlist-1/>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5381
msgid "When a drop target has accepted a dragged item, certain signals will be emitted, depending on what action has been selected. For instance, the user might have held down the <keycap>Shift</keycap> key to specify a <literal>move</literal> rather than a <literal>copy</literal>. Remember that the user can only select the actions which you have specified in your calls to <methodname>Gtk::DragSource::set_actions()</methodname> and <methodname>Gtk::DropTarget::set_actions()</methodname>."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:5394
msgid "<literal>drag_begin</literal>: Provides a <classname>Gdk::Drag</classname>."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:5395
msgid "<literal>prepare</literal>: Shall return a <classname>Gdk::ContentProvider</classname>, with the data to use for the drag that is about to start."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:5397
msgid "<literal>drag_end</literal>: Provides a <classname>Gdk::Drag</classname>, and a <type>bool</type> that tells if the drag was performing a <literal>move</literal> and the data should be deleted."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:5400
msgid "<literal>drag_cancel</literal>: Emitted on the drag source when a drag has failed."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5391
msgid "The source widget will emit these <classname>DragSource</classname> signals: <_:itemizedlist-1/>"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:5406
msgid "<literal>enter</literal>: Provides coordinates. Shall return the preferred <type>Gdk::DragAction</type>."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:5408
msgid "<literal>motion</literal>: Provides coordinates. Shall return the preferred <type>Gdk::DragAction</type>."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:5410
msgid "<literal>leave</literal>: Emitted on the drop site when the pointer leaves the widget."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:5412
msgid "<literal>accept</literal>: Provides a <classname>Gdk::Drop</classname>. You can call the <methodname>status()</methodname> method of the <classname>Gdk::Drop</classname> to indicate which actions will be accepted."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:5415
msgid "<literal>drop</literal>: Provides the data being dropped and coordinates. Shall return a <type>bool</type> indicating whether the drop was accepted."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5403
msgid "The target widget will emit these <classname>DropTarget</classname> signals: <_:itemizedlist-1/>"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:5425
msgid "<methodname>Gtk::DragSource::signal_prepare()</methodname>"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:5426
msgid "<methodname>Gtk::DropTarget::signal_enter()</methodname>"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:5427
msgid "<methodname>Gtk::DropTarget::signal_motion()</methodname>"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:5428
msgid "<methodname>Gtk::DropTarget::signal_accept()</methodname>"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:5429
msgid "<methodname>Gtk::DropTarget::signal_drop()</methodname>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5419
msgid "The following signals call only one signal handler when emitted. When you connect a handler to such a signal, your signal handler must be called before (instead of) the default handler, otherwise it won't be called. Set the <literal>after</literal> parameter in <methodname>connect()</methodname> to <literal>false</literal>. <_:itemizedlist-1/>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5438
msgid "Here is a very simple example, demonstrating a drag and drop <literal>Copy</literal> operation:"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:5443
msgctxt "_"
msgid "external ref='figures/drag_and_drop.png' md5='c13dd8b7faa3d523444c101e42572a10'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5447
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/drag_and_drop\">Source Code</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5449
msgid "There is a more complex example in examples/others/dnd."
msgstr ""

#. (itstool) path: chapter/title
#: C/index-in.docbook:5458
msgid "The Clipboard"
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:5460
msgid "Simple text copy-paste functionality is provided for free by widgets such as <classname>Gtk::Entry</classname> and <classname>Gtk::TextView</classname>, but you might need special code to deal with your own data formats. For instance, a drawing program would need special code to allow copy and paste within a view, or between documents."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:5466
msgid "You can get a clipboard instance with <methodname>Gtk::Widget::get_clipboard()</methodname> or <methodname>Gdk::Display::get_clipboard()</methodname>."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:5471
msgid "Your application doesn't need to wait for clipboard operations, particularly between the time when the user chooses Copy and then later chooses Paste. Many <classname>Gdk::Clipboard</classname> methods take <classname>sigc::slot</classname>s which specify callback methods. When <classname>Gdk::Clipboard</classname> is ready, it will call these methods, providing the requested data."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:5479
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGdk_1_1Clipboard.html\">Reference</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:5482
msgid "Formats"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5484
msgid "Different applications contain different types of data, and they might make that data available in a variety of formats. <application>gtkmm</application> calls these data types <literal>format</literal>s."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5488
msgid "For instance, <application>gedit</application> can supply and receive the <literal>text/plain</literal> mime type, so you can paste data into <application>gedit</application> from any application that supplies that format. Or two different image editing applications might supply and receive a variety of image formats. As long as one application can receive one of the formats that the other supplies then you will be able to copy data from one to the other."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5496
msgid "Clipboard data can be in a variety of binary formats. This chapter, and the examples, assume that the data is 8-bit text. This would allow us to use an XML format for the clipboard data. However this would probably not be appropriate for binary data such as images."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5503
msgid "The <link linkend=\"chapter-draganddrop\">Drag and Drop</link> API uses the same mechanism. You should probably use the same data formats for both Clipboard and Drag and Drop operations."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:5508
msgid "Copy"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5510
msgid "When the user asks to copy some data, you should copy the data to the <classname>Clipboard</classname>. For instance,"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:5514
#, no-wrap
msgid ""
"void ExampleWindow::on_button_copy()\n"
"{\n"
"  get_clipboard()-&gt;set_text(\"example_custom_target\");\n"
"}"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:5522
msgid "Paste"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5524
msgid "When the user asks to paste data from the <classname>Clipboard</classname>, you should request a specific format and provide a callback method which will be called with the actual data. For instance:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:5529
#, no-wrap
msgid ""
"void ExampleWindow::on_button_paste()\n"
"{\n"
"  get_clipboard()-&gt;read_text_async(sigc::mem_fun(*this,\n"
"              &amp;ExampleWindow::on_clipboard_received));\n"
"}"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5535
msgid "Here is an example callback method:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:5537
#, no-wrap
msgid ""
"void ExampleWindow::on_clipboard_received(Glib::RefPtr&lt;Gio::AsyncResult&gt;&amp; result)\n"
"{\n"
"  auto text = get_clipboard()-&gt;read_text_finish(result);\n"
"  //Do something with the pasted data.\n"
"}"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:5544
msgid "Discovering the available formats"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5546
msgid "To find out what formats are currently available on the <classname>Clipboard</classname> for pasting, call the <methodname>get_formats()</methodname> method. Then call a <classname>Gdk::ContentFormats</classname> method to find out if a format that your application supports is available."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:5560
#: C/index-in.docbook:5959
msgid "Simple"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5561
msgid "This example allows copy and pasting of application-specific data, using the standard text format. Although this is simple, it's not ideal because it does not identify the <classname>Clipboard</classname> data as being of a particular type."
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:5569
msgid "Clipboard - Simple"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:5571
msgctxt "_"
msgid "external ref='figures/clipboard_simple.png' md5='9eab8350b743743e1571f1d245aea35c'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5575
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/clipboard/simple/\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:5580
msgid "Ideal"
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:5583
msgid "Defines a custom clipboard target, though the format is still text."
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:5584
msgid "It uses the <methodname>Gdk::ContentFormats::signal_changed()</methodname> signal and disables the Paste button if it can't use anything on the clipboard."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5581
msgid "This is like the simple example, but it <_:orderedlist-1/>"
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:5590
msgid "Clipboard - Ideal"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:5592
msgctxt "_"
msgid "external ref='figures/clipboard_ideal.png' md5='8f284904600e27efa06d39f0741acc2d'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5596
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/clipboard/ideal/\">Source Code</link>"
msgstr ""

#. (itstool) path: chapter/title
#: C/index-in.docbook:5603
msgid "Printing"
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:5605
msgid "At the application development level, <application>gtkmm</application>'s printing API provides dialogs that are consistent across applications and allows use of Cairo's common drawing API, with Pango-driven text rendering. In the implementation of this common API, platform-specific backends and printer-specific drivers are used."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:5611
msgid "PrintOperation"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5613
msgid "The primary object is <classname>Gtk::PrintOperation</classname>, allocated for each print operation. To handle page drawing connect to its signals, or inherit from it and override the default virtual signal handlers. <classname>PrintOperation</classname> automatically handles all the settings affecting the print loop."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:5630
msgid "<literal>begin_print</literal>: You must handle this signal, because this is where you create and set up a <classname>Pango::Layout</classname> using the provided <classname>Gtk::PrintContext</classname>, and break up your printing output into pages."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:5640
msgid "<literal>paginate</literal>: Pagination is potentially slow so if you need to monitor it you can call the <methodname>PrintOperation::set_show_progress()</methodname> method and handle this signal."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:5654
msgid "<literal>request_page_setup</literal>: Provides a <classname>PrintContext</classname>, page number and <classname>Gtk::PageSetup</classname>. Handle this signal if you need to modify page setup on a per-page basis."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:5663
msgid "<literal>draw_page</literal>: You must handle this signal, which provides a <classname>PrintContext</classname> and a page number. The <classname>PrintContext</classname> should be used to create a <classname>Cairo::Context</classname> into which the provided page should be drawn. To render text, iterate over the <classname>Pango::Layout</classname> you created in the <literal>begin_print</literal> handler."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:5649
msgid "For each page that needs to be rendered, the following signals are emitted: <_:itemizedlist-1/>"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:5678
msgid "<literal>end_print</literal>: A handler for it is a safe place to free any resources related to a <classname>PrintOperation</classname>. If you have your custom class that inherits from <classname>PrintOperation</classname>, it is naturally simpler to do it in the destructor."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:5688
msgid "<literal>done</literal>: This signal is emitted when printing is finished, meaning when the print data is spooled. Note that the provided <literal>Gtk::PrintOperation::Result</literal> may indicate that an error occurred. In any case you probably want to notify the user about the final status."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:5698
msgid "<literal>status_changed</literal>: Emitted whenever a print job's status changes, until it is finished. Call the <methodname>PrintOperation::set_track_print_status()</methodname> method to monitor the job status after spooling. To see the status, use <methodname>get_status()</methodname> or <methodname>get_status_string()</methodname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5624
msgid "The <methodname>PrintOperation::run()</methodname> method starts the print loop, during which various signals are emitted: <_:itemizedlist-1/>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5711
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1PrintOperation.html\">Reference</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:5720
msgid "Page setup"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5722
msgid "The <classname>PrintOperation</classname> class has a method called <methodname>set_default_page_setup()</methodname> which selects the default paper size, orientation and margins. To show a page setup dialog from your application, use the <methodname>Gtk::run_page_setup_dialog()</methodname> method, which returns a <classname>Gtk::PageSetup</classname> object with the chosen settings. Use this object to update a <classname>PrintOperation</classname> and to access the selected <classname>Gtk::PaperSize</classname>, <literal>Gtk::PageOrientation</literal> and printer-specific margins."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5732
msgid "You should save the chosen <classname>Gtk::PageSetup</classname> so you can use it again if the page setup dialog is shown again."
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:5736
#, no-wrap
msgid ""
"\n"
"// Within a class that inherits from Gtk::Window and keeps m_refPageSetup\n"
"// and m_refSettings as members...\n"
"auto new_page_setup = Gtk::run_page_setup_dialog(*this, m_refPageSetup, m_refSettings);\n"
"m_refPageSetup = new_page_setup;\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5743
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1PageSetup.html\">Reference</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5747
msgid "The Cairo coordinate system, in the <literal>draw_page</literal> handler, is automatically rotated to the current page orientation. It is normally within the printer margins, but you can change that via the <methodname>PrintOperation::set_use_full_page()</methodname> method. The default measurement unit is device pixels. To select other units, use the <methodname>PrintOperation::set_unit()</methodname> method."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:5759
msgid "Rendering text"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5761
msgid "Text rendering is done using Pango. The <classname>Pango::Layout</classname> object for printing should be created by calling the <methodname>PrintContext::create_pango_layout()</methodname> method. The <classname>PrintContext</classname> object also provides the page metrics, via <methodname>get_width()</methodname> and <methodname>get_height()</methodname>. The number of pages can be set with <methodname>PrintOperation::set_n_pages()</methodname>. To actually render the Pango text in <literal>on_draw_page</literal>, get a <classname>Cairo::Context</classname> with <methodname>PrintContext::get_cairo_context()</methodname> and show the <classname>Pango::LayoutLine</classname>s that appear within the requested page number."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5776
msgid "See <link linkend=\"sec-printing-examples-simple\">an example</link> of exactly how this can be done."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:5784
msgid "Asynchronous operations"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5786
msgid "By default, <methodname>PrintOperation::run()</methodname> returns when a print operation is completed. If you need to run a non-blocking print operation, call <methodname>PrintOperation::set_allow_async()</methodname>. Note that <methodname>set_allow_async()</methodname> is not supported on all platforms, however the <literal>done</literal> signal will still be emitted."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5793
msgid "<methodname>run()</methodname> may return <literal>PrintOperation::Result::IN_PROGRESS</literal>. To track status and handle the result or error you need to implement signal handlers for the <literal>done</literal> and <literal>status_changed</literal> signals:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:5801
#, no-wrap
msgid ""
"\n"
"// in class ExampleWindow's method...\n"
"auto op = PrintOperation::create();\n"
"// ...set up op...\n"
"op-&gt;signal_done().connect(sigc::bind(sigc::mem_fun(\n"
"  *this, &amp;ExampleWindow::on_printoperation_done), op));\n"
"// run the op\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5810
msgid "Second, check for an error and connect to the <literal>status_changed</literal> signal. For instance:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:5812
#, no-wrap
msgid ""
"\n"
"void ExampleWindow::on_printoperation_done(Gtk::PrintOperation::Result result,\n"
"  const Glib::RefPtr&lt;PrintOperation&gt;&amp; op)\n"
"{\n"
"  if (result == Gtk::PrintOperation::Result::ERROR)\n"
"    //notify user\n"
"  else if (result == Gtk::PrintOperation::Result::APPLY)\n"
"    //Update PrintSettings with the ones used in this PrintOperation\n"
"\n"
"  if (! op-&gt;is_finished())\n"
"    op-&gt;signal_status_changed().connect(sigc::bind(sigc::mem_fun(\n"
"      *this, &amp;ExampleWindow::on_printoperation_status_changed), op));\n"
"}\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5827
msgid "Finally, check the status. For instance,"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:5828
#, no-wrap
msgid ""
"\n"
"void ExampleWindow::on_printoperation_status_changed(const Glib::RefPtr&lt;PrintOperation&gt;&amp; op)\n"
"{\n"
"  if (op-&gt;is_finished())\n"
"    //the print job is finished\n"
"  else\n"
"    //get the status with get_status() or get_status_string()\n"
"\n"
"  //update UI\n"
"}\n"
""
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:5843
msgid "Export to PDF"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5845
msgid "The 'Print to file' option is available in the print dialog, without the need for extra implementation. However, it is sometimes useful to generate a pdf file directly from code. For instance,"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:5848
#, no-wrap
msgid ""
"\n"
"auto op = Gtk::PrintOperation::create();\n"
"// ...set up op...\n"
"op-&gt;set_export_filename(\"test.pdf\");\n"
"auto res = op-&gt;run(Gtk::PrintOperation::Action::EXPORT);\n"
""
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:5858
msgid "Extending the print dialog"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:5865
msgid "Set the title of the tab via <methodname>PrintOperation::set_custom_tab_label()</methodname>, create a new widget and return it from the <literal>create_custom_widget</literal> signal handler. You'll probably want this to be a container widget, packed with some others."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:5875
msgid "Get the data from the widgets in the <literal>custom_widget_apply</literal> signal handler."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5860
msgid "You may add a custom tab to the print dialog: <_:itemizedlist-1/>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5883
msgid "Although the <literal>custom_widget_apply</literal> signal provides the widget you previously created, to simplify things you can keep the widgets you expect to contain some user input as class members. For example, let's say you have a <classname>Gtk::Entry</classname> called <literal>m_Entry</literal> as a member of your <classname>CustomPrintOperation</classname> class:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:5890
#, no-wrap
msgid ""
"\n"
"Gtk::Widget* CustomPrintOperation::on_create_custom_widget()\n"
"{\n"
"  set_custom_tab_label(\"My custom tab\");\n"
"\n"
"  auto hbox = new Gtk::Box(Gtk::Orientation::HORIZONTAL, 8);\n"
"  hbox-&gt;set_margin(6);\n"
"\n"
"  auto label = Gtk::make_managed&lt;Gtk::Label&gt;(\"Enter some text: \");\n"
"  hbox-&gt;append(*label);\n"
"\n"
"  hbox-&gt;append(m_Entry);\n"
"\n"
"  return hbox;\n"
"}\n"
"\n"
"void CustomPrintOperation::on_custom_widget_apply(Gtk::Widget* /* widget */)\n"
"{\n"
"  auto user_input = m_Entry.get_text();\n"
"  //...\n"
"}\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5913
msgid "The example in examples/book/printing/advanced demonstrates this."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:5920
msgid "Preview"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5922
msgid "The native GTK print dialog has a preview button, but you may also start a preview directly from an application:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:5926
#, no-wrap
msgid ""
"\n"
"// in a class that inherits from Gtk::Window...\n"
"auto op = PrintOperation::create();\n"
"// ...set up op...\n"
"op-&gt;run(Gtk::PrintOperation::Action::PREVIEW, *this);\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5933
msgid "On Unix, the default preview handler uses an external viewer program. On Windows, the native preview dialog will be shown. If necessary you may override this behavior and provide a custom preview dialog. See the example located in /examples/book/printing/advanced."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:5943
#: C/index-in.docbook:5980
msgid "PrintDialog"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5945
msgid "Since <application>gtkmm</application> 4.14 <classname>Gtk::PrintDialog</classname> is an alternative to <classname>Gtk::PrintOperation</classname>. <classname>PrintDialog</classname> uses the same <classname>PageSetup</classname> and <classname>PrintSettings</classname> classes as <classname>PrintOperation</classname>. The rendering with Cairo and Pango is also similar."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5961
msgid "The following example demonstrates how to print some input from a user interface using <classname>PrintOperation</classname>. It shows how to implement <literal>on_begin_print</literal> and <literal>on_draw_page</literal>, as well as how to track print status and update the print settings."
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:5969
msgid "Printing - Simple"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:5971
msgctxt "_"
msgid "external ref='figures/printing_simple.png' md5='8e7f72103094230cafcd912cb6b34277'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5975
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/printing/simple/\">Source Code</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5982
msgid "The following example demonstrates how to print some input from a user interface using <classname>PrintDialog</classname>. The user interface is similar to the previous example."
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:5989
msgid "Printing - PrintDialog"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:5991
msgctxt "_"
msgid "external ref='figures/printing_printdialog.png' md5='131a217e90587b80335c230cace02a57'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:5995
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/printing/print_dialog/\">Source Code</link>"
msgstr ""

#. (itstool) path: chapter/title
#: C/index-in.docbook:6002
msgid "Recently Used Documents"
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:6004
msgid "<application>gtkmm</application> provides an easy way to manage recently used documents. This functionality is implemented in the <classname>Gtk::RecentManager</classname> class."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:6008
msgid "Each item in the list of recently used files is identified by its URI, and can have associated metadata. The metadata can be used to specify how the file should be displayed, a description of the file, its mime type, which application registered it, whether it's private to the registering application, and several other things."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:6017
msgid "RecentManager"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6018
msgid "<classname>RecentManager</classname> acts as a database of recently used files. You use this class to register new files, remove files from the list, or look up recently used files. There is one list of recently used files per user."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6024
msgid "You can create a new <classname>RecentManager</classname>, but you'll most likely just want to use the default one. You can get a reference to the default <classname>RecentManager</classname> with <methodname>get_default()</methodname>."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:6032
msgid "Adding Items to the List of Recent Files"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6033
msgid "To add a new file to the list of recent documents, in the simplest case, you only need to provide the URI. For example:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:6037
#, no-wrap
msgid ""
"auto recent_manager = Gtk::RecentManager::get_default();\n"
"recent_manager-&gt;add_item(uri);"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6039
msgid "If you want to register a file with metadata, you can pass a <classname>RecentManager::Data</classname> parameter to <methodname>add_item()</methodname>. The metadata that can be set on a particular file item is as follows:"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:6047
msgid "<varname>app_exec</varname>: The command line to be used to launch this resource. This string may contain the \"f\" and \"u\" escape characters which will be expanded to the resource file path and URI respectively"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:6053
msgid "<varname>app_name</varname>: The name of the application that registered the resource"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:6057
msgid "<varname>description</varname>: A short description of the resource as a UTF-8 encoded string"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:6061
msgid "<varname>display_name</varname>: The name of the resource to be used for display as a UTF-8 encoded string"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:6065
msgid "<varname>groups</varname>: A list of groups associated with this item. Groups are essentially arbitrary strings associated with a particular resource. They can be thought of as 'categories' (such as \"email\", \"graphics\", etc) or tags for the resource."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:6071
msgid "<varname>is_private</varname>: Whether this resource should be visible only to applications that have registered it or not"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:6075
msgid "<varname>mime_type</varname>: The MIME type of the resource"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6078
msgid "In addition to adding items to the list, you can also look up items from the list and modify or remove items."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:6085
msgid "Looking up Items in the List of Recent Files"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6086
msgid "To look up recently used files, <classname>RecentManager</classname> provides several functions. To look up a specific item by its URI, you can use the <methodname>lookup_item()</methodname> function, which will return a <classname>RecentInfo</classname> class. If the specified URI did not exist in the list of recent files, <methodname>lookup_item()</methodname> throws a <classname>RecentManagerError</classname> exception. For example:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:6095
#, no-wrap
msgid ""
"Glib::RefPtr&lt;Gtk::RecentInfo&gt; info;\n"
"try\n"
"{\n"
"  info = recent_manager-&gt;lookup_item(uri);\n"
"}\n"
"catch(const Gtk::RecentManagerError&amp; ex)\n"
"{\n"
"  std::cerr &lt;&lt; \"RecentManagerError: \" &lt;&lt; ex.what() &lt;&lt; std::endl;\n"
"}\n"
"if (info)\n"
"{\n"
"  // item was found\n"
"}"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6108
msgid "A <classname>RecentInfo</classname> object is essentially an object containing all of the metadata about a single recently-used file. You can use this object to look up any of the properties listed <link linkend=\"list-file-metadata\">above</link>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6114
msgid "If you don't want to look for a specific URI, but instead want to get a list of all recently used items, <classname>RecentManager</classname> provides the <methodname>get_items()</methodname> function. The return value of this function is a <classname>std::vector</classname> of all recently used files. The following code demonstrates how you might get a list of recently used files:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:6122
#, no-wrap
msgid ""
"auto info_list = recent_manager-&gt;get_items();"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6123
msgid "The maximum age of items in the recently used files list can be set with <methodname>Gtk::Settings::property_gtk_recent_files_max_age()</methodname>. Default value: 30 days."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:6131
msgid "Modifying the List of Recent Files"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6132
msgid "There may be times when you need to modify the list of recent files. For instance, if a file is moved or renamed, you may need to update the file's location in the recent files list so that it doesn't point to an incorrect location. You can update an item's location by using <methodname>move_item()</methodname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6139
msgid "In addition to changing a file's URI, you can also remove items from the list, either one at a time or by clearing them all at once. The former is accomplished with <methodname>remove_item()</methodname>, the latter with <methodname>purge_items()</methodname>."
msgstr ""

#. (itstool) path: note/para
#: C/index-in.docbook:6146
msgid "The functions <methodname>move_item()</methodname>, <methodname>remove_item()</methodname> and <methodname>purge_items()</methodname> have no effect on the actual files that are referred to by the URIs, they only modify the list of recent files."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:6158
msgid "FileChooser and FileDialog"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6160
msgid "<classname>FileChooser</classname> is an interface that can be implemented by widgets displaying a list of files. <application>gtkmm</application> provides three built-in implementations for choosing recent files or other files: <classname>FileChooserWidget</classname>, <classname>FileChooserDialog</classname>, and <classname>FileChooserNative</classname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6169
msgid "<classname>FileChooserWidget</classname> is a simple widget for displaying a list of recently used files or other files. <classname>FileChooserWidget</classname> is the basic building block for <classname>FileChooserDialog</classname>, but you can embed it into your user interface if you want to."
msgstr ""

#. (itstool) path: note/para
#: C/index-in.docbook:6176
msgid "<classname>FileChooser</classname> and the classes that implement it are deprecated since <application>gtkmm</application> 4.10. They have been replaced by <classname>FileDialog</classname>, which is available since <application>gtkmm</application> 4.10."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:6182
msgid "Simple FileDialog example"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6184
msgid "Shown below is a simple example of how to use the <classname>FileDialog</classname> class in a program. This simple program has a menubar with a <guimenuitem>File Dialog</guimenuitem> menu item. When you select this menu item, a dialog pops up showing a list of files. If you select <guimenuitem>Recent</guimenuitem> in the sidebar, the list of recently used files is shown."
msgstr ""

#. (itstool) path: note/para
#: C/index-in.docbook:6194
msgid "If this is the first time you're using a program that uses the Recent Files framework, the dialog may be empty at first. Otherwise it should show the list of recently used documents registered by other applications."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6201
msgid "After selecting the <guimenuitem>File Dialog</guimenuitem> menu item and the <guimenuitem>Recent</guimenuitem> sidebar item, you should see something similar to the following window."
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:6207
msgctxt "_"
msgid "external ref='figures/recentfiles.png' md5='2ca280c98b5c8822ad48ca40f7ce0bb4'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6209
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/recent_files\">Source Code</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6210
msgid "The constructor for <classname>ExampleWindow</classname> creates the menu and the toolbar using <classname>Builder</classname> (see <xref linkend=\"chapter-menus-and-toolbars\"/> for more information). It then adds the menu and the toolbar to the window."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:6218
msgid "Filtering Files"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6219
msgid "For any of the <classname>FileChooser</classname> classes, if you don't wish to display all of the items in the list of files, you can filter the list to show only those that you want. You can filter the list with the help of the <classname>FileFilter</classname> class. This class allows you to filter files by their name (<methodname>add_pattern()</methodname>), or their mime type (<methodname>add_mime_type()</methodname>)."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6228
msgid "After you've created and set up the filter to match only the items you want, you can apply a filter to a chooser widget with the <methodname>FileChooser::add_filter()</methodname> function."
msgstr ""

#. (itstool) path: chapter/title
#: C/index-in.docbook:6238
msgid "Keyboard Events"
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:6239
msgid "Event signals differ in some ways from other signals. These differences are described in the <link linkend=\"sec-eventsignals\">Event signals</link> section in the appendix. Here we will use keyboard events to show how events can be used in a program."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:6246
msgid "Overview"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6248
msgid "Whenever you press or release a key, an event is emitted. You can add an event controller and connect a signal handler to handle such events."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6252
msgid "The event signal handler will receive arguments that depend on the type of event. For key press events the arguments are (<type>guint</type> <varname>keyval</varname>, <type>guint</type> <varname>keycode</varname>, <type>Gdk::ModifierType</type> <varname>state</varname>). As described in the <link linkend=\"sec-eventsignals\">appendix</link>, the key press event signal handler returns a <type>bool</type> value, to indicate that the signal is fully handled (<literal>true</literal>) or allow event propagation (<literal>false</literal>)."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6261
msgid "To determine which key was pressed or released, you read the value of the <varname>keyval</varname> argument and compare it with a constant in the <link xlink:href=\"https://gitlab.gnome.org/GNOME/gtk/tree/main/gdk/gdkkeysyms.h\"> <filename>&lt;gdk/gdkkeysyms.h&gt;</filename></link> header file. The states of modifier keys (shift, ctrl, etc.) are available as bit-flags in <varname>state</varname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6269
#: C/index-in.docbook:9240
msgid "Here's a simple example:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:6272
#, no-wrap
msgid ""
"\n"
"bool MyClass::on_key_pressed(guint keyval, guint, Gdk::ModifierType state)\n"
"{\n"
"  if (keyval == GDK_KEY_1 &amp;&amp;\n"
"    (state &amp; (Gdk::ModifierType::SHIFT_MASK | Gdk::ModifierType::CONTROL_MASK |\n"
"     Gdk::ModifierType::ALT_MASK)) == Gdk::ModifierType::ALT_MASK)\n"
"  {\n"
"    handle_alt_press();\n"
"    return true;\n"
"  }\n"
"  return false;\n"
"}\n"
"\n"
"// in MyClass constructor\n"
"auto controller = Gtk::EventControllerKey::create();\n"
"controller-&gt;signal_key_pressed().connect(\n"
"  sigc::mem_fun(*this, &amp;MyClass::on_key_pressed), false);\n"
"add_controller(controller);\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6295
msgid "In this example there are three keyboard shortcuts: <keycap>Alt</keycap>+<keycap>1</keycap> selects the first radio button, <keycap>Alt</keycap>+<keycap>2</keycap> selects the second one, and the <keycap>Esc</keycap> key hides (closes) the window."
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:6303
msgid "Keyboard Events - Simple"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:6305
msgctxt "_"
msgid "external ref='figures/keyboardevents_simple.png' md5='59e69135f7b646af1a9f528eba13a5df'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6309
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/keyboard_events/simple/\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:6314
msgid "Event Propagation"
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:6320
#: C/index-in.docbook:9280
msgid "Capture phase - runs from the toplevel down to the event widget."
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:6321
#: C/index-in.docbook:9281
msgid "Target phase - runs only on the event widget."
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:6322
#: C/index-in.docbook:9282
msgid "Bubble phase - runs from the event widget up to the toplevel."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6316
msgid "As described in the <link linkend=\"signal-handler-sequence\">appendix</link> event signals are propagated in 3 phases: <_:orderedlist-1/>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6325
msgid "A keyboard event is first sent to the toplevel window (<classname>Gtk::Window</classname>), where it will be checked for any keyboard shortcuts that may be set (accelerator keys and mnemonics, used for selecting menu items from the keyboard). After this (and assuming the event wasn't handled), it is propagated down until it reaches the widget which has keyboard focus. The event will then propagate up until it reaches the top-level widget, or until you stop the propagation by returning <literal>true</literal> from an event handler."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6335
msgid "Notice, that after canceling an event, no other function will be called (even if it is from the same widget)."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6343
msgid "In this example there are 9 <classname>EventControllerKey</classname>s, 3 in each of a <classname>Gtk::Window</classname>, a <classname>Gtk::Box</classname> and a <classname>Gtk::Label</classname>. In each of the widgets there is one event controller for each propagation phase."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6349
msgid "The purpose of this example is to show the steps the event takes when it is emitted."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6352
msgid "When you write in the label, a key press event will be emitted, which will go first, in the capture phase, to the toplevel window (<classname>Gtk::Window</classname>), then down to its child, the box, then to the box's child, the label with the keyboard focus. In the target phase the event goes only to the widget with the keyboard focus (the label). In the bubble phase the event goes first to the widget with the keyboard focus (the label), then to its parent (the box), then to the box's parent (the window). If the event propagates all the way down to the label and then up to the window without being stopped, the text you're writing will appear in the <classname>Label</classname> above the <classname>Label</classname> you're writing in."
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:6367
msgid "Keyboard Events - Event Propagation"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:6369
msgctxt "_"
msgid "external ref='figures/keyboardevents_propagation.png' md5='4250a1b17c413f3243cf11485e7a7bb9'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6373
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/keyboard_events/propagation/\">Source Code</link>"
msgstr ""

#. (itstool) path: chapter/title
#: C/index-in.docbook:6379
msgid "Timeouts, I/O and Idle Functions"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:6382
msgid "Timeouts"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6384
msgid "You may be wondering how to make <application>gtkmm</application> do useful work while it's idling along. Happily, you have several options. Using the following methods you can create a timeout method that will be called every few milliseconds."
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:6390
#, no-wrap
msgid ""
"\n"
"sigc::connection Glib::SignalTimeout::connect(const sigc::slot&lt;bool()&gt;&amp; slot,\n"
"                                      unsigned int interval, int priority = Glib::PRIORITY_DEFAULT);\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6395
msgid "The first argument is a <classname>slot</classname> you wish to have called when the timeout occurs. The second argument is the number of milliseconds between calls to that method. You receive a <classname>sigc::connection</classname> object that can be used to deactivate the connection using its <methodname>disconnect()</methodname> method:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:6403
#, no-wrap
msgid ""
"\n"
"my_connection.disconnect();\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6407
msgid "Another way of destroying the connection is your signal handler. It has to be of the type <classname>sigc::slot&lt;bool()&gt;</classname>. As you see from the definition your signal handler has to return a value of the type <literal>bool</literal>. A definition of a sample method might look like this:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:6415
#, no-wrap
msgid ""
"\n"
"bool MyCallback() { std::cout &lt;&lt; \"Hello World!\\n\" &lt;&lt; std::endl; return true; }\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6419
msgid "You can stop the timeout method by returning <literal>false</literal> from your signal handler. Therefore, if you want your method to be called repeatedly, it should return <literal>true</literal>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6425
msgid "Here's an example of this technique:"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6429
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/timeout/\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:6434
msgid "Monitoring I/O"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6436
msgid "A nifty feature of Glib (one of the libraries underlying <application>gtkmm</application>) is the ability to have it check for data on a file descriptor for you. This is especially useful for networking applications. The following method is used to do this:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:6443
#, no-wrap
msgid ""
"\n"
"sigc::connection Glib::SignalIO::connect(const sigc::slot&lt;bool(Glib::IOCondition)&gt;&amp; slot,\n"
"                                 Glib::PollFD::fd_t fd, Glib::IOCondition condition,\n"
"                                 int priority = Glib::PRIORITY_DEFAULT);\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6449
msgid "The first argument is a slot you wish to have called when the specified event (see argument 3) occurs on the file descriptor you specify using argument two. Argument three may be one or more (using <literal>|</literal>) of:"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:6458
msgid "Glib::IOCondition::IO_IN - Call your method when there is data ready for reading on your file descriptor."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:6464
msgid "Glib::IOCondition::IO_OUT - Call your method when the file descriptor is ready for writing."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:6470
msgid "Glib::IOCondition::IO_PRI - Call your method when the file descriptor has urgent data to be read."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:6475
msgid "Glib::IOCondition::IO_ERR - Call your method when an error has occurred on the file descriptor."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:6480
msgid "Glib::IOCondition::IO_HUP - Call your method when hung up (the connection has been broken usually for pipes and sockets)."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6486
msgid "The return value is a <classname>sigc::connection</classname> that may be used to stop monitoring this file descriptor using its <methodname>disconnect()</methodname> method. The <parameter>slot</parameter> signal handler should be declared as follows:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:6492
#, no-wrap
msgid ""
"\n"
"bool input_callback(Glib::IOCondition condition);\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6496
msgid "where <parameter>condition</parameter> is as specified above. As usual the slot is created with <function>sigc::mem_fun()</function> (for a member method of an object), or <function>sigc::ptr_fun()</function> (for a function). A lambda expression can be used, if you don't need the automatic disconnection that <function>sigc::mem_fun()</function> provides when the object goes out of scope."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6505
msgid "A little example follows. To use the example just execute it from a terminal; it doesn't create a window. It will create a pipe named <literal>testfifo</literal> in the current directory. Then start another shell and execute <literal>echo \"Hello\" &gt; testfifo</literal>. The example will print each line you enter until you execute <literal>echo \"Q\" &gt; testfifo</literal>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6514
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/input/\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:6519
msgid "Idle Functions"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6521
msgid "If you want to specify a method that gets called when nothing else is happening, use the following:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:6525
#, no-wrap
msgid ""
"\n"
"sigc::connection  Glib::SignalIdle::connect(const sigc::slot&lt;bool()&gt;&amp; slot,\n"
"                                    int priority = Glib::PRIORITY_DEFAULT_IDLE);\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6530
msgid "This causes <application>gtkmm</application> to call the specified method whenever nothing else is happening. You can add a priority (lower numbers are higher priorities). There are two ways to remove the signal handler: calling <methodname>disconnect()</methodname> on the <classname>sigc::connection</classname> object, or returning <literal>false</literal> in the signal handler, which should be declared as follows:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:6539
#, no-wrap
msgid ""
"\n"
"bool idleFunc();\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6543
msgid "Since this is very similar to the methods above this explanation should be sufficient to understand what's going on. However, here's a little example:"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6548
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/idle/\">Source Code</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6550
msgid "This example points out the difference of idle and timeout methods a little. If you need methods that are called periodically, and speed is not very important, then you want timeout methods. If you want methods that are called as often as possible (like calculating a fractal in background), then use idle methods."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6558
msgid "Try executing the example and increasing the system load. The upper progress bar will increase steadily; the lower one will slow down."
msgstr ""

#. (itstool) path: chapter/title
#: C/index-in.docbook:6568
msgid "Memory management"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:6574
msgid "Normal C++ memory management"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6576
msgid "<application>gtkmm</application> allows the programmer to control the lifetime (that is, the construction and destruction) of any widget in the same manner as any other C++ object. This flexibility allows you to use <literal>new</literal> and <literal>delete</literal> to create and destroy objects dynamically or to use regular class members (that are destroyed automatically when the class is destroyed) or to use local instances (that are destroyed when the instance goes out of scope). This flexibility is not present in some C++ GUI toolkits, which restrict the programmer to only a subset of C++'s memory management features."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6587
msgid "An important difference in <application>gtkmm</application>-4.0 vs. older versions is that a C++ widgetʼs destruction no longer causes the widget to be destroyed if itʼs within a parent; in that case the C GtkWidget stays alive. If you had relied on that behavior in an older version, in <application>gtkmm</application>-4.0 you must now remove the widget from its parent first. See <link linkend=\"changes-gtkmm4\">Changes in <application>gtkmm</application>-4.0</link>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6594
msgid "Here are some examples of normal C++ memory management:"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:6597
msgid "Class Scope widgets"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6598
msgid "If a programmer does not need dynamic memory allocation, automatic widgets in class scope may be used. One advantage of automatic widgets in class scope is that memory management is grouped in one place. The programmer does not risk memory leaks from failing to <literal>delete</literal> a widget."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6604
msgid "The primary disadvantage of using class scope widgets is revealing the class implementation rather than the class interface in the class header."
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:6608
#, no-wrap
msgid ""
"\n"
"#include &lt;gtkmm/button.h&gt;\n"
"#include &lt;gtkmm/window.h&gt;\n"
"class Foo : public Gtk::Window\n"
"{\n"
"private:\n"
"  Gtk::Button theButton;\n"
"  // will be destroyed when the Foo object is destroyed\n"
"};\n"
""
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:6621
msgid "Function scope widgets"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6622
msgid "If a programmer does not need a class scope widget, a function scope widget may also be used. The advantages to function scope over class scope are the increased data hiding and reduced dependencies."
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:6627
#, no-wrap
msgid ""
"\n"
"{\n"
"  Gtk::Button aButton;\n"
"  aButton.set_visible(true);\n"
"  ...\n"
"  app-&gt;run();\n"
"}\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6635
msgid "However, this technique is rarely useful. Most widgets can't safely be created before the application has been registered or activated. They can't safely be deleted after <methodname>Gtk::Application::run()</methodname> or <methodname>Gtk::Application::make_window_and_run()</methodname> returns."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:6645
msgid "Dynamic allocation with new and delete"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6646
msgid "Usually, the programmer will prefer to allow containers to automatically destroy their children by creating them using <function>Gtk::make_managed()</function> (see below). This is not strictly required, as the <literal>new</literal> and <literal>delete</literal> operators may also be used, but modern C++ style discourages those in favor of safer models of memory management, so it is better to create widgets using <function>Gtk::make_managed()</function> and let their parent destroy them, than to manually perform dynamic allocation."
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:6655
#, no-wrap
msgid ""
"\n"
"auto pButton = new Gtk::Button(\"Test\");\n"
"// do something useful with pButton\n"
"delete pButton;\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6660
msgid "Here, the programmer deletes <varname>pButton</varname> to prevent a memory leak."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:6667
msgid "Managed Widgets"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6669
msgid "Alternatively, you can let a widget's container control when the widget is destroyed. In most cases, you want a widget to last only as long as the container it is in. To delegate the management of a widget's lifetime to its container, create it with <function>Gtk::make_managed()</function> and then pack it into its container with <methodname>Gtk::Box::append()</methodname> or a similar method. Now the widget will be destroyed whenever its container is destroyed."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:6679
msgid "Dynamic allocation with make_managed() and append()"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6681
msgid "<application>gtkmm</application> provides ways including the <function>make_managed()</function> function and <methodname>Gtk::Box::append()</methodname> method to simplify creation and destruction of widgets whose lifetime can be managed by a parent."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6687
msgid "Every widget except a top-level window must be added to a parent container in order to be displayed. The <function>manage()</function> function marks a widget so that when that widget is added to a parent container, said container becomes responsible for deleting the widget, meaning the user no longer needs to do so. The original way to create widgets whose lifetime is managed by their parent in this way was to call <function>manage()</function>, passing in the result of a <literal>new</literal> expression that created a dynamically allocated widget."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6697
msgid "However, usually, when you create such a widget, you will already know that its parent container should be responsible for destroying it. In addition, modern C++ style discourages use of the <literal>new</literal> operator, which was required when passing a newly created widget to <function>manage()</function>. Therefore, <application>gtkmm</application> has added <function>make_managed()</function>, which combines creation and marking with <function>manage()</function> into a single step. This avoids you having to write <literal>new</literal>, which is discouraged in modern C++ style, and more clearly expresses intent to create a managed widget."
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:6708
#, no-wrap
msgid ""
"\n"
"MyContainer::MyContainer()\n"
"{\n"
"  auto pButton = Gtk::make_managed&lt;Gtk::Button&gt;(\"Test\");\n"
"  append(*pButton); //add *pButton to MyContainer\n"
"}\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6715
msgid "Now, when objects of type <classname>MyContainer</classname> are destroyed, the button will also be deleted. It is no longer necessary to delete <varname>pButton</varname> to free the button's memory; its deletion has been delegated to the <classname>MyContainer</classname> object."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6722
msgid "If you never added the widget to any parent container, it's your responsibility to delete it. If you add it to a container widget, and later remove it (for instance with <methodname>Gtk::Box::remove()</methodname>), it's deleted by the container."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6729
msgid "Of course, a top-level container will not be added to another container. The programmer is responsible for destroying the top-level container using one of the traditional C++ techniques. Or you can let <methodname>Gtk::Application::make_window_and_run()</methodname> create a top-level window and delete it when it's hidden."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:6741
msgid "Shared resources"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6743
msgid "Some objects, such as <classname>Gdk::Pixbuf</classname>s and <classname>Pango::Font</classname>s, are obtained from a shared store. Therefore you cannot instantiate your own instances. These classes typically inherit from <classname>Glib::Object</classname>. Rather than requiring you to reference and unreference these objects, <application>gtkmm</application> uses the <classname>Glib::RefPtr&lt;&gt;</classname> smartpointer. Cairomm has its own smartpointer, <classname>Cairo::RefPtr&lt;&gt;</classname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6753
msgid "Objects such as <classname>Gdk::Pixbuf</classname> can only be instantiated with a <methodname>create()</methodname> function. For instance,"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:6757
#, no-wrap
msgid ""
"\n"
"auto pixbuf = Gdk::Pixbuf::create_from_file(filename);\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6761
msgid "You have no way of getting a bare <classname>Gdk::Pixbuf</classname>. In the example, <varname>pixbuf</varname> is a smart pointer, so you can do this, much like a normal pointer:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:6766
#, no-wrap
msgid ""
"\n"
"auto width = 0;\n"
"if(pixbuf)\n"
"{\n"
"  width = pixbuf-&gt;get_width();\n"
"}\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6774
msgid "When <varname>pixbuf</varname> goes out of scope an <methodname>unref()</methodname> will happen in the background and you don't need to worry about it anymore. There's no <literal>new</literal> so there's no <literal>delete</literal>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6780
msgid "If you copy a <classname>RefPtr</classname>, for instance"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:6782
#, no-wrap
msgid ""
"\n"
"auto pixbuf2 = pixbuf;\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6785
msgid "or if you pass it as a method argument or a return type, then <classname>RefPtr</classname> will do any necessary referencing to ensure that the instance will not be destroyed until the last <classname>RefPtr</classname> has gone out of scope."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6790
msgid "See the <link linkend=\"chapter-refptr\">appendix</link> for detailed information about RefPtr."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:6795
msgid "Bjarne Stroustrup, \"The C++ Programming Language\" Fourth Edition - section 34.3"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:6798
msgid "Nicolai M. Josuttis, \"The C++ Standard Library\" - section 4.2"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6791
msgid "If you wish to learn more about smartpointers, you might look in these books: <_:itemizedlist-1/>"
msgstr ""

#. (itstool) path: chapter/title
#: C/index-in.docbook:6809
msgid "Gtk::Builder"
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:6811
msgid "Although you can use C++ code to instantiate and arrange widgets, this can soon become tedious and repetitive. And it requires a recompilation to show changes. The <link xlink:href=\"https://gitlab.gnome.org/jpu/cambalache\">Cambalache</link> application allows you to layout widgets on screen and then save an XML description of the arrangement. Your application can then use the <application>Gtk::Builder</application> API to load that XML file at runtime and obtain a pointer to specifically named widget instances."
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:6824
msgid "Less C++ code is required."
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:6825
msgid "UI changes can be seen more quickly, so UIs are able to improve."
msgstr ""

#. (itstool) path: listitem/simpara
#: C/index-in.docbook:6826
msgid "Designers without programming skills can create and edit UIs."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:6821
msgid "This has the following advantages: <_:orderedlist-1/>"
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:6830
msgid "You still need C++ code to deal with User Interface changes triggered by user actions, but using <application>Gtk::Builder</application> for the widget layout allows you to focus on implementing that functionality."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:6836
msgid "<application>Cambalache</application> replaces the <application>Glade</application> application. <application>Glade</application> can generate XML files to be used with gtk3/<application>gtkmm</application>3, but it does not support gtk4/<application>gtkmm</application>4."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:6843
msgid "Loading the .ui file"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6845
msgid "<classname>Gtk::Builder</classname> must be used via a <classname>Glib::RefPtr</classname>. Like all such classes, you need to use a <methodname>create()</methodname> method to instantiate it. For instance,"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:6849
#, no-wrap
msgid ""
"\n"
"auto builder = Gtk::Builder::create_from_file(\"basic.ui\");\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6852
msgid "This will instantiate the windows defined in the <filename class=\"extension\">.ui</filename> file."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6855
msgid "To instantiate just one window, or just one of the child widgets, you can specify the name of a widget as the second parameter. For instance,"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:6857
#, no-wrap
msgid ""
"\n"
"auto builder = Gtk::Builder::create_from_file(\"basic.ui\", \"treeview_products\");\n"
""
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:6864
msgid "Accessing widgets"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6866
msgid "To access a widget, for instance to show a dialog, use the <methodname>get_widget()</methodname> method, providing the widget's name. This name should be specified in the <application>Cambalache</application> window. If the widget could not be found, or is of the wrong type, then the pointer will be set to <literal>nullptr</literal>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6873
msgid "The dialogs in this chapter are derived from <classname>Gtk::Window</classname> because <classname>Gtk::Dialog</classname> is deprecated since <application>gtkmm</application> 4.10."
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:6877
#, no-wrap
msgid ""
"\n"
"auto pDialog = builder-&gt;get_widget&lt;Gtk::Window&gt;(\"DialogBasic\");\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6881
msgid "<classname>Gtk::Builder</classname> checks for a null pointer, and checks that the widget is of the expected type, and will show warnings on the command line about these."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6887
msgid "Remember that you are not instantiating a widget with <methodname>get_widget()</methodname>, you are just obtaining a pointer to one that already exists. You will always receive a pointer to the same instance when you call <methodname>get_widget()</methodname> on the same <classname>Gtk::Builder</classname>, with the same widget name. The widgets are instantiated during <methodname>Gtk::Builder::create_from_file()</methodname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6896
msgid "<methodname>get_widget()</methodname> returns child widgets that are <function>manage()</function>ed (see the <link linkend=\"chapter-memory\">Memory Management</link> chapter), so they will be deleted when their parent container is deleted. <classname>Window</classname>s (such as <classname>Dialog</classname>s) cannot be managed because they have no parent container, so you must delete them at some point. The documentation of <classname>Gtk::Builder</classname> has more to say about the memory management of different kinds of objects."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6906
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1Builder.html\">Reference</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6911
msgid "This simple example shows how to load a <filename class=\"extension\">.ui</filename> file at runtime and access the widgets with <classname>Gtk::Builder</classname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6916
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/builder/basic\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:6923
msgid "Using derived widgets"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6925
msgid "You can use <application>Cambalache</application> and <classname>Gtk::Builder</classname> to layout your own custom widgets derived from <application>gtkmm</application> widget classes. This keeps your code organized and encapsulated, separating declarative presentation from business logic, avoiding having most of your source just be setting properties and packing in containers."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6933
msgid "Use <methodname>Gtk::Builder::get_widget_derived()</methodname> like so:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:6935
#, no-wrap
msgid ""
"\n"
"auto pDialog = Gtk::Builder::get_widget_derived&lt;DerivedDialog&gt;(builder, \"DialogDerived\");\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6939
msgid "Your derived class must have a constructor that takes a pointer to the underlying C type, and the <classname>Gtk::Builder</classname> instance. All relevant classes of <application>gtkmm</application> typedef their underlying C type as <classname>BaseObjectType</classname> (<classname>Gtk::Window</classname> typedefs <classname>BaseObjectType</classname> as <type>GtkWindow</type>, for instance)."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6946
msgid "You must call the base class's constructor in the initialization list, providing the C pointer. For instance,"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:6950
#, no-wrap
msgid ""
"\n"
"DerivedDialog::DerivedDialog(BaseObjectType* cobject, const Glib::RefPtr&lt;Gtk::Builder&gt;&amp; builder)\n"
": Gtk::Window(cobject)\n"
"{\n"
"}\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6957
msgid "You could then encapsulate the manipulation of the child widgets in the constructor of the derived class, maybe using <methodname>get_widget()</methodname> or <methodname>get_widget_derived()</methodname> again. For instance,"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:6962
#, no-wrap
msgid ""
"\n"
"DerivedDialog::DerivedDialog(BaseObjectType* cobject, const Glib::RefPtr&lt;Gtk::Builder&gt;&amp; builder)\n"
": Gtk::Window(cobject),\n"
"  m_builder(builder),\n"
"  // Get the GtkBuilder-instantiated Button, and connect a signal handler:\n"
"  m_pButton(m_builder-&gt;get_widget&lt;Gtk::Button&gt;(\"quit_button\"))\n"
"{\n"
"  if (m_pButton)\n"
"  {\n"
"    m_pButton-&gt;signal_clicked().connect( sigc::mem_fun(*this, &amp;DerivedDialog::on_button_quit) );\n"
"  }\n"
"}\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6976
msgid "It's possible to pass additional arguments from <methodname>get_widget_derived()</methodname> to the constructor of the derived widget. For instance, this call to <methodname>get_widget_derived()</methodname>"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:6981
#, no-wrap
msgid ""
"\n"
"auto pDialog = Gtk::Builder::get_widget_derived&lt;DerivedDialog&gt;(builder, \"DialogDerived\", true);\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:6984
msgid "can invoke this constructor"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:6986
#, no-wrap
msgid ""
"\n"
"DerivedDialog::DerivedDialog(BaseObjectType* cobject,\n"
"  const Glib::RefPtr&lt;Gtk::Builder&gt;&amp; builder, bool warning)\n"
": Gtk::Window(cobject),\n"
"  m_builder(builder),\n"
"  m_pButton(m_builder-&gt;get_widget&lt;Gtk::Button&gt;(\"quit_button\"))\n"
"{\n"
"  // ....\n"
"}\n"
""
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:6998
msgid "Gtk::Builder and Glib::Property"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7000
msgid "If your derived widget uses <classname>Glib::Property</classname>, it becomes slightly more complicated. A derived widget that contains <classname>Glib::Property</classname> members must be registered with its own name in the <type>GType</type> system. It must be registered before any of the <methodname>create_from_*()</methodname> or <methodname>add_from_*()</methodname> methods are called, meaning that you may have to create an instance of your derived widget just to have its class registered. Your derived widget must have a constructor that has the parameters required by <methodname>get_widget_derived()</methodname> and calls the <classname>Glib::ObjectBase</classname> constructor to register the <type>GType</type>."
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:7011
#, no-wrap
msgid ""
"\n"
"DerivedButton::DerivedButton(BaseObjectType* cobject, const Glib::RefPtr&lt;Gtk::Builder&gt;&amp; builder)\n"
": Glib::ObjectBase(\"MyButton\"), // The GType name will be gtkmm__CustomObject_MyButton.\n"
"  Gtk::Button(cobject),\n"
"  prop_ustring(*this, \"button-ustring\"),\n"
"  prop_int(*this, \"button-int\", 10)\n"
"{\n"
"  // ....\n"
"}\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7021
msgid "It is possible also to specify properties of derived widgets, declared in C++ using <application>gtkmm</application>, within <filename class=\"extension\">.ui</filename> files and load/set these using <classname>Gtk::Builder</classname>. See the documentation of <classname>Gtk::Builder</classname> for more details on how to achieve this. <application>Cambalache</application> won’t recognize such properties as-is, but you should be able to add a few lines of hand-coded XML to the XML code generated by <application>Cambalache</application>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7035
msgid "This example shows how to load a <filename class=\"extension\">.ui</filename> file at runtime and access the widgets via derived classes."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7040
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/builder/derived\">Source Code</link>"
msgstr ""

#. (itstool) path: chapter/title
#: C/index-in.docbook:7049
msgid "Internationalization and Localization"
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:7051
msgid "<application>gtkmm</application> applications can easily support multiple languages, including non-European languages such as Chinese and right-to-left languages such as Arabic. An appropriately-written and translated <application>gtkmm</application> application will use the appropriate language at runtime based on the user's environment."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:7057
msgid "You might not anticipate the need to support additional languages, but you can never rule it out. And it's easier to develop the application properly in the first place rather than retrofitting later."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:7063
msgid "The process of writing source code that allows for translation is called <literal>internationalization</literal>, often abbreviated to <literal>i18n</literal>. The <literal>Localization</literal> process, sometimes abbreviated as <literal>l10n</literal>, provides translated text for other languages, based on that source code."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:7071
msgid "The main activity in the internationalization process is finding strings seen by users and marking them for translation. You do not need to do it all at once - if you set up the necessary project infrastructure correctly then your application will work normally regardless of how many strings you've covered."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:7079
msgid "String literals should be typed in the source code in English, but surrounded by a macro. The <application>gettext</application> (or intltool) utility can then extract the marked strings for translation, and substitute the translated text at runtime."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:7087
msgid "Preparing your project"
msgstr ""

#. (itstool) path: note/para
#: C/index-in.docbook:7090
msgid "In the instructions below we will assume that you will not be using <application>gettext</application> directly, but <application>intltool</application>, which was written specifically for <literal>GNOME</literal>. <application>intltool</application> uses <function>gettext()</function>, which extracts strings from source code, but <application>intltool</application> can also combine strings from other files, for example from desktop menu details, and GUI resource files such as <filename class=\"extension\">.ui</filename> files, into standard <application>gettext</application> <filename>.pot/.po</filename> files."
msgstr ""

#. (itstool) path: note/para
#: C/index-in.docbook:7101
msgid "We also assume that you are using autotools (<application>automake</application> and <application>autoconf</application>) to build your project (although autotools is not recommended for new applications), and that you are using <link xlink:href=\"https://gitlab.gnome.org/GNOME/gnome-common/blob/master/autogen.sh\"> <literal>./autogen.sh</literal> from <application>gnome-common</application></link> or a similar <literal>autogen.sh</literal> file, which, among other things, takes care of some <application>intltool</application> initialization."
msgstr ""

#. (itstool) path: note/para
#: C/index-in.docbook:7113
msgid "If you are using <application>meson</application> (recommended), see the <link xlink:href=\"https://mesonbuild.com/Localisation.html\">Localisation</link> chapter in Meson's manual. You can then skip this section."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7120
msgid "An alternative to <application>gnome-common</application>'s <literal>autogen.sh</literal> may look like this:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:7124
#, no-wrap
msgid ""
"#! /bin/sh -e\n"
"test -n \"$srcdir\" || srcdir=`dirname \"$0\"`\n"
"test -n \"$srcdir\" || srcdir=.\n"
"\n"
"autoreconf --force --install --verbose --warnings=all \"$srcdir\"\n"
"echo \"Running intltoolize --copy --force --automake\"\n"
"intltoolize --copy --force --automake\n"
"test -n \"$NOCONFIGURE\" || \"$srcdir/configure\" \"$@\""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7133
msgid "Create a sub-directory named <literal>po</literal> in your project's root directory. This directory will eventually contain all of your translations. Within it, create a file named <literal>LINGUAS</literal> and a file named <literal>POTFILES.in</literal>. It is common practice to also create a <literal>ChangeLog</literal> file in the <literal>po</literal> directory so that translators can keep track of translation changes."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7143
msgid "<literal>LINGUAS</literal> contains an alphabetically sorted list of codes identifying the languages for which your program is translated (comment lines starting with a <literal>#</literal> are ignored). Each language code listed in the <literal>LINGUAS</literal> file must have a corresponding <literal>.po</literal> file. So, if your program has German and Japanese translations, your <literal>LINGUAS</literal> file would look like this:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:7152
#, no-wrap
msgid ""
"# keep this file sorted alphabetically, one language code per line\n"
"de\n"
"ja"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7155
msgid "(In addition, you'd have the files <literal>de.po</literal> and <literal>ja.po</literal> in your <literal>po</literal> directory which contain the German and Japanese translations, respectively.)"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7162
msgid "<literal>POTFILES.in</literal> is a list of paths to all files which contain strings marked up for translation, starting from the project root directory. So for example, if your project sources were located in a subdirectory named <literal>src</literal>, and you had two files that contained strings that should be translated, your <literal>POTFILES.in</literal> file might look like this:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:7171
#, no-wrap
msgid ""
"src/main.cc\n"
"src/other.cc"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7174
msgid "If you are using <application>gettext</application> directly, you can only mark strings for translation if they are in source code file. However, if you use <application>intltool</application>, you can mark strings for translation in a variety of other file formats, including <filename class=\"extension\">.ui</filename> files, xml, <link xlink:href=\"http://standards.freedesktop.org/desktop-entry-spec/latest/\">.desktop files</link> and several more. So, if you have designed some of the application UI in xml files then also add your <filename class=\"extension\">.ui</filename> files to the list in <literal>POTFILES.in</literal>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7187
msgid "Now that there is a place to put your translations, you need to initialize <application>intltool</application> and <application>gettext</application>. Add the following code to your <literal>configure.ac</literal>, substituting 'programname' with the name of your program:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:7194
#, no-wrap
msgid ""
"IT_PROG_INTLTOOL([0.35.0])\n"
"\n"
"GETTEXT_PACKAGE=programname\n"
"AC_SUBST(GETTEXT_PACKAGE)\n"
"AC_DEFINE_UNQUOTED([GETTEXT_PACKAGE], [\"$GETTEXT_PACKAGE\"],\n"
"                   [The domain to use with gettext])\n"
"AM_GNU_GETTEXT([external])\n"
"AM_GNU_GETTEXT_VERSION([0.17])\n"
"\n"
"PROGRAMNAME_LOCALEDIR=[${datadir}/locale]\n"
"AC_SUBST(PROGRAMNAME_LOCALEDIR)"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7206
msgid "This <varname>PROGRAMNAME_LOCALEDIR</varname> variable will be used later in the <literal>Makefile.am</literal> file, to define a macro that will be used when you initialize <application>gettext</application> in your source code."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7213
msgid "<literal>AM_GLIB_GNU_GETTEXT</literal> has been an alternative to <literal>AM_GNU_GETTEXT</literal> and <literal>AM_GNU_GETTEXT_VERSION</literal>, but <literal>AM_GLIB_GNU_GETTEXT</literal> is now deprecated, and shall not be used in new code."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:7224
msgid "Add <literal>po</literal> to the <literal>SUBDIRS</literal> variable. Without this, your translations won't get built and installed when you build the program"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:7229
msgid "Define <literal>INTLTOOL_FILES</literal> as:"
msgstr ""

#. (itstool) path: listitem/programlisting
#: C/index-in.docbook:7231
#, no-wrap
msgid ""
"INTLTOOL_FILES = intltool-extract.in \\\n"
"                 intltool-merge.in \\\n"
"                 intltool-update.in"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:7236
msgid "Add <literal>INTLTOOL_FILES</literal> to the <literal>EXTRA_DIST</literal> list of files. This ensures that when you do a <command>make dist</command>, these files will be included in the source tarball."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:7244
msgid "Update your <literal>DISTCLEANFILES</literal>:"
msgstr ""

#. (itstool) path: listitem/programlisting
#: C/index-in.docbook:7246
#, no-wrap
msgid ""
"DISTCLEANFILES = ... intltool-extract \\\n"
"                 intltool-merge \\\n"
"                 intltool-update \\\n"
"                 po/.intltool-merge-cache"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:7252
msgid "Depending on the types of files that contain translatable strings, add code such as"
msgstr ""

#. (itstool) path: listitem/programlisting
#: C/index-in.docbook:7255
#, no-wrap
msgid ""
"desktopdir = $(datadir)/applications\n"
"desktop_in_files = programname.desktop.in\n"
"desktop_DATA = $(desktop_in_files:.desktop.in=.desktop)\n"
"@INTLTOOL_DESKTOP_RULE@"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7220
msgid "In the top-level Makefile.am: <_:itemizedlist-1/>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7263
msgid "In your <literal>src/Makefile.am</literal>, update your <literal>AM_CPPFLAGS</literal> to add the following preprocessor macro definition:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:7268
#, no-wrap
msgid ""
"AM_CPPFLAGS = ... -DPROGRAMNAME_LOCALEDIR=\\\"${PROGRAMNAME_LOCALEDIR}\\\""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7269
msgid "This macro will be used when you initialize <literal>gettext</literal> in your source code."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:7276
msgid "Marking strings for translation"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7278
msgid "String literals should be typed in the source code in English, but they should be surrounded by a call to the <function>gettext()</function> function. These strings will be extracted for translation and the translations may be used at runtime instead of the original English strings."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7286
msgid "The <application>GNU gettext</application> package allows you to mark strings in source code, extract those strings for translation, and use the translated strings in your application."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7292
msgid "However, <application>Glib</application> defines <function>gettext()</function> support macros which are shorter wrappers in an easy-to-use form. To use these macros, include <literal>&lt;glibmm/i18n.h&gt;</literal>, and then, for example, substitute:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:7298
#, no-wrap
msgid ""
"display_message(\"Getting ready for i18n.\");"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7299
msgid "with:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:7300
#, no-wrap
msgid ""
"display_message(_(\"Getting ready for i18n.\"));"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7302
msgid "For reference, it is possible to generate a file which contains all strings which appear in your code, even if they are not marked for translation, together with file name and line number references. To generate such a file named <literal>my-strings</literal>, execute the following command, within the source code directory:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:7311
#, no-wrap
msgid ""
"xgettext -a -o my-strings --omit-header *.cc *.h"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7313
msgid "Finally, to let your program use the translation for the current locale, add this code to the beginning of your <filename>main.cc</filename> file, to initialize gettext."
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:7318
#, no-wrap
msgid ""
"bindtextdomain(GETTEXT_PACKAGE, PROGRAMNAME_LOCALEDIR);\n"
"bind_textdomain_codeset(GETTEXT_PACKAGE, \"UTF-8\");\n"
"textdomain(GETTEXT_PACKAGE);"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:7323
msgid "How gettext works"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7325
msgid "The <application>intltool-update</application> or <application>xgettext</application> script extracts the strings and puts them in a <filename>mypackage.pot</filename> file. The translators of your application create their translations by first copying this <filename>.pot</filename> file to a <filename>localename.po</filename> file. A locale identifies a language and an encoding for that language, including date and numerical formats. Later, when the text in your source code has changed, the <application>msgmerge</application> or <application>intltool-update</application> script is used to update the <filename>localename.po</filename> files from the regenerated <filename>.pot</filename> file."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7339
msgid "At install time, the <filename>.po</filename> files are converted to a binary format (with the extension <filename>.mo</filename>) and placed in a system-wide directory for locale files, for example <filename>/usr/share/locale/</filename>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7346
msgid "When the application runs, the <application>gettext</application> library checks the system-wide directory to see if there is a <filename>.mo</filename> file for the user's locale environment (you can set the locale with, for instance, \"export LANG=de_DE.UTF-8\" from a bash console). Later, when the program reaches a <literal>gettext</literal> call, it looks for a translation of a particular string. If none is found, the original string is used."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:7358
msgid "Testing and adding translations"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7360
msgid "To convince yourself that you've done well, you may wish to add a translation for a new locale. In order to do that, go to the <filename>po</filename> subdirectory of your project and execute the following command:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:7366
#, no-wrap
msgid ""
"intltool-update --pot"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7368
msgid "That will create a file named <filename>programname.pot</filename>. Now copy that file to <filename>languagecode.po</filename>, such as <filename>de.po</filename> or <filename>hu.po</filename>. Also add that language code to <literal>LINGUAS</literal>. The <filename>.po</filename> file contains a header and a list of English strings, with space for the translated strings to be entered. Make sure you set the encoding of the <filename>.po</filename> file (specified in the header, but also as content) to <literal>UTF-8</literal>."
msgstr ""

#. (itstool) path: note/para
#: C/index-in.docbook:7381
msgid "It's possible that certain strings will be marked as <literal>fuzzy</literal> in the <filename>.po</filename> file. These translations will not substitute the original string. To make them appear, simply remove the <literal>fuzzy</literal> tag. A <literal>fuzzy</literal> tag appears if a string content changed, but the location is still the same."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:7393
msgid "Resources"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:7401
msgid "<link xlink:href=\"https://wiki.gnome.org/TranslationProject/DevGuidelines\"> L10N Guidelines for Developers</link>"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:7408
msgid "<link xlink:href=\"http://bazaar.launchpad.net/~intltool/intltool/trunk/view/head:/README\">Intltool README</link>"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:7414
msgid "<link xlink:href=\"https://wiki.gnome.org/TranslationProject/GitHowTo\">How to use Git for GNOME translators</link>"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:7420
msgid "<link xlink:href=\"http://www.gnu.org/software/gettext/manual/gettext.html\">gettext manual</link>"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:7426
msgid "<link xlink:href=\"http://ftp.gnome.org/pub/GNOME/sources/gtkmm_hello/\"><literal>gtkmm_hello</literal> example package</link>"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:7432
msgid "<link xlink:href=\"http://ftp.gnome.org/pub/GNOME/sources/gnomemm_hello/\"><literal>gnomemm_hello</literal> example package</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7395
msgid "More information about what lies behind the internationalization and localization process is presented and demonstrated in: <_:itemizedlist-1/>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:7443
msgid "Expecting UTF8"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7445
msgid "A properly internationalized application will not make assumptions about the number of bytes in a character. That means that you shouldn't use pointer arithmetic to step through the characters in a string, and it means you shouldn't use <classname>std::string</classname> or standard C functions such as <function>strlen()</function> because they make the same assumption."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7452
msgid "However, you probably already avoid bare char* arrays and pointer arithmetic by using <classname>std::string</classname>, so you just need to start using <classname>Glib::ustring</classname> instead. See the <link linkend=\"sec-basics-ustring\">Basics</link> chapter about <classname>Glib::ustring</classname>."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:7460
msgid "Glib::ustring and std::iostreams"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7463
msgid "Unfortunately, the integration with the standard iostreams is not completely foolproof. <application>gtkmm</application> converts <classname>Glib::ustring</classname>s to a locale-specific encoding (which usually is not UTF-8) if you output them to an <classname>ostream</classname> with <function>operator&lt;&lt;</function>. Likewise, retrieving <classname>Glib::ustring</classname>s from <classname>istream</classname> with <function>operator&gt;&gt;</function> causes a conversion in the opposite direction. But this scheme breaks down if you go through a <classname>std::string</classname>, e.g. by inputting text from a stream to a <classname>std::string</classname> and then implicitly converting it to a <classname>Glib::ustring</classname>. If the string contained non-ASCII characters and the current locale is not UTF-8 encoded, the result is a corrupted <classname>Glib::ustring</classname>. You can work around this with a manual conversion. For instance, to retrieve the <classname>std::string</classname> from a <classname>ostringstream</classname>:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:7479
#, no-wrap
msgid ""
"std::locale::global(std::locale(\"\")); // Set the global locale to the user's preferred locale.\n"
"                                      // Usually unnecessary here, because Glib::init()\n"
"                                      // or Gtk::Application::create() does it for you.\n"
"std::ostringstream output;\n"
"output &lt;&lt; percentage &lt;&lt; \" % done\";\n"
"label-&gt;set_text(Glib::locale_to_utf8(output.str()));"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:7490
msgid "Pitfalls"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7492
msgid "There are a few common mistakes that you would discover eventually yourself. But this section might help you to avoid them."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:7495
msgid "Same strings, different semantics"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7497
msgid "Sometimes two English strings are identical but have different meanings in different contexts, so they would probably not be identical when translated. Since the English strings are used as look-up keys, this causes problems."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7501
msgid "In these cases, you should add extra characters to the strings. For instance, use <literal>\"jumps[noun]\"</literal> and <literal>\"jumps[verb]\"</literal> instead of just <literal>\"jumps\"</literal> and strip them again outside the <function>gettext</function> call. If you add extra characters you should also add a comment for the translators before the <function>gettext</function> call. Such comments will be shown in the <filename>.po</filename> files. For instance:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:7510
#, no-wrap
msgid ""
"// note to translators: don't translate the \"[noun]\" part - it is\n"
"// just here to distinguish the string from another \"jumps\" string\n"
"text = strip(gettext(\"jumps[noun]\"), \"[noun]\");"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7514
msgid "If you use <application>Glib</application>'s support macros, it's easier. Use <function>C_()</function> instead of <function>_()</function>. For instance:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:7518
#, no-wrap
msgid ""
"GLib::ustring text(C_(\"noun\", \"jumps\"));"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:7523
msgid "Composition of strings"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7525
msgid "C programmers use <function>sprintf()</function> to compose and concatenate strings. C++ favors streams, but unfortunately, this approach makes translation difficult, because each fragment of text is translated separately, without allowing the translators to rearrange them according to the grammar of the language."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7532
msgid "For instance, this code would be problematic:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:7534
#, no-wrap
msgid ""
"std::cout &lt;&lt; _(\"Current amount: \") &lt;&lt; amount\n"
"          &lt;&lt; _(\" Future: \") &lt;&lt; future &lt;&lt; std::endl;\n"
"\n"
"label.set_text(_(\"Really delete \") + filename + _(\" now?\"));"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7539
msgid "So you should either avoid this situation or use <link xlink:href=\"https://gnome.pages.gitlab.gnome.org/glibmm/classGlib_1_1ustring.html\"><function>Glib::ustring::compose()</function></link> which supports syntax such as:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:7544
#, no-wrap
msgid ""
"std::cout &lt;&lt; Glib::ustring::compose(\n"
"             _(\"Current amount: %1 Future: %2\"), amount, future) &lt;&lt; std::endl;\n"
"\n"
"label.set_text(Glib::ustring::compose(_(\"Really delete %1 now?\"), filename));"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:7551
msgid "Assuming the displayed size of strings"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7553
msgid "You never know how much space a string will take on screen when translated. It might very possibly be twice the size of the original English string. Luckily, most <application>gtkmm</application> widgets will expand at runtime to the required size."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:7557
msgid "Unusual words"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7559
msgid "You should avoid cryptic abbreviations, slang, or jargon. They are usually difficult to translate, and are often difficult for even native speakers to understand. For instance, prefer \"application\" to \"app\""
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:7565
msgid "Using non-ASCII characters in strings"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7567
msgid "Currently, <application>gettext</application> does not support non-ASCII characters (i.e. any characters with a code above 127) in source code. For instance, you cannot use the copyright sign (©)."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7573
msgid "To work around this, you could write a comment in the source code just before the string, telling the translators to use the special character if it is available in their languages. For English, you could then make an American English <filename>en_US.po</filename> translation which used that special character."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:7581
msgid "Getting help with translations"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7583
msgid "If your program is free software, there is a whole <literal>GNOME</literal> subproject devoted to helping you make translations, the <link xlink:href=\"https://wiki.gnome.org/TranslationProject/\"><literal>GNOME</literal> Translation Project</link>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7588
msgid "The way it works is that you upload your source code to a git repository where translators can access it, then contact the gnome-i18n mailing list and ask to have your program added to the <link xlink:href=\"http://l10n.gnome.org/module/\">list of modules to translate</link>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7593
msgid "Then you make sure you update the file <filename>POTFILES.in</filename> in the <filename>po/</filename> subdirectory (<command>intltool-update -m</command> can help with this) so that the translators always access updated <filename>myprogram.pot</filename> files, and simply freeze the strings at least a couple of days before you make a new release, announcing it on gnome-i18n. Depending on the number of strings your program contains and how popular it is, the translations will then start to tick in as <filename>languagename.po</filename> files."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7605
msgid "Note that most language teams only consist of 1-3 persons, so if your program contains a lot of strings, it might last a while before anyone has the time to look at it. Also, most translators do not want to waste their time (translating is a very time-consuming task) so if they do not assess your project as being really serious (in the sense that it is polished and being maintained) they may decide to spend their time on some other project."
msgstr ""

#. (itstool) path: chapter/title
#. (itstool) path: section/title
#: C/index-in.docbook:7617
#: C/index-in.docbook:7699
msgid "Custom Widgets"
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:7619
msgid "<application>gtkmm</application> makes it very easy to derive new widgets by inheriting from an existing widget class, either by deriving from a container and adding child widgets, or by deriving from a single-item widget, and changing its behavior. But you might occasionally find that no suitable starting point already exists. In this case, you can implement a widget from scratch."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:7626
msgid "Custom Containers"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:7631
msgid "<methodname>get_request_mode_vfunc()</methodname>: Return what <literal>Gtk::SizeRequestMode</literal> is preferred by the container."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:7632
msgid "<methodname>measure_vfunc()</methodname>: Calculate the minimum and natural width or height of the container."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:7633
msgid "<methodname>size_allocate_vfunc()</methodname>: Position the child widgets, given the height and width that the container has actually been given."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7628
msgid "When deriving a custom container widget directly from <classname>Gtk::Widget</classname>, you should override the following virtual methods: <_:itemizedlist-1/>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7637
msgid "The <methodname>get_request_mode_vfunc()</methodname>, <methodname>measure_vfunc()</methodname>, and <methodname>size_allocate_vfunc()</methodname> virtual methods control the layout of the child widgets. For instance, if your container has 2 child widgets, with one below the other, your <methodname>get_request_mode_vfunc()</methodname> might request height-for-width layout. Then your <methodname>measure_vfunc()</methodname> might report the maximum of the widths of the child widgets when asked to report width, and it might report the sum of their heights when asked to report height. If you want padding between the child widgets then you would add that to the width and height too. Your widget's container will use this result to ensure that your widget gets enough space, and not less. By examining each widget's parent, and its parent, this logic will eventually decide the size of the top-level window."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7654
msgid "You are not guaranteed to get the <literal>Gtk::SizeRequestMode</literal> that you request. Therefore <methodname>measure_vfunc()</methodname> must return sensible values for all reasonable values of its input parameters. For a description of <methodname>measure_vfunc()</methodname>'s parameters see also the description of <methodname>Gtk::Widget::measure()</methodname>, which may be better documented than <methodname>measure_vfunc()</methodname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7661
msgid "<methodname>size_allocate_vfunc()</methodname> receives the actual height and width that the parent container has decided to give to your widget. This might be more than the minimum, or even more than the natural size, for instance if the top-level window has been expanded. You might choose to ignore the extra space and leave a blank area, or you might choose to expand your child widgets to fill the space, or you might choose to expand the padding between your widgets. It's your container, so you decide."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7670
msgid "Your container must unparent its children before the underlying C object (a <classname>gtkmm__GtkWidget</classname>) is finalized. If your container is used as a managed widget, it shall unparent its children in a <methodname>Gtk::Widget::signal_destroy()</methodname> handler (available since <application>gtkmm</application> 4.8). If your container is not managed, that signal handler is not called. Instead the children shall be unparented in the C++ destructor. If you want your container to be useful both ways, unparent the children both in the destructor and in a signal handler. See the example code."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7682
msgid "This example implements a container with child widgets, one above the other. Of course, in this case it would be far simpler just to use a vertical <classname>Gtk::Box</classname> or <classname>Gtk::Grid</classname>."
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:7687
msgid "Custom Container"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:7689
msgctxt "_"
msgid "external ref='figures/custom_container.png' md5='865833944746eeb806eae028f0b2a25b'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7693
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/custom/custom_container/\">Source Code</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7701
msgid "By deriving directly from <classname>Gtk::Widget</classname> you can do all the drawing for your widget directly, instead of just arranging child widgets. For instance, a <classname>Gtk::Label</classname> draws the text of the label, but does not do this by using other widgets."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:7712
msgid "<methodname>get_request_mode_vfunc()</methodname>: (optional) Return what <literal>Gtk::SizeRequestMode</literal> is preferred by the widget."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:7713
msgid "<methodname>measure_vfunc()</methodname>: Calculate the minimum and natural width or height of the widget."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:7714
msgid "<methodname>size_allocate_vfunc()</methodname>: (optional) Position the widget, given the height and width that it has actually been given."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:7715
msgid "<methodname>on_realize()</methodname>: (optional)"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:7716
msgid "<methodname>on_unrealize()</methodname>: (optional)"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:7717
msgid "<methodname>on_map()</methodname>: (optional)"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:7718
msgid "<methodname>on_unmap()</methodname>: (optional)"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:7719
msgid "<methodname>snapshot_vfunc()</methodname>: Create a render node, e.g. a <classname>Cairo::Context</classname> node, and draw on it."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7707
msgid "When deriving from <classname>Gtk::Widget</classname>, you should override the following virtual methods. The methods marked (optional) need not be overridden in all custom widgets. The base class's methods may be appropriate. <_:itemizedlist-1/>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7723
msgid "The first 3 methods in the previous table are also overridden in custom containers. They are briefly described in the <link linkend=\"sec-custom-containers\">Custom Containers</link> section."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:7729
msgid "Class Init and Instance Init Functions"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7731
msgid "Some <application>GTK</application> functions, if called at all, must be called from the class init function. Some other <application>GTK</application> functions, if called, must be called from the instance init function. If your custom widget must call any of those functions, you can derive a class from <classname>Glib::ExtraClassInit</classname> and derive your custom class from that class. The <link linkend=\"custom-css-name-example\">custom CSS name example</link> shows how that's done."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7743
msgid "This example implements a widget which draws Penrose triangles."
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:7746
msgid "Custom Widget"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:7748
msgctxt "_"
msgid "external ref='figures/custom_widget.png' md5='30f9b406a95d5b0d17b6fc081c359b98'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7752
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/custom/custom_widget/\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:7757
msgid "Custom CSS Names"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7759
msgid "Many aspects of the look of widgets are controlled by CSS (Cascading Style Sheet) files. With CSS files you can choose color, font, line thickness, etc. If you give some widgets their own names or their own CSS classes, you can define CSS rules that apply only to those widgets, for instance certain buttons, without affecting other similar widgets."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:7766
msgid "CSS Node Name, Widget Name, CSS Class Name"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:7770
msgid "<methodname>gtk_widget_class_set_css_name()</methodname> can only be called from the class init function. It sets the CSS node name of all instances of a class (a GType). See the <link linkend=\"custom-init-functions\"> Class Init and Instance Init Functions</link> section."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:7774
msgid "<methodname>Gtk::Widget::set_name()</methodname> can be called from a C++ constructor. It sets the name of a widget instance."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:7777
msgid "<methodname>Gtk::Widget::add_class_name()</methodname> can be called from a C++ constructor. It adds the name of a CSS class, used by a widget instance."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7768
msgid "There are three ways of referring from a widget to data in a CSS file: <_:itemizedlist-1/> The following example shows a button with its own CSS node name, a label with a widget name and a label that uses its own CSS class."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:7786
msgid "Custom Style Information"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7788
msgid "To add a style sheet to an application, use one of the <methodname>Gtk::CssProvider::load_from_*()</methodname> methods. Then add it with <methodname>Gtk::StyleProvider::add_provider_for_display()</methodname> (available since <application>gtkmm</application> 4.10) or <methodname>Gtk::StyleContext::add_provider_for_display()</methodname>. <classname>Gtk::StyleContext</classname> also contains methods to read some style information, but this class is deprecated since <application>gtkmm</application> 4.10."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7795
msgid "CSS files are described in the documentation of GTK."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7801
msgid "This example implements a button and two labels with custom style information."
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:7804
msgid "Custom CSS Name"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:7806
msgctxt "_"
msgid "external ref='figures/custom_css_name.png' md5='fb3d968b1fd40eb219e5a78946adff0f'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7810
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/custom/custom_css_name/\">Source Code</link>"
msgstr ""

#. (itstool) path: chapter/title
#: C/index-in.docbook:7817
msgid "Multi-threaded programs"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:7820
msgid "The constraints"
msgstr ""

#. (itstool) path: footnote/para
#: C/index-in.docbook:7831
msgid "These interactions arise from the fact that, amongst other things, a class inheriting from <classname>sigc::trackable</classname> will, via that inheritance, have a <classname>std::list</classname> object keeping track of slots created by calls to <function>sigc::mem_fun()</function> representing any of its non-static methods (more particularly it keeps a list of callbacks which will null the connected slots on its destruction). Each <classname>sigc::slot</classname> object also keeps, via <classname>sigc::slot_rep</classname>, its own <classname>sigc::trackable</classname> object to track any <classname>sigc::connection</classname> objects which it needs to inform about its demise, and also has a function to deregister itself from any <classname>sigc::trackable</classname> on disconnection or destruction. <classname>sigc::signal</classname> objects also keep lists of slots, which will be updated by a call to their <methodname>connect()</methodname> method or calls to any <classname>sigc::connection</classname> object relating to such a connection."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7822
msgid "Care is required when writing programs based on <application>gtkmm</application> using multiple threads of execution, arising from the fact that <application>libsigc++</application>, and in particular <classname>sigc::trackable</classname>, are not thread-safe. That's because none of the complex interactions that occur behind the scenes when using <application>libsigc++</application> are protected by a mutex or other means of synchronization. <_:footnote-1/>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:7855
msgid "The rules"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7857
msgid "This requires a number of rules to be observed when writing multi-threaded programs using <application>gtkmm</application>. These are set out below, but one point to note is that extra care is required when deriving classes from <classname>sigc::trackable</classname>, because the effects are unintuitive (see particularly points 4 and 5 below)."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:7868
msgid "Use <classname>Glib::Dispatcher</classname> to invoke <application>gtkmm</application> functions from worker threads (this is dealt with in more detail in the next section)."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:7876
msgid "A <classname>sigc::signal</classname> object should be regarded as owned by the thread which created it. Only that thread should connect a <classname>sigc::slot</classname> object to the signal object, and only that thread should <methodname>emit()</methodname> or call <methodname>operator()()</methodname> on the signal, or null any connected <classname>sigc::slot</classname> object. It follows (amongst other things) that any signal object provided by a <application>gtkmm</application> widget should only be operated on in the main GUI thread and any object deriving from <classname>sigc::trackable</classname> having its non-static methods referenced by slots connected to the signal object should only be destroyed in that thread."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:7892
msgid "Any <classname>sigc::connection</classname> object should be regarded as owned by the thread in which the method returning the <classname>sigc::connection</classname> object was called. Only that thread should call <classname>sigc::connection</classname> methods on the object."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:7902
msgid "A <classname>sigc::slot</classname> object created by a call to <function>sigc::mem_fun()</function> which references a method of a class deriving from <classname>sigc::trackable</classname> should never be copied to another thread, nor destroyed by a different thread than the one which created it."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:7912
msgid "If a particular class object derives from <classname>sigc::trackable</classname>, only one thread should create <classname>sigc::slot</classname> objects representing any of the class's non-static methods by calling <function>sigc::mem_fun()</function>. The first thread to create such a slot should be regarded as owning the relevant object for the purpose of creating further slots referencing <emphasis>any</emphasis> of its non-static methods using that function, or nulling those slots by disconnecting them or destroying the trackable object."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:7926
msgid "Although <application>glib</application> is itself thread-safe, any <application>glibmm</application> wrappers which use <application>libsigc++</application> will not be. So for example, only the thread in which a main loop runs should call <methodname>Glib::SignalIdle::connect()</methodname>, <methodname>Glib::SignalIO::connect()</methodname>, <methodname>Glib::SignalTimeout::connect()</methodname>, <methodname>Glib::SignalTimeout::connect_seconds</methodname> for that main loop, or manipulate any <classname>sigc::connection</classname> object returned by them."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:7938
msgid "The connect*_once() variants, <methodname>Glib::SignalIdle::connect_once()</methodname>, <methodname>Glib::SignalTimeout::connect_once()</methodname>, <methodname>Glib::SignalTimeout::connect_seconds_once()</methodname>, are thread-safe for any case where the slot is not created by a call to <function>sigc::mem_fun()</function> which represents a method of a class deriving from <classname>sigc::trackable</classname>."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:7956
msgid "Using Glib::Dispatcher"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7958
msgid "The slots connected to <classname>sigc::signal</classname> objects execute in the thread which calls <methodname>emit()</methodname> or <methodname>operator()()</methodname> on the signal. <classname>Glib::Dispatcher</classname> does not behave this way: instead its connected slots execute in the thread in which the <classname>Glib::Dispatcher</classname> object was constructed (which must have a glib main loop). If a <classname>Glib::Dispatcher</classname> object is constructed in the main GUI thread (which will therefore be the receiver thread), any worker thread can emit on it and have the connected slots safely execute <application>gtkmm</application> functions."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7972
msgid "Some thread safety rules on the use of <classname>Glib::Dispatcher</classname> still apply. As mentioned, a <classname>Glib::Dispatcher</classname> object must be constructed in the receiver thread (the thread in whose main loop it will execute its connected slots). By default this is the main program thread, although there is a <classname>Glib::Dispatcher</classname> constructor which can take the <classname>Glib::MainContext</classname> object of any thread which has a main loop. Only the receiver thread should call <methodname>connect()</methodname> on the <classname>Glib::Dispatcher</classname> object, or manipulate any related <classname>sigc::connection</classname> object, unless additional synchronization is employed. However, any worker thread can safely emit on the <classname>Glib::Dispatcher</classname> object without any locking once the receiver thread has connected the slots, provided that it is constructed before the worker thread is started (if it is constructed after the thread has started, additional synchronization will normally be required to ensure visibility)."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:7992
msgid "Aside from the fact that connected slots always execute in the receiver thread, <classname>Glib::Dispatcher</classname> objects are similar to <classname>sigc::signal&lt;void()&gt;</classname> objects. They therefore cannot pass unbound arguments nor return a value. The best way to pass unbound arguments is with a thread-safe (asynchronous) queue. At the time of writing <application>glibmm</application> does not have one, although most people writing multi-threaded code will have one available to them (they are relatively easy to write although there are subtleties in combining thread safety with strong exception safety)."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8005
msgid "A <classname>Glib::Dispatcher</classname> object can be emitted on by the receiver thread as well as by a worker thread, although this should be done within reasonable bounds. On unix-like systems <classname>Glib::Dispatcher</classname> objects share a single common pipe, which could in theory at least fill up on a very heavily loaded system running a program with a very large number of <classname>Dispatcher</classname> objects in use. Were the pipe to fill up before the receiver thread's main loop has had an opportunity to read from it to empty it, and the receiver thread attempt to emit and so write to it when it is in that condition, the receiver thread would block on the write, so deadlocking. Where the receiver thread is to emit, a normal <classname>sigc::signal&lt;void()&gt;</classname> object could of course be used instead."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8026
msgid "This is an example program with two threads, one GUI thread, like in all <application>gtkmm</application> programs, and one worker thread. The worker thread is created when you press the <literal>Start work</literal> button. It is deleted when the work is finished, when you press the <literal>Stop work</literal> button, or when you press the <literal>Quit</literal> button."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8034
msgid "A <classname>Glib::Dispatcher</classname> is used for sending notifications from the worker thread to the GUI thread. The <classname>ExampleWorker</classname> class contains data which is accessed by both threads. This data is protected by a <classname>std::mutex</classname>. Only the GUI thread updates the GUI."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8042
msgid "Compiling and linking a multi-threaded program can require special compiler and linker options. If you use the <application>g++</application> compiler, add the <literal>-pthread</literal> option. Other compilers may require other options. If you build with <application>meson</application>, it handles the multi-threading complications for you, if you add <function>dependency('threads')</function>."
msgstr ""

#. (itstool) path: figure/title
#: C/index-in.docbook:8051
msgid "Multi-Threaded Program"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:8053
msgctxt "_"
msgid "external ref='figures/multithread.png' md5='acc87c2afb17321ab098b7f0b8a46b27'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8057
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/multithread\">Source Code</link>"
msgstr ""

#. (itstool) path: chapter/title
#: C/index-in.docbook:8064
msgid "Recommended Techniques"
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:8066
msgid "This section is simply a gathering of wisdom, general style guidelines and hints for creating <application>gtkmm</application> applications."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:8070
msgid "Use <application>Meson</application>! It is your friend :) It examines C and C++ files, determines how they depend on each other, and generates <filename>build.ninja</filename> or an equivalent file so the files can be compiled in the correct order. <application>Meson</application> permits automatic configuration of software installation, handling a large number of system quirks to increase portability."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:8078
msgid "Subclass Widgets to better organize your code. You should probably subclass your main <classname>Window</classname> at least. Then you can make your child Widgets and signal handlers members of that class."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:8083
msgid "Create your own signals instead of passing pointers around. Objects can communicate with each other via signals and signal handlers. This is much simpler than objects holding pointers to each other and calling each other's methods. <application>gtkmm</application>'s classes use special versions of <classname>sigc::signal</classname>, but you should use normal <classname>sigc::signal</classname>s, as described in the <application>libsigc++</application> documentation."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:8092
msgid "Application Lifetime"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8093
msgid "Most applications will have only one <classname>Window</classname>, or only one main window. These applications can use <methodname>Gtk::Application::make_window_and_run(int argc, char** argv, T_Args&amp;&amp;... args)</methodname>. It creates and shows a window. When the window is hidden, <methodname>make_window_and_run()</methodname> deletes the window and returns to the caller. This might happen when the user closes the window, or when your code decides to hide the window with <methodname>set_visible(false)</methodname>. You can prevent the user from closing the window (for instance, if there are unsaved changes) by overriding <methodname>Gtk::Window::on_close_request()</methodname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8102
msgid "Most of our examples use this technique."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:8106
msgid "Using a <application>gtkmm</application> widget"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8108
msgid "Our examples all tend to have the same structure. They follow these steps for using a <classname>Widget</classname>:"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:8117
msgid "Declare a variable of the type of <classname>Widget</classname> you wish to use, generally as member variable of a derived container class. You could also declare a pointer to the widget type, and then create it with <literal>new</literal> or <function>Gtk::make_managed()</function> in your code."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:8126
msgid "Set the attributes of the widget. If the widget has no default constructor, then you will need to initialize the widget in the initializer list of your container class's constructor."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:8134
msgid "Connect any signals you wish to use to the appropriate handlers."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:8140
msgid "Pack the widget into a container using the appropriate call, e.g. <methodname>Gtk::Box::append()</methodname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8150
msgid "If you don't want all widgets to be shown, call <methodname>Gtk::Widget::set_visible(false)</methodname> on the widgets that you don't want to show. If a container widget is hidden, all of its child widgets are also hidden, even if <methodname>set_visible(false)</methodname> is not called on the child widgets."
msgstr ""

#. (itstool) path: chapter/title
#: C/index-in.docbook:8161
msgid "Building applications"
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:8163
msgid "This chapter is similar to <emphasis>Building applications</emphasis> and following sections in the <link xlink:href=\"https://docs.gtk.org/gtk4/getting_started.html\">Getting Started</link> chapter in the GTK documentation. The same application is built, but <application>gtkmm</application> is used instead of <application>GTK</application>."
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:8173
msgid "The binary file"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:8174
msgid "This gets installed in <filename>/usr/bin</filename>."
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:8177
msgid "A desktop file"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:8178
msgid "The desktop file provides important information about the application to the desktop shell, such as its name, icon, D-Bus name, commandline to launch it, etc. It is installed in <filename>/usr/share/applications</filename>."
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:8183
msgid "An icon"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:8184
msgid "The icon gets installed in <filename>/usr/share/icons/hicolor/48x48/apps</filename>, where it will be found regardless of the current theme."
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:8188
msgid "A settings schema"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:8189
msgid "If the application uses <classname>Gio::Settings</classname>, it will install its schema in <filename>/usr/share/glib-2.0/schemas</filename>, so that tools like dconf-editor can find it."
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:8194
msgid "Other resources"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:8195
msgid "Other files, such as <classname>Gtk::Builder</classname> ui files, are best loaded from resources stored in the application binary itself. This eliminates the need for most of the files that would traditionally be installed in an application-specific location in <filename>/usr/share</filename>."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:8169
msgid "An application consists of a number of files: <_:variablelist-1/>"
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:8203
msgid "<application>gtkmm</application> includes application support that is built on top of <classname>Gio::Application</classname>. In this chapter we'll build a simple application by starting from scratch, adding more and more pieces over time. Along the way, we'll learn about <classname>Gtk::Application</classname>, <classname>Gtk::Builder</classname>, resources, menus, settings, <classname>Gtk::HeaderBar</classname>, <classname>Gtk::Stack</classname>, <classname>Gtk::SearchBar</classname>, <classname>Gtk::ListBox</classname>, and more."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:8212
msgid "The full, buildable sources for these examples can be found in the <filename>examples/book/buildapp</filename> directory of the <application>gtkmm-documentation</application> source distribution, or online in the <link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/buildapp\"><application>gtkmm-documentation</application> git repository</link>. You can build each example separately by using <command>meson</command> and <command>ninja</command> with the <filename>meson.build</filename> file or by using <command>make</command> with the <filename>Makefile.example</filename> file. For more information, see the <filename>README</filename> included in the <filename>buildapp</filename> directory."
msgstr ""

#. (itstool) path: section/title
#. (itstool) path: figure/title
#: C/index-in.docbook:8225
#: C/index-in.docbook:8269
msgid "A trivial application"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8227
msgid "When using <classname>Gtk::Application</classname>, the <function>main()</function> function can be very simple. We just call <methodname>Gtk::Application::run()</methodname> on an instance of our application class."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8233
msgid "All the application logic is in the application class, which is a subclass of <classname>Gtk::Application</classname>. Our example does not yet have any interesting functionality. All it does is open a window when it is activated without arguments, and open the files it is given, if it is started with arguments. (Or rather, our application class tries to open the files, but our subclassed application window does not yet do what it's told to do.)"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8242
msgid "To handle these two cases, we override <methodname>signal_activate()</methodname>'s default handler, which gets called when the application is launched without commandline arguments, and <methodname>signal_open()</methodname>'s default handler, which gets called when the application is launched with commandline arguments."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8249
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/glibmm/classGio_1_1Application.html\">Gio::Application Reference</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8250
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/gtkmm/classGtk_1_1Application.html\">Gtk::Application Reference</link>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8252
msgid "Another important class that is part of the application support in <application>gtkmm</application> is <classname>Gtk::ApplicationWindow</classname>. It is typically subclassed as well. Our subclass does not do anything yet, so we will just get an empty window."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8258
msgid "As part of the initial setup of our application, we also create an icon and a desktop file. Note that @bindir@ in the desktop file needs to be replaced with the actual path to the binary before this desktop file can be used."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8264
msgid "Here is what we've achieved so far:"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:8271
msgctxt "_"
msgid "external ref='figures/buildapp_trivial_app.png' md5='fe94e3d80cb888d1827912f49af7a6f3'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8275
msgid "This does not look very impressive yet, but our application is already presenting itself on the session bus, it has single-instance semantics, and it accepts files as commandline arguments."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8280
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/buildapp/step1\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#. (itstool) path: figure/title
#: C/index-in.docbook:8285
#: C/index-in.docbook:8328
msgid "Populating the window"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8287
msgid "In this step, we use a <classname>Gtk::Builder</classname> instance to associate a <classname>Gtk::Builder</classname> ui file with our application window class."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8292
msgid "Our simple ui file gives the window a title, and puts a <classname>Gtk::Stack</classname> widget as the main content."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8297
msgid "To make use of this file in our application, we revisit our <classname>Gtk::ApplicationWindow</classname> subclass, and call <methodname>Gtk::Builder::create_from_resource()</methodname> and <methodname>Gtk::Builder::get_widget_derived()</methodname> from the <methodname>ExampleAppWindow::create()</methodname> method to get an instance of our subclassed <classname>Gtk::ApplicationWindow</classname>. See the <link linkend=\"sec-builder-using-derived-widgets\">Using derived widgets</link> section for more information about <methodname>get_widget_derived()</methodname>."
msgstr ""

#. (itstool) path: para/screen
#: C/index-in.docbook:8316
#, no-wrap
msgid ""
"$ glib-compile-resources --target=resources.c --generate-source exampleapp.gresource.xml"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8308
msgid "You may have noticed that we use the <methodname>_from_resource()</methodname> variant of the method that reads the ui file. Now we need to use <application>GLib</application>'s resource functionality to include the ui file in the binary. This is commonly done by listing all resources in a .gresource.xml file. This file has to be converted into a C source file that will be compiled and linked into the application together with the other source files. To do so, we use the <application>glib-compile-resources</application> utility: <_:screen-1/> The <link linkend=\"sec-gio-resource\">Gio::Resource and glib-compile-resources</link> section contains more information about resource files. If you build with Meson, use the <function>compile_resources()</function> function in Meson's <link xlink:href=\"https://mesonbuild.com/Gnome-module.html\">GNOME module</link>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8323
msgid "Our application now looks like this:"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:8330
msgctxt "_"
msgid "external ref='figures/buildapp_populating_window.png' md5='4af45b6a60b3973334ac91eb3f1dcf91'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8334
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/buildapp/step2\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#. (itstool) path: figure/title
#: C/index-in.docbook:8339
#: C/index-in.docbook:8375
msgid "Opening files"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8341
msgid "In this step, we make our application show the contents of all the files that it is given on the commandline."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8346
msgid "To this end, we add a data member to our application window and keep a pointer to the <classname>Gtk::Stack</classname> there. We get the pointer with a call to <methodname>Gtk::Builder::get_widget()</methodname> in the application window's constructor."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8352
msgid "Now we revisit the <methodname>ExampleAppWindow::open_file_view()</methodname> method that is called for each commandline argument, and construct a <classname>Gtk::TextView</classname> that we then add as a page to the stack."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8358
msgid "Lastly, we add a <classname>Gtk::StackSwitcher</classname> to the titlebar area in the ui file, and we tell it to display information about our stack."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8363
msgid "The stack switcher gets all its information it needs to display tabs from the stack that it belongs to. Here, we are passing the label to show for each file as the last argument to the <methodname>Gtk::Stack::add()</methodname> method."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8370
msgid "Our application is beginning to take shape:"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:8377
msgctxt "_"
msgid "external ref='figures/buildapp_opening_files.png' md5='ad2373e10879d9724c91408aa6dbd4c3'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8381
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/buildapp/step3\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#. (itstool) path: figure/title
#: C/index-in.docbook:8386
#: C/index-in.docbook:8421
msgid "A menu"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8388
msgid "The menu is shown at the right side of the headerbar. It is meant to collect infrequently used actions that affect the whole application."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8393
msgid "Just like the application window, we specify our menu in a ui file, and add it as a resource to our binary."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8398
msgid "To make the menu appear, we have to load the ui file and associate the resulting menu model with the menu button that we've added to the headerbar. Since menus work by activating <classname>Gio::Action</classname>s, we also have to add a suitable set of actions to our application."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8405
msgid "Adding the actions is best done in the <methodname>on_startup()</methodname> default signal handler, which is guaranteed to be called once for each primary application instance."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8410
msgid "Our preferences menu item does not do anything yet, but the Quit menu item is fully functional. It can also be activated by the usual Ctrl-Q shortcut. The shortcut is added with <methodname>Gtk::Application::set_accel_for_action()</methodname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8416
msgid "The menu looks like this:"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:8423
msgctxt "_"
msgid "external ref='figures/buildapp_menu.png' md5='a9d0d291ab0f472a7cd9c38c01130d8d'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8427
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/buildapp/step4\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#. (itstool) path: figure/title
#: C/index-in.docbook:8432
#: C/index-in.docbook:8505
msgid "A preference dialog"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8434
msgid "A typical application will have some preferences that should be remembered from one run to the next. Even for our simple example application, we may want to change the font that is used for the content."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8440
msgid "We are going to use <classname>Gio::Settings</classname> to store our preferences. <classname>Gio::Settings</classname> requires a schema that describes our settings, in our case the <filename>org.gtkmm.exampleapp.gschema.xml</filename> file."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8446
msgid "Before we can make use of this schema in our application, we need to compile it into the binary form that <classname>Gio::Settings</classname> expects. GIO provides macros to do this in autotools-based projects. See the description of <link xlink:href=\"https://docs.gtk.org/gio/class.Settings.html\">GSettings</link>. Meson provides the <function>compile_schemas()</function> function in the <link xlink:href=\"https://mesonbuild.com/Gnome-module.html\">GNOME module</link>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8455
msgid "Next, we need to connect our settings to the widgets that they are supposed to control. One convenient way to do this is to use <methodname>Gio::Settings::bind()</methodname> to bind settings keys to object properties, as we do for the transition setting in <classname>ExampleAppWindow</classname>'s constructor."
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:8461
#, no-wrap
msgid ""
"\n"
"m_settings = Gio::Settings::create(\"org.gtkmm.exampleapp\");\n"
"m_settings-&gt;bind(\"transition\", m_stack-&gt;property_transition_type());\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8466
msgid "The code to connect the font setting is a little more involved, since it corresponds to an object property in a <classname>Gtk::TextTag</classname> that we must first create. The code is in <methodname>ExampleAppWindow::open_file_view()</methodname>."
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:8471
#, no-wrap
msgid ""
"\n"
"auto tag = buffer-&gt;create_tag();\n"
"m_settings-&gt;bind(\"font\", tag-&gt;property_font());\n"
"buffer-&gt;apply_tag(tag, buffer-&gt;begin(), buffer-&gt;end());\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8477
msgid "At this point, the application will already react if you change one of the settings, e.g. using the <command>gsettings</command> commandline tool. Of course, we expect the application to provide a preference dialog for these. So lets do that now. Our preference dialog will be a subclass of <classname>Gtk::Window</classname>, and we'll use the same techniques that we've already seen in <classname>ExampleAppWindow</classname>: a <classname>Gtk::Builder</classname> ui file and settings bindings. In this case the bindings are more involved, though. We use <classname>Gtk::FontDialogButton</classname> and <classname>Gtk::DropDown</classname> in the preference dialog. The types of the properties in these classes can't be automatically converted to the string type that <classname>Gio::Settings</classname> requires."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8490
msgid "When we've created the <filename>prefs.ui</filename> file and the <classname>ExampleAppPrefs</classname> class, we revisit the <methodname>ExampleApplication::on_action_preferences()</methodname> method in our application class, and make it open a new preference dialog."
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:8495
#, no-wrap
msgid ""
"\n"
"auto prefs_dialog = ExampleAppPrefs::create(*get_active_window());\n"
"prefs_dialog-&gt;present();\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8500
msgid "After all this work, our application can now show a preference dialog like this:"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:8507
msgctxt "_"
msgid "external ref='figures/buildapp_pref_dialog.png' md5='ecc7fa5d31086c536a5ad279eddfbf23'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8511
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/buildapp/step5\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#. (itstool) path: figure/title
#: C/index-in.docbook:8516
#: C/index-in.docbook:8559
msgid "Adding a search bar"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8518
msgid "We continue to flesh out the functionality of our application. For now, we add search. <application>gtkmm</application> supports this with <classname>Gtk::SearchEntry</classname> and <classname>Gtk::SearchBar</classname>. The search bar is a widget that can slide in from the top to present a search entry."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8524
msgid "We add a toggle button to the header bar, which can be used to slide out the search bar below the header bar. The new widgets are added in the <filename>window.ui</filename> file."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8529
msgid "Implementing the search needs quite a few code changes that we are not going to completely go over here. The central piece of the search implementation is a signal handler that listens for text changes in the search entry, shown here without error handling."
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:8534
#, no-wrap
msgid ""
"\n"
"void ExampleAppWindow::on_search_text_changed()\n"
"{\n"
"  const auto text = m_searchentry-&gt;get_text();\n"
"  auto tab = dynamic_cast&lt;Gtk::ScrolledWindow*&gt;(m_stack-&gt;get_visible_child());\n"
"  auto view = dynamic_cast&lt;Gtk::TextView*&gt;(tab-&gt;get_child());\n"
"\n"
"  // Very simple-minded search implementation.\n"
"  auto buffer = view-&gt;get_buffer();\n"
"  Gtk::TextIter match_start;\n"
"  Gtk::TextIter match_end;\n"
"  if (buffer-&gt;begin().forward_search(text, Gtk::TextSearchFlags::CASE_INSENSITIVE,\n"
"      match_start, match_end))\n"
"  {\n"
"    buffer-&gt;select_range(match_start, match_end);\n"
"    view-&gt;scroll_to(match_start);\n"
"  }\n"
"}\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8554
msgid "With the search bar, our application now looks like this:"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:8561
msgctxt "_"
msgid "external ref='figures/buildapp_search_bar.png' md5='ca0d7fdb0f37cbd592f2c55904bb6f3f'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8565
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/buildapp/step6\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#. (itstool) path: figure/title
#: C/index-in.docbook:8570
#: C/index-in.docbook:8605
msgid "Adding a side bar"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8572
msgid "As another piece of functionality, we are adding a sidebar, which demonstrates <classname>Gtk::Revealer</classname> and <classname>Gtk::ListBox</classname>. The new widgets are added in the <filename>window.ui</filename> file."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8578
msgid "The code to populate the sidebar with buttons for the words found in each file is a little too involved to go into here. But we'll look at the code to add a checkbutton for the new feature to the menu. A menu item is added to the ui file <filename>gears_menu.ui</filename>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8585
msgid "To connect the menu item to the new <literal>show-words</literal> setting, we use a <classname>Gio::Action</classname> corresponding to the given <classname>Gio::Settings</classname> key. In <classname>ExampleAppWindow</classname>'s constructor:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:8590
#, no-wrap
msgid ""
"\n"
"// Connect the menu to the MenuButton m_gears, and bind the show-words setting\n"
"// to the win.show-words action and the \"Words\" menu item.\n"
"// (The connection between action and menu item is specified in gears_menu.ui.)\n"
"auto menu_builder = Gtk::Builder::create_from_resource(\"/org/gtkmm/exampleapp/gears_menu.ui\");\n"
"auto menu = menu_builder-&gt;get_object&lt;Gio::MenuModel&gt;(\"menu\");\n"
"m_gears-&gt;set_menu_model(menu);\n"
"add_action(m_settings-&gt;create_action(\"show-words\"));\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8600
msgid "What our application looks like now:"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:8607
msgctxt "_"
msgid "external ref='figures/buildapp_side_bar.png' md5='e13a4b6ebbcf73692dc59a0ba08e59e7'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8611
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/buildapp/step7\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#. (itstool) path: figure/title
#: C/index-in.docbook:8616
#: C/index-in.docbook:8658
msgid "Properties"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8618
msgid "Widgets and other objects have many useful properties. Here we show some ways to use them in new and flexible ways, by wrapping them in actions with <classname>Gio::PropertyAction</classname> or by binding them with <classname>Glib::Binding</classname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8624
msgid "To set this up, we add two labels to the header bar in our <filename>window.ui</filename> file, named <literal>lines_label</literal> and <literal>lines</literal>, and get pointers to them in the application window's constructor, as we've seen a couple of times by now. We add a new \"Lines\" menu item to the gears menu, which triggers the <literal>show-lines</literal> action."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8632
msgid "To make this menu item do something, we create a property action for the <literal>visible</literal> property of the <literal>lines</literal> label, and add it to the actions of the window. The effect of this is that the visibility of the label gets toggled every time the action is activated. Since we want both labels to appear and disappear together, we bind the <literal>visible</literal> property of the <literal>lines_label</literal> widget to the same property of the <literal>lines</literal> widget. In <classname>ExampleAppWindow</classname>'s constructor:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:8642
#, no-wrap
msgid ""
"add_action(Gio::PropertyAction::create(\"show-lines\", m_lines-&gt;property_visible()));\n"
"m_binding_lines_visible = Glib::Binding::bind_property(m_lines-&gt;property_visible(),\n"
"  m_lines_label-&gt;property_visible());\n"
"\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8648
msgid "We also need a function that counts the lines of the currently active tab, and updates the <literal>lines</literal> label. See the full source if you are interested in the details."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8653
msgid "This brings our example application to this appearance:"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:8660
msgctxt "_"
msgid "external ref='figures/buildapp_properties.png' md5='46c52e09cc1b4ddbc095e12f763a4427'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8664
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/buildapp/step8\">Source Code</link>"
msgstr ""

#. (itstool) path: section/title
#. (itstool) path: figure/title
#: C/index-in.docbook:8669
#: C/index-in.docbook:8695
msgid "Header bar"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8671
msgid "Our application already uses a <classname>Gtk::HeaderBar</classname> instead of a 'normal' window titlebar. The header bar is a direct child of the window, and its type is <literal>titlebar</literal>. This is set in the <filename>window.ui</filename> file."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8678
msgid "Here we'll just make two small changes to the header bar. The <literal>decoration-layout</literal> property is set in the <filename>window.ui</filename> file, to show only the close button, and hide the minimize and maximize buttons. We also include an icon in the resource file, and set up this icon as the window icon. In <classname>ExampleAppWindow</classname>'s constructor:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:8685
#, no-wrap
msgid ""
"Gtk::IconTheme::get_for_display(get_display())-&gt;add_resource_path(\"/org/gtkmm/exampleapp\");\n"
"set_icon_name(\"exampleapp\");\n"
"\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8690
msgid "Here is how the application now looks:"
msgstr ""

#. (itstool) path: imageobject/imagedata
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index-in.docbook:8697
msgctxt "_"
msgid "external ref='figures/buildapp_header_bar.png' md5='b2ab5d871b0deff13f04aac71700b1a0'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8701
msgid "The <filename>window.ui</filename> file sets a header bar title, but this title is not shown. That's because the stack switcher is a child of type <literal>title</literal>. The stack switcher becomes a custom title that hides the title label."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8707
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/buildapp/step9\">Source Code</link>"
msgstr ""

#. (itstool) path: chapter/title
#: C/index-in.docbook:8714
msgid "Contributing"
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:8716
msgid "This document, like so much other great software out there, was created for free by volunteers. If you are at all knowledgeable about any aspect of <application>gtkmm</application> that does not already have documentation, please consider contributing to this document."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:8722
msgid "Ideally, we would like you to <link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/-/merge_requests\"> provide a merge request</link> to the <filename>docs/tutorial/C/index-in.docbook</filename> file. This file is in the <literal>gtkmm-documentation</literal> module in GNOME git."
msgstr ""

#. (itstool) path: chapter/para
#: C/index-in.docbook:8728
msgid "If you do decide to contribute, please post your contribution as an issue or merge request to <link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation\">GitLab</link>. You can also discuss your ideas on GNOME's <link xlink:href=\"https://discourse.gnome.org\">Discourse</link> instance, under the <link xlink:href=\"https://discourse.gnome.org/c/platform/language-bindings\"> Platform/Language bindings</link> category with a <literal>cplusplus</literal> tag. Also, be aware that the entirety of this document is free, and any addition you provide must also be free. That is, people must be able to use any portion of your examples in their programs, and copies of this document (including your contribution) may be distributed freely."
msgstr ""

#. (itstool) path: appendix/title
#: C/index-in.docbook:8743
msgid "The RefPtr smartpointer"
msgstr ""

#. (itstool) path: appendix/para
#: C/index-in.docbook:8745
msgid "<classname>Glib::RefPtr</classname> is a smartpointer. Specifically, it is a reference-counting smartpointer. You might be familiar with <classname>std::unique_ptr&lt;&gt;</classname> and <classname>std::shared_ptr&lt;&gt;</classname>, which are also smartpointers. In <application>gtkmm</application>-4.0 <classname>Glib::RefPtr&lt;&gt;</classname> is an alias for <classname>std::shared_ptr&lt;&gt;</classname>, which is reference-counting. <classname>Glib::RefPtr&lt;&gt;</classname> was introduced long before there was a reference-counting smartpointer in the C++ Standard Library."
msgstr ""

#. (itstool) path: appendix/para
#: C/index-in.docbook:8756
msgid "If you make your own <classname>Glib::ObjectBase</classname>-derived classes with <methodname>create()</methodname> methods that return a <classname>Glib::RefPtr</classname>, you must use <function>Glib::make_refptr_for_instance()</function> in your <methodname>create()</methodname> methods. This function creates a <classname>std::shared_ptr</classname> with a special deleter, which handles the reference-count for the wrapped C object."
msgstr ""

#. (itstool) path: appendix/para
#: C/index-in.docbook:8764
msgid "<link xlink:href=\"https://gnome.pages.gitlab.gnome.org/glibmm/group__RefPtr.html\">Reference</link>"
msgstr ""

#. (itstool) path: appendix/para
#: C/index-in.docbook:8766
msgid "A smartpointer acts much like a normal pointer. Here are a few examples."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:8769
msgid "Copying"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8770
msgid "You can copy <classname>RefPtr</classname>s, just like normal pointers. But unlike normal pointers, you don't need to worry about deleting the underlying instance."
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:8775
#, no-wrap
msgid ""
"\n"
"auto refPixbuf = Gdk::Pixbuf::create_from_file(filename);\n"
"auto refPixbuf2 = refPixbuf;\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8779
msgid "Of course this means that you can store <classname>RefPtr</classname>s in standard containers, such as <classname>std::vector</classname> or <classname>std::list</classname>."
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:8783
#, no-wrap
msgid ""
"\n"
"std::list&lt;Glib::RefPtr&lt;Gdk::Pixbuf&gt;&gt; listPixbufs;\n"
"auto refPixbuf = Gdk::Pixbuf::create_from_file(filename);\n"
"listPixbufs.push_back(refPixbuf);\n"
""
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:8791
msgid "Dereferencing"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8792
msgid "You can dereference a smartpointer with the -&gt; operator, to call the methods of the underlying instance, just like a normal pointer."
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:8795
#, no-wrap
msgid ""
"\n"
"auto refPixbuf = Gdk::Pixbuf::create_from_file(filename);\n"
"auto width = refPixbuf-&gt;get_width();\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8799
msgid "You can also use the * operator and the <methodname>get()</methodname> method to access the underlying instance, but it's usually a bad idea to do so. Unless you are careful, you can end up with a pointer or a reference which is not included in the reference count."
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:8804
#, no-wrap
msgid ""
"\n"
"auto refPixbuf = Gdk::Pixbuf::create_from_file(filename);\n"
"auto&amp; underlying = *refPixbuf; // Possible, but not recommended\n"
""
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:8811
msgid "Casting"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8812
msgid "You can cast <classname>RefPtr</classname>s to base types, just like normal pointers."
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:8816
#, no-wrap
msgid ""
"\n"
"auto refStore = Gtk::TreeStore::create(columns);\n"
"Glib::RefPtr&lt;Gtk::TreeModel&gt; refModel = refStore;\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8820
msgid "This means that any method which takes a <type>const Glib::RefPtr&lt;BaseType&gt;&amp;</type> argument can also take a <type>const Glib::RefPtr&lt;DerivedType&gt;&amp;</type>. The cast is implicit, just as it would be for a normal pointer."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8824
msgid "You can also cast to a derived type, but the syntax is a little different than with a normal pointer."
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:8827
#, no-wrap
msgid ""
"\n"
"auto refStore = std::dynamic_pointer_cast&lt;Gtk::TreeStore&gt;(refModel);\n"
"auto refStore2 = std::static_pointer_cast&lt;Gtk::TreeStore&gt;(refModel);\n"
""
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:8834
msgid "Checking for nullptr"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8835
msgid "Just like normal pointers, you can check whether a <classname>RefPtr</classname> points to anything."
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:8839
#, no-wrap
msgid ""
"\n"
"auto refModel = m_TreeView.get_model();\n"
"if (refModel)\n"
"{\n"
"  auto cols_count = refModel-&gt;get_n_columns();\n"
"  ...\n"
"}\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8847
msgid "But unlike normal pointers, <classname>RefPtr</classname>s are automatically initialized to <literal>nullptr</literal> so you don't need to remember to do that yourself."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:8854
msgid "Constness"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8855
msgid "The use of the <literal>const</literal> keyword in C++ is not always clear. You might not realize that <type>const Something*</type> declares a pointer to a <type>const Something</type>. The pointer can be changed, but not the <type>Something</type> that it points to."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8861
msgid "Therefore, the <classname>RefPtr</classname> equivalent of <type>Something*</type> for a method parameter is <type>const Glib::RefPtr&lt;Something&gt;&amp;</type>, and the equivalent of <type>const Something*</type> is <type>const Glib::RefPtr&lt;const Something&gt;&amp;</type>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8868
msgid "The <literal>const ... &amp;</literal> around both is just for efficiency, like using <classname>const std::string&amp;</classname> instead of <classname>std::string</classname> for a method parameter to avoid unnecessary copying."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:8882
msgid "Connecting signal handlers"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8884
msgid "<application>gtkmm</application> widget classes have signal accessor methods, such as <methodname>Gtk::Button::signal_clicked()</methodname>, which allow you to connect your signal handler. Thanks to the flexibility of <application>libsigc++</application>, the callback library used by <application>gtkmm</application>, the signal handler can be almost any kind of function, but you will probably want to use a class method. Among <application>GTK</application> C coders, these signal handlers are often named callbacks."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8894
msgid "Here's an example of a signal handler being connected to a signal:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:8898
#, no-wrap
msgid ""
"\n"
"#include &lt;gtkmm/button.h&gt;\n"
"\n"
"void on_button_clicked()\n"
"{\n"
"  std::cout &lt;&lt; \"Hello World\" &lt;&lt; std::endl;\n"
"}\n"
"\n"
"class some_class\n"
"{\n"
"public:\n"
"  some_class\n"
"  {\n"
"    button.signal_clicked().connect(sigc::ptr_fun(&amp;on_button_clicked));\n"
"  }\n"
"private:\n"
"  Gtk::Button button {\"Hello World\"};\n"
"};\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8918
msgid "There's rather a lot to think about in this (non-functional) code. First let's identify the parties involved:"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:8926
msgid "The signal handler is <methodname>on_button_clicked()</methodname>."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:8932
msgid "We're hooking it up to the <classname>Gtk::Button</classname> object called <varname>button</varname>."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:8939
msgid "When the Button emits its <literal>clicked</literal> signal, <methodname>on_button_clicked()</methodname> will be called."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8947
msgid "Now let's look at the connection again:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:8951
#, no-wrap
msgid ""
"\n"
"    ...\n"
"    button.signal_clicked().connect(sigc::ptr_fun(&amp;on_button_clicked));\n"
"    ...\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8957
msgid "Note that we don't pass a pointer to <methodname>on_button_clicked()</methodname> directly to the signal's <methodname>connect()</methodname> method. Instead, we call <function>sigc::ptr_fun()</function>, and pass the result to <methodname>connect()</methodname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8964
msgid "<function>sigc::ptr_fun()</function> generates a <classname>sigc::slot</classname>. A slot is an object which looks and feels like a function, but is actually an object. These are also known as function objects, or functors. <function>sigc::ptr_fun()</function> generates a slot for a standalone function or static method. <function>sigc::mem_fun()</function> generates a slot for a member method of a particular instance."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8973
msgid "A C++ lambda expression is a functor which can be implicitly converted to a <classname>sigc::slot</classname> in the call to <methodname>connect()</methodname>. A lambda expression can be used instead of <function>sigc::ptr_fun()</function>. It's also possible to use a lambda expression instead of <function>sigc::mem_fun()</function>, but then you won't get automatic disconnection of the signal handler when a <classname>sigc::trackable</classname>-derived object goes out of scope."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:8982
msgid "Here's a slightly larger example of slots in action:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:8986
#, no-wrap
msgid ""
"\n"
"#include &lt;gtkmm/button.h&gt;\n"
"\n"
"void on_button_clicked()\n"
"{\n"
"  std::cout &lt;&lt; \"Hello World\" &lt;&lt; std::endl;\n"
"}\n"
"\n"
"class some_class\n"
"{\n"
"public:\n"
"  some_class\n"
"  {\n"
"    button.signal_clicked().connect(sigc::ptr_fun(&amp;on_button_clicked));\n"
"    button.signal_clicked().connect(sigc::mem_fun(*this, &amp;some_class::on_button_clicked));\n"
"  }\n"
"  void on_button_clicked();\n"
"private:\n"
"  Gtk::Button button {\"Hello World\"};\n"
"};\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9008
msgid "The first call to <methodname>connect()</methodname> is just like the one we saw last time; nothing new here."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9011
msgid "The next is more interesting. <function>sigc::mem_fun()</function> is called with two arguments. The first argument is <parameter>*this</parameter>, which is the object that our new slot will be pointing at. The second argument is a pointer to one of its methods. This particular version of <function>sigc::mem_fun()</function> creates a slot which will, when \"called\", call the pointed-to method of the specified object."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9020
msgid "Another thing to note about this example is that we made the call to <methodname>connect()</methodname> twice for the same signal object. This is perfectly fine - when the button is clicked, both signal handlers will be called."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9027
msgid "We just told you that the button's <literal>clicked</literal> signal is expecting to call a method with no arguments. All signals have requirements like this - you can't hook a function with two arguments to a signal expecting none (unless you use an adapter, such as <function>sigc::bind()</function>, of course). Therefore, it's important to know what type of signal handler you'll be expected to connect to a given signal."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:9039
msgid "Writing signal handlers"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9041
msgid "To find out what type of signal handler you can connect to a signal, you can look it up in the reference documentation or the header file. Here's an example of a signal declaration you might see in the <application>gtkmm</application> headers:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:9047
#, no-wrap
msgid ""
"\n"
"Glib::SignalProxy&lt;bool(Gtk::DirectionType)&gt; signal_focus()\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9051
msgid "Other than the signal's name (<literal>focus</literal>), the template arguments are important to note here. The first argument, <type>bool</type>, is the type that the signal handler should return; and the type within parentheses, <type>Gtk::DirectionType</type>, is the type of this signal's first, and only, argument. By looking at the reference documentation, you can see the names of the arguments too."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9060
msgid "The same principles apply for signals which have more arguments. Here's one with three (taken from <filename>&lt;gtkmm/textbuffer.h&gt;</filename>):"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:9065
#, no-wrap
msgid ""
"\n"
"Glib::SignalProxy&lt;void(TextBuffer::iterator&amp;, const Glib::ustrin&amp;, int)&gt; signal_insert();\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9069
msgid "It follows the same form. The first type is <type>void</type>, so that should be our signal handler's return type. The following three types are the argument types, in order. Our signal handler's prototype could look like this:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:9076
#, no-wrap
msgid ""
"\n"
"void on_insert(TextBuffer::iterator&amp; pos, const Glib::ustring&amp; text, int bytes)\n"
""
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:9082
msgid "Disconnecting signal handlers"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9084
msgid "Let's take another look at a Signal's <literal>connect</literal> method:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:9088
#, no-wrap
msgid ""
"\n"
"sigc::connection signal&lt;void(int)&gt;::connect(const sigc::slot&lt;void(int)&gt;&amp;);\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9092
msgid "The returned <classname>sigc::connection</classname> can be used to control the connection. By keeping a connection object you can disconnect its associated signal handler using the <methodname>sigc::connection::disconnect()</methodname> method."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:9100
msgid "Overriding default signal handlers"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9102
msgid "So far we've told you to perform actions in response to button-presses and the like by handling signals. That's certainly a good way to do things, but it's not the only way."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9109
msgid "Instead of laboriously connecting signal handlers to signals, you can simply make a new class which inherits from a widget - say, a Button - and then override the default signal handler, such as Button::on_clicked(). This can be a lot simpler than hooking up signal handlers for everything."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9116
msgid "Subclassing isn't always the best way to accomplish things. It is only useful when you want the widget to handle its own signal by itself. If you want some other class to handle the signal then you'll need to connect a separate handler. This is even more true if you want several objects to handle the same signal, or if you want one signal handler to respond to the same signal from different objects."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9121
msgid "<application>gtkmm</application> classes are designed with overriding in mind; they contain virtual member methods specifically intended to be overridden."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9126
msgid "Let's look at an example of overriding:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:9130
#, no-wrap
msgid ""
"\n"
"#include &lt;gtkmm/button.h&gt;\n"
"\n"
"class OverriddenButton : public Gtk::Button\n"
"{\n"
"protected:\n"
"  void on_clicked() override;\n"
"}\n"
"\n"
"void OverriddenButton::on_clicked()\n"
"{\n"
"  std::cout &lt;&lt; \"Hello World\" &lt;&lt; std::endl;\n"
"\n"
"  // call the base class's version of the method:\n"
"  Gtk::Button::on_clicked();\n"
"}\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9148
msgid "Here we define a new class called <classname>OverriddenButton</classname>, which inherits from <classname>Gtk::Button</classname>. The only thing we change is the <methodname>on_clicked()</methodname> method, which is called whenever <classname>Gtk::Button</classname> emits the <literal>clicked</literal> signal. This method prints \"Hello World\" to <literal>stdout</literal>, and then calls the original, overridden method, to let <classname>Gtk::Button</classname> do what it would have done had we not overridden."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9159
msgid "You don't always need to call the parent's method; there are times when you might not want to. Note that we called the parent method <emphasis>after</emphasis> writing \"Hello World\", but we could have called it before. In this simple example, it hardly matters much, but there are times when it will. With connected signal handlers, it's not quite so easy to change details like this, and you can do something here which you can't do at all with connected signal handlers: you can call the parent method in the <emphasis>middle</emphasis> of your custom code."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:9173
msgid "Binding extra arguments"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9175
msgid "If you use one signal handler to catch the same signal from several widgets, you might like that signal handler to receive some extra information. For instance, you might want to know which button was clicked. You can do this with <function>sigc::bind()</function>. Here's some code from the <link linkend=\"sec-helloworld2\">helloworld2</link> example."
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:9181
#, no-wrap
msgid ""
"\n"
"m_button1.signal_clicked().connect(sigc::bind(sigc::mem_fun(*this, &amp;HelloWorld::on_button_clicked), \"button 1\"));\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9184
msgid "This says that we want the signal to send an extra <classname>Glib::ustring</classname> argument to the signal handler, and that the value of that argument should be \"button 1\". Of course we will need to add that extra argument to the declaration of our signal handler:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:9189
#, no-wrap
msgid ""
"\n"
"void on_button_clicked(const Glib::ustring&amp; data);\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9192
msgid "Of course, a normal \"clicked\" signal handler would have no arguments."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9194
msgid "<function>sigc::bind()</function> is not commonly used, but you might find it helpful sometimes. If you are familiar with <application>GTK</application> programming then you have probably noticed that this is similar to the extra <literal>gpointer data</literal> arguments which all GTK callbacks have. This is generally overused in <application>GTK</application> to pass information that should be stored as member data in a derived widget, but widget derivation is very difficult in C. We have far less need of this hack in <application>gtkmm</application>."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:9206
msgid "Event signals"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9208
msgid "Event signals are emitted as a result of some user input, for instance a key press or a mouse motion. Usually you don't handle these events directly. Instead, you use a subclass of <classname>Gtk::EventController</classname>, such as <classname>Gtk::EventControllerKey</classname> or <classname>Gtk::GestureClick</classname>. Event controllers can be added to a widget with <methodname>Gtk::Widget::add_controller()</methodname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9215
msgid "You might occasionally find it useful to handle events when there's something you can't accomplish with normal signals. <classname>Gtk::Button</classname>, for example, does not send mouse-pointer coordinates with its <literal>clicked</literal> signal, but you could handle <methodname>Gtk::GestureClick::signal_pressed()</methodname> if you needed this information. <methodname>Gtk::EventControllerKey::signal_key_pressed()</methodname> is often used to handle key-presses."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9225
msgid "Some event controller signals behave slightly differently. The value returned from the signal handler indicates whether it has fully \"handled\" the event. If the value is <literal>false</literal> then <application>gtkmm</application> will pass the event on to the next signal handler. If the value is <literal>true</literal> then no other signal handlers will need to be called."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9233
msgid "Handling an event doesn't affect the Widget's other signals. If you handle <methodname>Gtk::GestureClick::signal_pressed()</methodname> for <classname>Gtk::Button</classname>, you'll still be able to get the <literal>clicked</literal> signal. They are emitted at (nearly) the same time."
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:9242
#, no-wrap
msgid ""
"\n"
"void on_button_press(int n_press, double x, double y);\n"
"Gtk::Button button(\"label\");\n"
"auto controller = Gtk::GestureClick::create();\n"
"controller-&gt;set_propagation_phase(Gtk::PropagationPhase::CAPTURE);\n"
"controller-&gt;signal_pressed().connect(sigc::ptr_fun(&amp;on_button_press));\n"
"button.add_controller(controller);\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9250
msgid "When the mouse is over the button and a mouse button is pressed, <methodname>on_button_press()</methodname> will be called."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9254
msgid "The call to <methodname>set_propagation_phase()</methodname> is necessary in this case because the <classname>GtkButton</classname> C class adds an event controller, handling button clicks in the capture phase. <classname>GtkButton</classname> claims the event, meaning that the event is not propagated in the bubble phase, where event controllers handle events by default."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:9263
msgid "Signal Handler sequence"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9265
msgid "By default, signal handlers that return <type>void</type> are called after any previously-connected signal handlers. However, this can be a problem with event signals that can stop event propagation by returning <literal>true</literal>. For instance, the existing signal handlers, or the default signal handler, might return <literal>true</literal> to stop other signal handlers from being called. To specify that your signal handler should be called before the other signal handlers, you can specify <literal>false</literal> for the <literal>after</literal> parameter. This <methodname>connect()</methodname> parameter is optional, if the signal handler returns <type>void</type>. For instance,"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:9275
#, no-wrap
msgid ""
"\n"
"key_controller-&gt;signal_key_pressed().connect(sigc::ptr_fun(&amp;on_mywindow_key_pressed), false);\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9278
msgid "The event is propagated between widgets in 3 phases. <_:orderedlist-1/>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9285
msgid "The <link xlink:href=\"https://docs.gtk.org/gtk4/input-handling.html\">Input Handling</link> chapter in the GTK documentation describes user input handling in more detail."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:9294
msgid "Exceptions in signal handlers"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9296
msgid "When a program is aborted because of an unhandled C++ exception, it's sometimes possible to use a debugger to find the location where the exception was thrown. This is more difficult than usual if the exception was thrown from a signal handler."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9301
msgid "This section describes primarily what you can expect on a Linux system, when you use <link xlink:href=\"http://www.gnu.org/software/gdb/\">the gdb debugger</link>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9305
msgid "First, let's look at a simple example where an exception is thrown from a normal function (no signal handler)."
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:9309
#, no-wrap
msgid ""
"\n"
"// without_signal.cc\n"
"#include &lt;gtkmm.h&gt;\n"
"\n"
"bool throwSomething()\n"
"{\n"
"  throw \"Something\";\n"
"  return true;\n"
"}\n"
"\n"
"int main(int argc, char** argv)\n"
"{\n"
"  throwSomething();\n"
"  auto app = Gtk::Application::create(\"org.gtkmm.without_signal\");\n"
"  return app-&gt;run();\n"
"}\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9326
msgid "Here is an excerpt from a <application>gdb</application> session. Only the most interesting parts of the output are shown."
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:9330
#, no-wrap
msgid ""
"\n"
"&gt; gdb without_signal\n"
"(gdb) run\n"
"terminate called after throwing an instance of 'char const*'\n"
"\n"
"Program received signal SIGABRT, Aborted.\n"
"(gdb) backtrace\n"
"#7  0x08048864 in throwSomething () at without_signal.cc:6\n"
"#8  0x0804887d in main (argc=1, argv=0xbfffecd4) at without_signal.cc:12\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9340
msgid "You can see that the exception was thrown from <filename>without_signal.cc</filename>, line 6 (<code>throw \"Something\";</code>)."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9343
msgid "Now let's see what happens when an exception is thrown from a signal handler. Here's the source code."
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:9347
#, no-wrap
msgid ""
"\n"
"// with_signal.cc\n"
"#include &lt;gtkmm.h&gt;\n"
"\n"
"bool throwSomething()\n"
"{\n"
"  throw \"Something\";\n"
"  return true;\n"
"}\n"
"\n"
"int main(int argc, char** argv)\n"
"{\n"
"  Glib::signal_timeout().connect(sigc::ptr_fun(throwSomething), 500);\n"
"  auto app = Gtk::Application::create(\"org.gtkmm.with_signal\");\n"
"  app-&gt;hold();\n"
"  return app-&gt;run();\n"
"}\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9365
msgid "And here's an excerpt from a <application>gdb</application> session."
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:9368
#, no-wrap
msgid ""
"\n"
"&gt; gdb with_signal\n"
"(gdb) run\n"
"(with_signal:2703): glibmm-ERROR **:\n"
"unhandled exception (type unknown) in signal handler\n"
"\n"
"Program received signal SIGTRAP, Trace/breakpoint trap.\n"
"(gdb) backtrace\n"
"#2  0x0063c6ab in glibmm_unexpected_exception () at exceptionhandler.cc:77\n"
"#3  Glib::exception_handlers_invoke () at exceptionhandler.cc:150\n"
"#4  0x0063d370 in glibmm_source_callback (data=0x804d620) at main.cc:212\n"
"#13 0x002e1b31 in Gtk::Application::run (this=0x804f300) at application.cc:178\n"
"#14 0x08048ccc in main (argc=1, argv=0xbfffecd4) at with_signal.cc:16\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9382
msgid "The exception is caught in <application>glibmm</application>, and the program ends with a call to <function>g_error()</function>. Other exceptions may result in different behavior, but in any case the exception from a signal handler is caught in <application>glibmm</application> or <application>gtkmm</application>, and <application>gdb</application> can't see where it was thrown."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9388
msgid "To see where the exception is thrown, you can use the <application>gdb</application> command <userinput>catch throw</userinput>."
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:9392
#, no-wrap
msgid ""
"\n"
"&gt; gdb with_signal\n"
"(gdb) catch throw\n"
"Catchpoint 1 (throw)\n"
"(gdb) run\n"
"Catchpoint 1 (exception thrown), 0x00714ff0 in __cxa_throw ()\n"
"(gdb) backtrace\n"
"#0  0x00714ff0 in __cxa_throw () from /usr/lib/i386-linux-gnu/libstdc++.so.6\n"
"#1  0x08048bd4 in throwSomething () at with_signal.cc:6\n"
"(gdb) continue\n"
"Continuing.\n"
"(with_signal:2375): glibmm-ERROR **\n"
"unhandled exception (type unknown) in signal handler\n"
"\n"
"Program received signal SIGTRAP, Trace/breakpoint trap.\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9408
msgid "If there are many caught exceptions before the interesting uncaught one, this method can be tedious. It can be automated with the following <application>gdb</application> commands."
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:9413
#, no-wrap
msgid ""
"\n"
"(gdb) catch throw\n"
"(gdb) commands\n"
"(gdb)   backtrace\n"
"(gdb)   continue\n"
"(gdb)   end\n"
"(gdb) set pagination off\n"
"(gdb) run\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9422
msgid "These commands will print a backtrace from each <code>throw</code> and continue. The backtrace from the last (or possibly the last but one) <code>throw</code> before the program stops, is the interesting one."
msgstr ""

#. (itstool) path: appendix/title
#: C/index-in.docbook:9431
msgid "Creating your own signals"
msgstr ""

#. (itstool) path: appendix/para
#: C/index-in.docbook:9433
msgid "Now that you've seen signals and signal handlers in <application>gtkmm</application>, you might like to use the same technique to allow interaction between your own classes. That's actually very simple by using the <application>libsigc++</application> library directly."
msgstr ""

#. (itstool) path: appendix/para
#: C/index-in.docbook:9439
msgid "This isn't purely a <application>gtkmm</application> or GUI issue. <application>gtkmm</application> uses <application>libsigc++</application> to implement its proxy wrappers for the <application>GTK</application> signal system, but for new, non-GTK signals, you can create pure C++ signals, using the <classname>sigc::signal&lt;&gt;</classname> template."
msgstr ""

#. (itstool) path: appendix/para
#: C/index-in.docbook:9446
msgid "For instance, to create a signal that sends 2 parameters, a <type>bool</type> and an <type>int</type>, just declare a <classname>sigc::signal</classname>, like so:"
msgstr ""

#. (itstool) path: appendix/programlisting
#: C/index-in.docbook:9451
#, no-wrap
msgid ""
"\n"
"sigc::signal&lt;void(bool, int)&gt; signal_something;\n"
""
msgstr ""

#. (itstool) path: appendix/para
#: C/index-in.docbook:9454
msgid "You could just declare that signal as a public member variable, but some people find that distasteful and prefer to make it available via an accessor method, like so:"
msgstr ""

#. (itstool) path: appendix/programlisting
#: C/index-in.docbook:9459
#, no-wrap
msgid ""
"\n"
"class Server\n"
"{\n"
"public:\n"
"  //signal accessor:\n"
"  using type_signal_something = sigc::signal&lt;void(bool, int)&gt;;\n"
"  type_signal_something signal_something();\n"
"\n"
"protected:\n"
"  type_signal_something m_signal_something;\n"
"};\n"
"\n"
"Server::type_signal_something Server::signal_something()\n"
"{\n"
"  return m_signal_something;\n"
"}\n"
""
msgstr ""

#. (itstool) path: appendix/para
#: C/index-in.docbook:9477
msgid "You can then connect to the signal using the same syntax used when connecting to <application>gtkmm</application> signals. For instance,"
msgstr ""

#. (itstool) path: appendix/programlisting
#: C/index-in.docbook:9481
#, no-wrap
msgid ""
"\n"
"server.signal_something().connect(\n"
"  sigc::mem_fun(client, &amp;Client::on_server_something) );\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9489
msgid "This is a full working example that defines and uses custom signals."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9493
msgid "<link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm-documentation/tree/master/examples/book/signals/custom/\">Source Code</link>"
msgstr ""

#. (itstool) path: appendix/title
#: C/index-in.docbook:9501
msgid "Comparison with other signalling systems"
msgstr ""

#. (itstool) path: appendix/para
#: C/index-in.docbook:9503
msgid "(An aside: <application>GTK</application> calls this scheme \"signalling\"; the sharp-eyed reader with GUI toolkit experience will note that this same design is often seen under the name of \"broadcaster-listener\" (e.g., in Metrowerks' PowerPlant framework for the Macintosh). It works in much the same way: one sets up <literal>broadcasters</literal>, and then connects <literal>listeners</literal> to them; the broadcaster keeps a list of the objects listening to it, and when someone gives the broadcaster a message, it calls all of its objects in its list with the message. In <application>gtkmm</application>, signal objects play the role of broadcasters, and slots play the role of listeners - sort of. More on this later.)"
msgstr ""

#. (itstool) path: appendix/para
#: C/index-in.docbook:9517
msgid "<application>gtkmm</application> signal handlers are strongly-typed, whereas <application>GTK</application> C code allows you to connect a callback with the wrong number and type of arguments, leading to a segfault at runtime. And, unlike <application>Qt</application>, <application>gtkmm</application> achieves this without modifying the C++ language."
msgstr ""

#. (itstool) path: appendix/para
#: C/index-in.docbook:9523
msgid "Re. Overriding signal handlers: You can do this in the straight-C world of GTK too; that's what GTK's object system is for. But in GTK, you have to go through some complicated procedures to get object-oriented features like inheritance and overloading. In C++, it's simple, since those features are supported in the language itself; you can let the compiler do the dirty work."
msgstr ""

#. (itstool) path: appendix/para
#: C/index-in.docbook:9531
msgid "This is one of the places where the beauty of C++ really comes out. One wouldn't think of subclassing a GTK widget simply to override its action method; it's just too much trouble. In GTK, you almost always use signals to get things done, unless you're writing a new widget. But because overriding methods is so easy in C++, it's entirely practical - and sensible - to subclass a button for that purpose."
msgstr ""

#. (itstool) path: appendix/title
#: C/index-in.docbook:9542
msgid "<application>gtkmm</application> and Win32"
msgstr ""

#. (itstool) path: appendix/para
#: C/index-in.docbook:9543
msgid "One of the major advantages of <application>gtkmm</application> is that it is crossplatform. <application>gtkmm</application> programs written on other platforms such as GNU/Linux can generally be transferred to Windows (and vice versa) with few modifications to the source."
msgstr ""

#. (itstool) path: appendix/para
#: C/index-in.docbook:9548
msgid "<application>gtkmm</application> currently works with the <link xlink:href=\"http://mingw.org/\">MinGW/GCC compiler</link> with a compiler version that supports C++17, such as gcc 7 or 8. It also works with Microsoft Visual C++ 2017 15.7.x or later (including the freely available express/community editions) on the Windows platform. There is an <link xlink:href=\"ftp://ftp.gnome.org/pub/GNOME/binaries/win32/gtkmm\">installer</link> available for <application>gtkmm</application> on Microsoft Windows, but as of this writing (October 2020) it has not been updated for a long time. Please be aware that although normally it is fine to mix builds done with Visual Studio 2017 and 2019, please do not do so when building <application>gtkmm</application> with its -mm dependencies."
msgstr ""

#. (itstool) path: appendix/para
#: C/index-in.docbook:9561
msgid "Refer to the <link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm/tree/master/README.win32\">README.win32</link>, as well as the <link xlink:href=\"https://gitlab.gnome.org/GNOME/gtkmm/tree/master/MSVC_NMake/README\">README</link> files in the <application>gtkmm</application>, pangomm and glibmm for instructions on how to build <application>gtkmm</application> on Windows."
msgstr ""

#. (itstool) path: appendix/title
#: C/index-in.docbook:9568
msgid "Working with gtkmm's Source Code"
msgstr ""

#. (itstool) path: appendix/para
#: C/index-in.docbook:9569
msgid "If you are interested in helping out with the development of <application>gtkmm</application>, or fixing a bug in <application>gtkmm</application>, you'll probably need to build the development version of <application>gtkmm</application>. However, you should not install a development version over your stable version. Instead, you should install it alongside your existing <application>gtkmm</application> installation, in a separate path."
msgstr ""

#. (itstool) path: appendix/para
#: C/index-in.docbook:9576
msgid "The easiest way to do this is using <link xlink:href=\"https://wiki.gnome.org/Projects/Jhbuild\">jhbuild</link>. <application>jhbuild</application> is a program that makes building GNOME software much easier by calculating dependencies and building things in the correct order. This section will give a brief explanation of how to set up <application>jhbuild</application> to build and install <application>gtkmm</application> from the source repository (git). For up-to-date information on <application>jhbuild</application>, please refer to the <link xlink:href=\"https://gnome.pages.gitlab.gnome.org/jhbuild/\">jhbuild manual</link>."
msgstr ""

#. (itstool) path: note/para
#: C/index-in.docbook:9586
msgid "Note that to build <application>gtkmm</application> from git, you'll often need to build many of its dependencies from git as well. <application>jhbuild</application> makes this easier than it would normally be, but it will take quite a while to build and install them all. You will probably encounter build problems, though these will usually be corrected quickly if you report them."
msgstr ""

#. (itstool) path: appendix/para
#: C/index-in.docbook:9594
msgid "<application>gnome-build-meta</application> is an alternative to <application>jhbuild</application>. It is described at the <link xlink:href=\"https://wiki.gnome.org/Newcomers/BuildSystemComponent\">Building system components</link> wiki page, but here we concentrate on <application>jhbuild</application>."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:9601
msgid "Setting up jhbuild"
msgstr ""

#. (itstool) path: para/screen
#: C/index-in.docbook:9610
#, no-wrap
msgid ""
"$ cp examples/sample.jhbuildrc ~/.config/jhbuildrc"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9603
msgid "To set up <application>jhbuild</application>, follow the basic installation instructions from the <link xlink:href=\"https://gnome.pages.gitlab.gnome.org/jhbuild/\">jhbuild manual</link>. After you have installed <application>jhbuild</application>, you should copy the sample <application>jhbuild</application> configuration file into your home directory by executing the following command from the <application>jhbuild</application> directory: <_:screen-1/>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9612
msgid "The <application>gtkmm</application> module is defined in the <filename>gnome-suites-core-deps-latest.modules</filename> moduleset. So edit your <filename>jhbuildrc</filename> file and set your moduleset setting like so:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:9617
#, no-wrap
msgid ""
"moduleset = 'gnome-suites-core-deps-latest'"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9618
msgid "After setting the correct moduleset, you need to tell <application>jhbuild</application> which module or modules to build. To build <application>gtkmm</application> and all of its dependencies, set <varname>modules</varname> like so:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:9624
#, no-wrap
msgid ""
"modules = [ 'gtkmm' ]"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9625
msgid "You can build several modules by setting the <varname>modules</varname> variable to a meta-package, e.g. <literal>meta-gnome-core</literal>, or listing more than one module name. The <varname>modules</varname> variable specifies which modules will be built when you don't explicitly specify anything on the command line. You can always build a different moduleset later by specifying it on the commandline (e.g. <command>jhbuild build gtkmm</command>)."
msgstr ""

#. (itstool) path: important/title
#: C/index-in.docbook:9635
msgid "Setting a prefix"
msgstr ""

#. (itstool) path: important/para
#: C/index-in.docbook:9636
msgid "By default, <application>jhbuild</application>'s configuration is configured to install all software built with <application>jhbuild</application> under the <filename>~/jhbuild/install</filename> prefix. You can choose a different prefix, but it is recommended that you keep this prefix different from other software that you've installed (don't set it to <filename>/usr</filename>!) If you've followed the jhbuild instructions then this prefix belongs to your user, so you don't need to run jhbuild as <literal>root</literal>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9648
msgid "You should also set <varname>buildroot</varname> in <filename>jhbuildrc</filename>. <application>jhbuild</application> builds <application>gtkmm</application> and many of its dependencies with Meson. Meson does not allow building in the source tree. <application>jhbuild</application>'s default action is to build in a <filename>build</filename> directory directly below the source root directory. Some modules have a <filename>build</filename> directory with files used when building with Autotools. Those files can be destroyed if you let <application>jhbuild</application> build in that directory."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9658
msgid "When you downloaded <application>jhbuild</application> from the git repository, you got a number of <filename>.modules</filename> files, specifying dependencies between modules. By default <application>jhbuild</application> does not use the downloaded versions of these files, but reads the latest versions in the git repository. This is usually what you want. If you don't want it, use the <varname>use_local_modulesets</varname> variable in <filename>jhbuildrc</filename>."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:9669
msgid "Installing and Using the git version of <application>gtkmm</application>"
msgstr ""

#. (itstool) path: para/screen
#: C/index-in.docbook:9678
#, no-wrap
msgid ""
"$ jhbuild bootstrap\n"
"$ jhbuild sanitycheck"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9671
msgid "Once you've configured <application>jhbuild</application> as described above, building <application>gtkmm</application> should be relatively straightforward. The first time you run <application>jhbuild</application>, you should run the following sequence of commands to ensure that <application>jhbuild</application> has the required tools and verify that it is set up correctly: <_:screen-1/>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:9682
msgid "Installing <application>gtkmm</application> with <application>jhbuild</application>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9684
msgid "If everything worked correctly, you should be able to build <application>gtkmm</application> and all of its dependencies from git by executing <command>jhbuild build</command> (or, if you didn't specify <application>gtkmm</application> in the <varname>modules</varname> variable, with the command <command>jhbuild build gtkmm</command>)."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9691
msgid "This command will build and install a series of modules and will probably take quite a long time the first time through. After the first time, however, it should go quite a bit faster since it only needs to rebuild files that changed since the last build. Alternatively, after you've built and installed <application>gtkmm</application> the first time, you can rebuild <application>gtkmm</application> by itself (without rebuilding all of its dependencies) with the command <command>jhbuild buildone gtkmm</command>."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:9702
msgid "Using the git version of <application>gtkmm</application>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9704
msgid "After you've installed the git version of <application>gtkmm</application>, you're ready to start using and experimenting with it. In order to use the new version of <application>gtkmm</application> you've just installed, you need to set some environment variables so that your <filename>configure</filename> or <filename>meson.build</filename> script knows where to find the new libraries. Fortunately, <application>jhbuild</application> offers an easy solution to this problem. Executing the command <command>jhbuild shell</command> will start a new shell with all of the correct environment variables set. Now if you re-configure and build your project just as you usually do, it should link against the newly installed libraries. To return to your previous environment, simply exit the <application>jhbuild</application> shell."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9718
msgid "Once you've built your software, you'll need to run your program within the jhbuild environment as well. To do this, you can again use the <command>jhbuild shell</command> command to start a new shell with the <application>jhbuild</application> environment set up. Alternatively, you can execute a one-off command in the <application>jhbuild</application> environment using the following command: <command>jhbuild run command-name</command>. In this case, the command will be run with the correct environment variables set, but will return to your previous environment after the program exits."
msgstr ""

#. (itstool) path: appendix/title
#: C/index-in.docbook:9735
msgid "Wrapping C Libraries with gmmproc"
msgstr ""

#. (itstool) path: appendix/para
#: C/index-in.docbook:9737
msgid "<application>gtkmm</application> uses the <command>gmmproc</command> tool to generate most of its source code, using .defs files that define the APIs of <classname>GObject</classname>-based libraries. So it's quite easy to create additional gtkmm-style wrappers of other glib/GObject-based libraries."
msgstr ""

#. (itstool) path: appendix/para
#: C/index-in.docbook:9742
msgid "This involves a variety of tools, some of them crufty, but at least they work, and has been used successfully by several projects."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:9747
msgid "The build structure"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9749
msgid "Generation of the source code for a gtkmm-style wrapper API requires use of tools such as <command>gmmproc</command> and <filename>generate_wrap_init.pl</filename>, which are included in <application>glibmm</application>. In theory you could write your own build files to use these appropriately, but a much better option is to make use of the build infrastructure provided by the <application>mm-common</application> module. To get started, it helps a lot to pick an existing binding module as an example to look at."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9757
msgid "For instance, let's pretend that we are wrapping a C library called libsomething. It provides a <classname>GObject</classname>-based API with types named, for instance, <classname>SomeWidget</classname> and <classname>SomeStuff</classname>."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:9763
msgid "Copying the skeleton project"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9765
msgid "Typically our wrapper library would be called libsomethingmm. We can start by copying the <link xlink:href=\"https://gitlab.gnome.org/GNOME/mm-common/tree/master/skeletonmm\"> skeleton source tree</link> from the <application>mm-common</application> module. Starting with <application>mm-common</application> 1.0.0 this skeleton application is built with the <link xlink:href=\"https://mesonbuild.com/\">Meson build system</link>."
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:9771
#, no-wrap
msgid ""
"\n"
"  $ git clone https://gitlab.gnome.org/GNOME/mm-common.git\n"
"  $ cp -a mm-common/skeletonmm libsomethingmm\n"
""
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:9780
msgid "<filename>libsomethingmm</filename>: The top-level directory."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:9782
msgid "<filename>libsomething</filename>: Contains the main include file and the pkg-config .pc file."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:9784
msgid "<filename>src</filename>: Contains .hg and .ccg source files."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:9785
msgid "<filename>libsomethingmm</filename>: Contains hand-written .h and .cc files."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9775
msgid "This provides a directory structure for the source .hg and .ccg files and the hand-written .h and .cc files, with <filename>meson.build</filename> files that can specify the various files in use, in terms of Meson variables. The directory structure usually looks like this, after we have renamed the directories appropriately: <_:itemizedlist-1/>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9794
msgid "As well as renaming the directories, we should rename some of the source files. For instance:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:9796
#, no-wrap
msgid ""
"\n"
"$ for f in $(find libsomethingmm -depth -name '*skeleton*'); do \\\n"
"    d=\"${f%/*}\"; b=\"${f##*/}\"; mv \"$f\" \"$d/${b//skeleton/libsomething}\"; \\\n"
"  done\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9801
msgid "A number of the skeleton files must still be filled in with project-specific content later."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9803
msgid "Note that files ending in <filename>.in</filename> will be used to generate files with the same name but without the <filename>.in</filename> suffix, by replacing some variables with actual values during the configure stage."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9806
msgid "Generated files are saved in the build tree, which is separated from the source tree when <command>meson</command> and <command>ninja</command> are used."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:9811
msgid "Modifying build files"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9813
msgid "Now we edit the files to adapt them to our needs. You might prefer to use a multiple-file search-replace utility for this, such as <command>regexxer</command>. Note that nearly all of the files provided with the skeleton source tree contain placeholder text. Thus, the substitutions should be performed globally, and not be limited to the Meson files."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9817
msgid "All mentions of <varname>skeleton</varname> should be replaced by the correct name of the C library you are wrapping, such as \"something\" or \"libsomething\". In the same manner, all instances of <varname>SKELETON</varname> should be replaced by \"SOMETHING\" or \"LIBSOMETHING\", and all occurrences of <varname>Skeleton</varname> changed to \"Something\"."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9821
msgid "Likewise, replace all instances of <varname>Joe Hacker</varname> by the name of the intended copyright holder, which is probably you. Do the same for the <varname>joe@example.com</varname> email address."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:9826
msgid "meson.build in the top-level directory"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:9830
msgid "It is common for binding modules to track the version number of the library they are wrapping. So, for instance, if the C library is at version 1.23.4, then the initial version of the binding module would be 1.23.0. However, avoid starting with an even minor version number as that usually indicates a stable release."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:9835
msgid "In the <function>project()</function> function, change the license and the C++ version, if necessary."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:9837
msgid "You probably need to add more required modules than <application>glibmm</application> and <application>skeleton</application> (<application>libsomething</application>)."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:9845
msgid "Other meson.build files"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:9849
msgid "<filename>skeleton/meson.build</filename>: Perhaps not much to change here more than the global name substitutions."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:9852
msgid "<filename>skeleton/skeletonmm/meson.build</filename>"
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:9855
msgid "<varname>defs_basefiles</varname>"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:9856
msgid "If we have more .defs and docs.xml files, we add them here."
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:9860
msgid "<varname>hg_ccg_basenames</varname>"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:9861
msgid "We must mention all of our <filename>.hg</filename> and <filename>.ccg</filename> files here."
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:9865
msgid "<varname>extra_cc_files, extra_h_files</varname>"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:9866
msgid "Any additional hand-written <filename>.h</filename> and <filename>.cc</filename> source files go here."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9847
msgid "Next we must adapt the other <filename>meson.build</filename> files: <_:itemizedlist-1/>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:9876
msgid "Creating .hg and .ccg files"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9878
msgid "We should now create our first <filename>.hg</filename> and <filename>.ccg</filename> files, to wrap one of the objects in the C library. One pair of example source files already exists: <filename>skeleton.ccg</filename> and <filename>skeleton.hg</filename>. Create copies of these files as necessary."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9882
msgid "In the <link linkend=\"sec-wrapping-hg-files\">.hg and .ccg files</link> section you can learn about the syntax used in these files."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:9889
msgid "Generating the .defs files."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:9894
msgid "objects (GObjects, widgets, interfaces, boxed-types and plain structs)"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:9895
msgid "functions"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:9896
msgid "enums"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:9897
msgid "signals"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:9898
msgid "properties"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:9899
msgid "vfuncs"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9891
msgid "The <filename>.defs</filename> files are text files, in a lisp format, that describe the API of a C library, including its <_:itemizedlist-1/>"
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:9908
msgid "<filename>gtk.defs</filename>"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:9909
msgid "Includes the other files."
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:9912
msgid "<filename>gtk_methods.defs</filename>"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:9913
msgid "Objects and functions."
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:9916
msgid "<filename>gtk_enums.defs</filename>"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:9917
msgid "Enumerations."
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:9920
msgid "<filename>gtk_signals.defs</filename>"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:9921
msgid "Signals and properties."
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:9924
msgid "<filename>gtk_vfuncs.defs</filename>"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:9925
msgid "vfuncs (function pointer member fields in structs), written by hand."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9902
msgid "At the moment, we have separate tools for generating different parts of these <filename>.defs</filename>, so we split them up into separate files. For instance, in the <filename>gtk/src</filename> directory of the <application>gtkmm</application> sources, you will find these files: <_:variablelist-1/>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9929
msgid "The <filename>skeletonmm/tools/generate_defs_and_docs.sh</filename> script generates all <filename>.defs</filename> files and the <filename>*_docs.xml</filename> file, described in the <link linkend=\"sec-wrapping-documentation\">Documentation</link> section."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:9935
msgid "Generating the methods .defs"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9937
msgid "This <filename>.defs</filename> file describes objects and their functions. It is generated by the <command>h2def.py</command> script which you can find in glibmm's <filename>tools/defs_gen</filename> directory. For instance,"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:9941
#, no-wrap
msgid ""
"\n"
"$ ./h2def.py /usr/include/gtk-4.0/gtk/*.h &gt; gtk_methods.defs\n"
""
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:9947
msgid "Generating the enums .defs"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9949
msgid "This <filename>.defs</filename> file describes enum types and their possible values. It is generated by the <filename>enumextract.py</filename> script which you can also find in glibmm's <filename>tools/defs_gen</filename> directory. For instance,"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:9953
#, no-wrap
msgid ""
"\n"
"$ ./enumextract.py /usr/include/gtk-4.0/gtk/*.h &gt; gtk_enums.defs\n"
""
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:9959
msgid "Generating the signals and properties .defs"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9961
msgid "This <filename>.defs</filename> file describes signals and properties. It is generated by the special <filename>generate_extra_defs</filename> utility that is in every wrapping project, such as <filename>gtkmm/tools/extra_defs_gen/</filename>. For instance"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:9966
#, no-wrap
msgid ""
"\n"
"$ cd tools/extra_defs_gen\n"
"$ ./generate_extra_defs &gt; gtk_signals.defs\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9970
msgid "You must edit the source code of your own <filename>generate_extra_defs</filename> tool in order to generate the <filename>.defs</filename> for the GObject C types that you wish to wrap. In the skeleton source tree, the source file is named <filename>tools/extra_defs_gen/generate_defs_skeleton.cc</filename>. If not done so already, the file should be renamed, with the basename of your new binding substituted for the <varname>skeleton</varname> placeholder. The <filename>tools/extra_defs_gen/meson.build</filename> file should also mention the new source filename."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9977
msgid "Then edit the <filename>.cc</filename> file to specify the correct types. For instance, your <function>main()</function> function might look like this:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:9980
#, no-wrap
msgid ""
"\n"
"#include &lt;glibmm_generate_extra_defs/generate_extra_defs.h&gt;\n"
"#include &lt;libsomething.h&gt;\n"
"#include &lt;iostream&gt;\n"
"\n"
"int main(int, char**)\n"
"{\n"
"  something_init();\n"
"\n"
"  std::cout &lt;&lt; get_defs(SOME_TYPE_WIDGET)\n"
"            &lt;&lt; get_defs(SOME_TYPE_STUFF);\n"
"  return 0;\n"
"}\n"
""
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:9997
msgid "Writing the vfuncs .defs"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:9999
msgid "This <filename>.defs</filename> file describes virtual functions (vfuncs). It must be written by hand. There is the skeleton file <filename>skeleton/src/skeleton_vfunc.defs</filename> to start from. You can also look at <application>gtkmm</application>'s <filename>gtk/src/gtk_vfuncs.defs</filename> file."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:10010
msgid "The .hg and .ccg files"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10011
msgid "The .hg and .ccg source files are very much like .h and .cc C++ source files, but they contain extra macros, such as <function>_CLASS_GOBJECT()</function> and <function>_WRAP_METHOD()</function>, from which <command>gmmproc</command> generates appropriate C++ source code, usually at the same position in the header. Any additional C++ source code will be copied verbatim into the corresponding .h or .cc file."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10019
msgid "A .hg file will typically include some headers and then declare a class, using some macros to add API or behavior to this class. For instance, <application>gtkmm</application>'s <filename>button.hg</filename> looks roughly like this:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:10024
#, no-wrap
msgid ""
"\n"
"#include &lt;gtkmm/widget.h&gt;\n"
"#include &lt;gtkmm/actionable.h&gt;\n"
"_DEFS(gtkmm,gtk)\n"
"_PINCLUDE(gtkmm/private/widget_p.h)\n"
"\n"
"namespace Gtk\n"
"{\n"
"\n"
"class Button\n"
"  : public Widget,\n"
"    public Actionable\n"
"{\n"
"  _CLASS_GTKOBJECT(Button, GtkButton, GTK_BUTTON, Gtk::Widget, GtkWidget)\n"
"  _IMPLEMENTS_INTERFACE(Actionable)\n"
"public:\n"
"\n"
"  _CTOR_DEFAULT\n"
"  explicit Button(const Glib::ustring&amp; label, bool mnemonic = false);\n"
"\n"
"  _WRAP_METHOD(void set_label(const Glib::ustring&amp; label), gtk_button_set_label)\n"
"\n"
"  ...\n"
"\n"
"  _WRAP_SIGNAL(void clicked(), \"clicked\")\n"
"\n"
"  ...\n"
"\n"
"  _WRAP_PROPERTY(\"label\", Glib::ustring)\n"
"};\n"
"\n"
"} // namespace Gtk\n"
""
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:10060
msgid "<function>_DEFS()</function>"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:10061
msgid "Specifies the destination directory for generated sources, and the name of the main .defs file that <command>gmmproc</command> should parse."
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:10064
msgid "<function>_PINCLUDE()</function>"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:10065
msgid "Tells <command>gmmproc</command> to include a header in the generated <filename>private/button_p.h</filename> file."
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:10068
msgid "<function>_CLASS_GTKOBJECT()</function>"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:10069
msgid "Tells <command>gmmproc</command> to add some typedefs, constructors, and standard methods to this class, as appropriate when wrapping a widget."
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:10072
msgid "<function>_IMPLEMENTS_INTERFACE()</function>"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:10073
msgid "Tells <command>gmmproc</command> to add initialization code for the interface."
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:10076
msgid "<function>_CTOR_DEFAULT</function>"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:10077
msgid "Adds a default constructor."
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:10080
msgid "<function>_WRAP_METHOD()</function>, <function>_WRAP_SIGNAL()</function>, and <function>_WRAP_PROPERTY()</function>"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:10083
msgid "Add methods to wrap parts of the C API."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10057
msgid "The macros in this example do the following: <_:variablelist-1/>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10087
msgid "The .h and .cc files will be generated from the .hg and .ccg files by processing them with <command>gmmproc</command> like so, though this happens automatically when using the above build structure:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:10091
#, no-wrap
msgid ""
"\n"
"$ cd gtk/src\n"
"$ /usr/lib/glibmm-2.68/proc/gmmproc -I ../../tools/m4 --defs . button . ./../gtkmm\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10095
msgid "Notice that we provided <command>gmmproc</command> with the path to the .m4 convert files, the path to the .defs file, the name of a .hg file, the source directory, and the destination directory."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10098
msgid "You should avoid including the C header from your C++ header, to avoid polluting the global namespace, and to avoid exporting unnecessary public API. But you will need to include the necessary C headers from your .ccg file."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10103
msgid "The macros are explained in more detail in the following sections."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:10106
msgid "m4 Conversions"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10108
msgid "The macros that you use in the .hg and .ccg files often need to know how to convert a C++ type to a C type, or vice-versa. <command>gmmproc</command> takes this information from an .m4 file in your <literal>tools/m4/</literal> or <literal>codegen/m4/</literal> directory. This allows it to call a C function in the implementation of your C++ method, passing the appropriate parameters to that C function. For instance, this tells <command>gmmproc</command> how to convert a <classname>GtkTreeView</classname> pointer to a <classname>Gtk::TreeView</classname> pointer:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:10116
#, no-wrap
msgid ""
"\n"
"_CONVERSION(`GtkTreeView*',`TreeView*',`Glib::wrap($3)')\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10120
msgid "<literal>$3</literal> will be replaced by the parameter name when this conversion is used by <command>gmmproc</command>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10124
msgid "Some extra macros make this easier and consistent. Look in <application>gtkmm</application>'s .m4 files for examples. For instance:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:10128
#, no-wrap
msgid ""
"\n"
"_CONVERSION(`PrintSettings&amp;',`GtkPrintSettings*',__FR2P)\n"
"_CONVERSION(`const PrintSettings&amp;',`GtkPrintSettings*',__FCR2P)\n"
"_CONVERSION(`const Glib::RefPtr&lt;Printer&gt;&amp;',`GtkPrinter*',__CONVERT_REFPTR_TO_P($3))\n"
""
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:10136
msgid "m4 Initializations"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10138
msgid "Often when wrapping methods, it is desirable to store the return of the C function in what is called an output parameter. In this case, the C++ method returns <type>void</type> but an output parameter in which to store the value of the C function is included in the argument list of the C++ method. <command>gmmproc</command> allows such functionality, but appropriate initialization macros must be included to tell <command>gmmproc</command> how to initialize the C++ parameter from the return of the C function."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10147
msgid "For example, if there was a C function that returned a <type>GtkWidget*</type> and for some reason, instead of having the C++ method also return the widget, it was desirable to have the C++ method place the widget in a specified output parameter, an initialization macro such as the following would be necessary:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:10154
#, no-wrap
msgid ""
"\n"
"_INITIALIZATION(`Gtk::Widget&amp;',`GtkWidget*',`$3 = Glib::wrap($4)')\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10158
msgid "<literal>$3</literal> will be replaced by the output parameter name of the C++ method and <literal>$4</literal> will be replaced by the return of the C function when this initialization is used by <command>gmmproc</command>. For convenience, <literal>$1</literal> will also be replaced by the C++ type without the ampersand (&amp;) and <literal>$2</literal> will be replaced by the C type."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:10168
msgid "Class macros"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10170
msgid "The class macro declares the class itself and its relationship with the underlying C type. It generates some internal constructors, the member <varname>gobject_</varname>, typedefs, the <function>gobj()</function> accessors, type registration, and the <function>Glib::wrap()</function> method, among other things."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10175
msgid "Other macros, such as <function>_WRAP_METHOD()</function> and <function>_WRAP_SIGNAL()</function> may only be used after a call to a <function>_CLASS_*</function> macro."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:10180
msgid "_CLASS_GOBJECT"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10182
msgid "This macro declares a wrapper for a type that is derived from <classname>GObject</classname>, but whose wrapper is not derived from <classname>Gtk::Object</classname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10185
msgid "<function>_CLASS_GOBJECT( C++ class, C class, C casting macro, C++ base class, C base class )</function>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10186
msgid "For instance, from <filename>adjustment.hg</filename>:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:10187
#, no-wrap
msgid ""
"\n"
"_CLASS_GOBJECT(Adjustment, GtkAdjustment, GTK_ADJUSTMENT, Glib::Object, GObject)\n"
""
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:10193
msgid "_CLASS_GTKOBJECT"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10195
msgid "This macro declares a wrapper for a type whose wrapper is derived from <classname>Gtk::Object</classname>, such as a widget or dialog."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10197
msgid "<function>_CLASS_GTKOBJECT( C++ class, C class, C casting macro, C++ base class, C base class )</function>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10198
#: C/index-in.docbook:10702
#: C/index-in.docbook:10807
msgid "For instance, from <filename>button.hg</filename>:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:10199
#, no-wrap
msgid ""
"\n"
"_CLASS_GTKOBJECT(Button, GtkButton, GTK_BUTTON, Gtk::Widget, GtkWidget)\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10202
msgid "You will typically use this macro when the class already derives from <classname>Gtk::Object</classname>. For instance, you will use it when wrapping a GTK Widget, because <classname>Gtk::Widget</classname> derives from <classname>Gtk::Object</classname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10206
msgid "You might also derive non-widget classes from <classname>Gtk::Object</classname> so they can be used without <classname>Glib::RefPtr</classname>. For instance, they could then be instantiated with <function>Gtk::make_managed()</function> or on the stack as a member variable. This is convenient, but you should use this only when you are sure that true reference-counting is not needed. We consider it useful for widgets."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:10216
msgid "_CLASS_BOXEDTYPE"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10218
msgid "This macro declares a wrapper for a non-<classname>GObject</classname> struct, registered with <function>g_boxed_type_register_static()</function>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10221
msgid "<function>_CLASS_BOXEDTYPE( C++ class, C class, new function, copy function, free function )</function>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10222
msgid "For instance, from <classname>Gdk::RGBA</classname>:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:10223
#, no-wrap
msgid ""
"\n"
"_CLASS_BOXEDTYPE(RGBA, GdkRGBA, NONE, gdk_rgba_copy, gdk_rgba_free)\n"
""
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:10229
msgid "_CLASS_BOXEDTYPE_STATIC"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10231
msgid "This macro declares a wrapper for a simple assignable struct such as <classname>GdkRectangle</classname>. It is similar to <function>_CLASS_BOXEDTYPE</function>, but the C struct is not allocated dynamically."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10235
msgid "<function>_CLASS_BOXEDTYPE_STATIC( C++ class, C class )</function>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10236
msgid "For instance, for <classname>Gdk::Rectangle</classname>:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:10237
#, no-wrap
msgid ""
"\n"
"_CLASS_BOXEDTYPE_STATIC(Rectangle, GdkRectangle)\n"
""
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:10243
msgid "_CLASS_OPAQUE_COPYABLE"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10245
msgid "This macro declares a wrapper for an opaque struct that has copy and free functions. The new, copy and free functions will be used to instantiate the default constructor, copy constructor and destructor."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10248
msgid "<function>_CLASS_OPAQUE_COPYABLE( C++ class, C class, new function, copy function, free function )</function>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10249
msgid "For instance, from <classname>Glib::VariantType</classname>:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:10250
#, no-wrap
msgid ""
"\n"
"_CLASS_OPAQUE_COPYABLE(VariantType, GVariantType, NONE, g_variant_type_copy, g_variant_type_free)\n"
""
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:10256
msgid "_CLASS_OPAQUE_REFCOUNTED"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10258
msgid "This macro declares a wrapper for a reference-counted opaque struct. The C++ wrapper cannot be directly instantiated and can only be used with <classname>Glib::RefPtr</classname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10261
msgid "<function>_CLASS_OPAQUE_REFCOUNTED( C++ class, C class, new function, ref function, unref function )</function>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10262
msgid "For instance, for <classname>Gtk::CssSection</classname>:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:10263
#, no-wrap
msgid ""
"\n"
"_CLASS_OPAQUE_REFCOUNTED(CssSection, GtkCssSection, NONE, gtk_css_section_ref, gtk_css_section_unref)\n"
""
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:10269
msgid "_CLASS_GENERIC"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10271
msgid "This macro can be used to wrap structs which don't fit into any specialized category."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10273
msgid "<function>_CLASS_GENERIC( C++ class, C class )</function>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10274
msgid "For instance, for <classname>Gdk::TimeCoord</classname>:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:10275
#, no-wrap
msgid ""
"\n"
"_CLASS_GENERIC(TimeCoord, GdkTimeCoord)\n"
""
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:10281
msgid "_CLASS_INTERFACE"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10283
msgid "This macro declares a wrapper for a type that is derived from <classname>GTypeInterface</classname>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10286
msgid "<function>_CLASS_INTERFACE( C++ class, C class, C casting macro, C interface struct, Base C++ class (optional), Base C class (optional) )</function>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10287
msgid "For instance, from <filename>celleditable.hg</filename>:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:10289
#, no-wrap
msgid ""
"\n"
"_CLASS_INTERFACE(CellEditable, GtkCellEditable, GTK_CELL_EDITABLE, GtkCellEditableIface)\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10292
msgid "Two extra optional parameters were once added, for the case that the interface derives from another interface, which was believed to be the case when the GInterface has another GInterface as a prerequisite. This is a misunderstanding, though. When GInterface A has GInterface B as a prerequisite, it means that every class that implements A shall also implement B. For instance, from <filename>loadableicon.hg</filename> in glibmm-2.4:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:10298
#, no-wrap
msgid ""
"\n"
"_CLASS_INTERFACE(LoadableIcon, GLoadableIcon, G_LOADABLE_ICON, GLoadableIconIface, Icon, GIcon)\n"
""
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:10306
msgid "Constructor macros"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10308
msgid "The <function>_CTOR_DEFAULT()</function> and <function>_WRAP_CTOR()</function> macros add constructors, wrapping the specified <function>*_new()</function> C functions. These macros assume that the C object has properties with the same names as the function parameters, as is usually the case, so that it can supply the parameters directly to a <function>g_object_new()</function> call. These constructors never actually call the <function>*_new()</function> C functions, because <application>gtkmm</application> must actually instantiate derived GTypes, and the <function>*_new()</function> C functions are meant only as convenience functions for C programmers."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10318
msgid "When using <function>_CLASS_GOBJECT()</function>, the constructors should be protected (rather than public) and each constructor should have a corresponding <function>_WRAP_CREATE()</function> in the public section. This prevents the class from being instantiated without using a <classname>RefPtr</classname>. For instance:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:10323
#, no-wrap
msgid ""
"\n"
"class TextMark : public Glib::Object\n"
"{\n"
"  _CLASS_GOBJECT(TextMark, GtkTextMark, GTK_TEXT_MARK, Glib::Object, GObject)\n"
"\n"
"protected:\n"
"  _WRAP_CTOR(TextMark(const Glib::ustring&amp; name, bool left_gravity = true), gtk_text_mark_new)\n"
"\n"
"public:\n"
"  _WRAP_CREATE(const Glib::ustring&amp; name, bool left_gravity = true)\n"
""
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:10336
msgid "_CTOR_DEFAULT"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10338
msgid "This macro creates a default constructor with no arguments."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:10343
msgid "_WRAP_CTOR"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10345
msgid "This macro creates a constructor with arguments, equivalent to a <function>*_new()</function> C function. It won't actually call the <function>*_new()</function> function, but will simply create an equivalent constructor with the same argument types. It takes a C++ constructor signature, and a C function name."
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:10355
#: C/index-in.docbook:10874
msgid "errthrow"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:10357
msgid "This tells <command>gmmproc</command> that the C <function>*_new()</function> has a final <type>GError**</type> parameter which should be ignored."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10352
msgid "It also takes an optional extra argument: <_:variablelist-1/>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:10366
msgid "Hand-coding constructors"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10368
msgid "When a constructor must be partly hand written because, for instance, the <function>*_new()</function> C function's parameters do not correspond directly to object properties, or because the <function>*_new()</function> C function does more than call <function>g_object_new()</function>, the <function>_CONSTRUCT()</function> macro may be used in the .ccg file to save some work. The <function>_CONSTRUCT</function> macro takes a series of property names and values. For instance, from <filename>button.ccg</filename>:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:10376
#, no-wrap
msgid ""
"\n"
"Button::Button(const Glib::ustring&amp; label, bool mnemonic)\n"
":\n"
"  _CONSTRUCT(\"label\", label.c_str(), \"use_underline\", gboolean(mnemonic))\n"
"{}\n"
""
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:10387
msgid "Macros that suppress generation of some code"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10389
msgid "Some macros suppress the generation of some code when they are used after a <function>_CLASS_*</function> macro. Some suppress the definition in the generated .cc file, others suppress both the declaration in the .h file and the definition in the .cc file."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:10396
msgid "_CUSTOM_DEFAULT_CTOR"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10398
msgid "Suppresses declaration and definition of default constructor in <function>_CLASS_BOXEDTYPE</function>, <function>_CLASS_BOXEDTYPE_STATIC</function> and <function>_CLASS_OPAQUE_COPYABLE</function>."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:10405
msgid "_CUSTOM_CTOR_CAST"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10407
msgid "Suppresses declaration and definition of the constructor that takes a pointer to the wrapped C object in <function>_CLASS_BOXEDTYPE</function> and <function>_CLASS_BOXEDTYPE_STATIC</function>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10411
msgid "Suppresses definition of the constructor that takes a pointer to the wrapped C object in <function>_CLASS_INTERFACE</function> and <function>_CLASS_OPAQUE_COPYABLE</function>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10415
msgid "Suppresses definition of the constructor that takes a pointer to the wrapped C object and the constructor that takes construct_params in <function>_CLASS_GOBJECT</function> and <function>_CLASS_GTKOBJECT</function>."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:10422
msgid "_CUSTOM_DTOR"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10424
msgid "Suppresses definition of destructor in <function>_CLASS_GOBJECT</function> and <function>_CLASS_GTKOBJECT</function>."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:10430
msgid "_CUSTOM_MOVE_OPERATIONS"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10432
msgid "Suppresses declaration and definition of move constructor and move assignment operator in <function>_CLASS_GOBJECT</function> and <function>_CLASS_GTKOBJECT</function>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10436
msgid "For example:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:10437
#, no-wrap
msgid ""
"\n"
"class Derived : public Glib::Object\n"
"{\n"
"  _CLASS_GOBJECT(Derived, GDerived, G_DERIVED, Glib::Object, GObject)\n"
"\n"
"  _CUSTOM_MOVE_OPERATIONS\n"
"\n"
"public:\n"
"  Derived(Derived&amp;&amp; src) noexcept;\n"
"  Derived&amp; operator=(Derived&amp;&amp; src) noexcept;\n"
"  // ...\n"
"};\n"
""
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:10453
msgid "_CUSTOM_WRAP_NEW"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10455
msgid "Suppresses definition of <function>Glib::wrap_new()</function> function in <function>_CLASS_GOBJECT</function>."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:10461
msgid "_CUSTOM_WRAP_FUNCTION"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10463
msgid "Suppresses definition of <function>Glib::wrap()</function> function in <function>_CLASS_GOBJECT</function> and <function>_CLASS_GTKOBJECT</function>."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:10469
msgid "_NO_WRAP_FUNCTION"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10471
msgid "Suppresses declaration and definition of <function>Glib::wrap()</function> function in <function>_CLASS_GOBJECT</function>, <function>_CLASS_BOXEDTYPE</function>, <function>_CLASS_BOXEDTYPE_STATIC</function>, <function>_CLASS_OPAQUE_COPYABLE</function>, <function>_CLASS_INTERFACE</function> and <function>_CLASS_GTKOBJECT</function>."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:10481
msgid "Method macros"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:10484
msgid "_WRAP_METHOD"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10486
msgid "This macro generates the C++ method to wrap a C function."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10487
msgid "<function>_WRAP_METHOD( C++ method signature, C function name)</function>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10488
msgid "For instance, from <filename>entry.hg</filename>:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:10489
#, no-wrap
msgid ""
"\n"
"_WRAP_METHOD(void set_text(const Glib::ustring&amp; text), gtk_entry_set_text)\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10492
msgid "The C function (e.g. <function>gtk_entry_set_text</function>) is described more fully in the .defs file, and the <filename>convert*.m4</filename> files contain the necessary conversion from the C++ parameter type to the C parameter type. This macro also generates doxygen documentation comments based on the <filename>*_docs.xml</filename> and <filename>*_docs_override.xml</filename> files."
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:10501
#: C/index-in.docbook:10739
#: C/index-in.docbook:10849
msgid "refreturn"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:10503
msgid "Do an extra <function>reference()</function> on the return value, in case the C function does not provide a reference."
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:10508
#: C/index-in.docbook:10639
msgid "errthrow [\"&lt;exceptions&gt;\"]"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:10510
msgid "Use the last GError** parameter of the C function to throw an exception. The optional \"&lt;exceptions&gt;\" is a comma-separated list of exceptions that can be thrown. It determines which @throws Doxygen commands are added to the documentation. Default value is <classname>Glib::Error</classname>. If you want a comma in the description of an exception, precede it by a backslash. Example: <code>errthrow \"Glib::OptionError Hello\\, world, Glib::ConvertError\"</code>"
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:10521
#: C/index-in.docbook:10747
#: C/index-in.docbook:10814
#: C/index-in.docbook:11057
msgid "deprecated [\"&lt;text&gt;\"]"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:10523
#: C/index-in.docbook:10749
#: C/index-in.docbook:10816
#: C/index-in.docbook:11059
msgid "Puts the generated code in #ifdef blocks. Text about the deprecation can be specified as an optional parameter."
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:10529
msgid "ignore_deprecations"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:10531
msgid "Puts the generated code in the .cc file in a G_GNUC_BEGIN_IGNORE_DEPRECATIONS / G_GNUC_END_IGNORE_DEPRECATIONS block. (Only in glibmm &gt;= 2.70.1)"
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:10537
msgid "constversion"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:10539
msgid "Just call the non-const version of the same function, instead of generating almost duplicate code."
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:10544
#: C/index-in.docbook:10652
#: C/index-in.docbook:10754
#: C/index-in.docbook:10821
#: C/index-in.docbook:11064
msgid "newin \"&lt;version&gt;\""
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:10546
#: C/index-in.docbook:10654
#: C/index-in.docbook:10756
#: C/index-in.docbook:10823
#: C/index-in.docbook:11066
msgid "Adds a @newin Doxygen command to the documentation, or replaces the @newin command generated from the C documentation."
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:10551
#: C/index-in.docbook:10761
#: C/index-in.docbook:10896
#: C/index-in.docbook:10984
msgid "ifdef &lt;identifier&gt;"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:10553
#: C/index-in.docbook:10763
#: C/index-in.docbook:10898
#: C/index-in.docbook:10986
msgid "Puts the generated code in #ifdef blocks."
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:10557
#: C/index-in.docbook:10902
msgid "slot_name &lt;parameter_name&gt;"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:10559
#: C/index-in.docbook:10904
msgid "Specifies the name of the slot parameter of the method, if it has one. This enables <command>gmmproc</command> to generate code to copy the slot and pass the copy on to the C function in its final <literal>gpointer user_data</literal> parameter. The <literal>slot_callback</literal> option must also be used to specify the name of the glue callback function to also pass on to the C function."
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:10569
#: C/index-in.docbook:10914
msgid "slot_callback &lt;function_name&gt;"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:10571
#: C/index-in.docbook:10916
msgid "Used in conjunction with the <literal>slot_name</literal> option to specify the name of the glue callback function that handles extracting the slot and then calling it. The address of this callback is also passed on to the C function that the method wraps."
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:10579
#: C/index-in.docbook:10924
msgid "no_slot_copy"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:10581
#: C/index-in.docbook:10926
msgid "Tells <command>gmmproc</command> not to pass a copy of the slot to the C function, if the method has one. Instead the slot itself is passed. The slot parameter name and the glue callback function must have been specified with the <literal>slot_name</literal> and <literal>slot_callback</literal> options respectively."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10498
#: C/index-in.docbook:10636
#: C/index-in.docbook:10709
#: C/index-in.docbook:10811
#: C/index-in.docbook:10846
#: C/index-in.docbook:11002
msgid "There are some optional extra arguments: <_:variablelist-1/>"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:10594
msgid "Objects used via <classname>RefPtr</classname>: Pass the <classname>RefPtr</classname> as a const reference. For instance, <code>const Glib::RefPtr&lt;Gtk::FileFilter&gt;&amp; filter</code>."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:10598
msgid "Const Objects used via <classname>RefPtr</classname>: If the object should not be changed by the function, then make sure that the object is const, even if the <classname>RefPtr</classname> is already const. For instance, <code>const Glib::RefPtr&lt;const Gtk::FileFilter&gt;&amp; filter</code>."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:10603
msgid "Wrapping <classname>GList*</classname> and <classname>GSList*</classname> parameters: First, you need to discover what objects are contained in the list's data field for each item, usually by reading the documentation for the C function. The list can then be wrapped by a <classname>std::vector</classname> type. For instance, <code>std::vector&lt;Glib::RefPtr&lt;Gdk::Pixbuf&gt;&gt;</code>. You may need to define a Traits type to specify how the C and C++ types should be converted."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:10611
msgid "Wrapping <classname>GList*</classname> and <classname>GSList*</classname> return types: You must discover whether the caller should free the list and whether it should release the items in the list, again by reading the documentation of the C function. With this information you can choose the ownership (none, shallow or deep) for the m4 conversion rule, which you should probably put directly into the .hg file because the ownership depends on the function rather than the type. For instance:"
msgstr ""

#. (itstool) path: listitem/programlisting
#: C/index-in.docbook:10619
#, no-wrap
msgid ""
"#m4 _CONVERSION(`GSList*',`std::vector&lt;Widget*&gt;',`Glib::SListHandler&lt;Widget*&gt;::slist_to_vector($3, Glib::OWNERSHIP_SHALLOW)')"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10590
msgid "Selecting which C++ types should be used is also important when wrapping C API. Though it's usually obvious what C++ types should be used in the C++ method, here are some hints: <_:itemizedlist-1/>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:10625
msgid "_WRAP_METHOD_DOCS_ONLY"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10627
msgid "This macro is like <function>_WRAP_METHOD()</function>, but it generates only the documentation for a C++ method that wraps a C function. Use this when you must hand-code the method, but you want to use the documentation that would be generated if the method was generated."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10631
msgid "<function>_WRAP_METHOD_DOCS_ONLY(C function name)</function>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10632
msgid "For instance, from <filename>recentinfo.hg</filename>:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:10633
#, no-wrap
msgid ""
"\n"
"_WRAP_METHOD_DOCS_ONLY(gtk_recent_info_get_applications)\n"
""
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:10641
msgid "Excludes documentation of the last GError** parameter of the C function. The optional \"&lt;exceptions&gt;\" is a comma-separated list of exceptions that can be thrown. It determines which @throws Doxygen commands are added to the documentation. Default value is <classname>Glib::Error</classname>. If you want a comma in the description of an exception, precede it by a backslash. Example: <code>errthrow \"Glib::OptionError Hello\\, world, Glib::ConvertError\"</code>"
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:10659
msgid "voidreturn"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:10661
msgid "Don't include a @return Doxygen command in the documentation. Useful if the wrapped C function returns a value, but the corresponding C++ method returns <type>void</type>."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:10671
msgid "_IGNORE, _IGNORE_SIGNAL, _IGNORE_PROPERTY"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10673
msgid "<command>gmmproc</command> will warn you on stdout about functions, signals, properties and child properties that you have forgotten to wrap, helping to ensure that you are wrapping the complete API. But if you don't want to wrap some functions, signals, properties or child properties, or if you chose to hand-code some methods then you can use the _IGNORE(), _IGNORE_SIGNAL() or _IGNORE_PROPERTY() macro to make <command>gmmproc</command> stop complaining."
msgstr ""

#. (itstool) path: para/literallayout
#: C/index-in.docbook:10681
#, no-wrap
msgid ""
"<function>_IGNORE(C function name 1, C function name 2, etc)\n"
"_IGNORE_SIGNAL(C signal name 1, C signal name 2, etc)\n"
"_IGNORE_PROPERTY(C property name 1, C property name 2, etc)</function>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10685
msgid "For instance, from <filename>flowbox.hg</filename>:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:10686
#, no-wrap
msgid ""
"\n"
"_IGNORE(gtk_flow_box_set_filter_func, gtk_flow_box_set_sort_func)\n"
"_IGNORE_SIGNAL(activate-cursor-child, toggle-cursor-child, move-cursor)\n"
""
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:10693
msgid "_WRAP_SIGNAL"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10695
msgid "This macro generates the C++ libsigc++-style signal to wrap a C GObject signal. It actually generates a public accessor method, such as <function>signal_clicked()</function>, which returns a proxy object. <command>gmmproc</command> uses the .defs file to discover the C parameter types and the .m4 convert files to discover appropriate type conversions."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10701
msgid "<function>_WRAP_SIGNAL( C++ signal handler signature, C signal name)</function>"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:10703
#, no-wrap
msgid ""
"\n"
"_WRAP_SIGNAL(void clicked(),\"clicked\")\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10706
msgid "Signals usually have function pointers in the GTK struct, with a corresponding enum value and a <function>g_signal_new()</function> in the .c file."
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:10712
msgid "no_default_handler"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:10714
msgid "Do not generate an <function>on_something()</function> virtual method to allow easy overriding of the default signal handler. Use this when adding a signal with a default signal handler would break the ABI by increasing the size of the class's virtual function table, and when adding a signal without a public C default handler."
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:10723
msgid "custom_default_handler"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:10725
msgid "Generate a declaration of the <function>on_something()</function> virtual method in the <filename>.h</filename> file, but do not generate a definition in the <filename>.cc</filename> file. Use this when you must generate the definition by hand."
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:10732
msgid "custom_c_callback"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:10734
msgid "Do not generate a C callback function for the signal. Use this when you must generate the callback function by hand."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:10741
msgid "Do an extra <function>reference()</function> on the return value of the <function>on_something()</function> virtual method, in case the C function does not provide a reference."
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:10767
#: C/index-in.docbook:10950
msgid "exception_handler &lt;method_name&gt;"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:10769
#: C/index-in.docbook:10952
msgid "Allows to use custom exception handler instead of default one. Exception might be rethrown by user-defined handler, and it will be caught by default handler."
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:10775
msgid "detail_name &lt;parameter_name&gt;"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:10777
msgid "Adds a <type>const Glib::ustring&amp;</type> parameter to the <methodname>signal_something()</methodname> method. Use it, if the signal accepts a detailed signal name, i.e. if the underlying C code registers the signal with the <literal>G_SIGNAL_DETAILED</literal> flag."
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:10784
msgid "two_signal_methods"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:10786
msgid "Used in conjunction with the <literal>detail_name</literal> option to generate two <methodname>signal_something()</methodname> methods, one without a parameter and one with a parameter without a default value. With only the <literal>detail_name</literal> option one method is generated, with a parameter with default value. Use the <literal>two_signal_methods</literal> option, if it's necessary in order to preserve ABI."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:10800
msgid "_WRAP_PROPERTY"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10802
msgid "This macro generates the C++ method to wrap a C GObject property. You must specify the property name and the wanted C++ type for the property. <command>gmmproc</command> uses the .defs file to discover the C type and the .m4 convert files to discover appropriate type conversions."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10806
msgid "<function>_WRAP_PROPERTY(C property name, C++ type)</function>"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:10808
#, no-wrap
msgid ""
"\n"
"_WRAP_PROPERTY(\"label\", Glib::ustring)\n"
""
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:10832
msgid "_WRAP_VFUNC"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10834
msgid "This macro generates the C++ method to wrap a virtual C function."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10835
msgid "<function>_WRAP_VFUNC( C++ method signature, C function name)</function>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10836
msgid "For instance, from <filename>widget.hg</filename>:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:10837
#, no-wrap
msgid ""
"\n"
"_WRAP_VFUNC(SizeRequestMode get_request_mode() const, get_request_mode)\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10840
msgid "The C function (e.g. <function>get_request_mode</function>) is described more fully in the <filename>*_vfuncs.defs</filename> file, and the <filename>convert*.m4</filename> files contain the necessary conversion from the C++ parameter type to the C parameter type. Conversions can also be written in the .hg file. Virtual functions often require special conversions that are best kept local to the .hg file where they are used."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:10851
msgid "Do an extra <function>reference()</function> on the return value of the <function>something_vfunc()</function> function, in case the virtual C function does not provide a reference."
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:10857
msgid "refreturn_ctype"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:10859
msgid "Do an extra <function>reference()</function> on the return value of an overridden <function>something_vfunc()</function> function in the C callback function, in case the calling C function expects it to provide a reference."
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:10866
msgid "keep_return"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:10868
msgid "Keep a copy of the return value in the C callback function, in case the calling C function does not expect to get its own reference."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:10876
msgid "Use the last GError** parameter of the C virtual function (if there is one) to throw an exception."
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:10881
msgid "custom_vfunc"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:10883
msgid "Do not generate a definition of the vfunc in the <filename>.cc</filename> file. Use this when you must generate the vfunc by hand."
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:10889
msgid "custom_vfunc_callback"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:10891
msgid "Do not generate a C callback function for the vfunc. Use this when you must generate the callback function by hand."
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:10934
msgid "return_value &lt;value&gt;"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:10936
msgid "Defines a non-default return value."
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:10940
msgid "err_return_value &lt;value&gt;"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:10942
msgid "Defines a non-default return value, used only if the C++ <function>something_vfunc()</function> function throws an exception which is propagated to the C callback function. If return_value is specified, but err_return_value is not, then return_value is used also when an exception is propagated."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10959
msgid "A rule to which there may be exceptions: If the virtual C function returns a pointer to an object derived from <classname>GObject</classname>, i.e. a reference-counted object, then the virtual C++ function shall return a <classname>Glib::RefPtr&lt;&gt;</classname> object. One of the extra arguments <parameter>refreturn</parameter> or <parameter>refreturn_ctype</parameter> is required."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:10970
msgid "Other macros"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:10973
msgid "_IMPLEMENTS_INTERFACE"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10975
msgid "This macro generates initialization code for the interface."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10976
msgid "<function>_IMPLEMENTS_INTERFACE(C++ interface name)</function>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10977
msgid "For instance, from <filename>grid.hg</filename>:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:10978
#, no-wrap
msgid ""
"\n"
"_IMPLEMENTS_INTERFACE(Orientable)\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10981
msgid "There is one optional extra argument: <_:variablelist-1/>"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:10994
msgid "_WRAP_ENUM"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10996
msgid "This macro generates a C++ enum to wrap a C enum. You must specify the desired C++ name and the name of the underlying C enum."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:10998
msgid "For instance, from <filename>enums.hg</filename>:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:10999
#, no-wrap
msgid ""
"\n"
"_WRAP_ENUM(Orientation, GtkOrientation)\n"
""
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:11005
msgid "NO_GTYPE"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:11007
msgid "Use this option, if the enum is not a <classname>GType</classname>. This is the case when there is no <function>*_get_type()</function> function for the C enum, but be careful that you don't just need to include an extra header for that function. You should also file a bug against the C API, because all enums should be registered as GTypes."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:11012
msgid "If you specify <literal>NO_GTYPE</literal>, don't use that enum as the type in _WRAP_PROPERTY. It would cause a runtime error, when the generated <methodname>property_*()</methodname> method is called."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:11015
msgid "For example, from <filename>icontheme.hg</filename>:"
msgstr ""

#. (itstool) path: listitem/programlisting
#: C/index-in.docbook:11016
#, no-wrap
msgid ""
"\n"
"_WRAP_ENUM(IconLookupFlags, GtkIconLookupFlags, NO_GTYPE)\n"
"      "
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:11022
msgid "gtype_func &lt;function_name&gt;"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:11024
msgid "Specifies the name of the <function>*_get_type()</function> function for the C enum. Use this parameter if <command>gmmproc</command> can't deduce the correct function name from the name of the C enum type."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:11027
msgid "For example, from <filename>dbusproxy.hg</filename> in glibmm:"
msgstr ""

#. (itstool) path: listitem/programlisting
#: C/index-in.docbook:11028
#, no-wrap
msgid ""
"\n"
"_WRAP_ENUM(ProxyFlags, GDBusProxyFlags, gtype_func g_dbus_proxy_flags_get_type)\n"
"      "
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:11034
msgid "CONV_TO_INT"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:11036
msgid "\"Convertible to int.\" Generates a plain enum (not an enum class) within a class. Such an enum is scoped like an enum class, but unlike an enum class, it can be implicitly converted to <type>int</type>."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:11039
msgid "For example, from <filename>dialog.hg</filename>:"
msgstr ""

#. (itstool) path: listitem/programlisting
#: C/index-in.docbook:11040
#, no-wrap
msgid ""
"\n"
"_WRAP_ENUM(ResponseType, GtkResponseType, CONV_TO_INT)\n"
"      "
msgstr ""

#. (itstool) path: varlistentry/term
#: C/index-in.docbook:11046
msgid "s#&lt;from&gt;#&lt;to&gt;#"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:11048
msgid "Substitutes (part of) the name of one or more enum constants. You can add any number of substitutions."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:11050
msgid "For example, from <filename>iochannel.hg</filename> in glibmm:"
msgstr ""

#. (itstool) path: listitem/programlisting
#: C/index-in.docbook:11051
#, no-wrap
msgid ""
"\n"
"_WRAP_ENUM(SeekType, GSeekType, NO_GTYPE, s#^SEEK_#SEEK_TYPE_#)\n"
"      "
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:11075
msgid "_WRAP_ENUM_DOCS_ONLY"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11077
msgid "This macro just generates a Doxygen documentation block for the enum. This is useful for enums that can't be wrapped with <function>_WRAP_ENUM()</function> because they are complexly defined (maybe using C macros) but including the generated enum documentation is still desired. It is used with the same syntax as <function>_WRAP_ENUM()</function> and also processes the same options (though NO_GTYPE, gtype_func &lt;function_name&gt; and CONV_TO_INT are ignored because they make no difference when just generating the enum's documentation)."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:11089
msgid "_WRAP_GERROR"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11091
msgid "This macro generates a C++ exception class, derived from <classname>Glib::Error</classname>, with a <type>Code</type> enum and a <methodname>code()</methodname> method. You must specify the desired C++ name, the name of the corresponding C enum, and the prefix for the C enum values."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11094
msgid "This exception can then be thrown by methods which are generated from _WRAP_METHOD() with the errthrow option."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11096
msgid "For instance, from <filename>pixbuf.hg</filename>:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:11097
#, no-wrap
msgid ""
"\n"
"_WRAP_GERROR(PixbufError, GdkPixbufError, GDK_PIXBUF_ERROR)\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11100
msgid "_WRAP_GERROR() accepts the same optional arguments as _WRAP_ENUM() (though CONV_TO_INT is ignored because all exception class enums are plain enums within a class)."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:11106
msgid "_MEMBER_GET / _MEMBER_SET"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11107
msgid "Use these macros if you're wrapping a simple struct or boxed type that provides direct access to its data members, to create getters and setters for the data members."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11111
msgid "<function>_MEMBER_GET(C++ name, C name, C++ type, C type)</function>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11112
msgid "<function>_MEMBER_SET(C++ name, C name, C++ type, C type)</function>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11113
msgid "For example, in <filename>rectangle.hg</filename>:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:11116
#, no-wrap
msgid ""
"_MEMBER_GET(x, x, int, int)"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:11120
msgid "_MEMBER_GET_PTR / _MEMBER_SET_PTR"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11121
msgid "Use these macros to automatically provide getters and setters for a data member that is a pointer type. For the getter function, it will create two methods, one const and one non-const."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11126
msgid "<function>_MEMBER_GET_PTR(C++ name, C name, C++ type, C type)</function>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11127
msgid "<function>_MEMBER_SET_PTR(C++ name, C name, C++ type, C type)</function>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11128
msgid "For example, for <classname>Pango::Analysis</classname> in <filename>item.hg</filename>:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:11130
#, no-wrap
msgid ""
"\n"
"// _MEMBER_GET_PTR(engine_lang, lang_engine, EngineLang*, PangoEngineLang*)\n"
"// It's just a comment. It's difficult to find a real-world example.\n"
""
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:11137
msgid "_MEMBER_GET_GOBJECT / _MEMBER_SET_GOBJECT"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11138
msgid "Use these macros to provide getters and setters for a data member that is a <classname>GObject</classname> type that must be referenced before being returned."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11143
msgid "<function>_MEMBER_GET_GOBJECT(C++ name, C name, C++ type, C type)</function>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11144
msgid "<function>_MEMBER_SET_GOBJECT(C++ name, C name, C++ type, C type)</function>"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11145
msgid "For example, in Pangomm, <filename>layoutline.hg</filename>:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:11146
#, no-wrap
msgid ""
"\n"
"_MEMBER_GET_GOBJECT(layout, layout, Pango::Layout, PangoLayout*)\n"
""
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:11154
msgid "gmmproc Parameter Processing"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11155
msgid "<command>gmmproc</command> allows processing the parameters in a method signature for the macros that process method signatures (like <function>_WRAP_METHOD()</function>, <function>_WRAP_CTOR()</function> and <function>_WRAP_CREATE()</function>) in a variety of ways:"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:11162
msgid "Parameter Reordering"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11164
msgid "For all the macros that process method signatures, it is possible to specify a different order for the C++ parameters than the existing order in the C function, virtual function or signal. For example, say that the following C function were being wrapped as a C++ method for the <classname>Gtk::Widget</classname> class:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:11170
#, no-wrap
msgid ""
"\n"
"void gtk_widget_set_device_events(GtkWidget* widget, GdkDevice* device,\n"
"  GdkEventMask events);\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11174
msgid "However, changing the order of the C++ method's two parameters is necessary. Something like the following would wrap the function as a C++ method with a different order for the two parameters:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:11178
#, no-wrap
msgid ""
"\n"
"_WRAP_METHOD(void set_device_events(Gdk::EventMask events{events},\n"
"  const Glib::RefPtr&lt;const Gdk::Device&gt;&amp; device{device}),\n"
"  gtk_widget_set_device_events)\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11183
msgid "The <literal>{c_param_name}</literal> following the method parameter names tells <command>gmmproc</command> to map the C++ parameter to the specified C parameter within the <literal>{}</literal>. Since the C++ parameter names correspond to the C ones, the above could be re-written as:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:11188
#, no-wrap
msgid ""
"\n"
"_WRAP_METHOD(void set_device_events(Gdk::EventMask events{.},\n"
"  const Glib::RefPtr&lt;const Gdk::Device&gt;&amp; device{.}),\n"
"  gtk_widget_set_device_events)\n"
""
msgstr ""

#. (itstool) path: warning/para
#: C/index-in.docbook:11194
msgid "Please note that when reordering parameters for a <function>_WRAP_SIGNAL()</function> method signature, the C parameter names would always be <literal>p0</literal>, <literal>p1</literal>, etc. because the <filename>generate_extra_defs</filename> utility uses those parameter names no matter what the C API's parameter names may be. It's how the utility is written presently."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:11206
msgid "Optional Parameter Processing"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11208
msgid "For all macros processing method signatures except <function>_WRAP_SIGNAL()</function> and <function>_WRAP_VFUNC()</function> it is also possible to make the parameters optional so that extra C++ methods are generated without the specified optional parameter. For example, say that the following <function>*_new()</function> function were being wrapped as a constructor in the <classname>Gtk::ToolButton</classname> class:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:11216
#, no-wrap
msgid ""
"\n"
"GtkToolItem* gtk_tool_button_new(GtkWidget* icon_widget, const gchar* label);\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11219
msgid "Also, say that the C API allowed NULL for the function's <parameter>label</parameter> parameter so that that parameter is optional. It would be possible to have <command>gmmproc</command> generate the original constructor (with all the parameters) along with an additional constructor without that optional parameter by appending a <literal>{?}</literal> to the parameter name like so:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:11225
#, no-wrap
msgid ""
"\n"
"_WRAP_CTOR(ToolButton(Widget&amp; icon_widget, const Glib::ustring&amp; label{?}),\n"
"  gtk_tool_button_new)\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11229
msgid "In this case, two constructors would be generated: One with the optional parameter and one without it."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:11235
msgid "Output Parameter Processing"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11237
msgid "With <function>_WRAP_METHOD()</function> it is also possible for the return of the wrapped C function (if it has one) to be placed in an output parameter of the C++ method instead of having the C++ method also return a value like the C function does. To do that, simply include the output parameter in the C++ method parameter list appending a <literal>{OUT}</literal> to the output parameter name. For example, if <function>gtk_widget_get_request_mode()</function> is declared as the following:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:11246
#, no-wrap
msgid ""
"\n"
"GtkSizeRequestMode gtk_widget_get_request_mode(GtkWidget* widget);\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11249
msgid "And having the C++ method set an output parameter is desired instead of returning a <type>SizeRequestMode</type>, something like the following could be used:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:11252
#, no-wrap
msgid ""
"\n"
"_WRAP_METHOD(void get_request_mode(SizeRequestMode&amp; mode{OUT}) const,\n"
"  gtk_widget_get_request_mode)\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11256
msgid "The <literal>{OUT}</literal> appended to the name of the <parameter>mode</parameter> output parameter tells <command>gmmproc</command> to place the return of the C function in that output parameter. In this case, however, a necessary initialization macro like the following would also have to be specified:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:11261
#, no-wrap
msgid ""
"\n"
"_INITIALIZATION(`SizeRequestMode&amp;',`GtkSizeRequestMode',`$3 = (SizeRequestMode)($4)')\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11264
msgid "Which could also be written as:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:11265
#, no-wrap
msgid ""
"\n"
"_INITIALIZATION(`SizeRequestMode&amp;',`GtkSizeRequestMode',`$3 = ($1)($4)')\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11268
msgid "<function>_WRAP_METHOD()</function> also supports setting C++ output parameters from C output parameters if the C function being wrapped has any. Suppose, for example, that we want to wrap the following C function that returns a value in its C output parameter <parameter>out_mime_type</parameter>:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:11274
#, no-wrap
msgid ""
"\n"
"GInputStream* gdk_clipboard_read_finish(GdkClipboard* clipboard,\n"
"  GAsyncResult* result, const char** out_mime_type, GError** error)\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11278
msgid "To have <command>gmmproc</command> place the value returned in the C++ <parameter>out_mime_type</parameter> output parameter, something like the following <function>_WRAP_METHOD()</function> macro could be used:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:11282
#, no-wrap
msgid ""
"\n"
"_WRAP_METHOD(Glib::RefPtr&lt;Gio::InputStream&gt; read_finish(\n"
"  const Glib::RefPtr&lt;Gio::AsyncResult&gt;&amp; result,\n"
"  Glib::ustring&amp; out_mime_type{&gt;&gt;}), gdk_clipboard_read_finish, errthrow)\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11287
msgid "The <literal>{&gt;&gt;}</literal> following the <parameter>out_mime_type</parameter> parameter name indicates that the C++ output parameter should be set from the value returned in the C parameter from the C function. <command>gmmproc</command> will generate a declaration of a temporary variable in which to store the value of the C output parameter and a statement that sets the C++ output parameter from the temporary variable. In this case it may be necessary to have an <function>_INITIALIZATION()</function> describing how to set a <classname>Glib::ustring&amp;</classname> from a <classname>const char**</classname> such as the following:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:11297
#, no-wrap
msgid ""
"\n"
"_INITIALIZATION(`Glib::ustring&amp;',`const char*',`$3 = Glib::convert_const_gchar_ptr_to_ustring($4)')\n"
""
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:11303
msgid "String Parameter Processing"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11305
msgid "A string-valued input parameter in a C++ method is usually a <type>const Glib::ustring&amp;</type> or a <type>const std::string&amp;</type>. In C code it's a <type>const gchar*</type>. When an empty string is converted to <type>const gchar*</type>, it can be converted either to <literal>nullptr</literal> or to a pointer to an empty string (with <methodname>c_str()</methodname>). Some parameters in some C functions accept a <literal>nullptr</literal>, and interpret it in a special way. Other parameters must not be <literal>nullptr</literal>."
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:11318
msgid "for mandatory parameters (with or without default values): empty string to empty string,"
msgstr ""

#. (itstool) path: listitem/para
#: C/index-in.docbook:11320
msgid "for optional parameters (with appended <literal>{?}</literal>): empty string to <literal>nullptr</literal>."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11314
msgid "The default conversion in <function>_WRAP_METHOD()</function> and similar macros is <_:itemizedlist-1/> If the default conversion is not the best conversion, append <literal>{NULL}</literal> to a mandatory parameter or <literal>{?!NULL}</literal> to an optional parameter (<literal>!NULL</literal> = not <literal>NULL</literal>). If you append both a C parameter name and <literal>NULL</literal>, separate them with a space: <literal>{c_param_name NULL}</literal>."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:11334
msgid "Basic Types"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11335
msgid "Some of the basic types that are used in C APIs have better alternatives in C++. For example, there's no need for a <type>gboolean</type> type since C++ has <type>bool</type>. The following list shows some commonly-used types in C APIs and what you might convert them to in a C++ wrapper library."
msgstr ""

#. (itstool) path: segmentedlist/segtitle
#: C/index-in.docbook:11342
msgid "C type"
msgstr ""

#. (itstool) path: segmentedlist/segtitle
#: C/index-in.docbook:11343
msgid "C++ type"
msgstr ""

#. (itstool) path: seglistitem/seg
#: C/index-in.docbook:11344
msgid "<type>gboolean</type>"
msgstr ""

#. (itstool) path: seglistitem/seg
#: C/index-in.docbook:11344
msgid "<type>bool</type>"
msgstr ""

#. (itstool) path: seglistitem/seg
#: C/index-in.docbook:11345
msgid "<type>gint</type>"
msgstr ""

#. (itstool) path: seglistitem/seg
#: C/index-in.docbook:11345
msgid "<type>int</type>"
msgstr ""

#. (itstool) path: seglistitem/seg
#: C/index-in.docbook:11346
#: C/index-in.docbook:11346
msgid "<type>guint</type>"
msgstr ""

#. (itstool) path: seglistitem/seg
#: C/index-in.docbook:11347
msgid "<type>gdouble</type>"
msgstr ""

#. (itstool) path: seglistitem/seg
#: C/index-in.docbook:11347
msgid "<type>double</type>"
msgstr ""

#. (itstool) path: seglistitem/seg
#: C/index-in.docbook:11348
#: C/index-in.docbook:11348
msgid "<type>gunichar</type>"
msgstr ""

#. (itstool) path: seglistitem/seg
#: C/index-in.docbook:11349
msgid "<type>gchar*</type>"
msgstr ""

#. (itstool) path: seglistitem/seg
#: C/index-in.docbook:11349
msgid "<classname>Glib::ustring</classname> (or <classname>std::string</classname> for filenames)"
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:11355
msgid "Hand-coded source files"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11357
msgid "You might want to include additional source files that will not be generated by <command>gmmproc</command> from <filename>.hg</filename> and <filename>.ccg</filename> files. You can simply place these in your <filename>libsomething/libsomethingmm</filename> directory and mention them in the <filename>meson.build</filename> in the <varname>extra_h_files</varname> and <varname>extra_cc_files</varname> variables."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:11367
msgid "Initialization"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11369
msgid "Your library must be initialized before it can be used, to register the new types that it makes available. Also, the C library that you are wrapping might have its own initialization function that you should call. You can do this in an <function>init()</function> function that you can place in hand-coded <filename>init.h</filename> and <filename>init.cc</filename> files. This function should initialize your dependencies (such as the C function, and <application>gtkmm</application>) and call your generated <function>wrap_init()</function> function. For instance:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:11377
#, no-wrap
msgid ""
"\n"
"void init()\n"
"{\n"
"  Gtk::init_gtkmm_internals(); //Sets up the g type system and the Glib::wrap() table.\n"
"  wrap_init(); //Tells the Glib::wrap() table about the libsomethingmm classes.\n"
"}\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11384
msgid "The implementation of the <function>wrap_init()</function> method in <filename>wrap_init.cc</filename> is generated by <filename>generate_wrap_init.pl</filename>, but the declaration in <filename>wrap_init.h</filename> is hand-coded, so you will need to adjust <filename>wrap_init.h</filename> so that the <function>wrap_init()</function> function appears in the correct C++ namespace."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:11393
msgid "Problems in the C API."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11395
msgid "You are likely to encounter some problems in the library that you are wrapping, particularly if it is a new project. Here are some common problems, with solutions."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:11397
msgid "Unable to predeclare structs"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11399
msgid "By convention, structs are declared in glib/GTK-style headers like so:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:11400
#, no-wrap
msgid ""
"\n"
"typedef struct _ExampleWidget ExampleWidget;\n"
"\n"
"struct _ExampleWidget\n"
"{\n"
"  ...\n"
"};\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11408
msgid "The extra typedef allows the struct to be used in a header without including its full definition, simply by predeclaring it, by repeating that typedef. This means that you don't have to include the C library's header in your C++ header, thus keeping it out of your public API. <command>gmmproc</command> assumes that this technique was used, so you will see compiler errors if that is not the case."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11413
msgid "This compiler error might look like this:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:11415
#, no-wrap
msgid ""
"\n"
"example-widget.h:56: error: using typedef-name 'ExampleWidget' after 'struct'\n"
"../../libexample/libexamplemm/example-widget.h:34: error: 'ExampleWidget' has a previous declaration here\n"
"make[4]: *** [example-widget.lo] Error 1\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11420
msgid "or this:"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:11421
#, no-wrap
msgid ""
"\n"
"example-widget.h:60: error: '_ExampleWidget ExampleWidget' redeclared as different kind of symbol\n"
"../../libexample/libexamplemm/example-widget.h:34: error: previous declaration of 'typedef struct _ExampleWidget ExampleWidget'\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11425
msgid "This is easy to correct in the C library, so do send a patch to the relevant maintainer."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:11429
msgid "Lack of properties"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11431
msgid "By convention, glib/GTK-style objects have <function>*_new()</function> functions, such as <function>example_widget_new()</function> that do nothing more than call <function>g_object_new()</function> and return the result. The input parameters are supplied to <function>g_object_new()</function> along with the names of the properties for which they are values. For instance,"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:11437
#, no-wrap
msgid ""
"\n"
"GtkWidget* example_widget_new(int something, const char* thing)\n"
"{\n"
"        return g_object_new (EXAMPLE_TYPE_WIDGET, \"something\", something, \"thing\", thing, NULL);\n"
"}\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11443
msgid "This allows language bindings to implement their own equivalents (such as C++ constructors), without using the <function>*_new()</function> function. This is often necessary so that they can actually instantiate a derived GType, to add their own hooks for signal handlers and vfuncs."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11447
msgid "At the least, the <function>_new()</function> function should not use any private API (functions that are only in a .c file). Even when there are no functions, we can sometimes reimplement 2 or 3 lines of code in a <function>_new()</function> function as long as those lines of code use API that is available to us."
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11452
msgid "Another workaround is to add a <function>*_construct()</function> function that the C++ constructor can call after instantiating its own type. For instance,"
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:11455
#, no-wrap
msgid ""
"\n"
"GtkWidget* example_widget_new(int something, const char* thing)\n"
"{\n"
"        ExampleWidget* widget;\n"
"        widget = g_object_new (EXAMPLE_TYPE_WIDGET, NULL);\n"
"        example_widget_construct(widget, \"something\", something, \"thing\", thing);\n"
"}\n"
"\n"
"void example_widget_construct(ExampleWidget* widget, int something, const char* thing)\n"
"{\n"
"        //Do stuff that uses private API:\n"
"        widget-&gt;priv-&gt;thing = thing;\n"
"        do_something(something);\n"
"}\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11470
msgid "Adding properties, and ensuring that they interact properly with each other, is relatively difficult to correct in the C library, but it is possible, so do file a bug and try to send a patch to the relevant maintainer."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:11478
msgid "Documentation"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11480
msgid "In general, gtkmm-style projects use Doxygen, which reads specially formatted C++ comments and generates HTML documentation. You may write these doxygen comments directly in the header files."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:11483
msgid "Reusing C documentation"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11485
msgid "You might wish to reuse documentation that exists for the C library that you are wrapping. GTK-style C libraries typically use gtk-doc or gi-docgen and therefore have source code comments formatted for gtk-doc or gi-docgen and some extra documentation in .sgml and .xml files. The docextract_to_xml.py script, from glibmm's <filename>tools/defs_gen</filename> directory, can read these files and generate an .xml file that <command>gmmproc</command> can use to generate doxygen comments. <command>gmmproc</command> will even try to transform the documentation to make it more appropriate for a C++ API."
msgstr ""

#. (itstool) path: section/programlisting
#: C/index-in.docbook:11495
#, no-wrap
msgid ""
"./docextract_to_xml.py -s ~/checkout/gnome/gtk/gtk/ &gt; gtk_docs.xml\n"
""
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11497
msgid "Because this automatic transformation is not always appropriate, you might want to provide hand-written text for a particular method. You can do this by copying the XML node for the function from your <filename>something_docs.xml</filename> file to the <filename>something_docs_override.xml</filename> file and changing the contents. Alternatively you can write your own documentation in the <filename>.hg</filename> file."
msgstr ""

#. (itstool) path: section/title
#: C/index-in.docbook:11507
msgid "Documentation build structure"
msgstr ""

#. (itstool) path: section/para
#: C/index-in.docbook:11509
msgid "If you copied the skeleton source tree in <application>mm-common</application> and substituted the placeholder text, then you will already have suitable <filename>meson.build</filename> and <filename>Doxyfile.in</filename> files in the <filename>doc/reference/</filename> directory. You probably need to modify the <varname>tag_file_modules</varname> variable in <filename>meson.build</filename>, though. With the <application>mm-common</application> build setup, the list of Doxygen input files is not defined in the Doxygen configuration file, but passed along from <command>meson/ninja</command> to the standard input of <command>doxygen</command>."
msgstr ""