# Chinese (China) translation for gtkmm-documentation.
# Copyright (C) 2010 gtkmm-documentation's COPYRIGHT HOLDER
# This file is distributed under the same license as the gtkmm-documentation package.
# Tao Wang <dancefire@gmail.com>, 2010.
#
msgid ""
msgstr ""
"Project-Id-Version: gtkmm-documentation master\n"
"POT-Creation-Date: 2010-07-20 22:25+0000\n"
"PO-Revision-Date: 2010-07-16 23:48+1000\n"
"Last-Translator: Tao Wang <dancefire@gmail.com>\n"
"Language-Team: Chinese (China) <i18n-zh@googlegroups.com>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#: C/gtkmm-tutorial-in.xml:34(title)
msgid "Programming with <application>gtkmm</application>"
msgstr "<application>gtkmm</application> 程序设计"

#: C/gtkmm-tutorial-in.xml:38(firstname)
msgid "Murray"
msgstr "Murray"

#: C/gtkmm-tutorial-in.xml:39(surname)
msgid "Cumming"
msgstr "Cumming"

#: C/gtkmm-tutorial-in.xml:42(firstname)
msgid "Bernhard"
msgstr "Bernhard"

#: C/gtkmm-tutorial-in.xml:43(surname)
msgid "Rieder"
msgstr "Rieder"

#: C/gtkmm-tutorial-in.xml:44(contrib)
msgid "Chapter on \"Timeouts\"."
msgstr "章节《超时》"

#: C/gtkmm-tutorial-in.xml:47(firstname)
msgid "Jonathon"
msgstr "Jonathon"

#: C/gtkmm-tutorial-in.xml:48(surname)
msgid "Jongsma"
msgstr "Jongsma"

#: C/gtkmm-tutorial-in.xml:49(contrib)
msgid "Chapter on \"Drawing with Cairo\"."
msgstr "章节《使用 Cairo 绘图》"

#: C/gtkmm-tutorial-in.xml:50(contrib)
msgid "Chapter on \"Working with gtkmm's Source Code\"."
msgstr "章节《使用 gtkmm 源代码》"

#: C/gtkmm-tutorial-in.xml:51(contrib)
msgid "Chapter on \"Recent Files\"."
msgstr "章节《最近的文件》"

#: C/gtkmm-tutorial-in.xml:54(firstname)
msgid "Jason"
msgstr "Jason"

#: C/gtkmm-tutorial-in.xml:55(surname)
msgid "M'Sadoques"
msgstr "M'Sadoques"

#: C/gtkmm-tutorial-in.xml:56(contrib)
msgid "Chapter on \"Drawing Area\"."
msgstr "章节《绘图区域》"

#: C/gtkmm-tutorial-in.xml:59(firstname)
msgid "Ole"
msgstr "Ole"

#: C/gtkmm-tutorial-in.xml:60(surname)
msgid "Laursen"
msgstr "Laursen"

#: C/gtkmm-tutorial-in.xml:61(contrib) C/gtkmm-tutorial-in.xml:77(contrib)
msgid "Parts of chapter on \"Internationalization\"."
msgstr "部分章节《国际化》"

#: C/gtkmm-tutorial-in.xml:64(firstname)
msgid "Gene"
msgstr "Gene"

#: C/gtkmm-tutorial-in.xml:65(surname)
msgid "Ruebsamen"
msgstr "Ruebsamen"

#: C/gtkmm-tutorial-in.xml:66(contrib) C/gtkmm-tutorial-in.xml:71(contrib)
msgid "Chapter on \"Win32 Installation\"."
msgstr "章节《Win32 安装》"

#: C/gtkmm-tutorial-in.xml:69(firstname)
msgid "Cedric"
msgstr "Cedric"

#: C/gtkmm-tutorial-in.xml:70(surname)
msgid "Gustin"
msgstr "Gustin"

#: C/gtkmm-tutorial-in.xml:74(firstname)
msgid "Marko"
msgstr "Marko"

#: C/gtkmm-tutorial-in.xml:75(surname)
msgid "Anastasov"
msgstr "Anastasov"

#: C/gtkmm-tutorial-in.xml:76(contrib)
msgid "Chapter on \"Printing\"."
msgstr "章节《打印》"

#: C/gtkmm-tutorial-in.xml:80(firstname)
msgid "Alan"
msgstr "Alan"

#: C/gtkmm-tutorial-in.xml:81(surname)
msgid "Ott"
msgstr "Ott"

#: C/gtkmm-tutorial-in.xml:82(contrib)
msgid "Appendix on \"Visual Studio 2005\"."
msgstr "章节《Visual Studio 2005》"

#: C/gtkmm-tutorial-in.xml:85(firstname)
msgid "Daniel"
msgstr "Daniel"

#: C/gtkmm-tutorial-in.xml:86(surname)
msgid "Elstner"
msgstr "Elstner"

#: C/gtkmm-tutorial-in.xml:87(contrib)
msgid ""
"Section \"Build Structure\" of chapter on \"Wrapping C Libraries with gmmproc"
"\"."
msgstr "《使用 gmmproc 封装 C 库》章的〈构建结构〉节。"

#. This text is copied from the introduction.
#: C/gtkmm-tutorial-in.xml:95(para)
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 ""
"本书说明了使用<application>gtkmm</application> C++ API 创建用户界面的重要概"
"念，并且介绍了主要的用户界面元素(“widget”)。"

#: C/gtkmm-tutorial-in.xml:101(year)
msgid "2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010"
msgstr "2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010"

#: C/gtkmm-tutorial-in.xml:102(holder)
msgid "Murray Cumming"
msgstr "Murray Cumming"

#: C/gtkmm-tutorial-in.xml:106(para)
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 ""
"根据由自由软件基金发布的 GNU 自由文档协议版本1.2或更高版本的条款，授权复制、"
"分发和/或修改此文档；并且，没有不可变章节，没有封面文本，并且没有封底文本。您"
"可以通过访问自由软件基金(FSF)的网站或写邮件至：Free Software Foundation, "
"Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. 来获得一份 "
"GNU 自由文档协议。"

#: C/gtkmm-tutorial-in.xml:118(title)
msgid "Introduction"
msgstr "序言"

#: C/gtkmm-tutorial-in.xml:121(title)
msgid "This book"
msgstr "本书"

#: C/gtkmm-tutorial-in.xml:123(para)
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 ""
"本书说明了使用<application>gtkmm</application> C++ API 创建用户界面的重要概"
"念，并且介绍了主要的用户界面元素(“widget”)。虽然提到了类、构造函数和方法，但"
"是并不会深入其细节。因此，如果需要完整的 API 信息，您应当顺着链接访问参考文"
"档。"

#: C/gtkmm-tutorial-in.xml:125(para)
msgid ""
"This book assumes a good understanding of C++, and how to create C++ "
"programs."
msgstr "本书假定读者拥有对 C++ 良好的理解，并且知道如何去创建一个 C++ 程序。"

#: C/gtkmm-tutorial-in.xml:127(para)
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 ""
"我们非常愿意聆听您在使用此文档学习 <application>gtkmm</application> 时碰到的"
"任何问题，并且感激对此作出的改进。请访问 <link linkend=\"chapter-contributing"
"\">贡献</link> 节以获得进一步的信息。"

#: C/gtkmm-tutorial-in.xml:134(title)
msgid "gtkmm"
msgstr "gtkmm"

#: C/gtkmm-tutorial-in.xml:135(para)
msgid ""
"<application>gtkmm</application> is a C++ wrapper for <ulink url=\"http://"
"www.gtk.org/\">GTK+</ulink>, 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 ""
"<application>gtkmm</application> 是一个 <ulink url=\"http://www.gtk.org/"
"\">GTK+</ulink> 的 C++ 封装，GTK+ 是一个用于创建图形用户界面的软件库。它使用 "
"LGPL 协议，因此您可以使用 <application>gtkmm</application> 开发开放软件、自由"
"软件，甚至商业非免费软件而不需支付任何版权费用。"

#: C/gtkmm-tutorial-in.xml:143(para)
msgid ""
"<application>gtkmm</application> was originally named gtk-- because GTK+ "
"already has 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 ""
"<application>gtkmm</application> 曾经被称为 gtk--，那是因为 GTK+ 的名字中已经"
"有了一个加号。但是，由于 -- 不容易被搜索引擎索引，所以项目名字就渐渐的变成了"
"<application>gtkmm</application>，后来我们就一直使用这个名字。"

#: C/gtkmm-tutorial-in.xml:146(title)
msgid "Why use <application>gtkmm</application> instead of GTK+?"
msgstr "为什么要使用 <application>gtkmm</application> 而不是 GTK+？"

#: C/gtkmm-tutorial-in.xml:147(para)
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 realise that this leads to clearer and "
"better organized code."
msgstr ""
"<application>gtkmm</application> 允许你使用常用的 C++ 技术来撰写代码，比如封"
"装、继承和多态。作为一个 C++ 程序员，你可能已经意识到这会让代码更加清晰、更加"
"良好的管理代码。"

#: C/gtkmm-tutorial-in.xml:148(para)
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 ""
"<application>gtkmm</application> 更加类型安全，因此编译器可以检测出一些 C 只"
"能在运行时才能检测出来的错误。这种使用特定类型的方法同样使得 API 更加清晰，因"
"为你只需要通过看一下函数声明就可以知道应该使用什么类型了。"

#: C/gtkmm-tutorial-in.xml:149(para)
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 ""
"可以使用继承来衍生新的部件。在 GTK+ 中使用 C 代码来衍生新部件是非常复杂的，并"
"且很容易出错，因此几乎没有 C 的程序员这么做。作为 C++ 开发人员，你知道继承是"
"一个基本的面向对象技术。"

#: C/gtkmm-tutorial-in.xml:150(para)
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 ""
"可以使用成员实例，简化了内存管理。所有的 GTK+ 的 C 部件都是使用指针进行操作"
"的。作为 C++ 程序员，你知道指针应当尽量避免使用。"

#: C/gtkmm-tutorial-in.xml:151(para)
msgid ""
"<application>gtkmm</application> involves less code compared to GTK+, which "
"uses prefixed function names and lots of cast macros."
msgstr ""
"<application>gtkmm</application> 比 GTK+ 的代码更加简短，GTK+ 使用了大量带前"
"缀的函数名以及大量的转型宏。"

#: C/gtkmm-tutorial-in.xml:155(title)
msgid "<application>gtkmm</application> compared to Qt"
msgstr "<application>gtkmm</application> 对比 Qt"

#: C/gtkmm-tutorial-in.xml:156(para)
msgid ""
"Trolltech's Qt is the closest competition to <application>gtkmm</"
"application>, so it deserves discussion."
msgstr ""
"Trolltech 公司的 Qt 是和 <application>gtkmm</application> 最相似的有竞争力的"
"产品，所以应该对其进行一下讨论。"

#: C/gtkmm-tutorial-in.xml:158(para)
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 standardised 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 FAQ for more detailed "
"differences."
msgstr ""
"<application>gtkmm</application> 开发人员更倾向于使用 <application>gtkmm</"
"application> 而不是 Qt，因为 <application>gtkmm</application> 的使用更加符合 "
"C++ 的方式。Qt 是诞生自 C++ 及其库尚未标准化或尚未被大多数编译器所支持的年"
"代。它重复了大量的现存于标准库中的东西，比如容器、类型信息等等。最重要的是，"
"Trolltech 修改了 C++ 语言以提供信号的功能，这样 Qt 的类无法很容易的与非 Qt 类"
"共同使用。<application>gtkmm</application> 则可以使用标准 C++ 提供信号功能，"
"而无需修改 C++ 语言。请看常见问题以得到进一步的差异。"

#: C/gtkmm-tutorial-in.xml:162(title)
msgid "<application>gtkmm</application> is a wrapper"
msgstr "<application>gtkmm</application> 是一个封装"

#: C/gtkmm-tutorial-in.xml:163(para)
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 ""
"<application>gtkmm</application> 并不是一个原生的 C++ 工具集，而是一个对于 C "
"工具集的 C++ 封装。这种分离接口和实现的方式存在诸多优势。<application>gtkmm</"
"application> 开发人员用了他们大量的时间来讨论如何让 <application>gtkmm</"
"application> 提供一个最清晰的 API，而不必为模糊的技术细节尴尬的进行妥协。我们"
"想其他的 C 程序员、Perl 程序员和 Python 程序员等等一样，对底层的 GTK+ 代码库"
"进行了一点点贡献。因此，GTK+ 可以从比某个语言特定的工具集更广泛的用户群中获得"
"好处，有更多的实现、更多的开发人员、更多的测试人员以及更多的用户。"

#: C/gtkmm-tutorial-in.xml:171(title)
msgid "Installation"
msgstr "安装"

#: C/gtkmm-tutorial-in.xml:173(title)
msgid "Dependencies"
msgstr "依赖关系"

#: C/gtkmm-tutorial-in.xml:174(para)
msgid ""
"Before attempting to install <application>gtkmm</application> 2.4, you might "
"first need to install these other packages."
msgstr ""
"在试图安装 <application>gtkmm</application> 2.4之前，你必须已经安装了这些包。"

#: C/gtkmm-tutorial-in.xml:179(application)
msgid "libsigc++ 2.0"
msgstr "libsigc++ 2.0"

#: C/gtkmm-tutorial-in.xml:180(application)
msgid "GTK+ 2.4"
msgstr "GTK+ 2.4"

#: C/gtkmm-tutorial-in.xml:181(application)
msgid "cairomm"
msgstr "cairomm"

#: C/gtkmm-tutorial-in.xml:183(para)
msgid ""
"These dependencies have their own dependencies, including the following "
"applications and libraries:"
msgstr "这些依赖有它们自己所依赖的软件包，包括下列应用程序和软件库："

#: C/gtkmm-tutorial-in.xml:188(application)
msgid "pkg-config"
msgstr "pkg-config"

#: C/gtkmm-tutorial-in.xml:189(application)
msgid "glib"
msgstr "glib"

#: C/gtkmm-tutorial-in.xml:190(application)
msgid "ATK"
msgstr "ATK"

#: C/gtkmm-tutorial-in.xml:191(application)
msgid "Pango"
msgstr "Pango"

#: C/gtkmm-tutorial-in.xml:192(application)
msgid "cairo"
msgstr "cairo"

#: C/gtkmm-tutorial-in.xml:197(title)
msgid "Unix and Linux"
msgstr "Unix 和 Linux"

#: C/gtkmm-tutorial-in.xml:200(title)
msgid "Prebuilt Packages"
msgstr "预编译的包"

#: C/gtkmm-tutorial-in.xml:202(para)
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 ""
"<application>gtkmm</application> 最新的版本的软件包几乎存在于今天每一个主流"
"的 Linux 发布版本中。所以，如果你使用 Linux，你可能只需要从官方的软件库安装相"
"应的软件包，然后就可以开始使用 <application>gtkmm</application> 了。已经在它"
"们的软件库里面包含了 <application>gtkmm</application> 的发布版本有：Debian、"
"Ubuntu、Red Hat、Fedora、Mandriva、SuSE 等等。"

#: C/gtkmm-tutorial-in.xml:210(para)
msgid ""
"The names of the <application>gtkmm</application> packages vary from "
"distribution to distribution (e.g. <application>libgtkmm2.4-dev</"
"application> on Debian and Ubuntu or <application>gtkmm24-devel</"
"application> on Red Hat 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 ""
"<application>gtkmm</application> 软件包的名字可能在不同的发行版中所不同 (例"
"如，在 Debian 和 Ubuntu 上的名字是<application>libgtkmm2.4-dev</"
"application>，而在 Red Hat Fedora 上则是 <application>gtkmm24-devel</"
"application>)，因此，在你的发行版的软件包管理程序中查一下正确的名字，然后像其"
"它软件包一样的安装它。"

#: C/gtkmm-tutorial-in.xml:218(para)
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> 2.8 supplied by Debian's "
"<application>libgtkmm2.4-dev</application> package."
msgstr ""
"当新的 API/ABI 兼容的 <application>gtkmm</application> 版本发布后，其包的名称"
"将不会改变。否则的话，就说明 API/ABI 不兼容。所以，如果在 Debian 的 "
"<application>libgtkmm2.4-dev</application> 包中发现提供的实际上是 "
"<application>gtkmm</application> 2.8 的话不要太惊讶。"

#: C/gtkmm-tutorial-in.xml:228(title)
msgid "Installing From Source"
msgstr "从源代码安装"

#: C/gtkmm-tutorial-in.xml:230(para)
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 <ulink url=\"http://www.gtkmm.org/\"/>."
msgstr ""
"如果你的发行版没提供预编译的 <application>gtkmm</application> 包，或者如果你"
"想安装一个和发行版所提供的不同的版本，那么你也可以从源代码安装 "
"<application>gtkmm</application>。可以从 <ulink url=\"http://www.gtkmm.org/"
"\"/> 中下载 <application>gtkmm</application> 的源代码。"

#: C/gtkmm-tutorial-in.xml:236(para)
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 and "
"installed with the following sequence of commands:"
msgstr ""
"在安装了所有依赖的库后，下载 <application>gtkmm</application> 源代码、解压"
"缩，并且切换到新创建的目录。然后可以用下列命令序列构件和安装 "
"<application>gtkmm</application>："

#: C/gtkmm-tutorial-in.xml:241(screen)
#, no-wrap
msgid ""
"\n"
"# ./configure\n"
"# make\n"
"# make install\n"
msgstr ""
"\n"
"# ./configure\n"
"# make\n"
"# make install\n"

#: C/gtkmm-tutorial-in.xml:247(para)
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> "
"command will allow you to enter the <literal>root</literal> password and "
"have <literal>root</literal> status temporarily."
msgstr ""
"记住，在 Unix 或 Linux 操作系统上，你也许需要 <literal>root</literal> 权限以"
"安装软件。<command>su</command> 命令允许你输入 <literal>root</literal> 密码，"
"并且临时拥有 <literal>root</literal> 权限。"

#: C/gtkmm-tutorial-in.xml:254(para)
msgid ""
"The <filename>configure</filename> script 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 ""
"<filename>configure</filename> 将会检查以确认所有必须的依赖软件包都已经正确的"
"安装了。如果你遗漏了某个依赖软件包的话，它会退出并提示错误信息。"

#: C/gtkmm-tutorial-in.xml:259(para)
msgid ""
"By default, <application>gtkmm</application> 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 so: "
"<screen>\n"
"# ./configure --prefix=/usr\n"
"</screen>"
msgstr ""
"默认情况下，<application>gtkmm</application> 将会被安装在 <filename>/usr/"
"local</filename> 目录。在有些系统中，你也许需要安装到不同的位置。比如，在 "
"Red Hat Linux 系统中，你也许需要使用 <literal>--prefix</literal> 选项进行配"
"置，例如：<screen>\n"
"# ./configure --prefix=/usr\n"
"</screen>"

#: C/gtkmm-tutorial-in.xml:270(para)
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 ""
"在安装到标准系统前缀时，如 <filename>/usr</filename>，你必须非常小心。Linux "
"发行版会安装软件到 <filename>/usr</filename>，所以安装源代码包到这个位置可能"
"会破坏或与使用软件包管理器安装的软件冲突。理想情况下，你应当将从源代码安装的"
"软件都安装到一个独立位置。"

#: C/gtkmm-tutorial-in.xml:279(para)
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 ""
"如果你想帮助开发 <application>gtkmm</application>，或实验一些新的功能，你也可"
"以直接从 Git 安装 <application>gtkmm</application>。大多数用户绝对不需要这么"
"做，但是如果你对帮助 <application>gtkmm</application> 开发感兴趣，请看附录："
"<link linkend=\"chapter-working-with-source\">使用 gtkmm 源代码</link>。"

#: C/gtkmm-tutorial-in.xml:290(title)
msgid "Microsoft Windows"
msgstr "Microsoft Windows"

#: C/gtkmm-tutorial-in.xml:291(para)
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 <ulink url=\"http://live.gnome.org/"
"gtkmm/MSWindows\">Windows Installation</ulink> page for Windows-specific "
"installation instructions and notes."
msgstr ""
"GTK+ and <application>gtkmm</application> 被设计成在 Microsoft Windows 上也能"
"很好地工作，而且开发者们鼓励在 win32 平台上使用它们。然而，还有没为 Wnidows "
"平台的开发库提供标准的安装方法。请参考 <ulink url=\"http://live.gnome.org/"
"gtkmm/MSWindows\">Windows Intallation</ulink> (<ulink url=\"http://live."
"gnome.org/Chinese/gtkmm/MSWindows\">中文翻译</ulink>) 以得到进一步关于 "
"Windows 相关的安装方法和注意事项。"

#: C/gtkmm-tutorial-in.xml:298(title)
msgid "Basics"
msgstr "基础"

#: C/gtkmm-tutorial-in.xml:300(para)
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 ""
"这一章将介绍 <application>gtkmm</application> 编程中一些重要的方面。这些将由"
"一些可以运行的示例代码来演示。然而，这仅仅是一种尝试，你还需要继续看其它章"
"节，以得到更实质性的信息。"

#: C/gtkmm-tutorial-in.xml:303(para)
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 ""
"你现有的 C++ 知识将会帮助你使用 <application>gtkmm</application>，因为它可以"
"和任何库一同工作。除非我们额外声明，你可以期待 <application>gtkmm</"
"application> 类会像任何其它 C++ 类一样，并且你可以期待在 <application>gtkmm</"
"application> 类上使用你现有的知识。"

#: C/gtkmm-tutorial-in.xml:308(title) C/gtkmm-tutorial-in.xml:3748(title)
msgid "Simple Example"
msgstr "简单的例子"

#: C/gtkmm-tutorial-in.xml:310(para)
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 ""
"在开始介绍 <application>gtkmm</application> 之前，我们将以一个尽可能简单的程"
"序开始。这个程序创建一个 200 x 200 像素大小的空窗口。"

#: C/gtkmm-tutorial-in.xml:315(ulink) C/gtkmm-tutorial-in.xml:492(ulink)
#: C/gtkmm-tutorial-in.xml:708(ulink) C/gtkmm-tutorial-in.xml:816(ulink)
#: C/gtkmm-tutorial-in.xml:925(ulink) C/gtkmm-tutorial-in.xml:1090(ulink)
#: C/gtkmm-tutorial-in.xml:1139(ulink) C/gtkmm-tutorial-in.xml:1194(ulink)
#: C/gtkmm-tutorial-in.xml:1241(ulink) C/gtkmm-tutorial-in.xml:1268(ulink)
#: C/gtkmm-tutorial-in.xml:1293(ulink) C/gtkmm-tutorial-in.xml:1441(ulink)
#: C/gtkmm-tutorial-in.xml:1507(ulink) C/gtkmm-tutorial-in.xml:1531(ulink)
#: C/gtkmm-tutorial-in.xml:1606(ulink) C/gtkmm-tutorial-in.xml:1647(ulink)
#: C/gtkmm-tutorial-in.xml:1692(ulink) C/gtkmm-tutorial-in.xml:1727(ulink)
#: C/gtkmm-tutorial-in.xml:1766(ulink) C/gtkmm-tutorial-in.xml:1895(ulink)
#: C/gtkmm-tutorial-in.xml:2389(ulink) C/gtkmm-tutorial-in.xml:2432(ulink)
#: C/gtkmm-tutorial-in.xml:2591(ulink) C/gtkmm-tutorial-in.xml:2641(ulink)
#: C/gtkmm-tutorial-in.xml:2709(ulink) C/gtkmm-tutorial-in.xml:3306(ulink)
#: C/gtkmm-tutorial-in.xml:3325(ulink) C/gtkmm-tutorial-in.xml:3344(ulink)
#: C/gtkmm-tutorial-in.xml:3366(ulink) C/gtkmm-tutorial-in.xml:3388(ulink)
#: C/gtkmm-tutorial-in.xml:3464(ulink) C/gtkmm-tutorial-in.xml:3477(ulink)
#: C/gtkmm-tutorial-in.xml:3513(ulink) C/gtkmm-tutorial-in.xml:3526(ulink)
#: C/gtkmm-tutorial-in.xml:3757(ulink) C/gtkmm-tutorial-in.xml:3932(ulink)
#: C/gtkmm-tutorial-in.xml:3945(ulink) C/gtkmm-tutorial-in.xml:4001(ulink)
#: C/gtkmm-tutorial-in.xml:4258(ulink) C/gtkmm-tutorial-in.xml:4320(ulink)
#: C/gtkmm-tutorial-in.xml:4347(ulink) C/gtkmm-tutorial-in.xml:4369(ulink)
#: C/gtkmm-tutorial-in.xml:4392(ulink) C/gtkmm-tutorial-in.xml:4588(ulink)
#: C/gtkmm-tutorial-in.xml:4685(ulink) C/gtkmm-tutorial-in.xml:4766(ulink)
#: C/gtkmm-tutorial-in.xml:4934(ulink) C/gtkmm-tutorial-in.xml:5148(ulink)
#: C/gtkmm-tutorial-in.xml:5308(ulink) C/gtkmm-tutorial-in.xml:5328(ulink)
#: C/gtkmm-tutorial-in.xml:5706(ulink) C/gtkmm-tutorial-in.xml:5921(ulink)
#: C/gtkmm-tutorial-in.xml:6055(ulink) C/gtkmm-tutorial-in.xml:6161(ulink)
#: C/gtkmm-tutorial-in.xml:6258(ulink) C/gtkmm-tutorial-in.xml:6295(ulink)
#: C/gtkmm-tutorial-in.xml:6646(ulink) C/gtkmm-tutorial-in.xml:6714(ulink)
#: C/gtkmm-tutorial-in.xml:7330(ulink) C/gtkmm-tutorial-in.xml:7354(ulink)
#: C/gtkmm-tutorial-in.xml:8103(ulink)
msgid "Source Code"
msgstr "源代码"

#: C/gtkmm-tutorial-in.xml:317(para)
msgid "We will now explain each line of the example"
msgstr "我们会逐行讲解这个例子"

#: C/gtkmm-tutorial-in.xml:318(programlisting)
#, no-wrap
msgid "#include &lt;gtkmm.h&gt;"
msgstr "#include &lt;gtkmm.h&gt;"

#: C/gtkmm-tutorial-in.xml:319(para)
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 ""
"所有的 <application>gtkmm</application> 程序都需要包含一些特定的 "
"<application>gtkmm</application> 头文件；<literal>gtkmm.h</literal> 包含了所"
"有 <application>gtkmm</application> 的内容。通常来说，这并不是一个好主意，因"
"为它包括了一兆左右的头文件。当然，对于这个简单的程序，这就够了。"

#: C/gtkmm-tutorial-in.xml:329(programlisting)
#, no-wrap
msgid "Gtk::Main kit(argc, argv);"
msgstr "Gtk::Main kit(argc, argv);"

#: C/gtkmm-tutorial-in.xml:326(para)
msgid ""
"The next line: <placeholder-1/> creates a <classname>Gtk::Main</classname> "
"object. This is needed in all <application>gtkmm</application> applications. "
"The constructor for this object initializes <application>gtkmm</"
"application>, and checks the arguments passed to your application on the "
"command line, looking for standard options such as <literal>-display</"
"literal>. It takes these from the argument list, leaving anything it does "
"not recognize for your application to parse or ignore. This ensures that all "
"<application>gtkmm</application> applications accept the same set of "
"standard arguments."
msgstr ""
"下面一行：<placeholder-1/> 创建了一个 <classname>Gtk::Main</classname> 对象。"
"这是所有的 <application>gtkmm</application> 程序中所必须的。这个对象的构造函"
"数初始化了 <application>gtkmm</application>，并且检查传递给你的程序的命令行参"
"数，从中寻找像 <literal>-display</literal> 这样的标准选项。然后它会将这些可以"
"识别的参数从参数列表中删除，留下那些它不能识别的选项，交由你的程序处理或者忽"
"略。这样就保证了 <application>gtkmm</application> 应用程序能和其它程序一样接"
"受所有的标准参数。"

#: C/gtkmm-tutorial-in.xml:339(para)
msgid "The next two lines of code create and display a window:"
msgstr "接下来的两行代码创建并显示了一个窗口："

#: C/gtkmm-tutorial-in.xml:342(programlisting)
#, no-wrap
msgid "Gtk::Window window;"
msgstr "Gtk::Window window;"

#: C/gtkmm-tutorial-in.xml:343(para)
msgid ""
"The last line shows the window and enters the <application>gtkmm</"
"application> main processing loop, which will finish when the window is "
"closed."
msgstr ""
"最后一行显示窗口，并且进入 <application>gtkmm</application> 的主处理循环，它"
"将一直运行到窗口被关闭。"

#: C/gtkmm-tutorial-in.xml:347(programlisting)
#, no-wrap
msgid "Gtk::Main::run(window);"
msgstr "Gtk::Main::run(window);"

#: C/gtkmm-tutorial-in.xml:351(programlisting)
#, no-wrap
msgid "g++ simple.cc -o simple `pkg-config gtkmm-2.4 --cflags --libs`"
msgstr "g++ simple.cc -o simple `pkg-config gtkmm-2.4 --cflags --libs`"

#: C/gtkmm-tutorial-in.xml:349(para)
msgid ""
"After putting the source code in <literal>simple.cc</literal> you can "
"compile the above program with gcc using: <placeholder-1/> 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."
msgstr ""
"将源代码保存到 <literal>simple.cc</literal> 后，你可以使用 gcc 编译上面的程"
"序：<placeholder-1/> 注意，你必须将 <literal>pkg-config</literal> 的调用包含"
"在一对反单引号中。反单引号会导致其内的命令由 shell 执行，并且将命令的输出做为"
"该命令行的一部分来使用。"

#: C/gtkmm-tutorial-in.xml:360(title)
msgid "Headers and Linking"
msgstr "头文件和链接"

#: C/gtkmm-tutorial-in.xml:361(para)
msgid ""
"Although we have shown the compilation command for the simple example, you "
"really should use the automake and autoconf tools, as described in "
"\"Autoconf, Automake, Libtool\", by G. V. Vaughan et al. The examples used "
"in this book are included in the <application>gtkmm</application> package, "
"with appropriate build files, so we won't show the build commands in future. "
"You'll just need to find the appropriate directory and type <literal>make</"
"literal>."
msgstr ""
"虽然我们已经给出了这个简单的例子的编译命令，但是你最好还是使用 automake 和 "
"autoconf 工具，就像 G. V. Vaughan 等在《Autoconf, Automake, Libtool》中所描述"
"的那样。本书中用到的例子都包含在 <application>gtkmm</application> 包内，同时"
"附有适当的编译构建的文件，所以我们以后不会再给出任何编译命令。你只需要找到恰"
"当的目录然后键入 <literal>make</literal>。"

#: C/gtkmm-tutorial-in.xml:364(para)
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 ""
"为了简化编译的过程，我们使用了 <literal>pkg-config</literal>，它存在于所有的"
"(也许已经安装的) <application>gtkmm</application> 安装文件中。这个程序“知"
"道”编译使用了 <application>gtkmm</application> 的程序所需要的编译器选项。"
"<literal>--cflags</literal> 选项使 <literal>pkg-config</literal> 输出一个包含"
"编译时需要用到的头文件的目录列表；而使用 <literal>--libs</literal> 选项将得到"
"一个需要编译器去链接的库列表和一个用于寻找它们的目录列表。试着在你的命令行提"
"示符下运行它，看看在你的系统上会有什么样的结果。"

#: C/gtkmm-tutorial-in.xml:377(programlisting)
#, no-wrap
msgid "PKG_CHECK_MODULES([MYAPP], [gtkmm-2.4 &gt;= 2.8.0])"
msgstr "PKG_CHECK_MODULES([MYAPP], [gtkmm-2.4 &gt;= 2.8.0])"

#: C/gtkmm-tutorial-in.xml:374(para)
msgid ""
"However, this is even simpler when using the <function>PKG_CHECK_MODULES()</"
"function> macro in a standard configure.ac file with autoconf and automake. "
"For instance: <placeholder-1/> This checks for the presence of gtkmm and "
"defines MYAPP_LIBS and MYAPP_CFLAGS for use in your Makefile.am files."
msgstr ""
"然而，在标准的 configure.ac 中使用 <function>PKG_CHECK_MODULES()</function> "
"宏，并且运行 autoconf 和 automake 后，这变的更加简单。例如：<placeholder-1/> "
"这将会检查是否存在 gtkmm，并且定义了可以在你的 Makefile.am 文件中使用的 "
"MYAPP_LIBS 和 MYAPP_CFLAGS 变量。"

#: C/gtkmm-tutorial-in.xml:380(para)
msgid ""
"gtkmm-2.4 is the name of the current stable API. There was an older API "
"called gtkmm-2-0 which installs in parallel when it is available. There are "
"several versions of gtkmm-2.4, such as gtkmm 2.10. Note that the API name "
"does not change for every version because that would be an incompatible API "
"and ABI break. Theoretically, there might be a future gtkmm-3.0 API which "
"would install in parallel with gtkmm-2.4 without affecting existing "
"applications."
msgstr ""
"gtkmm-2.4 是当前稳定 API 的名字。更早期的 API 叫做 gtkmm-2.0，如果需要的话它"
"可以和 gtkmm-2.4 同时安装到系统。gtkmm-2.4 有许多版本，例如，gtkmm-2.10。注"
"意，API 的名字并不会随着每个版本变化而发生变化，因为如果这个发生变化了，则意"
"味着 API 和 ABI 不再同以前保持兼容。理论上，将来可以有 gtkmm-3.0 API 与现在"
"的 gtkmm-2.4 同时安装到系统，而现有应用程序不会受到影响。"

#: C/gtkmm-tutorial-in.xml:383(para)
msgid ""
"Note that if you mention extra modules in addition to gtkmm-2.4, they should "
"be separated by spaces, not commas."
msgstr ""
"注意，如果你提到了除 gtkmm-2.4 之外的模块，它们需要以空格分开，而不是逗号。"

#: C/gtkmm-tutorial-in.xml:385(para)
msgid ""
"Openismus has more <ulink url=\"http://www.openismus.com/documents/linux/"
"automake/automake.shtml\">basic help with automake and autoconf</ulink>."
msgstr ""
"Openismus 有更多 <ulink url=\"http://www.openismus.com/documents/linux/"
"automake/automake.shtml\">帮助使用 automake 和 autoconf 的基础知识</ulink>。"

#: C/gtkmm-tutorial-in.xml:392(title) C/gtkmm-tutorial-in.xml:6318(title)
msgid "Widgets"
msgstr "组件"

#: C/gtkmm-tutorial-in.xml:393(para)
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 ""
"<application>gtkmm</application> 应用程序由一系列包含了如按钮、文本框之类组件"
"的窗口构成。在一些其它的系统上，组件可能被称为“控件”。对于你的应用程序窗口中"
"的每个组件，在你的代码里就会有一个对应的 C++ 对象。所以当你想控制组件行为的时"
"候，只需要调用这个组件对象的相应方法即可。"

#: C/gtkmm-tutorial-in.xml:395(programlisting)
#, no-wrap
msgid ""
"m_box.pack_start(m_Button1);\n"
"m_box.pack_start(m_Button2);"
msgstr ""
"m_box.pack_start(m_Button1);\n"
"m_box.pack_start(m_Button2);"

#: C/gtkmm-tutorial-in.xml:398(programlisting)
#, no-wrap
msgid "m_frame.add(m_box);"
msgstr "m_frame.add(m_box);"

#: C/gtkmm-tutorial-in.xml:394(para)
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 Gtk::VBox, are not visible - they exist only to arrange other "
"widgets. Here is some example code that adds 2 Gtk::Button widgets to a Gtk::"
"VBox container widgets: <placeholder-1/> and here is how to add the Gtk::"
"VBox, containing those buttons, to a Gtk::Frame, which has a visible frame "
"and title: <placeholder-2/>"
msgstr ""
"组件被安置在褚如 frame、notebook 这样的容器组件中，以一种组件包含组件的层次结"
"构的形式。其中一些容器组件，像 Gtk::VBox 这样的容器组件是不可见的，它们只是被"
"用来安置其它组件的。这有一些示例代码，将两个 Gtk::Button 组件放到一个 Gtk::"
"VBox 容器组件中：<placeholder-1/> 接下来是如何把这个包含两个按钮的 Gtk::VBox "
"添加到一个 Gtk::Frame 中，它包含一个可视的边框和标题：<placeholder-2/>"

#: C/gtkmm-tutorial-in.xml:400(para)
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 ""
"本书中的大部分章节都是讲解特定的组件。要得到更多关于添加组件到容器组件的信"
"息，请看 <link linkend=\"chapter-container-widgets\">容器组件</link> 这一章。"

#: C/gtkmm-tutorial-in.xml:404(para)
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 <literal>Glade</literal> and load them at runtime with "
"<literal>Gtk::Builder</literal>. See the <link linkend=\"chapter-builder"
"\">Glade and Gtk::Builder</link> chapter."
msgstr ""
"尽管你可以使用 C++ 代码来指定窗口和组件的外观和布局，但你可能会发现使用 "
"Glade 来设计你的界面，并且使用 <literal>Gtk::Builder</literal> 在运行时动态加"
"载界面是更方便。请参考 <link linkend=\"chapter-builder\">Glade 与 Gtk::"
"Builder</link> 这一章。"

#: C/gtkmm-tutorial-in.xml:407(para)
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. <function>Gtk::manage()</function> allows you to say that a "
"child widget is owned by the container into which you place it. This allows "
"you to <function>new</function> the widget, add it to the container and "
"forget about deleting it. You can learn more about <application>gtkmm</"
"application> memory management techniques in the <link linkend=\"chapter-"
"memory\">Memory Management chapter</link>."
msgstr ""
"尽管 <application>gtkmm</application> 组件实例拥有像其它 C++ 类那样的生存时间"
"和作用域，<application>gtkmm</application> 还是有一些可选的节省时间的特性，接"
"下来你会在接下来的一些例子中看到。<function>Gtk::manage()</function> 允许你指"
"定一个子组件是被其容器组件所拥有。这将允许你 <function>new</function> 组件、"
"添加到容器中，然后忘记删除它。如果你需要了解更多关于 <application>gtkmm</"
"application> 内存管理技术的话，请看 <link linkend=\"chapter-memory\">内存管理"
"</link> 章节。"

#: C/gtkmm-tutorial-in.xml:413(title) C/gtkmm-tutorial-in.xml:712(title)
#: C/gtkmm-tutorial-in.xml:5068(title) C/gtkmm-tutorial-in.xml:5361(title)
#: C/gtkmm-tutorial-in.xml:7639(title)
msgid "Signals"
msgstr "信号"

#: C/gtkmm-tutorial-in.xml:415(para)
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 ""
"像大多数 GUI 工具集一样，<application>gtkmm</application> 是<emphasis>事件驱"
"动</emphasis>的。当一个事件发生时，比如说一个鼠标按键被按下，那么所点击的组件"
"就会<emphasis>发出</emphasis>一个合适的信号。每种组件都可以发出一套不同的信"
"号。为了使这个按钮点击产生一个动作，我们可以设置一个<emphasis>信号处理函数"
"(signal handler)</emphasis>来捕捉这个“clicked”信号。"

#: C/gtkmm-tutorial-in.xml:423(programlisting)
#, no-wrap
msgid ""
"m_button1.signal_clicked().connect( sigc::mem_fun(*this,\n"
"  &amp;HelloWorld::on_button_clicked) );"
msgstr ""
"m_button1.signal_clicked().connect( sigc::mem_fun(*this,\n"
"  &amp;HelloWorld::on_button_clicked) );"

#: C/gtkmm-tutorial-in.xml:422(para)
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\": "
"<placeholder-1/>"
msgstr ""
"<application>gtkmm</application> 使用 libsigc++ 来实现信号操作。下面这个例子"
"演示怎样把 Gtk::Button “clicked” 信号连接到命名为“on_button_clicked”的信号处"
"理函数上：<placeholder-1/>"

#: C/gtkmm-tutorial-in.xml:427(para)
msgid ""
"For more detailed information about signals, see the <link linkend=\"chapter-"
"signals\">appendix</link>."
msgstr ""
"要得到更多关于信号的信息，请参考<link linkend=\"chapter-signals\">附录</"
"link>。"

#: C/gtkmm-tutorial-in.xml:428(para)
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 ""
"要想知道如何实现你自己的信号，而不仅仅是连接到现有的 <application>gtkmm</"
"application> 信号，请参考 <link linkend=\"chapter-custom-signals\">附录</"
"link>。"

#: C/gtkmm-tutorial-in.xml:434(title) C/gtkmm-tutorial-in.xml:9187(classname)
msgid "Glib::ustring"
msgstr "Glib::ustring"

#: C/gtkmm-tutorial-in.xml:435(para)
msgid ""
"You might be surprised to learn that <application>gtkmm</application> "
"doesn't use <classname>std::string</classname> in it its interfaces. Instead "
"it uses <classname>Glib::ustring</classname>, which is so similar and "
"unobtrusive that you could actually pretend that each Glib::ustring 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 ""
"你一定很惊讶得知 <application>gtkmm</application> 没有在它的接口上使用 "
"<classname>std::string</classname>，相反，它使用了 <classname>Glib::ustring</"
"classname>。 <classname>Glib::ustring</classname>与 <classname>std::string</"
"classname> 非常相似，甚至在某些场合，你甚至可以把它当成 <classname>std::"
"string</classname> 来使用，而忽略本节后面的内容。但是如果你希望在你的应用程序"
"中使用英语以外的语言的话，那么请继续读下去。"

#: C/gtkmm-tutorial-in.xml:436(para)
msgid ""
"std::string uses 8 bit per character, but 8 bits aren't enough to encode "
"languages such as Arabic, Chinese, and Japanese. Although the encodings for "
"these languages has now been specified by the Unicode Constortium, the C and "
"C++ languages do not yet provide any standardised Unicode support. 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 ""
"std::string 对每个字符使用8位编码，但是这对于像阿拉伯语、汉语和日语这样的语言"
"来说，8位是不够的。尽管 Unicode 协会已经详细定义了这些语言的编码，但是 C 和 C"
"++ 仍未提供任何标准的 Unicode 支持。GTK+ 和 GNOME 采用 UTF-8 编码来实现 "
"Unicode，这就是 Glib::ustring 所包装的东西。它提供了和 std::string 几乎相同的"
"接口，以及和 std::string 的自动类型转换的功能。"

#: C/gtkmm-tutorial-in.xml:437(para)
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 ""
"UTF-8 编码的优点之一是，如果不需要你可以不使用它，所以你不需要一次性的翻新你"
"的代码。<classname>std::string</classname> 还可以继续使用7位的 ASCII 字符串。"
"但是一旦你想本地化你的程序，比如说汉化，那你就会开始遇到各种奇怪的问题，可能"
"还会崩溃。那时，你所需要做的就是开始使用 <classname>Glib::ustring</"
"classname> 来取而代之。"

#: C/gtkmm-tutorial-in.xml:438(para)
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 ""
"要注意的是 UTF-8 和其它一些8位的编码如 ISO-8859-1 并不兼容。比如，德语中的元"
"音变音并不在 ASCII 码的编码范围内，在 UTF-8 编码中需要额外的一个字节来表示。"
"如果你的代码中包含8位的字符串文字，你需要把它们转变成 UTF-8 编码 (比如，巴伐"
"利亚的问候语“Grüß Gott”可能会显示成“Gr\\xC3\\xBC\\xC3\\x9F Gott”)。"

#: C/gtkmm-tutorial-in.xml:439(para)
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 ""
"你应该尽量避免 C 风格的指针算法，以及像 strlen() 这样的函数。在 UTF-8 编码"
"中，每个字符可能占1到6个字节，所以你并不能假定下一个字节一定是另一个字符。所"
"有的这些细节 <classname>Glib::ustring</classname> 都已经帮你考虑到了，所以你"
"可以从字符的层面上考虑使用 Glib::ustring::substr() 这样的函数，而不用再去考虑"
"字节这样的细节了。"

#: C/gtkmm-tutorial-in.xml:441(para)
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 ""
"不像 Windows 的 UCS-2 Unicode 解决方案，这并不需要编译器提供特别的选项来处理"
"这样字符串，也不会导致为 Unicode 编译的可执行文件或库与含为 ASCII 的不兼容之"
"类的问题。"

#: C/gtkmm-tutorial-in.xml:443(ulink) C/gtkmm-tutorial-in.xml:692(ulink)
#: C/gtkmm-tutorial-in.xml:790(ulink) C/gtkmm-tutorial-in.xml:805(ulink)
#: C/gtkmm-tutorial-in.xml:908(ulink) C/gtkmm-tutorial-in.xml:962(ulink)
#: C/gtkmm-tutorial-in.xml:980(ulink) C/gtkmm-tutorial-in.xml:1026(ulink)
#: C/gtkmm-tutorial-in.xml:1123(ulink) C/gtkmm-tutorial-in.xml:1178(ulink)
#: C/gtkmm-tutorial-in.xml:1224(ulink) C/gtkmm-tutorial-in.xml:1424(ulink)
#: C/gtkmm-tutorial-in.xml:1472(ulink) C/gtkmm-tutorial-in.xml:1520(ulink)
#: C/gtkmm-tutorial-in.xml:1595(ulink) C/gtkmm-tutorial-in.xml:1636(ulink)
#: C/gtkmm-tutorial-in.xml:1677(ulink) C/gtkmm-tutorial-in.xml:1710(ulink)
#: C/gtkmm-tutorial-in.xml:1750(ulink) C/gtkmm-tutorial-in.xml:2353(ulink)
#: C/gtkmm-tutorial-in.xml:2420(ulink) C/gtkmm-tutorial-in.xml:2573(ulink)
#: C/gtkmm-tutorial-in.xml:2630(ulink) C/gtkmm-tutorial-in.xml:2698(ulink)
#: C/gtkmm-tutorial-in.xml:2745(ulink) C/gtkmm-tutorial-in.xml:2761(ulink)
#: C/gtkmm-tutorial-in.xml:2779(ulink) C/gtkmm-tutorial-in.xml:2887(ulink)
#: C/gtkmm-tutorial-in.xml:3410(ulink) C/gtkmm-tutorial-in.xml:3486(ulink)
#: C/gtkmm-tutorial-in.xml:3565(ulink) C/gtkmm-tutorial-in.xml:3593(ulink)
#: C/gtkmm-tutorial-in.xml:3622(ulink) C/gtkmm-tutorial-in.xml:3674(ulink)
#: C/gtkmm-tutorial-in.xml:3694(ulink) C/gtkmm-tutorial-in.xml:3742(ulink)
#: C/gtkmm-tutorial-in.xml:4240(ulink) C/gtkmm-tutorial-in.xml:4297(ulink)
#: C/gtkmm-tutorial-in.xml:4308(ulink) C/gtkmm-tutorial-in.xml:4335(ulink)
#: C/gtkmm-tutorial-in.xml:4357(ulink) C/gtkmm-tutorial-in.xml:4380(ulink)
#: C/gtkmm-tutorial-in.xml:5176(ulink) C/gtkmm-tutorial-in.xml:5451(ulink)
#: C/gtkmm-tutorial-in.xml:5483(ulink) C/gtkmm-tutorial-in.xml:7507(ulink)
msgid "Reference"
msgstr "参考"

#: C/gtkmm-tutorial-in.xml:445(para)
msgid ""
"See the <link linkend=\"chapter-internationalization\">Internationalization</"
"link> section for information about providing the UTF-8 string literals."
msgstr ""
"要得到更多关于 UTF-8 字符的信息，请参考<link linkend=\"chapter-"
"internationalization\">国际化</link>这一节。"

#: C/gtkmm-tutorial-in.xml:450(title)
msgid "Intermediate types"
msgstr "中间类型"

#: C/gtkmm-tutorial-in.xml:453(para)
msgid ""
"<classname>Glib::StringArrayHandle</classname> or <classname>Glib::"
"ArrayHandle&lt;Glib::ustring&gt;</classname>: Use <classname>std::vector&lt;"
"Glib::ustring&gt;</classname>, <classname>std::list&lt;Glib::ustring&gt;</"
"classname>, <type>const char*[]</type>, etc."
msgstr ""
"<classname>Glib::StringArrayHandle</classname> 或 <classname>Glib::"
"ArrayHandle&lt;Glib::ustring&gt;</classname>：使用 <classname>std::vector&lt;"
"Glib::ustring&gt;</classname>、<classname>std::list&lt;Glib::ustring&gt;</"
"classname>、<type>const char*[]</type> 等。"

#: C/gtkmm-tutorial-in.xml:454(para)
msgid ""
"<classname>Glib::ListHandle&lt;Gtk::Widget*&gt;</classname>: Use "
"<classname>std::vector&lt;Gtk::Widget*&gt;</classname>, <classname>std::"
"list&lt;Gtk::Widget*&gt;</classname>, etc."
msgstr ""
"<classname>Glib::ListHandle&lt;Gtk::Widget*&gt;</classname>：使用 "
"<classname>std::vector&lt;Gtk::Widget*&gt;</classname>、<classname>std::"
"list&lt;Gtk::Widget*&gt;</classname> 等。"

#: C/gtkmm-tutorial-in.xml:455(para)
msgid ""
"<classname>Glib::SListHandle&lt;Gtk::Widget*&gt;</classname>: Use "
"<classname>std::vector&lt;Gtk::Widget*&gt;</classname>, <classname>std::"
"list&lt;Gtk::Widget*&gt;</classname>, etc."
msgstr ""
"<classname>Glib::SListHandle&lt;Gtk::Widget*&gt;</classname>：使用 "
"<classname>std::vector&lt;Gtk::Widget*&gt;</classname>、<classname>std::"
"list&lt;Gtk::Widget*&gt;</classname> 等。"

#: C/gtkmm-tutorial-in.xml:451(para)
msgid ""
"Some parts of the <application>gtkmm</application> API use intermediate data "
"containers, such as <classname>Glib::StringArrayHandle</classname> instead "
"of a specific Standard C++ container such as <classname>std::vector</"
"classname> or <classname>std::list</classname>. You should not declare these "
"types yourself -- you should use whatever Standard C++ container you prefer "
"instead. <application>gtkmm</application> will do the conversion for you. "
"Here are some of these intermediate types: <placeholder-1/>"
msgstr ""
"部分 <application>gtkmm</application> API 使用了中间数据容器，如 "
"<classname>Glib::StringArrayHandle</classname> 而不是特定的标准 C++ 容器 "
"<classname>std::vector</classname> 或 <classname>std::list</classname>。但是"
"你不应该自己声明这些类型，你应当使用你所倾向的标准 C++ 容器。"
"<application>gtkmm</application> 将会帮你进行类型转换。这里有一些这类中间类"
"型：<placeholder-1/>"

#: C/gtkmm-tutorial-in.xml:463(title)
msgid "Mixing C and C++ APIs"
msgstr "混合使用 C 和 C++ API"

#: C/gtkmm-tutorial-in.xml:464(para)
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 GObject system."
msgstr ""
"你可以使用那些尚未提供 C++ 接口的 C API。对于 C++ 而言这一般不是什么问题，"
"<application>gtkmm</application> 可以提供帮助访问底层的 C 对象，并且也提供了"
"一个简单的方式来从一个 C 对象创建一个 C++ 封装的对象，当然，这个 C API 是需要"
"基于 GObject 系统的。"

#: C/gtkmm-tutorial-in.xml:466(para)
msgid ""
"To use a <application>gtkmm</application> instance with a C function that "
"requires a C GObject instance, use the <function>gobj()</function> function "
"to obtain a pointer to the underlying GObject instance. For instance"
msgstr ""
"要用 C 函数使用一个 <application>gtkmm</application> 实例需要一个 C GObject "
"实例，使用 <function>gobj()</function> 函数可以得到一个底层 GObject 实例的指"
"针。例如"

#: C/gtkmm-tutorial-in.xml:469(programlisting)
#, no-wrap
msgid ""
"\n"
"Gtk::Button* button = new Gtk::Button(\"example\");\n"
"gtk_button_do_something_new(button-&gt;gobj());\n"
msgstr ""
"\n"
"Gtk::Button* button = new Gtk::Button(\"example\");\n"
"gtk_button_do_something_new(button-&gt;gobj());\n"

#: C/gtkmm-tutorial-in.xml:475(para)
msgid ""
"To obtain a <application>gtkmm</application> instance from a C GObject "
"instance, use the Glib::wrap() function. For instance"
msgstr ""
"要从 C GObject 实例得到一个 <application>gtkmm</application> 实例，则使用 "
"Glib::wrap() 函数。例如"

#: C/gtkmm-tutorial-in.xml:477(programlisting)
#, no-wrap
msgid ""
"\n"
"GtkButton* cbutton = get_a_button();\n"
"Gtk::Button* button = Glib::wrap(cbutton);\n"
msgstr ""
"\n"
"GtkButton* cbutton = get_a_button();\n"
"Gtk::Button* button = Glib::wrap(cbutton);\n"

#: C/gtkmm-tutorial-in.xml:485(title)
msgid "Hello World in <application>gtkmm</application>"
msgstr "用 <application>gtkmm</application> 写 Hello World"

#: C/gtkmm-tutorial-in.xml:487(para)
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 ""
"目前我们已经可以自己所学的知识来写一个真正的程序了。根据计算机科学的传统，我"
"们现在以 <application>gtkmm</application> 的方式来介绍 Hello World 程序："

#: C/gtkmm-tutorial-in.xml:494(para)
msgid ""
"Try to compile and run it before going on. You should see something like "
"this:"
msgstr "在继续讲解之前，可以尝试着编译并运行这个程序，你会看到这样的结果："

#: C/gtkmm-tutorial-in.xml:499(title)
msgid "Hello World"
msgstr "Hello World"

#: C/gtkmm-tutorial-in.xml:505(para)
msgid ""
"Pretty thrilling, eh? Let's examine the code. First, the "
"<classname>HelloWorld</classname> class:"
msgstr ""
"真让人激动，不是吗？让我们回过头来看一下代码。首先看一下 "
"<classname>HelloWorld</classname> 类："

#: C/gtkmm-tutorial-in.xml:510(programlisting)
#, no-wrap
msgid ""
"class HelloWorld : public Gtk::Window\n"
"{\n"
"\n"
"public:\n"
"  HelloWorld();\n"
"  virtual ~HelloWorld();\n"
"\n"
"protected:\n"
"  //Signal handlers:\n"
"  virtual void on_button_clicked();\n"
"\n"
"  //Member widgets:\n"
"  Gtk::Button m_button;\n"
"};"
msgstr ""
"class HelloWorld : public Gtk::Window\n"
"{\n"
"\n"
"public:\n"
"  HelloWorld();\n"
"  virtual ~HelloWorld();\n"
"\n"
"protected:\n"
"  //Signal handlers:\n"
"  virtual void on_button_clicked();\n"
"\n"
"  //Member widgets:\n"
"  Gtk::Button m_button;\n"
"};"

#: C/gtkmm-tutorial-in.xml:525(para)
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 "
"initialisation work for the window, including setting up the signals. Here "
"it is, with the comments omitted:"
msgstr ""
"这个类实现了“Hello World”窗口。它由 <classname>Gtk::Window</classname> 派生，"
"并且只有一个 <classname>Gtk::Button</classname> 成员。我们已经使用构造函数为"
"该窗口完成了所有的初始化工作，包括挂接消息。在这，已经去掉注释的代码："

#: C/gtkmm-tutorial-in.xml:534(programlisting)
#, no-wrap
msgid ""
"HelloWorld::HelloWorld()\n"
":\n"
"  m_button (\"Hello World\")\n"
"{\n"
"  set_border_width(10);\n"
"  m_button.signal_clicked().connect(sigc::mem_fun(*this,\n"
"    &amp;HelloWorld::on_button_clicked));\n"
"  add(m_button);.\n"
"  m_button.show();\n"
"}"
msgstr ""
"HelloWorld::HelloWorld()\n"
":\n"
"  m_button (\"Hello World\")\n"
"{\n"
"  set_border_width(10);\n"
"  m_button.signal_clicked().connect(sigc::mem_fun(*this,\n"
"    &amp;HelloWorld::on_button_clicked));\n"
"  add(m_button);.\n"
"  m_button.show();\n"
"}"

#: C/gtkmm-tutorial-in.xml:545(para)
msgid ""
"Notice that we've used an initialiser statement to give the "
"<literal>m_button</literal> object the label \"Hello World\"."
msgstr ""
"注意，我们使用初始化列表的方式给 <literal>m_button</literal> 对象添加了一"
"个“Hello World”的标签。"

#: C/gtkmm-tutorial-in.xml:550(para)
msgid ""
"Next we call the Window's <methodname>set_border_width()</methodname> "
"method. This sets the amount of space between the sides of the window and "
"the widget it contains."
msgstr ""
"接下来调用 Windows 类的 <methodname>set_border_width()</methodname> 方法。设"
"置窗口的边框和它所包含的组件之间的空白距离。"

#: C/gtkmm-tutorial-in.xml:556(para)
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 ""
"然后，把 <literal>m_button</literal> 的 <literal>clicked</literal> 消息挂接到"
"信号处理函数上。这会向 <literal>stdout</literal> (标准输出) 打印出友好的问候"
"语。"

#: C/gtkmm-tutorial-in.xml:561(para)
msgid ""
"Next, we use the Window's <methodname>add()</methodname> method to put "
"<literal>m_button</literal> in the Window. (<methodname>add()</methodname> "
"comes from <classname>Gtk::Container</classname>, which is described in the "
"chapter on container widgets.) The <methodname>add()</methodname> method "
"places the Widget in the Window, but it doesn't display the widget. "
"<application>gtkmm</application> widgets are always invisible when you "
"create them - to display them, you must call their <methodname>show()</"
"methodname> method, which is what we do in the next line."
msgstr ""
"下一步，我们使用 Window 类的 <methodname>add()</methodname> 方法把 "
"<literal>m_button</literal> 加到 Window 类中。(<methodname>add()</"
"methodname> 方法由 <classname>Gtk::Container</classname> 类继承而来，我们将在"
"容器组件这一章中具体介绍。) <methodname>add()</methodname> 方法仅仅将组件添加"
"到窗口中，它并不负责显示这些组件。<application>gtkmm</application> 组件在创建"
"以后都是不可见的。要显示它们，你必须调用 <methodname>show()</methodname> 方"
"法，通常我们会在接下来的一行就调用它。"

#: C/gtkmm-tutorial-in.xml:571(para)
msgid ""
"Now let's look at our program's <function>main()</function> function. Here "
"it is, without comments:"
msgstr "现在让我们来看看程序中没有注释过的 <function>main()</function> 函数："

#: C/gtkmm-tutorial-in.xml:576(programlisting)
#, no-wrap
msgid ""
"int main(int argc, char** argv)\n"
"{\n"
"  Gtk::Main kit(argc, argv);\n"
"\n"
"  HelloWorld helloworld;\n"
"  Gtk::Main::run(helloworld);\n"
"\n"
"  return 0;\n"
"}"
msgstr ""
"int main(int argc, char** argv)\n"
"{\n"
"  Gtk::Main kit(argc, argv);\n"
"\n"
"  HelloWorld helloworld;\n"
"  Gtk::Main::run(helloworld);\n"
"\n"
"  return 0;\n"
"}"

#: C/gtkmm-tutorial-in.xml:586(para)
msgid ""
"First we instantiate an object called <literal>kit</literal>. This is of "
"type <classname>Gtk::Main</classname>. Every <application>gtkmm</"
"application> program must have one of these. We pass our command-line "
"arguments to its constructor. It takes the arguments it wants, and leaves "
"you the rest, as we described earlier."
msgstr ""
"我们首先初始化一个名为 <literal>kit</literal> 的对象，它的类型为 "
"<classname>Gtk::Main</classname> 。每一个 <application>gtkmm</application> 程"
"序都有这样的一个东西。我们将命令行参数传递给它的构造函数。它会提取自己需要的"
"参数，将剩下的部分留给我们，就像前面描述过的那样。"

#: C/gtkmm-tutorial-in.xml:593(para)
msgid ""
"Next we make an object of our <classname>HelloWorld</classname> class, whose "
"constructor takes no arguments, but it isn't visible yet. When we call Gtk::"
"Main::run(), giving it the helloworld Window, it shows the 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, run() will return, causing the final line of our main() function be "
"to executed. The application will then finish."
msgstr ""
"接着我们创建了 <classname>HelloWorld</classname> 类的对象，它的构造函数没有参"
"数，当然，它现在还不是可视的。当我们调用 Gtk::Main::run() 并给它提供一个 "
"helloworld 窗口作为参数时，它将显示这个窗口并进入 <application>gtkmm</"
"application><emphasis>消息循环</emphasis>。在消息循环中，<application>gtkmm</"
"application> 是空闲的，它等待用户的操作并作出相应的反应。当用户关闭窗口时，"
"run() 函数将返回，导致 main() 函数的最后一行将被执行。然后程序就结束了。"

#: C/gtkmm-tutorial-in.xml:603(title)
msgid "Buttons"
msgstr "按钮"

#: C/gtkmm-tutorial-in.xml:605(para)
msgid "<application>gtkmm</application> provides four basic types of buttons:"
msgstr "<application>gtkmm</application> 提供以下四种基本按钮控件："

#: C/gtkmm-tutorial-in.xml:612(term)
msgid "Push-Buttons"
msgstr "按钮 (Button)"

#: C/gtkmm-tutorial-in.xml:614(para)
msgid ""
"<ulink url=\"http://library.gnome.org/devel/gtkmm/unstable/"
"classGtk_1_1Button.html\"><classname>Gtk::Button</classname></ulink>. "
"Standard buttons, usually marked with a label or picture. Pushing one "
"triggers an action. See the <link linkend=\"sec-pushbuttons\">Button</link> "
"section."
msgstr ""
"<ulink url=\"http://library.gnome.org/devel/gtkmm/unstable/"
"classGtk_1_1Button.html\"><classname>Gtk::Button</classname></ulink>。这是标"
"准按钮，通常标有文字标签或者图片。按一下就会触发一个动作。参看 <link linkend="
"\"sec-pushbuttons\">Button</link> 小节。"

#: C/gtkmm-tutorial-in.xml:621(term)
msgid "Toggle buttons"
msgstr "开关按钮 (ToggleButton)"

#: C/gtkmm-tutorial-in.xml:623(para)
msgid ""
"<ulink url=\"http://library.gnome.org/devel/gtkmm/unstable/"
"classGtk_1_1ToggleButton.html\"><classname>Gtk::ToggleButton</classname></"
"ulink>. 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 ""
"<ulink url=\"http://library.gnome.org/devel/gtkmm/unstable/"
"classGtk_1_1ToggleButton.html\"><classname>Gtk::ToggleButton</classname></"
"ulink>。和一般按下后会自动弹起的按钮不一样，ToggleButton 需要你再按一次才会弹"
"起。它作为一个开关可能比较有用。参看 <link linkend=\"sec-toggle-buttons"
"\">ToggleButton</link> 小节。"

#: C/gtkmm-tutorial-in.xml:631(term)
msgid "Checkboxes"
msgstr "复选框 (CheckButton)"

#: C/gtkmm-tutorial-in.xml:633(para)
msgid ""
"<ulink url=\"http://library.gnome.org/devel/gtkmm/unstable/"
"classGtk_1_1CheckButton.html\"><classname>Gtk::CheckButton</classname></"
"ulink>. 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-checkboxes"
"\">CheckBox</link> section."
msgstr ""
"<ulink url=\"http://library.gnome.org/devel/gtkmm/unstable/"
"classGtk_1_1CheckButton.html\"><classname>Gtk::CheckButton</classname></"
"ulink>。它们用起来和 ToggleButtons 很像，只不过它们用一个小方块来显示自己的状"
"态，而且旁边还有一个文字标签。在大多数需要布尔值设置的情况都可以使用它。参看 "
"<link linkend=\"sec-checkboxes\">CheckBox</link> 小节。"

#: C/gtkmm-tutorial-in.xml:643(term)
msgid "Radio buttons"
msgstr "单选框 (RadioButton)"

#: C/gtkmm-tutorial-in.xml:645(para)
msgid ""
"<ulink url=\"http://library.gnome.org/devel/gtkmm/unstable/"
"classGtk_1_1RadioButton.html\"><classname>Gtk::RadioButton</classname></"
"ulink>. 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 "
"CheckBoxes (a small widget with a label at the side), but usually look "
"different. See the <link linkend=\"sec-radio-buttons\">RadioButton</link> "
"section."
msgstr ""
"<ulink url=\"http://library.gnome.org/devel/gtkmm/unstable/"
"classGtk_1_1RadioButton.html\"><classname>Gtk::RadioButton</classname></"
"ulink>。它是根据老式汽车内的收音机的选台器来命名的，选台器是一组选择按钮并且"
"它们是互斥的。按下其中任何一个都会使这一组中的其它按钮都弹起。它们的布局和 "
"CheckButton (一个旁边有标签的小组件)很相似，但是通常看起来不太一样。参看 "
"<link linkend=\"sec-radio-buttons\">RadioButton</link> 小节。"

#: C/gtkmm-tutorial-in.xml:659(para)
msgid ""
"Note that, due to GTK+'s theming system, the appearance of these widgets "
"will vary. In the case of checkboxes and radio buttons, they may vary "
"considerably."
msgstr ""
"请注意，由于GTK＋的主题不同，这些控件外观可能会不同。特别是复选框和单选按钮可"
"能会很不一样。"

#: C/gtkmm-tutorial-in.xml:666(title)
msgid "Button"
msgstr "Button (按钮)"

#: C/gtkmm-tutorial-in.xml:668(title)
msgid "Constructors"
msgstr "构造函数"

#: C/gtkmm-tutorial-in.xml:670(para)
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 ""
"可以通过两种方式来创建按钮，你可以在 <classname>Gtk::Button</classname> 构造"
"函数中指定标签字符串，或者以后调用 <methodname>set_label()</methodname> 来指"
"定标签。"

#: C/gtkmm-tutorial-in.xml:676(para)
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 ""
"如果你想为按钮定义一个快捷键，那么可以在标签字符串中的某个字符前面加上一个下"
"划线，并且指定可选的参数助记符(mnemonic)为 true。例如："

#: C/gtkmm-tutorial-in.xml:678(programlisting)
#, no-wrap
msgid "Gtk::Button* pButton = new Gtk::Button(\"_Something\", true);"
msgstr "Gtk::Button* pButton = new Gtk::Button(\"_Something\", true);"

#: C/gtkmm-tutorial-in.xml:682(programlisting)
#, no-wrap
msgid "Gtk::Button* pButton = new Gtk::Button(Gtk::Stock::OK);"
msgstr "Gtk::Button* pButton = new Gtk::Button(Gtk::Stock::OK);"

#: C/gtkmm-tutorial-in.xml:680(para)
msgid ""
"Wherever possible you should use Stock items, to ensure consistency with "
"other applications, and to improve the appearance of your applications by "
"using icons. For instance, <placeholder-1/> This will use standard text, in "
"all languages, with standard keyboard accelerators, with a standard icon."
msgstr ""
"任何时候你都应尽可能的使用 Stock Item，这样可以使你的应用程序和其它的保持一"
"致，并且可以通过使用图标来改善程序的外观。例如， <placeholder-1/> 这样在所有"
"的语言中都会使用标准的文字，标准的快捷键，以及标准的图标。"

#: C/gtkmm-tutorial-in.xml:686(para)
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 ""
"<classname>Gtk::Button</classname> 同时也是一个容器，因此你可以在其中放任何其"
"它的组件，比如放一个 <classname>Gtk::Image</classname> 在里面。"

#: C/gtkmm-tutorial-in.xml:695(title) C/gtkmm-tutorial-in.xml:807(title)
#: C/gtkmm-tutorial-in.xml:912(title) C/gtkmm-tutorial-in.xml:1073(title)
#: C/gtkmm-tutorial-in.xml:1125(title) C/gtkmm-tutorial-in.xml:1428(title)
#: C/gtkmm-tutorial-in.xml:1498(title) C/gtkmm-tutorial-in.xml:1522(title)
#: C/gtkmm-tutorial-in.xml:1597(title) C/gtkmm-tutorial-in.xml:1638(title)
#: C/gtkmm-tutorial-in.xml:1679(title) C/gtkmm-tutorial-in.xml:1713(title)
#: C/gtkmm-tutorial-in.xml:1753(title) C/gtkmm-tutorial-in.xml:2385(title)
#: C/gtkmm-tutorial-in.xml:2423(title) C/gtkmm-tutorial-in.xml:2577(title)
#: C/gtkmm-tutorial-in.xml:2632(title) C/gtkmm-tutorial-in.xml:2700(title)
#: C/gtkmm-tutorial-in.xml:4243(title) C/gtkmm-tutorial-in.xml:4311(title)
#: C/gtkmm-tutorial-in.xml:4338(title) C/gtkmm-tutorial-in.xml:4360(title)
#: C/gtkmm-tutorial-in.xml:4383(title) C/gtkmm-tutorial-in.xml:4550(title)
#: C/gtkmm-tutorial-in.xml:4673(title) C/gtkmm-tutorial-in.xml:4753(title)
#: C/gtkmm-tutorial-in.xml:5138(title) C/gtkmm-tutorial-in.xml:5687(title)
#: C/gtkmm-tutorial-in.xml:6640(title) C/gtkmm-tutorial-in.xml:6709(title)
#: C/gtkmm-tutorial-in.xml:7317(title) C/gtkmm-tutorial-in.xml:7343(title)
#: C/gtkmm-tutorial-in.xml:8097(title)
msgid "Example"
msgstr "示例"

#: C/gtkmm-tutorial-in.xml:697(para)
msgid "This example creates a button with a picture and a label."
msgstr "这个示例创建了一个有图片和文字标签的按钮。"

#: C/gtkmm-tutorial-in.xml:702(title)
msgid "buttons example"
msgstr "按钮示例"

#: C/gtkmm-tutorial-in.xml:714(para)
msgid ""
"The <classname>Gtk::Button</classname> widget has the following signals, but "
"most of the time you will just handle the <literal>clicked</literal> signal:"
msgstr ""
"<classname>Gtk::Button</classname> 组件有下面列出的那些信号，不过大多数情况"
"下，你只需要处理 <literal>clicked</literal> 信号："

#: C/gtkmm-tutorial-in.xml:722(literal)
msgid "pressed"
msgstr "pressed (按下)"

#: C/gtkmm-tutorial-in.xml:724(para)
msgid "Emitted when the button is pressed."
msgstr "当按钮按下时发出。"

#: C/gtkmm-tutorial-in.xml:730(literal)
msgid "released"
msgstr "released (释放)"

#: C/gtkmm-tutorial-in.xml:732(para)
msgid "Emitted when the button is released."
msgstr "当按钮释放后发出。"

#: C/gtkmm-tutorial-in.xml:738(literal)
msgid "clicked"
msgstr "clicked (点击)"

#: C/gtkmm-tutorial-in.xml:740(para)
msgid "Emitted when the button is pressed and released."
msgstr "当按钮按下并抬起时发出。"

#: C/gtkmm-tutorial-in.xml:746(literal)
msgid "enter"
msgstr "enter (进入)"

#: C/gtkmm-tutorial-in.xml:748(para)
msgid "Emitted when the mouse pointer moves over the button's window."
msgstr "当鼠标指针移到按钮上时发出。"

#: C/gtkmm-tutorial-in.xml:754(literal)
msgid "leave"
msgstr "leave (离开)"

#: C/gtkmm-tutorial-in.xml:756(para)
msgid "Emitted when the mouse pointer leaves the button's window."
msgstr "当鼠标指针离开按钮时发出。"

#: C/gtkmm-tutorial-in.xml:768(title)
msgid "ToggleButton"
msgstr "ToggleButton (开关按钮)"

#: C/gtkmm-tutorial-in.xml:770(para)
msgid ""
"<classname>ToggleButton</classname>s are like normal <classname>Button</"
"classname>s, but when clicked they remain activated, or pressed, until "
"clicked again."
msgstr ""
"<classname>ToggleButton</classname> 和普通的 <classname>Button</classname> 相"
"似，但是它们在点击后会保持激活(或称为按下的)状态，直到再次点击它为止。"

#: C/gtkmm-tutorial-in.xml:772(para)
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 ""
"要得到 <classname>ToggleButton</classname> 的状态，你可以使用 "
"<methodname>get_active()</methodname> 方法。如果按钮被按下了，就返回 true。当"
"然，你也可以通过 <methodname>set_active()</methodname> 来设置开关按钮的状态。"
"请注意，如果你这样做了，并且它的状态的确改变了，那么这将会引发“clicked”信号。"
"当然，一般来说，这就是你希望看到的结果。"

#: C/gtkmm-tutorial-in.xml:779(para)
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 ""
"你可以使用 <methodname>toggled()</methodname> 方法来改变按钮的状态，而不要强"
"行的是设置它是开还是关：这个方法将会改变按钮的状态，并会引发 "
"<literal>toggled</literal> 信号。"

#: C/gtkmm-tutorial-in.xml:784(para)
msgid ""
"<classname>Gtk::ToggleButton</classname> is most useful as a base class for "
"the <classname>Gtk::CheckButton</classname> and <classname>Gtk::RadioButton</"
"classname> classes."
msgstr ""
"<classname>Gtk::ToggleButton</classname> 类最有用的是作为 <classname>Gtk::"
"CheckButton</classname> 类和 <classname>Gtk::RadioButton</classname> 类的基"
"类。"

#: C/gtkmm-tutorial-in.xml:795(title) C/gtkmm-tutorial-in.xml:810(title)
msgid "CheckButton"
msgstr "CheckButton (多选按钮)"

#: C/gtkmm-tutorial-in.xml:797(para)
msgid ""
"<classname>Gtk::CheckButton</classname> inherits from <classname>Gtk::"
"ToggleButton</classname>. The only real difference between the two is "
"<classname>Gtk::CheckButton</classname>'s appearance. You can check, set, "
"and toggle a checkbox using the same member methods as for <classname>Gtk::"
"ToggleButton</classname>."
msgstr ""
"<classname>Gtk::CheckButton</classname> 继承自 <classname>Gtk::ToggleButton</"
"classname>。二者实际上只是外观不同而已。因此你可以像 <classname>Gtk::"
"ToggleButton</classname> 一样使用同样的方法来检查、设置和转换多选按钮的状态。"

#: C/gtkmm-tutorial-in.xml:822(title) C/gtkmm-tutorial-in.xml:919(title)
msgid "RadioButton"
msgstr "RadioButton (单选按钮)"

#: C/gtkmm-tutorial-in.xml:824(para)
msgid ""
"Like checkboxes, radio buttons also inherit from <classname>Gtk::"
"ToggleButton</classname>, but these work in groups, and only one RadioButton "
"in a group can be selected at any one time."
msgstr ""
"和 <classname>Gtk::CheckButton</classname> 一样，<classname>Gtk::"
"RadioButton</classname> 也继承自 <classname>Gtk::ToggleButton</classname>，只"
"是它们是按组工作的，并且一个组内一次只能选中一个 RadioButton。"

#: C/gtkmm-tutorial-in.xml:830(title)
msgid "Groups"
msgstr "组"

#: C/gtkmm-tutorial-in.xml:831(para)
msgid ""
"There are two ways to set up a group of radio buttons. The first way is to "
"create the buttons, and set up their groups afterwards. Only the first two "
"constructors are used. In the following example, we make a new window class "
"called <classname>RadioButtons</classname>, and then put three radio buttons "
"in it:"
msgstr ""
"有两种方式创建一个单选按钮的组。第一种方式是先创建按钮，然后再设置它们的组。"
"这种方式只用到了前两个构造函数。在下面的示例中，我们创建了一个新的窗口类 "
"<classname>RadioButtons</classname>，然后在其中放置3个单选按钮："

#: C/gtkmm-tutorial-in.xml:839(programlisting)
#, no-wrap
msgid ""
"class RadioButtons : public Gtk::Window\n"
"{\n"
"public:\n"
"    RadioButtons();\n"
"\n"
"protected:\n"
"    Gtk::RadioButton m_rb1, m_rb2, m_rb3;\n"
"};\n"
"\n"
"RadioButtons::RadioButtons()\n"
"  : m_rb1(\"button1\"),\n"
"    m_rb2(\"button2\"),\n"
"    m_rb3(\"button3\")\n"
"{\n"
"    Gtk::RadioButton::Group group = m_rb1.get_group();\n"
"    m_rb2.set_group(group);\n"
"    m_rb3.set_group(group);\n"
"}"
msgstr ""
"class RadioButtons : public Gtk::Window\n"
"{\n"
"public:\n"
"    RadioButtons();\n"
"\n"
"protected:\n"
"    Gtk::RadioButton m_rb1, m_rb2, m_rb3;\n"
"};\n"
"\n"
"RadioButtons::RadioButtons()\n"
"  : m_rb1(\"button1\"),\n"
"    m_rb2(\"button2\"),\n"
"    m_rb3(\"button3\")\n"
"{\n"
"    Gtk::RadioButton::Group group = m_rb1.get_group();\n"
"    m_rb2.set_group(group);\n"
"    m_rb3.set_group(group);\n"
"}"

#: C/gtkmm-tutorial-in.xml:857(para)
msgid ""
"We told <application>gtkmm</application> to put all three "
"<classname>RadioButton</classname>s in the same group by obtaining the group "
"with <methodname>get_group()</methodname> and using <methodname>set_group()</"
"methodname> to tell the other <classname>RadioButton</classname>s to share "
"that group."
msgstr ""
"我们告诉 <application>gtkmm</application> 把三个 <classname>RadioButton</"
"classname> 都放到一个组内，通过 <methodname>get_group()</methodname> 来得到这"
"个组，然后使用 <methodname>set_group()</methodname> 告诉其它的 "
"<classname>RadioButton</classname> 来共享这个组。"

#: C/gtkmm-tutorial-in.xml:866(programlisting)
#, no-wrap
msgid "m_rb2.set_group(m_rb1.get_group()); //doesn't work"
msgstr "m_rb2.set_group(m_rb1.get_group()); //无法工作"

#: C/gtkmm-tutorial-in.xml:864(para)
msgid ""
"Note that you can't just do <placeholder-1/> because the group is modified "
"by <methodname>set_group()</methodname> and therefore non-const."
msgstr ""
"注意，你不能只是 <placeholder-1/> 因为该组会由 <methodname>set_group()</"
"methodname> 修改，所以它不能是一个常量。"

#: C/gtkmm-tutorial-in.xml:872(para)
msgid ""
"The second way to set up radio buttons is to make a group first, and then "
"add radio buttons to it. Here's an example:"
msgstr ""
"第二种创建单选按钮的方式是，先创建一个组，然后再向该组加入按钮。请看下面的示"
"例："

#: C/gtkmm-tutorial-in.xml:876(programlisting)
#, no-wrap
msgid ""
"class RadioButtons : public Gtk::Window\n"
"{\n"
"public:\n"
"    RadioButtons();\n"
"};\n"
"\n"
"RadioButtons::RadioButtons()\n"
"{\n"
"    Gtk::RadioButton::Group group;\n"
"    Gtk::RadioButton *m_rb1 = Gtk::manage(\n"
"      new Gtk::RadioButton(group,\"button1\"));\n"
"    Gtk::RadioButton *m_rb2 = manage(\n"
"      new Gtk::RadioButton(group,\"button2\"));\n"
"      Gtk::RadioButton *m_rb3 = manage(\n"
"        new Gtk::RadioButton(group,\"button3\"));\n"
"}"
msgstr ""
"class RadioButtons : public Gtk::Window\n"
"{\n"
"public:\n"
"    RadioButtons();\n"
"};\n"
"\n"
"RadioButtons::RadioButtons()\n"
"{\n"
"    Gtk::RadioButton::Group group;\n"
"    Gtk::RadioButton *m_rb1 = Gtk::manage(\n"
"      new Gtk::RadioButton(group,\"button1\"));\n"
"    Gtk::RadioButton *m_rb2 = manage(\n"
"      new Gtk::RadioButton(group,\"button2\"));\n"
"      Gtk::RadioButton *m_rb3 = manage(\n"
"        new Gtk::RadioButton(group,\"button3\"));\n"
"}"

#: C/gtkmm-tutorial-in.xml:893(para)
msgid ""
"We made a new group by simply declaring a variable, <literal>group</"
"literal>, of type <classname>Gtk::RadioButton::Group</classname>. Then we "
"made three radio buttons, using a constructor to make each of them part of "
"<literal>group</literal>."
msgstr ""
"我们通过声明一个类型为 <classname>Gtk::RadioButton::Group</classname> 的名为 "
"<literal>group</literal> 的变量。然后我们创建三个单选按钮，用构造函数把它们放"
"置到组 <literal>group</literal> 中。"

#: C/gtkmm-tutorial-in.xml:901(title) C/gtkmm-tutorial-in.xml:1378(title)
#: C/gtkmm-tutorial-in.xml:5011(title)
msgid "Methods"
msgstr "方法"

#: C/gtkmm-tutorial-in.xml:902(para)
msgid ""
"<classname>RadioButtons</classname> 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 ""
"当 <classname>RadioButtons</classname> 创建后默认是未选中的，也就是说当你第一"
"次创建一组单选按钮的时候，它们都会是未选中的。所以别忘了使用 "
"<methodname>set_active()</methodname> 来选中一个："

#: C/gtkmm-tutorial-in.xml:913(para)
msgid ""
"The following example demonstrates the use of <classname>RadioButton</"
"classname>s:"
msgstr "接下来的例子中演示了 <classname>RadioButton</classname> 的用法："

#: C/gtkmm-tutorial-in.xml:935(title) C/gtkmm-tutorial-in.xml:1084(title)
msgid "Range Widgets"
msgstr "Range 组件"

#: C/gtkmm-tutorial-in.xml:937(para)
msgid ""
"<classname>Gtk::Scale</classname> and <classname>Gtk::Scrollbar</classname> "
"both inherit from <classname>Gtk::Range</classname> and share much "
"functionality. They 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 behaviour."
msgstr ""
"<classname>Gtk::Scale</classname> 和 <classname>Gtk::Scrollbar</classname> 都"
"是继承自 <classname>Gtk::Range</classname>，并且共享了很多功能。他们都有一"
"个“滑轨(trough)”和“滑块(slider)”(在其它 GUI 环境中可能被称为“指轮"
"(thumbwheel)”)。在滑轨内可以用鼠标拖动滑块，而在滑轨上点击的话则会让滑块向点"
"击的位置移动，可能是移动到终点，也可能是移动一段距离，这取决于你用的是鼠标的"
"哪个按键。这和滚动条的行为很类似。"

#: C/gtkmm-tutorial-in.xml:948(para)
msgid ""
"As will be explained in the <link linkend=\"chapter-adjustment\">Adjustment</"
"link> section, all Range widgets are associated with a "
"<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 <classname>Range</"
"classname> 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 ""
"就象将在后面的<link linkend=\"chapter-adjustment\">Adjustment</link> 小节要谈"
"到的那样，所有的 Range 组件都有一个关联的 <classname>Adjustment</classname> "
"对象。如果你想修改组件的最小值、最大值以及当前值，你需要调用该组件关联的 "
"<classname>Adjustment</classname> 对象的方法，该对象可以通过调用 "
"<methodname>get_adjustment()</methodname> 方法来得到。<classname>Range</"
"classname> 组件默认构造函数会自动的创建一个 <classname>Adjustment</"
"classname>，当然，你也可以指定一个现有的 <classname>Adjustment</classname>，"
"而且还可以和其它组件共享。请参看 <link linkend=\"chapter-adjustment"
"\">Adjustments</link> 部分以得到更详细的信息。"

#: C/gtkmm-tutorial-in.xml:965(title)
msgid "Scrollbar Widgets"
msgstr "滚动条组件 (Scrollbar)"

#: C/gtkmm-tutorial-in.xml:967(para)
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 ""
"这些是标准的滚动条。它们应该只被用于滚动其它组件，比如 <classname>Gtk::"
"Entry</classname> 或 <classname>Gtk::Viewport</classname>，当然，通常使用 "
"<classname>Gtk::ScrolledWindow</classname> 会更容易一些。"

#: C/gtkmm-tutorial-in.xml:974(para)
msgid ""
"There are horizontal and vertical scrollbar classes - <classname>Gtk::"
"HScrollbar</classname> and <classname>Gtk::VScrollbar</classname>."
msgstr ""
"分别有水平的和垂直的滚动条类：<classname>Gtk::HScrollbar</classname> 和 "
"<classname>Gtk::VScrollbar</classname>。"

#: C/gtkmm-tutorial-in.xml:985(title)
msgid "Scale Widgets"
msgstr "比例组件 (Scale)"

#: C/gtkmm-tutorial-in.xml:987(para)
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 ""
"<classname>Gtk::Scale</classname> 组件 (或者说“滑块”) 可以让用户在指定范围内"
"直观地调节它的值。例如，你可以用它来调节一副预览图片的放大率、或者控制颜色的"
"亮度，或者指定多少分钟后执行屏幕保护。"

#: C/gtkmm-tutorial-in.xml:996(para)
msgid ""
"As with <classname>Scrollbar</classname>s, there are separate widget types "
"for horizontal and vertical widgets - <classname>Gtk::HScale</classname> and "
"<classname>Gtk::VScale</classname>. The default constructors create 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 behaviour."
msgstr ""
"像 <classname>Scrollbar</classname> 一样，也分别有水平和垂直两种组件："
"<classname>Gtk::HScale</classname> 和 <classname>Gtk::VScale</classname>。默"
"认构造函数会创建一个 <classname>Adjustment</classname>，并且所有值都设为 "
"<literal>0.0</literal>。当然，这显然没有意义，所以你需要设置一些 "
"<classname>Adjustment</classname> 的细节来让它获得有意义的行为。"

#: C/gtkmm-tutorial-in.xml:1006(title)
msgid "Useful methods"
msgstr "一些有用的方法"

#: C/gtkmm-tutorial-in.xml:1008(para)
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 ""
"<classname>Scale</classname> 可以在滑轨旁显示它们的当前值。默认情况下是显示这"
"个数值的，但是你可以通过调用 <methodname>set_draw_value()</methodname> 方法来"
"设置是否显示该值。"

#: C/gtkmm-tutorial-in.xml:1014(para)
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 ""
"默认情况下，Scale 组件会显示 <classname>Gtk::Adjustment</classname> 的 "
"<literal>value</literal> 的数值，并且会被四舍五入到一位小数。你可以通过 "
"<methodname>set_digits()</methodname> 方法来改变显示的小数位数。"

#: C/gtkmm-tutorial-in.xml:1021(para)
msgid ""
"Also, the value can be drawn in different positions relative to the trough, "
"specified by the <methodname>set_value_pos()</methodname> method."
msgstr ""
"另外，通过使用 <methodname>set_value_pos()</methodname>，可以使值显示在相对于"
"滑块不同的位置。"

#: C/gtkmm-tutorial-in.xml:1032(title)
msgid "Update Policies"
msgstr "更新策略"

#: C/gtkmm-tutorial-in.xml:1044(para)
msgid ""
"<literal>Gtk::UPDATE_CONTINUOUS</literal> - This is the default. The "
"<literal>value_changed</literal> signal is emitted continuously, i.e. "
"whenever the slider is moved by even the tiniest amount."
msgstr ""
"<literal>Gtk::UPDATE_CONTINUOUS</literal> - 这是默认的更新规则。会连续不断的"
"发出 <literal>value_changed</literal> 信号，即使滑块只是被移动了一点点，也会"
"发出该信号。"

#: C/gtkmm-tutorial-in.xml:1052(para)
msgid ""
"<literal>Gtk::UPDATE_DISCONTINUOUS</literal> - The <literal>value_changed</"
"literal> signal is only emitted once the slider has stopped moving and the "
"user has released the mouse button."
msgstr ""
"<literal>Gtk::UPDATE_DISCONTINUOUS</literal> - 只有在滑块停止了移动并且用户释"
"放了鼠标的时候才会发出 <literal>value_changed</literal> 信号。"

#: C/gtkmm-tutorial-in.xml:1060(para)
msgid ""
"<literal>Gtk::UPDATE_DELAYED</literal> - The <literal>value_changed</"
"literal> signal is emitted when the user releases the mouse button, or if "
"the slider stops moving for a short period of time."
msgstr ""
"<literal>Gtk::UPDATE_DELAYED</literal> - 只有当用户释放鼠标，或者滑块停止移动"
"一小段时间后，才发出 <literal>value_changed</literal> 信号。"

#: C/gtkmm-tutorial-in.xml:1034(para)
msgid ""
"The <emphasis>update policy</emphasis> of a <classname>Range</classname> "
"widget defines at what points during user interaction it will change the "
"<literal>value</literal> field of its <classname>Gtk::Adjustment</classname> "
"and emit the <literal>value_changed</literal> signal. The update policies, "
"set with the <methodname>set_update_policy()</methodname> method, are: "
"<placeholder-1/>"
msgstr ""
"<classname>Range</classname> 组件的 <emphasis>更新策略</emphasis> 定义了在用"
"户操作期间的什么时候更新 <classname>Gtk::Adjustment</classname> 的值 "
"<literal>value</literal>，并且何时发出 <literal>value_changed</literal> 信"
"号。可以使用 <methodname>set_update_policy()</methodname> 方法来设置更新策"
"略。这些策略包括：<placeholder-1/>"

#: C/gtkmm-tutorial-in.xml:1075(para)
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 ""
"这个示例显示了一个窗口，其中有三个关联到同一个 Adjustment 对象的 Range 组件，"
"还有几个控制组件用来调整前文讨论过的一些参数，这样你可以很清楚地看到那些参数"
"是如何影响这些组件的行为方式的。"

#: C/gtkmm-tutorial-in.xml:1097(title)
msgid "Miscellaneous Widgets"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1100(title) C/gtkmm-tutorial-in.xml:1133(title)
msgid "Label"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1102(para)
msgid ""
"Labels are the main method of placing non-editable text in windows, for "
"instance to place a title next to a <classname>Entry</classname> widget. You "
"can specify the text in the constructor, or with the <methodname>set_text()</"
"methodname> method."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1109(para)
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 ""

#: C/gtkmm-tutorial-in.xml:1113(para)
msgid ""
"The label text can be justified using the <methodname>set_justify()</"
"methodname> method. The widget is also capable of word-wrapping - this can "
"be activated with <methodname>set_line_wrap()</methodname>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1119(para)
msgid "TODO: gtkmm2: markup."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1126(para)
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.)"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1146(title) C/gtkmm-tutorial-in.xml:1188(title)
msgid "Entry"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1149(title)
msgid "Simple Use"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1151(para)
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 ""

#: C/gtkmm-tutorial-in.xml:1156(para)
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 ""

#: C/gtkmm-tutorial-in.xml:1162(para)
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 ""

#: C/gtkmm-tutorial-in.xml:1168(para)
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> and <literal>changed</literal>, for just this "
"purpose. <literal>activate</literal> is emitted when the user presses the "
"enter 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."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1180(title)
msgid "Simple Entry Example"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1181(para)
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 ""

#: C/gtkmm-tutorial-in.xml:1201(title) C/gtkmm-tutorial-in.xml:1235(title)
msgid "Entry Completion"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1202(para)
msgid ""
"A <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 ""

#: C/gtkmm-tutorial-in.xml:1207(para)
msgid ""
"To enable this functionality, you must create a <classname>EntryCompletion</"
"classname> object, and provide it to the <classname>Entry</classname> widget "
"via the <methodname>set_completion()</methodname> method."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1212(para)
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 ""

#: C/gtkmm-tutorial-in.xml:1218(para)
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>. That callback function. This is "
"also useful if you wish to match on a part of the string other than the "
"start."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1226(title)
msgid "Entry Completion Example"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1227(para)
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 ""

#: C/gtkmm-tutorial-in.xml:1247(title)
msgid "Entry Icons"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1248(para)
msgid ""
"An <classname>Entry</classname> widget can show an icon at the start or end "
"of the text area. The icon can be specifed by methods such as "
"<methodname>set_icon_from_pixbuf()</methodname> or "
"<methodname>set_icon_from_stock()</methodname>. An application can respond "
"to the user pressing the icon by handling the <methodname>signal_icon_press</"
"methodname> signal."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1255(title)
msgid "Entry Icon Example"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1256(para)
msgid ""
"This example shows a <classname>Gtk::Entry</classname> widget with a stock "
"search icon, and prints text to the terminal when the icon is pressed."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1262(title)
msgid "Entry with Icon"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1274(title)
msgid "Entry Progress"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1275(para)
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 ""

#: C/gtkmm-tutorial-in.xml:1280(title)
msgid "Entry Progress Example"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1281(para)
msgid ""
"This example shows a <classname>Gtk::Entry</classname> widget with a "
"progress bar."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1287(title)
msgid "Entry with Progress Bar"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1301(title) C/gtkmm-tutorial-in.xml:1435(title)
msgid "SpinButton"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1303(para)
msgid ""
"A <classname>SpinButton</classname> allows the user to select a value from a "
"range of numeric values. It has an Entry widget with up and down arrow "
"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 ""

#: C/gtkmm-tutorial-in.xml:1311(para)
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 one of the arrows can optionally cause the "
"value to change more quickly the longer the arrow is held down."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1326(para)
msgid "<literal>value</literal>: value for the Spin Button"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1332(para)
msgid "<literal>lower</literal>: lower range value"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1338(para)
msgid "<literal>upper</literal>: upper range value"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1343(para)
msgid ""
"<literal>step_increment</literal>: value to increment/decrement when "
"pressing mouse button 1 on a button"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1350(para)
msgid ""
"<literal>page_increment</literal>: value to increment/decrement when "
"pressing mouse button 2 on a button"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1357(para)
msgid "<literal>page_size</literal>: unused"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1318(para)
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: "
"<placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1365(para)
msgid ""
"Additionally, mouse button 3 can be used to jump directly to the "
"<literal>upper</literal> or <literal>lower</literal> values."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1370(para)
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 ""

#: C/gtkmm-tutorial-in.xml:1380(para)
msgid ""
"The number of decimal places can be altered using the <methodname>set_digits"
"()</methodname> method."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1385(para)
msgid ""
"You can set the spinbutton's value using the <methodname>set_value()</"
"methodname> method, and retrieve it with <methodname>get_value()</"
"methodname>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1390(para)
msgid ""
"The <methodname>spin()</methodname> method 'spins' the "
"<classname>SpinButton</classname>, as if one of its arrows had been clicked. "
"You need to specify a <classname>Gtk::SpinType</classname> to specify the "
"direction or new position."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1397(para)
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 ""

#: C/gtkmm-tutorial-in.xml:1402(para)
msgid ""
"To make the <classname>SpinButton</classname> 'wrap' between its upper and "
"lower bounds, use the <methodname>set_wrap()</methodname> method."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1407(para)
msgid ""
"To force it to snap to the nearest <literal>step_increment</literal>, use "
"<methodname>set_snap_to_ticks()</methodname>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1412(para)
msgid ""
"You can modify the update policy using the <methodname>set_update_policy()</"
"methodname> method, specifying either <literal>Gtk::UPDATE_ALWAYS</literal> "
"or <literal>Gtk::UPDATE_IF_VALID</literal>. <literal>Gtk::UPDATE_ALWAYS</"
"literal> causes the <classname>SpinButton</classname> to ignore errors "
"encountered while converting the text in the entry box to a numeric value. "
"This setting also therefore allows the <classname>SpinButton</classname> to "
"accept non-numeric values. You can force an immediate update using the "
"<methodname>update()</methodname> method."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1430(para)
msgid "Here's an example of a <classname>SpinButton</classname> in action:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1448(title) C/gtkmm-tutorial-in.xml:1501(title)
msgid "ProgressBar"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1450(para)
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 ""

#: C/gtkmm-tutorial-in.xml:1456(para)
msgid ""
"To change the value shown, use the <methodname>set_fraction()</methodname> "
"method, passing a double between 0 and 1 to provide the new percentage."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1461(para)
msgid ""
"where <literal>percentage</literal> is a number, from 0 to 1, indicating "
"what fraction of the bar should be filled."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1466(para)
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 ""

#: C/gtkmm-tutorial-in.xml:1475(title)
msgid "Activity Mode"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1476(para)
msgid ""
"Besides indicating the amount of progress that has occured, 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 ""

#: C/gtkmm-tutorial-in.xml:1486(para)
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 ""

#: C/gtkmm-tutorial-in.xml:1492(para)
msgid ""
"When in continuous mode, the progress bar can also display a configurable "
"text string within its trough, using the <methodname>set_text()</methodname> "
"method."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1515(title) C/gtkmm-tutorial-in.xml:1525(title)
msgid "InfoBar"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1517(para)
msgid ""
"An <classname>InfoBar</classname> may show small items of information or to "
"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 ""

#: C/gtkmm-tutorial-in.xml:1538(title)
msgid "Tooltips"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1540(para)
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::ToolItem</classname>s are not <classname>Widget</"
"classname>s, but have the same method for convenience. <classname>Gtk::"
"Tooltip</classname> is used for more advanced tooltip usage, such as showing "
"an image as well as text."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1550(ulink)
msgid "Widget Reference"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1551(ulink)
msgid "Tooltip Reference"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1558(title)
msgid "Container Widgets"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1560(para)
msgid ""
"All container widgets derive from <classname>Gtk::Container</classname>, not "
"always directly. Some container widgets, such as <classname>Gtk::Table</"
"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 ""

#: C/gtkmm-tutorial-in.xml:1569(title)
msgid "Single-item Containers"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1571(para)
msgid ""
"The single-item container widgets derive from <classname>Gtk::Bin</"
"classname>, which provides the <methodname>add()</methodname> and "
"<methodname>remove()</methodname> methods for the child widget. Note that "
"<classname>Gtk::Button</classname> and <classname>Gtk::Window</classname> "
"are technically single-item containers, but we have discussed them already "
"elsewhere."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1579(para)
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 ""

#: C/gtkmm-tutorial-in.xml:1586(title) C/gtkmm-tutorial-in.xml:1600(title)
msgid "Frame"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1588(para)
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>RadioButton</"
"classname>s or <classname>CheckButton</classname>s in a <classname>Frame</"
"classname>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1614(title) C/gtkmm-tutorial-in.xml:1641(title)
msgid "Paned"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1616(para)
msgid ""
"Panes divide a widget into two halves, separated by a moveable divider. "
"There are two such widgets: <classname>Gtk::HPaned</classname> adds a "
"horizontal divider, and <classname>Gtk::VPaned</classname> adds a vertical "
"one. Other than the names and the orientations, there's no difference "
"between the two."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1623(para)
msgid ""
"Unlike the other widgets in this chapter, pane widgets contain not one but "
"two child widgets, one in each pane. Therefore, you should use "
"<methodname>add1()</methodname> and <methodname>add2()</methodname> instead "
"of the <methodname>add()</methodname> method."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1630(para)
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 ""

#: C/gtkmm-tutorial-in.xml:1654(title) C/gtkmm-tutorial-in.xml:1686(title)
msgid "ScrolledWindow"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1656(para)
msgid ""
"<classname>ScrolledWindow</classname> widgets create a scrollable area. You "
"can insert any type of widget into a <classname>ScrolledWindow</classname> "
"window, 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 ""

#: C/gtkmm-tutorial-in.xml:1665(para)
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 one of <literal>Gtk::POLICY_AUTOMATIC</literal> or "
"<literal>Gtk::POLICY_ALWAYS</literal>. <literal>Gtk::POLICY_AUTOMATIC</"
"literal> will cause the scrolled window to display the scrollbar only if the "
"contained widget is larger than the visible area. <literal>Gtk::"
"POLICY_ALWAYS</literal> will cause the scrollbar to be displayed always."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1681(para)
msgid ""
"Here is a simple example that packs 100 toggle buttons into a "
"ScrolledWindow. Try resizing the window to see the scrollbars react."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1699(title) C/gtkmm-tutorial-in.xml:1721(title)
msgid "AspectFrame"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1701(para)
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 ""

#: C/gtkmm-tutorial-in.xml:1714(para)
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 ""

#: C/gtkmm-tutorial-in.xml:1734(title) C/gtkmm-tutorial-in.xml:1760(title)
msgid "Alignment"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1736(para)
msgid ""
"The <classname>Alignment</classname> widget allows you to place a widget at "
"a position and size relative to the size of the <classname>Alignment</"
"classname> widget itself. For instance, it might be used to center a widget."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1742(para)
msgid ""
"You need to specify the <classname>Alignment</classname>'s characteristics "
"to the constructor, or to the <methodname>set()</methodname> method. In "
"particular, you won't notice much effect unless you specify a number other "
"than 1.0 for the <literal>xscale</literal> and <literal>yscale</literal> "
"parameters, because 1.0 simply means that the child widget will expand to "
"fill all available space."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1754(para)
msgid ""
"This example right-aligns a button in a window by using an "
"<classname>Alignment</classname> widget."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1768(para)
msgid ""
"See the <link linkend=\"sec-progressbar\">ProgressBar</link> section for "
"another example that uses an <classname>Alignment</classname>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1780(title)
msgid "Multiple-item widgets"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1782(para)
msgid ""
"Multiple-item widgets inherit from <classname>Gtk::Container</classname>; "
"just as with <classname>Gtk::Bin</classname>, you use the <methodname>add()</"
"methodname> and <methodname>remove()</methodname> methods to add and remove "
"contained widgets. Unlike <methodname>Gtk::Bin::remove()</methodname>, "
"however, the <methodname>remove()</methodname> method for <classname>Gtk::"
"Container</classname> takes an argument, specifiying which widget to remove."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1792(title)
msgid "Packing"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1793(para)
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 ""

#: C/gtkmm-tutorial-in.xml:1798(para)
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 ""

#: C/gtkmm-tutorial-in.xml:1805(para)
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 ""

#: C/gtkmm-tutorial-in.xml:1809(para)
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 ""

#: C/gtkmm-tutorial-in.xml:1813(para)
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 ""

#: C/gtkmm-tutorial-in.xml:1819(para)
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 tables. "
"<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 padding distance 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 ""

#: C/gtkmm-tutorial-in.xml:1828(para)
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 flavours "
"of containers: single-child containers, which are all descendants of "
"<classname>Gtk::Bin</classname>, and multiple-child containers, which are "
"descendants of <classname>Gtk::Container</classname>. Most widgets in "
"<application>gtkmm</application> are descendants of <classname>Gtk::Bin</"
"classname>, including <classname>Gtk::Window</classname>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1839(para)
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:VBox</"
"classname>, <classname>Gtk::HBox</classname>, and <classname>Gtk::Table</"
"classname>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1851(para)
msgid ""
"<classname>Gtk::VBox</classname> and <classname>Gtk::HBox</classname> "
"arrange their child widgets vertically and horizontally, respectively. Use "
"<methodname>pack_start()</methodname> and <methodname>pack_end()</"
"methodname> to insert child widgets."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1860(para)
msgid ""
"<classname>Gtk::Table</classname> arranges its widgets in a grid. Use "
"<methodname>attach()</methodname> to insert widgets."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1868(para)
msgid "There are several other containers, which we will also discuss."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1872(para)
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 ""

#: C/gtkmm-tutorial-in.xml:1882(title)
msgid "An improved Hello World"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1884(para)
msgid ""
"Let's take a look at a slightly improved <literal>helloworld</literal>, "
"showing what we've learnt."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1889(title)
msgid "Hello World 2"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1897(para)
msgid ""
"After building and running this program, try resizing the window to see the "
"behaviour. Also, try playing with the options to <methodname>pack_start()</"
"methodname> while reading the <link linkend=\"sec-boxes\">Boxes</link> "
"section."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1907(title)
msgid "STL-style APIs"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1909(para)
msgid ""
"TODO: Use 'Standard Library' instead of STL. If you're an accomplished C++ "
"programmer, you'll be happy to hear that most of the <application>gtkmm</"
"application><classname>Container</classname> widgets provide STL-style APIs, "
"available via accessor methods, such as <methodname>Gtk::Box::children()</"
"methodname> or <methodname>Gtk::Notebook::pages()</methodname>. They don't "
"use actual STL containers (there are good reasons for this), but they look, "
"feel, and act much like STL container classes."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1920(para)
msgid ""
"These APIs are so similar to STL container APIs that, rather than explaining "
"them in detail, we can refer you to the STL documentation for most of their "
"methods. This is all part of <application>gtkmm</application>'s policy of "
"reusing existing standards."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1924(para)
msgid ""
"However, STL-style APIs can require awkward or lengthy code in some "
"situations, so some people prefer not to use them, while other people use "
"them religiously. Therefore, you are not forced to use them - most container "
"widgets have a simpler non-STL-style API, with methods such as "
"<methodname>append()</methodname> and <methodname>prepend()</methodname>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:1938(para)
msgid ""
"<methodname>begin()</methodname> returns a <literal>begin</literal> iterator"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1944(para)
msgid ""
"<methodname>end()</methodname> returns an <literal>end</literal> iterator"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1950(para)
msgid ""
"<methodname>rbegin()</methodname> returns a reverse <literal>begin</literal> "
"iterator"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1956(para)
msgid ""
"<methodname>rend()</methodname> returns a reverse <literal>end</literal> "
"iterator"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1963(methodname)
msgid "size()"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1969(methodname)
msgid "max_size()"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1975(methodname)
msgid "empty()"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1981(methodname)
msgid "insert()"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1987(methodname)
msgid "push_front()"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1993(methodname)
msgid "push_back()"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1999(methodname)
msgid "pop_front()"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2005(methodname)
msgid "pop_back()"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2011(methodname)
msgid "clear()"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2017(methodname)
msgid "erase()"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2023(methodname)
msgid "remove()"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2029(methodname)
msgid "find()"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2035(methodname)
msgid "front()"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2041(methodname)
msgid "back()"
msgstr ""

#: C/gtkmm-tutorial-in.xml:1932(para)
msgid ""
"At a minimum, <application>gtkmm</application> container lists support "
"iterators and the usual insertion, deletion, and addition methods. You can "
"always expect the following methods to be available for <application>gtkmm</"
"application> STL-style APIs: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2049(para)
msgid ""
"Also, the <literal>[]</literal> operator is overloaded, but that is usually "
"order N, so if performance is a consideration, or the list has a large "
"number of elements, think carefully before using it."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2055(para)
msgid ""
"The element objects and list objects are defined, for each container, in a "
"namespace whose name ends in <literal>_Helpers</literal>. For example, the "
"helper namespace for the notebook widget is <classname>Gtk::"
"Notebook_Helpers</classname>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2063(title)
msgid "Adding items"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2064(para)
msgid ""
"There is a major difference between <application>gtkmm</application> STL-"
"style APIs and real STL containers. Normally, when you use a <classname>std::"
"vector</classname>, for example, you expect that whatever you put in, you'll "
"get out, unmodified. You wouldn't make a <classname>std::vector&lt;int&gt;</"
"classname> and expect to get <literal>double</literal>s out of it. But, "
"<application>gtkmm</application> STL-style APIs don't always work like that "
"- you will often put one kind of object in, and later get a different kind "
"out. Why this odd behaviour?"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2074(para)
msgid ""
"Consider a menu widget, which must maintain a hierarchical list of menus and "
"menu items. Menus can only contain certain objects, such as menu items, "
"separators, and submenus. To ensure consistency, a \"filter\" is needed to "
"keep out illegal objects. Also, since only a few types of objects are "
"allowed, convenience methods can be provided to make it easy to build up "
"menus."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2083(para)
msgid ""
"<application>gtkmm</application> takes care of both requirements using "
"special <emphasis>helper elements</emphasis>. Helper elements are temporary "
"- they're typically constructed and passed to an insertion method in the "
"same call. The list insertion method uses the information in the helper "
"element to construct the real object, which is then inserted into the "
"container."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2091(para)
msgid ""
"As an example, let's look at the <classname>Notebook</classname> widget "
"(explained in the section on <link linkend=\"sec-notebook\">Notebooks</"
"link>). <classname>Notebook</classname> widgets contain a series of \"pages"
"\"."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2097(para)
msgid ""
"Each page in a notebook requires, at minimum, the following information:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2105(para)
msgid "A child widget (zero or one), to be placed in the page"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2111(para)
msgid "A label for the page's tab"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2118(para)
msgid ""
"(The <application>gtkmm</application> notebook widget keeps other data for "
"each page as well.)"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2122(para)
msgid ""
"To insert a new page in a notebook, we can use one of the notebook helper "
"classes, like this:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2126(programlisting)
#, no-wrap
msgid ""
"notebook-&gt;pages().push_back(\n"
"          Gtk::Notebook_Helpers::TabElem(*frame, bufferl));"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2129(para)
msgid ""
"Let's see what's going on here. Assume we have a pointer to a "
"<classname>Notebook</classname> widget called <literal>notebook</literal>; "
"we go from that to a member method called <methodname>pages()</methodname>, "
"which returns an STL-like list object. On this we call the method "
"<methodname>push_back()</methodname> (this should be familiar to those who "
"know STL)."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2138(para)
msgid ""
"The object that the <methodname>pages()</methodname> method returns is "
"called a <classname>Notebook_Helpers::PageList</classname>. It's one of the "
"STL-like containers that we keep referring to. Let's take a look at this "
"class (this has been heavily edited for clarity; see <filename>&lt;gtkmm/"
"notebook.h&gt;</filename> for the actual definition):"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2146(programlisting)
#, no-wrap
msgid ""
"namespace Notebook_Helpers\n"
"{\n"
"    class PageList\n"
"    {\n"
"    public:\n"
"             . . .\n"
"        void push_back(const Element&amp; e);\n"
"             . . .\n"
"        Page* operator[](size_type l);\n"
"    };\n"
"};"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2163(para)
msgid ""
"The <methodname>push_back()</methodname> method takes as argument an "
"<classname>Element</classname> object (helper);"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2170(para)
msgid ""
"The overloaded <literal>[]</literal> operator returns a pointer to a "
"<classname>Page</classname>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2158(para)
msgid "There are two important things to notice here: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2180(para)
msgid "This scheme has some important advantages:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2187(para)
msgid ""
"We can provide as many different Helper objects as desired, making it simple "
"to construct complex widgets like Menus."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2195(para)
msgid ""
"Construction of the actual objects can be delayed until an appropriate time. "
"Sometimes we don't have enough information until later with GTK+."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2202(para)
msgid ""
"The definitions of the objects contained in the list can change; their "
"interfaces need not concern the programmer. For example, even if the "
"<classname>Page</classname> object changes drastically, the programmer need "
"not be concerned; the <classname>Element</classname>s need not change, and "
"will continue to work as expected."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2212(para)
msgid ""
"New <classname>Element</classname> objects can be added at any time to "
"support new features, without breaking existing code."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2220(para)
msgid ""
"All multi-item containers have an <classname>Element</classname> object in "
"their helper namespaces, and usually there are additional classes available "
"(like <classname>TabElem</classname> and <classname>MenuElem</classname>) "
"which derive from <classname>Element</classname>. <classname>Element</"
"classname> classes vary from container to container, since each contains "
"different kinds of objects."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2229(para)
msgid ""
"It's very important to remember that <classname>Element</classname>s are not "
"\"real\" objects. They exist only temporarily, and they are never stored in "
"the container. They are used <emphasis>only</emphasis> as temporary "
"\"parameter-holders\". Therefore, the following segment of code is illegal:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2235(programlisting)
#, no-wrap
msgid ""
"MenuElem* m = new MenuElem(\"hello\");\n"
"m-&gt;right_justify();\n"
"items().push_back(*m);"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2239(para)
msgid ""
"We constructed a new <classname>MenuElem</classname> helper object, and then "
"tried to invoke <methodname>right_justify()</methodname> on it before adding "
"it to the menu. The trouble is that there is no <methodname>right_justify()</"
"methodname> method in the <classname>MenuElem</classname> class. The correct "
"way to accomplish this would be:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2247(programlisting)
#, no-wrap
msgid ""
"items().push_back(MenuElem(\"hello\"));\n"
"items().back()-&gt;right_justify();"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2250(para)
msgid ""
"Here, we've constructed a <classname>MenuElem</classname> and inserted it "
"into the menu by passing it to <methodname>push_back()</methodname>, causing "
"the real menu item to be created. We've then called <methodname>right_justify"
"()</methodname> on the object retrieved from the list. This is correct - the "
"object retrieved from the list is not a <classname>MenuElem</classname>, but "
"a real <classname>MenuItem</classname>, and therefore supports the "
"<methodname>right_justify()</methodname> method as expected."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2266(title)
msgid "Boxes"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2268(para)
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 or "
"right to left depending on whether <methodname>pack_start()</methodname> or "
"<methodname>pack_end()</methodname> is used. In a vertical box, widgets are "
"packed from top to bottom or vice versa. You may use any combination of "
"boxes inside or beside other boxes to create the desired effect."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2279(title) C/gtkmm-tutorial-in.xml:2478(title)
msgid "Adding widgets"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2280(title)
msgid "Per-child packing options"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2281(para)
msgid ""
"The <methodname>pack_start()</methodname> and <methodname>pack_end()</"
"methodname> methods place widgets inside these containers. The "
"<methodname>pack_start()</methodname> method will start at the top and work "
"its way down in a <classname>VBox</classname>, or pack left to right in an "
"<classname>HBox</classname>. <methodname>pack_end()</methodname> will do the "
"opposite, packing from bottom to top in a <classname>VBox</classname>, or "
"right to left in an <classname>HBox</classname>. Using these methods allows "
"us to right justify or left justify our widgets. We will use "
"<methodname>pack_start()</methodname> in most of our examples."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2294(para)
msgid ""
"There are several options governing how widgets are to be packed, and this "
"can be confusing at first. If you have difficulties then it is sometimes a "
"good idea to play with the <application>glade</application> GUI designer to "
"see what is possible. You might even decide to use the <application>Gtk::"
"Builder</application> API to load your GUI at runtime."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2302(para)
msgid "There are basically five different styles, as shown in this picture:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2308(title)
msgid "Box Packing 1"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2314(para)
msgid ""
"Each line contains one horizontal box (<classname>HBox</classname>) with "
"several buttons. Each of the buttons on a line is packed into the "
"<classname>HBox</classname> with the same arguments to the "
"<methodname>pack_start()</methodname> method)."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2321(para)
msgid ""
"This is the declaration of the <methodname>pack_start()</methodname> method:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2324(programlisting)
#, no-wrap
msgid ""
"void pack_start(Gtk::Widget&amp; child,\n"
"                PackOptions options = PACK_EXPAND_WIDGET,\n"
"                guint padding = 0);"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2328(para)
msgid ""
"The first argument is the widget you're packing. In our example these are "
"all <classname>Button</classname>s."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2335(para)
msgid ""
"<literal>PACK_SHRINK</literal>: Space is contracted to the child widget "
"size. The widget will take up just-enough space and never expand."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2336(para)
msgid ""
"<literal>PACK_EXPAND_PADDING</literal>: Extra space is filled with padding. "
"The widgets will be spaced out evenly, but their sizes won't change - there "
"will be empty space between the widgets instead."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2337(para)
msgid ""
"<literal>PACK_EXPAND_WIDGET</literal>: Extra space is taken up by increasing "
"the child widget size, without changing the amount of space between widgets."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2332(para)
msgid ""
"The <parameter>options</parameter> argument can take one of these three "
"options: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2341(para)
msgid ""
"The <parameter>padding</parameter> argument specifies the width of an extra "
"border area to leave around the packed widget."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2346(para)
msgid ""
"Instead of the <methodname>pack_start()</methodname> and <methodname>pack_end"
"()</methodname> methods, you might prefer to use the STL-style API, "
"available via the <literal>children</literal> method. See the <link linkend="
"\"sec-stl-style\">STL-style APIs</link> section for more details."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2357(title)
msgid "Per-container packing options"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2360(programlisting)
#, no-wrap
msgid "Gtk::Box(bool homogeneous = false, int spacing = 0);"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2358(para)
msgid ""
"Here's the constructor for the box widgets: <placeholder-1/> Passing "
"<literal>true</literal> for <parameter>homogeneous</parameter> 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 ""

#: C/gtkmm-tutorial-in.xml:2367(para)
msgid ""
"What's the difference between spacing (set when the box is created) and "
"padding (set when elements are packed)? Spacing is added between objects, "
"and padding is added on either side of a widget. The following figure should "
"make it clearer:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2375(title)
msgid "Box Packing 2"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2386(para)
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 ""

#: C/gtkmm-tutorial-in.xml:2395(title)
msgid "ButtonBoxes"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2397(para)
msgid ""
"Button boxes are a convenient way to quickly arrange a group of buttons. "
"They come in both horizontal (<classname>Gtk::HButtonBox</classname>) and "
"vertical (<classname>Gtk::VButtonBox</classname>) flavours. They are exactly "
"alike, except in name and orientation."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2404(para)
msgid ""
"<classname>ButtonBox</classname>es help to make applications appear "
"consistent because they use standard settings, such as inter-button spacing "
"and packing."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2409(para)
msgid ""
"Buttons are added to a <classname>ButtonBox</classname> with the "
"<methodname>add()</methodname> method."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2414(para)
msgid ""
"Button boxes support several layout styles. The style can be retrieved and "
"changed using <methodname>get_layout()</methodname> and "
"<methodname>set_layout()</methodname>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2426(title)
msgid "ButtonBox"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2439(title) C/gtkmm-tutorial-in.xml:2585(title)
msgid "Table"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2441(para)
msgid "Tables allows us to place widgets in a grid."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2445(title)
msgid "Constructor"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2446(para)
msgid "The grid's dimensions need to be specified in the constructor:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2449(programlisting)
#, no-wrap
msgid "Gtk::Table(int rows = 1, int columns = 1, bool homogeneous = false);"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2451(para)
msgid ""
"The first argument is the number of rows to make in the table, while the "
"second, obviously, is the number of columns. If <parameter>homogeneous</"
"parameter> is <literal>true</literal>, the table cells will all be the same "
"size (the size of the largest widget in the table)."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2458(para)
msgid ""
"The rows and columns are indexed starting at 0. If you specify "
"<parameter>rows</parameter> = 2 and <parameter>columns</parameter> = 2, the "
"layout would look something like this:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2464(programlisting)
#, no-wrap
msgid ""
"\n"
" 0          1          2\n"
"0+----------+----------+\n"
" |          |          |\n"
"1+----------+----------+\n"
" |          |          |\n"
"2+----------+----------+\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2473(para)
msgid "Note that the coordinate system starts in the upper left hand corner."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2479(para)
msgid "To place a widget into a box, use the following method:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2482(programlisting)
#, no-wrap
msgid ""
"void Gtk::Table::attach(Gtk::Widget&amp; child,\n"
"                        guint left_attach, guint right_attach,\n"
"                        guint top_attach, guint bottom_attach,\n"
"                        guint xoptions = Gtk::FILL | Gtk::EXPAND,\n"
"                        guint yoptions = Gtk::FILL | Gtk::EXPAND,\n"
"                        guint xpadding = 0, guint ypadding = 0);"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2488(para)
msgid "The first argument is the widget you wish to place in the table."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2492(para)
msgid ""
"The <parameter>left_attach</parameter> and <parameter>right_attach</"
"parameter> arguments specify where to place the widget, and how many boxes "
"to use. For example, if you want a button in the lower-right cell of a 2 x 2 "
"table, and want it to occupy that cell <emphasis>only</emphasis>, then "
"<parameter>left_attach</parameter> would be 1, <parameter>right_attach</"
"parameter> 2, <parameter>top_attach</parameter> 1, and "
"<parameter>bottom_attach</parameter> 2. If, on the other hand, you wanted a "
"widget to take up the entire top row of our 2 x 2 table, you'd set "
"<parameter>left_attach</parameter> = 0, <parameter>right_attach</parameter> "
"= 2, <parameter>top_attach</parameter> = 0, and <parameter>bottom_attach</"
"parameter> = 1."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2508(para)
msgid ""
"<parameter>xoptions</parameter> and <parameter>yoptions</parameter> are used "
"to specify packing options and may be bitwise ORed together to allow "
"multiple options. These options are:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2518(literal)
msgid "Gtk::FILL"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2520(para)
msgid ""
"If the table box is larger than the widget, and <literal>Gtk::FILL</literal> "
"is specified, the widget will expand to use all the room available."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2528(literal)
msgid "Gtk::SHRINK"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2530(para)
msgid ""
"If the table widget is allocated less space than it requested (because the "
"user resized the window), then the widgets will normally just disappear off "
"the bottom of the window. If <literal>Gtk::SHRINK</literal> is specified, "
"the widgets will shrink with the table."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2541(literal)
msgid "Gtk::EXPAND"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2543(para)
msgid ""
"This will cause the table to expand to use up anyremaining space in the "
"window."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2551(para)
msgid ""
"The padding arguments work just as they do for <methodname>pack_start()</"
"methodname>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2557(title)
msgid "Other methods"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2559(para)
msgid ""
"<methodname>set_row_spacing()</methodname> and <methodname>set_col_spacing()"
"</methodname> set the spacing between the rows at the specified row or "
"column. Note that for columns, the space goes to the right of the column, "
"and for rows, the space goes below the row."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2566(para)
msgid ""
"You can also set a consistent spacing for all rows and/or columns with "
"<methodname>set_row_spacings()</methodname> and <methodname>set_col_spacings"
"()</methodname>. Note that with these calls, the last row and last column do "
"not get any spacing."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2578(para)
msgid ""
"In the following example, we make a window with three buttons in a 2 x 2 "
"table. The first two buttons will be placed in the upper row. A third button "
"is placed in the lower row, spanning both columns."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2598(title) C/gtkmm-tutorial-in.xml:2635(title)
msgid "Notebook"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2600(para)
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 ""

#: C/gtkmm-tutorial-in.xml:2609(para)
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 ""

#: C/gtkmm-tutorial-in.xml:2616(para)
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 ""

#: C/gtkmm-tutorial-in.xml:2623(para)
msgid ""
"To programmatically change the selected page, use the "
"<methodname>set_current_page()</methodname> method."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2628(para)
msgid ""
"There is also an <link linkend=\"sec-notebook-stl-style\">STL-style API</"
"link> which you might find more obvious."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2646(title)
msgid "STL-style API"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2647(para)
msgid ""
"The <classname>Gtk::Notebook</classname> widget has an STL-style API, "
"available via the <methodname>pages()</methodname> method, which you might "
"prefer to use to add and access pages. See the <link linkend=\"sec-stl-style"
"\">STL-style APIs</link> section for generic information."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2653(ulink)
msgid "PageList Reference"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2655(para)
msgid ""
"To insert pages into a notebook, use the <classname>TabElem</classname> "
"helper class, like so:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2659(programlisting)
#, no-wrap
msgid ""
"m_Notebook.pages().push_back(\n"
"    Gtk::Notebook_Helpers::TabElem(m_ChildWidget, \"tab 1\") );"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2662(para)
msgid ""
"<ulink url=\"http://library.gnome.org/devel/gtkmm/unstable/"
"classGtk_1_1Notebook__Helpers_1_1TabElem.html\">TabElem Reference</ulink>. "
"TODO: Correct URL."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2664(para)
msgid ""
"To access an existing child widget, you can call <methodname>get_child()</"
"methodname> on one of the <classname>Page</classname> elements of the "
"<classname>PageList</classname>:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2669(programlisting)
#, no-wrap
msgid "Gtk::Widget* pWidget = m_Notebook.pages()[2].get_child();"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2676(title) C/gtkmm-tutorial-in.xml:2703(title)
msgid "Assistant"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2678(para)
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 ""

#: C/gtkmm-tutorial-in.xml:2682(para)
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 ""

#: C/gtkmm-tutorial-in.xml:2686(para)
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 ""

#: C/gtkmm-tutorial-in.xml:2690(para)
msgid ""
"To set the title of a page, use the <methodname>set_page_title()</"
"methodname> method. The header and side images of a page can be set with the "
"<methodname>set_page_header_image()</methodname> and "
"<methodname>set_page_side_image()</methodname> methods."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2694(para)
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 ""

#: C/gtkmm-tutorial-in.xml:2721(title)
msgid "The TreeView widget"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2722(para)
msgid ""
"The <classname>Gtk::TreeView</classname> widget can contain lists or trees "
"of data, in columns."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2728(title)
msgid "The Model"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2729(para)
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 ""

#: C/gtkmm-tutorial-in.xml:2739(para)
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 ""

#: C/gtkmm-tutorial-in.xml:2748(title)
msgid "ListStore, for rows"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2749(para)
msgid ""
"The <classname>ListStore</classname> contains simple rows of data, and each "
"row has no children."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2755(title) C/gtkmm-tutorial-in.xml:3300(title)
msgid "TreeView - ListStore"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2766(title)
msgid "TreeStore, for a hierarchy"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2767(para)
msgid ""
"The <classname>TreeStore</classname> contains rows of data, and each row may "
"have child rows."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2773(title) C/gtkmm-tutorial-in.xml:3319(title)
msgid "TreeView - TreeStore"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2784(title)
msgid "Model Columns"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2785(para)
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>TreeModelColumns</classname> 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 ""

#: C/gtkmm-tutorial-in.xml:2796(programlisting)
#, 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 ""

#: C/gtkmm-tutorial-in.xml:2809(para)
msgid ""
"You specify the <classname>ColumnRecord</classname> when creating the Model, "
"like so:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2813(programlisting)
#, no-wrap
msgid ""
"Glib::RefPtr&lt;Gtk::ListStore&gt; refListStore =\n"
"    Gtk::ListStore::create(m_Columns);"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2815(para)
msgid ""
"Note that the instance (such as m_Columns here) should usually not be "
"static, because it often needs to be instantiated after glibmm has been "
"instantiated."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2820(title)
msgid "Adding Rows"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2821(para)
msgid ""
"Add rows to the model with the <methodname>append()</methodname>, "
"<methodname>prepend()</methodname>, or <methodname>insert()</methodname> "
"methods."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2825(programlisting)
#, no-wrap
msgid "Gtk::TreeModel::iterator iter = m_refListStore-&gt;append();"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2826(para)
msgid "You can dereference the iterator to get the Row:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2828(programlisting)
#, no-wrap
msgid "Gtk::TreeModel::Row row = *iter;"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2829(title)
msgid "Adding child rows"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2830(para)
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 ""

#: C/gtkmm-tutorial-in.xml:2835(programlisting)
#, no-wrap
msgid ""
"Gtk::TreeModel::iterator iter_child =\n"
"    m_refListStore-&gt;append(row.children());"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2842(title)
msgid "Setting values"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2843(para)
msgid ""
"You can use the <methodname>operator[]</methodname> override to set the data "
"for a particular column in the row, specifying the "
"<classname>TreeModelColumn</classname> used to create the model."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2848(programlisting)
#, no-wrap
msgid "row[m_Columns.m_col_text] = \"sometext\";"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2852(title)
msgid "Getting values"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2853(para)
msgid ""
"You can use the <methodname>operator[]</methodname> override to get the data "
"in a particular column in a row, specifiying the <classname>TreeModelColumn</"
"classname> used to create the model."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2858(programlisting)
#, no-wrap
msgid ""
"Glib::ustring strText = row[m_Columns.m_col_text];\n"
"int number = row[m_Columns.m_col_number];"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2860(para)
msgid ""
"The compiler will complain if you use an inappropriate type. For instance, "
"this would generate a compiler error:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2864(programlisting)
#, no-wrap
msgid ""
"//compiler error - no conversion from ustring to int.\n"
"int number = row[m_Columns.m_col_text];"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2869(title)
msgid "\"Hidden\" Columns"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2870(para)
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 ""

#: C/gtkmm-tutorial-in.xml:2879(title) C/gtkmm-tutorial-in.xml:3679(title)
msgid "The View"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2880(para)
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 ""

#: C/gtkmm-tutorial-in.xml:2890(title)
msgid "Using a Model"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2891(para)
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 ""

#: C/gtkmm-tutorial-in.xml:2896(programlisting)
#, no-wrap
msgid "m_TreeView.set_model(m_refListStore);"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2900(title)
msgid "Adding View Columns"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2901(para)
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 ""

#: C/gtkmm-tutorial-in.xml:2906(programlisting)
#, no-wrap
msgid "m_TreeView.append_column(\"Messages\", m_Columns.m_col_text);"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2907(para)
msgid ""
"When using this simple <methodname>append_column()</methodname> override, "
"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 ""

#: C/gtkmm-tutorial-in.xml:2923(title)
msgid "More than one Model Column per View Column"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2924(para)
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 ""

#: C/gtkmm-tutorial-in.xml:2930(para)
msgid ""
"Then use <methodname>append_column()</methodname> to add the view Column to "
"the View. Notice that <methodname>Gtk::View::append_column()</methodname> is "
"overridden to accept either a prebuilt <classname>Gtk::View::Column</"
"classname> widget, or just the <classname>TreeModelColumn</classname> from "
"which it generates an appropriate <classname>Gtk::View::Column</classname> "
"widget."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2937(para)
msgid ""
"Here is some example code from <filename>demos/gtk-demo/example_stockbrowser."
"cc</filename>, which has a pixbuf icon and a text name in the same column:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2942(programlisting)
#, no-wrap
msgid ""
"Gtk::TreeView::Column* pColumn =\n"
"    Gtk::manage( new Gtk::TreeView::Column(\"Symbol\") );\n"
"\n"
"// m_columns.icon and m_columns.symbol are columns in the model.\n"
"// pColumn is the column in the TreeView:\n"
"pColumn-&gt;pack_start(m_columns.icon, false); //false = don't expand.\n"
"pColumn-&gt;pack_start(m_columns.symbol);\n"
"\n"
"m_TreeView.append_column(*pColumn);"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2954(title)
msgid "Specifying CellRenderer details"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2955(para)
msgid ""
"The default <classname>CellRenderers</classname> and their default behaviour "
"will normally suffice, but you might occasionally need finer control. For "
"instance, this example code from <filename>demos/gtk-demo/example_treestore."
"cc</filename>, manually constructs a <classname>Gtk::CellRenderer</"
"classname> widget and instructs it to render the data from various model "
"columns through various aspects of its appearance."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2963(programlisting)
#, no-wrap
msgid ""
"Gtk::CellRendererToggle* pRenderer =\n"
"    Gtk::manage( new Gtk::CellRendererToggle() );\n"
"int cols_count = m_TreeView.append_column(\"Alex\", *pRenderer);\n"
"Gtk::TreeViewColumn* pColumn = m_TreeView.get_column(cols_count-1);\n"
"if(pColumn)\n"
"{\n"
"  pColumn-&gt;add_attribute(pRenderer-&gt;property_active(),\n"
"      m_columns.alex);\n"
"  pColumn-&gt;add_attribute(pRenderer-&gt;property_visible(),\n"
"      m_columns.visible);\n"
"  pColumn-&gt;add_attribute(pRenderer-&gt;property_activatable(),\n"
"      m_columns.world);"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2976(para)
msgid ""
"You can also connect to <classname>CellRenderer</classname> signals to "
"detect user actions. For instance:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2980(programlisting)
#, no-wrap
msgid ""
"Gtk::CellRendererToggle* pRenderer =\n"
"    Gtk::manage( new Gtk::CellRendererToggle() );\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 ""

#: C/gtkmm-tutorial-in.xml:2989(title) C/gtkmm-tutorial-in.xml:3329(title)
msgid "Editable Cells"
msgstr ""

#: C/gtkmm-tutorial-in.xml:2992(title)
msgid "Automatically-stored editable cells."
msgstr ""

#: C/gtkmm-tutorial-in.xml:2993(para)
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 ""

#: C/gtkmm-tutorial-in.xml:3007(title)
msgid "Implementing custom logic for editable cells."
msgstr ""

#: C/gtkmm-tutorial-in.xml:3008(para)
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 ""

#: C/gtkmm-tutorial-in.xml:3013(para)
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 ""

#: C/gtkmm-tutorial-in.xml:3019(para)
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 ""

#: C/gtkmm-tutorial-in.xml:3023(para)
msgid ""
"For instance, for a CellRendererText, you would set the cell's "
"<emphasis>editable</emphasis> property to true, like so:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3026(programlisting)
#, no-wrap
msgid "cell.property_editable() = true;"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3027(para)
msgid ""
"For a CellRendererToggle, you would set the <emphasis>activatable</emphasis> "
"property instead."
msgstr ""

#: C/gtkmm-tutorial-in.xml:3031(para)
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_cell_renderers()</methodname> on that view "
"Column."
msgstr ""

#: C/gtkmm-tutorial-in.xml:3039(para)
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 ""

#: C/gtkmm-tutorial-in.xml:3051(title)
msgid "Iterating over Model Rows"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3052(para)
msgid ""
"<classname>Gtk::TreeModel</classname> provides an STL-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 ""

#: C/gtkmm-tutorial-in.xml:3058(programlisting)
#, no-wrap
msgid ""
"typedef Gtk::TreeModel::Children type_children; //minimise code length.\n"
"type_children children = refModel-&gt;children();\n"
"for(type_children::iterator iter = children.begin();\n"
"    iter != children.end(); ++iter)\n"
"{\n"
"  Gtk::TreeModel::Row row = *iter;\n"
"  //Do something with the row - see above for set/get.\n"
"}"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3068(title)
msgid "Row children"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3074(programlisting)
#, no-wrap
msgid "Gtk::TreeModel::Children children = row.children();"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3069(para)
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 STL-style container of "
"child <classname>Row</classname>s: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3081(title)
msgid "The Selection"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3082(para)
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 ""

#: C/gtkmm-tutorial-in.xml:3087(programlisting)
#, no-wrap
msgid ""
"Glib::RefPtr&lt;Gtk::TreeSelection&gt; refTreeSelection =\n"
"    m_TreeView.get_selection();"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3091(title)
msgid "Single or multiple selection"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3095(programlisting)
#, no-wrap
msgid "refTreeSelection-&gt;set_mode(Gtk::SELECTION_MULTIPLE);"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3092(para)
msgid ""
"By default, only single rows can be selected, but you can allow multiple "
"selection by setting the mode, like so: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3100(title)
msgid "The selected rows"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3101(para)
msgid ""
"For single-selection, you can just call <methodname>get_selected()</"
"methodname>, like so:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3105(programlisting)
#, no-wrap
msgid ""
"TreeModel::iterator iter = refTreeSelection-&gt;get_selected();\n"
"if(iter) //If anything is selected\n"
"{\n"
"  TreeModel::Row row = *iter;\n"
"  //Do something with the row.\n"
"}"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3112(para)
msgid ""
"For multiple-selection, you need to 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 ""

#: C/gtkmm-tutorial-in.xml:3118(programlisting)
#, 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::iterator&amp; iter)\n"
"{\n"
"  TreeModel::Row row = *iter;\n"
"  //Do something with the row.\n"
"}"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3131(title)
msgid "The \"changed\" signal"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3132(para)
msgid ""
"To respond to the user clicking on a row or range of rows, connect to the "
"signal like so:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3136(programlisting)
#, no-wrap
msgid ""
"refTreeSelection-&gt;signal_changed().connect(\n"
"    sigc::mem_fun(*this, &amp;Example_StockBrowser::on_selection_changed)\n"
");"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3142(title)
msgid "Preventing row selection"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3143(para)
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 ""

#: C/gtkmm-tutorial-in.xml:3148(para)
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 ""

#: C/gtkmm-tutorial-in.xml:3153(programlisting)
#, no-wrap
msgid ""
"m_refTreeSelection-&gt;set_select_function( sigc::mem_fun(*this,\n"
"    &amp;DemoWindow::select_function) );"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3155(para)
msgid "and then"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3158(programlisting)
#, 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 Gtk::TreeModel::iterator iter = model-&gt;get_iter(path);\n"
"  return iter-&gt;children().empty(); // only allow leaf nodes to be selected\n"
"}"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3168(title)
msgid "Changing the selection"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3169(para)
msgid ""
"To change the selection, specify a <classname>Gtk::TreeModel::iterator</"
"classname> or <classname>Gtk::TreeModel::Row</classname>, like so:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3174(programlisting)
#, no-wrap
msgid ""
"Gtk::TreeModel::Row row = m_refModel-&gt;children()[5]; //The fifth row.\n"
"if(row)\n"
"  refTreeSelection-&gt;select(row);"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3177(para)
msgid "or"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3180(programlisting)
#, no-wrap
msgid ""
"Gtk::TreeModel::iterator iter = m_refModel-&gt;children().begin()\n"
"if(iter)\n"
"  refTreeSelection-&gt;select(iter);"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3189(title)
msgid "Sorting"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3190(para)
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 ""

#: C/gtkmm-tutorial-in.xml:3194(ulink)
msgid "TreeSortable Reference"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3197(title)
msgid "Sorting by clicking on columns"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3198(para)
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::TreeViewModel::set_sort_column()</methodname>, supplying "
"the model column on which model should be sorted when the header is clicked. "
"For instance:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3201(programlisting)
#, no-wrap
msgid ""
"Gtk::TreeView::Column* pColumn = treeview.get_column(0);\n"
"if(pColumn)\n"
"  pColumn-&gt;set_sort_column(m_columns.m_col_id);"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3207(title)
msgid "Independently sorted views of the same model"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3208(para)
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::TreeViewModel::"
"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 ""

#: C/gtkmm-tutorial-in.xml:3211(programlisting)
#, no-wrap
msgid ""
"Glib::RefPtr&lt;Gtk::TreeModelSort&gt; sorted_model =\n"
"    Gtk::TreeModelSort::create(model);\n"
"sorted_model-&gt;set_sort_column(columns.m_col_name, Gtk::SORT_ASCENDING);\n"
"treeview.set_model(sorted_model);"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3216(para)
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 ""

#: C/gtkmm-tutorial-in.xml:3218(programlisting)
#, no-wrap
msgid ""
"void ExampleWindow::on_button_delete()\n"
"{\n"
"  Glib::RefPtr&lt;Gtk::TreeSelection&gt; refTreeSelection =\n"
"      m_treeview.get_selection();\n"
"  if(refTreeSelection)\n"
"  {\n"
"    Gtk::TreeModel::iterator sorted_iter =\n"
"        m_refTreeSelection-&gt;get_selected();\n"
"    if(sorted_iter)\n"
"    {\n"
"      Gtk::TreeModel::iterator iter =\n"
"          m_refModelSort-&gt;convert_iter_to_child_iter(sorted_iter);\n"
"      m_refModel-&gt;erase(iter);\n"
"    }\n"
"  }\n"
"}"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3235(ulink)
msgid "TreeModelSort Reference"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3241(title) C/gtkmm-tutorial-in.xml:3348(title)
#: C/gtkmm-tutorial-in.xml:3985(title) C/gtkmm-tutorial-in.xml:4982(title)
#: C/gtkmm-tutorial-in.xml:5142(title)
msgid "Drag and Drop"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3242(para)
msgid ""
"<classname>Gtk::TreeView</classname> already implments simple drag-and-drop "
"when used with the <classname>Gtk::ListStore</classname> or <classname>Gtk::"
"TreeStore</classname> models. If necessary, it also allows you to implement "
"more complex behaviour when items are dragged and dropped, using the normal "
"<link linkend=\"chapter-draganddrop\">Drag and Drop</link> API."
msgstr ""

#: C/gtkmm-tutorial-in.xml:3251(title)
msgid "Reorderable rows"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3252(para)
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 ""

#: C/gtkmm-tutorial-in.xml:3257(para)
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()</literal> and <literal>Gdk::"
"TreeDragDest::row_drop_possible()</literal> virtual methods. You can examine "
"the <literal>Gtk::TreeModel::Path</literal>s provided and allow or disallow "
"dragging or dropping by return <literal>true</literal> or <literal>false</"
"literal>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:3258(para)
msgid "This is demonstrated in the drag_and_drop example."
msgstr ""

#: C/gtkmm-tutorial-in.xml:3264(title) C/gtkmm-tutorial-in.xml:3370(title)
msgid "Popup Context Menu"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3265(para)
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. Apart from one or two points, it's much the same as a "
"normal context menu, as described in the <link linkend=\"sec-menus-popup"
"\">menus chapter</link>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:3274(title)
msgid "Handling <literal>button_press_event</literal>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3275(para)
msgid ""
"To detect a click of the right mouse button, you need to handle the "
"<literal>button_press_event</literal> signal, and check exactly which button "
"was pressed. Because the <classname>TreeView</classname> normally handles "
"this signal completely, you need to either override the default signal "
"handler in a derived <classname>TreeView</classname> class, or use "
"<methodname>connect_nofify()</methodname> instead of <methodname>connect()</"
"methodname>. You probably also want to call the default handler before doing "
"anything else, so that the right-click will cause the row to be selected "
"first."
msgstr ""

#: C/gtkmm-tutorial-in.xml:3285(para)
msgid "This is demonstrated in the Popup Custom Menu example."
msgstr ""

#: C/gtkmm-tutorial-in.xml:3290(title) C/gtkmm-tutorial-in.xml:3746(title)
#: C/gtkmm-tutorial-in.xml:3921(title) C/gtkmm-tutorial-in.xml:5291(title)
msgid "Examples"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3292(title)
msgid "ListStore"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3293(para)
msgid ""
"This example has a <classname>Gtk::TreeView</classname> widget, with a "
"<classname>Gtk::ListStore</classname> model."
msgstr ""

#: C/gtkmm-tutorial-in.xml:3310(title)
msgid "TreeStore"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3312(para)
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 ""

#: C/gtkmm-tutorial-in.xml:3331(para)
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 ""

#: C/gtkmm-tutorial-in.xml:3338(title)
msgid "TreeView - Editable Cells"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3350(para)
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 ""

#: C/gtkmm-tutorial-in.xml:3360(title)
msgid "TreeView - Drag And Drop"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3372(para)
msgid ""
"This example is much like the <classname>ListStore</classname> example, but "
"derives a custom <classname>TreeView</classname> in order to override the "
"<literal>button_press_event</literal>, and also to encapsulate the tree "
"model code in our derived class. See the <link linkend=\"sec-treeview-"
"contextmenu\">TreeView Popup Context Menu</link> section."
msgstr ""

#: C/gtkmm-tutorial-in.xml:3382(title)
msgid "TreeView - Popup Context Menu"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3399(title)
msgid "Combo Boxes"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3401(para)
msgid ""
"The <classname>ComboBox</classname> and <classname>ComboBoxEntry</classname> "
"widgets offers a list (or tree) of choices in a dropdown menu. If "
"appropriate, they can show extra information about each item, such as text, "
"a picture, a checkbox, or a progress bar. The <classname>ComboBox</"
"classname> widget restricts the user to the available choices, but the "
"<classname>ComboBoxEntry</classname> contains an <classname>Entry</"
"classname>, allowing the user to enter arbitrary text if the none of the "
"available choices are suitable."
msgstr ""

#: C/gtkmm-tutorial-in.xml:3404(para)
msgid ""
"For both widgets, 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>. This provides a "
"great deal of flexibility and compile-time type-safety, but the "
"<classname>ComboBoxText</classname> and <classname>ComboBoxEntryText</"
"classname> classes provide a simple text-based specialisation in case that "
"flexibility is not required."
msgstr ""

#: C/gtkmm-tutorial-in.xml:3408(title) C/gtkmm-tutorial-in.xml:3458(title)
#: C/gtkmm-tutorial-in.xml:3471(title)
msgid "ComboBox"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3413(title)
msgid "The model"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3414(para)
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 columns, like so:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3416(programlisting)
#, no-wrap
msgid ""
"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 ""

#: C/gtkmm-tutorial-in.xml:3425(para)
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 methods 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 ""

#: C/gtkmm-tutorial-in.xml:3429(title)
msgid "The chosen item"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3430(para)
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 Combo. For "
"instance:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3432(programlisting)
#, no-wrap
msgid ""
"Gtk::TreeModel::iterator iter = m_Combo.get_active();\n"
"if(iter)\n"
"{\n"
"  Gtk::TreeModel::Row row = *iter;\n"
"\n"
"  //Get the data for the selected row, using our knowledge\n"
"  //of the tree model:\n"
"  int 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 ""

#: C/gtkmm-tutorial-in.xml:3447(title)
msgid "Responding to changes"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3448(para)
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 \"changed"
"\" signal. For instance:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3451(programlisting)
#, no-wrap
msgid ""
"m_combo.signal_changed().connect( sigc::mem_fun(*this,\n"
"      &amp;ExampleWindow::on_combo_changed) );"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3455(title) C/gtkmm-tutorial-in.xml:3504(title)
msgid "Full Example"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3468(title) C/gtkmm-tutorial-in.xml:3517(title)
msgid "Simple Text Example"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3484(title) C/gtkmm-tutorial-in.xml:3507(title)
msgid "ComboBoxEntry"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3489(title)
msgid "The text column"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3491(programlisting)
#, no-wrap
msgid "m_combo.set_text_column(m_columns.m_col_name);"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3490(para)
msgid ""
"Unlike a regular <classname>ComboBox</classname>, a "
"<classname>ComboBoxEntry</classname> contains a <classname>Entry</classname> "
"widget for entering of arbitrary text. So that this Entry can interact with "
"the drop-down list of choices, you must specify which of your model columns "
"are the text column, with <methodname>set_text_column()</methodname>. For "
"instance: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3493(para)
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 ""

#: C/gtkmm-tutorial-in.xml:3499(title)
msgid "The entry"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3500(para)
msgid ""
"Because the user may enter arbitrary text, an active model row isn't enough "
"to tell us what text the user has inputted. Therefore, you should retrieve "
"the <classname>Entry</classname> widget with the <methodname>ComboBoxEntry::"
"get_entry()</methodname> method and call <methodname>get_text()</methodname> "
"on that."
msgstr ""

#: C/gtkmm-tutorial-in.xml:3520(title)
msgid "ComboBoxEntryText"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3539(title) C/gtkmm-tutorial-in.xml:3751(title)
msgid "TextView"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3540(para)
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 ""

#: C/gtkmm-tutorial-in.xml:3548(title)
msgid "The Buffer"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3549(para)
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 ""

#: C/gtkmm-tutorial-in.xml:3559(para)
msgid ""
"The <classname>TextView</classname> creates its own default "
"<classname>TextBuffer</classname>, which you can access via the "
"<methodname>get_buffer()</methodname> method."
msgstr ""

#: C/gtkmm-tutorial-in.xml:3568(title)
msgid "Iterators"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3574(title)
msgid "Tags and Formatting"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3577(title)
msgid "Tags"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3578(para)
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 ""

#: C/gtkmm-tutorial-in.xml:3581(programlisting)
#, no-wrap
msgid ""
"Glib::RefPtr&lt;Gtk::TextBuffer::Tag&gt; refTagMatch =\n"
"    Gtk::TextBuffer::Tag::create();\n"
"refTagMatch-&gt;property_background() = \"orange\";"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3584(para)
msgid ""
"You can specify a name for the <classname>Tag</classname> when using the "
"<methodname>create()</methodname> method, but it is not necessary."
msgstr ""

#: C/gtkmm-tutorial-in.xml:3589(para)
msgid "The <classname>Tag</classname> class has many other properties."
msgstr ""

#: C/gtkmm-tutorial-in.xml:3598(title)
msgid "TagTable"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3600(para)
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 ""

#: C/gtkmm-tutorial-in.xml:3608(programlisting)
#, no-wrap
msgid ""
"Glib::RefPtr&lt;Gtk::TextBuffer::TagTable&gt; refTagTable =\n"
"    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"
"Glib::RefPtr&lt;Gtk::TextBuffer&gt; refBuffer =\n"
"    Gtk::TextBuffer::create(refTagTable);"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3616(para)
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 ""

#: C/gtkmm-tutorial-in.xml:3627(title)
msgid "Applying Tags"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3628(para)
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 ""

#: C/gtkmm-tutorial-in.xml:3635(programlisting)
#, no-wrap
msgid "refBuffer-&gt;apply_tag(refTagMatch, iterRangeStart, iterRangeStop);"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3636(para)
msgid ""
"Or you could specify the tag when first inserting the text: refBuffer-&gt;"
"insert_with_tag(iter, \"Some text\", refTagMatch);"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3641(para)
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 ""

#: C/gtkmm-tutorial-in.xml:3653(title)
msgid "Marks"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3654(para)
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 ""

#: C/gtkmm-tutorial-in.xml:3659(programlisting)
#, no-wrap
msgid ""
"Glib::RefPtr&lt;Gtk::TextBuffer::Mark&gt; refMark =\n"
"    refBuffer-&gt;create_mark(iter);"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3662(para)
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 ""

#: C/gtkmm-tutorial-in.xml:3667(para)
msgid ""
"There are two built-in <classname>Mark</classname>s - <literal>insert</"
"literal> and <literal>select_bound</literal>, which you can access with "
"<classname>TextBuffer</classname>'s <methodname>get_insert()</methodname> "
"and <methodname>get_selection_bound()</methodname> methods."
msgstr ""

#: C/gtkmm-tutorial-in.xml:3680(para)
msgid ""
"As mentioned above, each <classname>TextView</classname> has a "
"<classname>TextBuffer</classname>, and one or more <classname>TextView</"
"classname> can share the same <classname>TextBuffer</classname>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:3687(para)
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 ""

#: C/gtkmm-tutorial-in.xml:3697(title)
msgid "Default formatting"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3698(para)
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 ""

#: C/gtkmm-tutorial-in.xml:3709(title)
msgid "Scrolling"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3710(para)
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_iter()</methodname> to show the "
"found text."
msgstr ""

#: C/gtkmm-tutorial-in.xml:3725(title)
msgid "Widgets and ChildAnchors"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3726(para)
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>iterators</classname>. For "
"instance, to create a child anchor at a particular position, use "
"<methodname>Gtk::TextBuffer::create_child_anchor()</methodname>:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3733(programlisting)
#, no-wrap
msgid ""
"Glib::RefPtr&lt;Gtk::TextChildAnchor&gt; refAnchor =\n"
"    refBuffer-&gt;create_child_anchor(iter);"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3736(para)
msgid ""
"Then, to add a widget at that position, use <methodname>Gtk::TextView::"
"add_child_at_anchor()</methodname>:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3740(programlisting)
#, no-wrap
msgid "m_TextView.add_child_at_anchor(m_Button, refAnchor);"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3766(title)
msgid "Menus and Toolbars"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3768(para)
msgid ""
"There are specific APIs for Menus and toolbars, but you should usually deal "
"with them together, using the <classname>UIManager</classname> to define "
"<classname>Action</classname>s which you can then arrange in menu 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."
msgstr ""

#: C/gtkmm-tutorial-in.xml:3776(para)
msgid ""
"This involves the use of the <classname>Gtk::ActionGroup</classname>, "
"<classname>Gtk::Action</classname>, and <classname>UIManager</classname> "
"classes, all of which should be instantiated via their <methodname>create()</"
"methodname> methods, which return <classname>RefPtr</classname>s."
msgstr ""

#: C/gtkmm-tutorial-in.xml:3785(title)
msgid "Actions"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3786(para)
msgid ""
"First create the <classname>Action</classname>s and add them to an "
"<classname>ActionGroup</classname>, with <methodname>ActionGroup::add()</"
"methodname>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:3792(para)
msgid ""
"The arguments to <methodname>Action::create()</methodname> specify the "
"action's name and how it will appear in menus and toolbars. Use stock items "
"where possible so that you don't need to specify the label, accelerator, "
"icon, and tooltips, and so you can use pre-existing translations."
msgstr ""

#: C/gtkmm-tutorial-in.xml:3798(para)
msgid ""
"You can also specify a signal handler when calling <methodname>ActionGroup::"
"add()</methodname>. This signal handler will be called when the action is "
"activated via either a menu item or a toolbar button."
msgstr ""

#: C/gtkmm-tutorial-in.xml:3803(para)
msgid "Note that you must specify actions for sub menus as well as menu items."
msgstr ""

#: C/gtkmm-tutorial-in.xml:3805(para)
msgid "For instance:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3807(programlisting)
#, no-wrap
msgid ""
"m_refActionGroup = Gtk::ActionGroup::create();\n"
"\n"
"m_refActionGroup-&gt;add( Gtk::Action::create(\"MenuFile\", \"_File\") );\n"
"m_refActionGroup-&gt;add( Gtk::Action::create(\"New\", Gtk::Stock::NEW),\n"
"  sigc::mem_fun(*this, &amp;ExampleWindow::on_action_file_new) );\n"
"m_refActionGroup-&gt;add( Gtk::Action::create(\"ExportData\", \"Export Data\"),\n"
"  sigc::mem_fun(*this, &amp;ExampleWindow::on_action_file_open) );\n"
"m_refActionGroup-&gt;add( Gtk::Action::create(\"Quit\", Gtk::Stock::QUIT),\n"
"  sigc::mem_fun(*this, &amp;ExampleWindow::on_action_file_quit) );"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3817(para)
msgid ""
"Note that this is where we specify the names of the actions as they will be "
"seen by users in menus and toolbars. Therefore, this is where you should "
"make strings translatable, by putting them inside the _() macro. When we use "
"the Gtk::Stock items, of course, translations are automatically available."
msgstr ""

#: C/gtkmm-tutorial-in.xml:3822(title)
msgid "UIManager"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3823(para)
msgid ""
"Next you should create a <classname>UIManager</classname> and add the "
"<classname>ActionGroup</classname> to the <classname>UIManager</classname> "
"with <methodname>insert_action_group()</methodname> At this point is also a "
"good idea to tell the parent window to respond to the specified keyboard "
"shortcuts, by using <methodname>add_accel_group()</methodname>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:3831(para) C/gtkmm-tutorial-in.xml:5209(para)
msgid "For instance,"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3833(programlisting)
#, no-wrap
msgid ""
"Glib::RefPtr&lt;Gtk::UIManager&gt; m_refUIManager =\n"
"    Gtk::UIManager::create();\n"
"m_refUIManager-&gt;insert_action_group(m_refActionGroup);\n"
"add_accel_group(m_refUIManager-&gt;get_accel_group());"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3837(para)
msgid ""
"Then, you can define the actual visible layout of the menus and toolbars, "
"and add the UI layout to the <classname>UIManager</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 ""

#: C/gtkmm-tutorial-in.xml:3843(programlisting)
#, no-wrap
msgid ""
"Glib::ustring ui_info =\n"
"    \"&lt;ui&gt;\"\n"
"    \"  &lt;menubar name='MenuBar'&gt;\"\n"
"    \"    &lt;menu action='MenuFile'&gt;\"\n"
"    \"      &lt;menuitem action='New'/&gt;\"\n"
"    \"      &lt;menuitem action='Open'/&gt;\"\n"
"    \"      &lt;separator/&gt;\"\n"
"    \"      &lt;menuitem action='Quit'/&gt;\"\n"
"    \"    &lt;/menu&gt;\"\n"
"    \"    &lt;menu action='MenuEdit'&gt;\"\n"
"    \"      &lt;menuitem action='Cut'/&gt;\"\n"
"    \"      &lt;menuitem action='Copy'/&gt;\"\n"
"    \"      &lt;menuitem action='Paste'/&gt;\"\n"
"    \"    &lt;/menu&gt;\"\n"
"    \"  &lt;/menubar&gt;\"\n"
"    \"  &lt;toolbar  name='ToolBar'&gt;\"\n"
"    \"    &lt;toolitem action='Open'/&gt;\"\n"
"    \"    &lt;toolitem action='Quit'/&gt;\"\n"
"    \"  &lt;/toolbar&gt;\"\n"
"    \"&lt;/ui&gt;\";\n"
"\n"
"m_refUIManager-&gt;add_ui_from_string(ui_info);"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3866(para)
msgid ""
"Remember that these names are just the identifiers that we used when "
"creating the actions. They are not the text that the user will see in the "
"menus and toolbars. We provided those human-readable names when we created "
"the actions."
msgstr ""

#: C/gtkmm-tutorial-in.xml:3867(para)
msgid ""
"To instantiate a <classname>Gtk::MenuBar</classname> or <classname>Gtk::"
"Toolbar</classname> which you can actually show, you should use the "
"<methodname>UIManager::get_widget()</methodname> method, and then add the "
"widget to a container. For instance:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3873(programlisting)
#, no-wrap
msgid ""
"Gtk::Widget* pMenubar = m_refUIManager-&gt;get_widget(\"/MenuBar\");\n"
"pBox-&gt;add(*pMenuBar, Gtk::PACK_SHRINK);"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3879(title)
msgid "Popup Menus"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3880(para)
msgid ""
"<classname>Menus</classname> 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 ""

#: C/gtkmm-tutorial-in.xml:3887(para)
msgid ""
"The UI layout for a popup menu should use the <literal>popup</literal> node. "
"For instance:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3889(programlisting)
#, no-wrap
msgid ""
"Glib::ustring ui_info =\n"
"    \"&lt;ui&gt;\"\n"
"    \"  &lt;popup name='PopupMenu'&gt;\"\n"
"    \"    &lt;menuitem action='ContextEdit'/&gt;\"\n"
"    \"    &lt;menuitem action='ContextProcess'/&gt;\"\n"
"    \"    &lt;menuitem action='ContextRemove'/&gt;\"\n"
"    \"  &lt;/popup&gt;\"\n"
"    \"&lt;/ui&gt;\";\n"
"\n"
"m_refUIManager-&gt;add_ui_from_string(ui_info);"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3900(para)
msgid ""
"To show the popup menu, use <classname>Gtk::Menu</classname>'s "
"<methodname>popup()</methodname> method, providing the button identifier and "
"the time of activation, as provided by the <literal>button_press_event</"
"literal> signal, which you will need to handle anyway. For instance:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3906(programlisting)
#, no-wrap
msgid ""
"bool ExampleWindow::on_button_press_event(GdkEventButton* event)\n"
"{\n"
"  if( (event-&gt;type == GDK_BUTTON_PRESS) &amp;&amp;\n"
"      (event-&gt;button == 3) )\n"
"  {\n"
"    m_Menu_Popup-&gt;popup(event-&gt;button, event-&gt;time);\n"
"    return true; //It has been handled.\n"
"  }\n"
"  else\n"
"    return false;\n"
"}"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3923(title)
msgid "Main Menu example"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3926(title)
msgid "Main Menu"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3936(title)
msgid "Popup Menu example"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3939(title)
msgid "Popup Menu"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3954(title) C/gtkmm-tutorial-in.xml:3995(title)
msgid "ToolPalette"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3956(para)
msgid ""
"A <classname>ToolPalette</classname> is similar to a <classname>Toolbar</"
"classname> but can contain a grid of items, categorized into groups. The "
"user may hide or expand each group. As in a toolbar, the items may be "
"displayed as only icons, as only text, or as icons with text."
msgstr ""

#: C/gtkmm-tutorial-in.xml:3958(para)
msgid ""
"The <classname>ToolPalette</classname>'s items might be dragged or simply "
"activated. For instance, the user might drag objects to a canvas to create "
"new items there. Or the user might click an item to activate a certain brush "
"size in a drawing application."
msgstr ""

#: C/gtkmm-tutorial-in.xml:3959(para)
msgid ""
"<classname>ToolItemGroup</classname>s should be added to the tool pallete "
"via the base class's <function>Gtk::Container::add()</function> method, for "
"instance like so:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3962(programlisting)
#, no-wrap
msgid ""
"\n"
"Gtk::ToolItemGroup* group_brushes =\n"
"  Gtk::manage(new Gtk::ToolItemGroup(\"Brushes\"));\n"
"m_ToolPalette.add(*group_brushes);\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3968(para)
msgid ""
"<classname>Gtk::ToolItem</classname>s can then be added to the group. For "
"instance, like so:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3972(programlisting)
#, no-wrap
msgid ""
"\n"
"Gtk::ToolButton* button = Gtk::manage(new Gtk::ToolButton(icon, \"Big\"));\n"
"button-&gt;set_tooltip_text(\"Big Brush);\n"
"group_brushes-&gt;insert(*button);\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3978(para)
msgid ""
"You might then handle the <classname>ToolButton</classname>'s "
"<literal>clicked</literal> signal. Alternatively, you could allow the item "
"to be dragged to another widget, by calling <methodname>Gtk::ToolPalette::"
"add_drag_dest()</methodname> and then using <methodname>Gtk::ToolPalette::"
"get_drag_item()</methodname> in the other widget's "
"<literal>drag_data_received</literal> signal handler."
msgstr ""

#: C/gtkmm-tutorial-in.xml:3980(ulink)
msgid "ToolPalette Reference"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3981(ulink)
msgid "ToolItemGroup Reference"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3982(ulink)
msgid "ToolItem Reference"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3986(para)
msgid ""
"Call <methodname>add_drag_dest()</methodname> to allow items or groups to be "
"dragged from the tool palette to a particular destination widget. You can "
"then use <methodname>get_drag_item()</methodname> to discover which ToolItem "
"or ToolItemGroup is being dragged. You can use <literal>dynamic_cast</"
"literal> to discover whether is it an item or a group. For instance, you "
"might use this in your <literal>drag_data_received</literal> signal handler, "
"to add a dropped item, or to show a suitable icon while dragging."
msgstr ""

#: C/gtkmm-tutorial-in.xml:3987(para)
msgid ""
"See the <link linkend=\"chapter-draganddrop\">Drag and Drop</link> chapter "
"for general advice about Drag and Drop with gtkmm."
msgstr ""

#: C/gtkmm-tutorial-in.xml:3990(title)
msgid "ToolPalette Example"
msgstr ""

#: C/gtkmm-tutorial-in.xml:3992(para)
msgid ""
"This example adds a <classname>ToolPalette</classname> and a "
"<classname>DrawingArea</classname> to a window and allows the user to drag "
"icons from the tool palette to the drawing area. The tool palette contains "
"several groups of items. The combo boxes allow the user to change the style "
"and orientation of the tool palette."
msgstr ""

#: C/gtkmm-tutorial-in.xml:4008(title)
msgid "Adjustments"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4010(para)
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 ""

#: C/gtkmm-tutorial-in.xml:4020(para)
msgid ""
"So that applications can react to changes, for instance when a user moves a "
"scrollbar, <classname>Gtk::Adjustment</classname> has a <literal>changed</"
"literal> signal. You can then use the <methodname>get_changed()</methodname> "
"method to discover the new value."
msgstr ""

#: C/gtkmm-tutorial-in.xml:4028(title)
msgid "Creating an Adjustment"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4030(para)
msgid "The <classname>Gtk::Adjustment</classname> constructor is as follows:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4034(programlisting)
#, no-wrap
msgid ""
"Gtk::Adjustment(float value,\n"
"                float lower,\n"
"                float upper,\n"
"                float step_increment = 1,\n"
"                float page_increment = 10,\n"
"                float page_size = 0);"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4041(para)
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 specifies 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 bottom most or right most coordinate in a "
"panning widget's child. TODO: Investigate the upper argument properly. There "
"was some unclear stuff about it not always being the upper value."
msgstr ""

#: C/gtkmm-tutorial-in.xml:4060(title)
msgid "Using Adjustments the Easy Way"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4062(para)
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 ""

#: C/gtkmm-tutorial-in.xml:4067(para)
msgid ""
"The group which treats the values as arbitrary numbers includes the "
"<classname>Range</classname> widgets (<classname>Scrollbars</classname> and "
"<classname>Scales</classname>, the <classname>Progressbar</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 ""

#: C/gtkmm-tutorial-in.xml:4079(para)
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 ""

#: C/gtkmm-tutorial-in.xml:4088(para)
msgid ""
"TODO: Text widget is deprecated: Look at GTK+ tutorial for up-to-date "
"example. If you share an adjustment object between a Scrollbar and a Text "
"widget, manipulating the scrollbar will automagically adjust the Text "
"widget. You can set it up like this:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4094(programlisting)
#, no-wrap
msgid ""
"// creates its own adjustments\n"
"Gtk::Text text(0, 0);\n"
"// uses the newly-created adjustment for the scrollbar as well\n"
"Gtk::VScrollbar vscrollbar (*(text.get_vadjustment()));"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4102(title)
msgid "Adjustment Internals"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4104(para)
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 ""

#: C/gtkmm-tutorial-in.xml:4112(para)
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 ""

#: C/gtkmm-tutorial-in.xml:4121(para)
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 ""

#: C/gtkmm-tutorial-in.xml:4126(programlisting)
#, no-wrap
msgid ""
"void cb_rotate_picture (Gtk::Widget *picture)\n"
"{\n"
"  picture-&gt;set_rotation (adj-&gt;value);\n"
"..."
msgstr ""

#: C/gtkmm-tutorial-in.xml:4130(para)
msgid "and connect it to the scale widget's adjustment like this:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4133(programlisting)
#, no-wrap
msgid ""
"adj.value_changed.connect(sigc::bind&lt;Widget*&gt;(sigc::mem_fun(*this,\n"
"    &amp;cb_rotate_picture), picture));"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4136(para)
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 ""

#: C/gtkmm-tutorial-in.xml:4143(para)
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 ""

#: C/gtkmm-tutorial-in.xml:4152(para)
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 ""

#: C/gtkmm-tutorial-in.xml:4156(programlisting)
#, no-wrap
msgid "adjustment-&gt;changed();"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4163(title)
msgid "Widgets Without X-Windows"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4165(para)
msgid ""
"Some Widgets do not have an associated X-Window, so they therefore do not "
"receive X events. This means that the signals described in the <link linkend="
"\"sec-xeventsignals\">X event signals</link> section will not be emitted. If "
"you want to capture events for these widgets you can use a special container "
"called <classname>Gtk::EventBox</classname>, which is described in the <link "
"linkend=\"sec-eventbox\">EventBox</link> section."
msgstr ""

#: C/gtkmm-tutorial-in.xml:4174(para)
msgid "Here is a list of some of these Widgets:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4177(programlisting)
#, no-wrap
msgid ""
"Gtk::Alignment\n"
"Gtk::Arrow\n"
"Gtk::Bin\n"
"Gtk::Box\n"
"Gtk::Button\n"
"Gtk::CheckButton\n"
"Gtk::Fixed\n"
"Gtk::Image\n"
"Gtk::Item\n"
"Gtk::Label\n"
"Gtk::MenuItem\n"
"Gtk::Notebook\n"
"Gtk::Paned\n"
"Gtk::Pixmap\n"
"Gtk::RadioButton\n"
"Gtk::Range\n"
"Gtk::ScrolledWindow\n"
"Gtk::Separator\n"
"Gtk::Table\n"
"Gtk::Toolbar\n"
"Gtk::AspectFrame\n"
"Gtk::Frame\n"
"Gtk::VBox\n"
"Gtk::HBox\n"
"Gtk::VSeparator\n"
"Gtk::HSeparator"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4204(para)
msgid ""
"These widgets are mainly used for decoration or layout, so you won't often "
"need to capture events on them. They are intended to have no X-Window in "
"order to improve performance."
msgstr ""

#: C/gtkmm-tutorial-in.xml:4210(title) C/gtkmm-tutorial-in.xml:4252(title)
msgid "EventBox"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4212(para)
msgid ""
"Some <application>gtkmm</application> widgets don't have associated X "
"windows; they draw on their parents' windows. Because of this, they cannot "
"receive events. Also, if they are incorrectly sized, they don't clip, so you "
"can get messy overwriting etc. To receive events on one of these widgets, "
"you can it inside an <classname>EventBox</classname> widget and then call "
"<methodname>Gtk::Widget::set_events()</methodname> on the EventBox before "
"showing it."
msgstr ""

#: C/gtkmm-tutorial-in.xml:4220(para)
msgid ""
"Although the name <classname>EventBox</classname> emphasises the event-"
"handling method, the widget can also be used for clipping (and more; see the "
"example below)."
msgstr ""

#: C/gtkmm-tutorial-in.xml:4224(para)
msgid ""
"TODO: Why don't they have X Windows - explain clipping. Also, how does this "
"affect platform such as Windows and MacOS that don't use X."
msgstr ""

#: C/gtkmm-tutorial-in.xml:4228(para)
msgid "The constructor for <classname>Gtk::EventBox</classname> is:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4232(programlisting)
#, no-wrap
msgid "Gtk::EventBox();"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4234(para)
msgid ""
"A child widget can be added to the <classname>EventBox</classname> using:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4238(programlisting)
#, no-wrap
msgid "event_box.add(child_widget);"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4244(para)
msgid ""
"The following example demonstrates both uses of an <classname>EventBox</"
"classname> - a label is created that is clipped to a small box, and set up "
"so that a mouse-click on the label causes the program to exit. Resizing the "
"window reveals varying amounts of the label."
msgstr ""

#: C/gtkmm-tutorial-in.xml:4266(title)
msgid "Dialogs"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4268(para)
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 <methodname>run()</methodname> "
"method which blocks until the user dismisses the dialog."
msgstr ""

#: C/gtkmm-tutorial-in.xml:4275(para)
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 ""

#: C/gtkmm-tutorial-in.xml:4282(para)
msgid ""
"To pack widgets into a custom dialog, you should pack them into the "
"<classname>Gtk::VBox</classname>, available via <methodname>get_vbox()</"
"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 ""

#: C/gtkmm-tutorial-in.xml:4290(para)
msgid ""
"The <methodname>run()</methodname> method returns an <literal>int</literal>. "
"This may be a value from the <literal>Gtk::ResponseType</literal> if the "
"user closed the button by clicking a standard button, or it could be the "
"custom response value that you specified when using <methodname>add_button()"
"</methodname>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:4299(title) C/gtkmm-tutorial-in.xml:4314(title)
msgid "MessageDialog"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4300(para)
msgid ""
"<classname>MessageDialog</classname> is a convenience class, used to create "
"simple, standard message dialogs, with a message, an icon, and buttons for "
"user response. You can specify the type of message and the text in the "
"constructor, as well as specifying standard buttons via the <literal>Gtk::"
"ButtonsType</literal> enum."
msgstr ""

#: C/gtkmm-tutorial-in.xml:4325(title)
msgid "FileChooserDialog"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4326(para)
msgid ""
"The <classname>FileChooserDialog</classname> is suitable for use with \"Open"
"\" or \"Save\" menu items."
msgstr ""

#: C/gtkmm-tutorial-in.xml:4330(para)
msgid ""
"Most of the useful member methods for this class are actually in the "
"<classname>Gtk::FileChooser</classname> base class."
msgstr ""

#: C/gtkmm-tutorial-in.xml:4341(title)
msgid "FileChooser"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4351(title) C/gtkmm-tutorial-in.xml:4363(title)
msgid "ColorSelectionDialog"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4352(para)
msgid ""
"The <classname>ColorSelectionDialog</classname> allows the user to choose a "
"color."
msgstr ""

#: C/gtkmm-tutorial-in.xml:4374(title) C/gtkmm-tutorial-in.xml:4386(title)
msgid "FontSelectionDialog"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4375(para)
msgid ""
"The <classname>FontSelectionDialog</classname> allows the user to choose a "
"font."
msgstr ""

#: C/gtkmm-tutorial-in.xml:4401(title)
msgid "The Drawing Area Widget"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4402(para)
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 handle expose events 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 "
"DrawingArea does not, allowing you to write your own expose event signal "
"handler to determine how the contents of the widget will be drawn. This is "
"most often done by overriding the virtual <methodname>on_expose_event()</"
"methodname> member function."
msgstr ""

#: C/gtkmm-tutorial-in.xml:4414(para)
msgid ""
"GTK+ uses the <ulink url=\"http://cairographics.org\">Cairo</ulink> drawing "
"API. With gtkmm, you may use the <ulink url=\"http://www.cairographics.org/"
"cairomm/\">cairomm</ulink> C++ API for cairo."
msgstr ""

#: C/gtkmm-tutorial-in.xml:4419(para)
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 ""

#: C/gtkmm-tutorial-in.xml:4429(title)
msgid "Cairo and Pango"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4430(para)
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 ""

#: C/gtkmm-tutorial-in.xml:4435(para)
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 ""

#: C/gtkmm-tutorial-in.xml:4442(title)
msgid "The Cairo Drawing Model"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4443(para)
msgid ""
"The basic concept of drawing in Cairo involves defining 'invisible' paths "
"and then stroking or filling them to make them visible."
msgstr ""

#: C/gtkmm-tutorial-in.xml:4447(para)
msgid ""
"To do any drawing in <application>gtkmm</application> with Cairo, you must "
"first create 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. In <application>gtkmm</"
"application>, a <classname>Cairo::Context</classname> is created by calling "
"the <methodname>Gdk::Window::create_cairo_context()</methodname> function. "
"Since Cairo context are reference-counted objects, this function returns a "
"<classname>Cairo::RefPtr&lt;Cairo::Context&gt;</classname> object."
msgstr ""

#: C/gtkmm-tutorial-in.xml:4460(para)
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 ""

#: C/gtkmm-tutorial-in.xml:4465(programlisting)
#, no-wrap
msgid ""
"Gtk::DrawingArea myArea;\n"
"Cairo::RefPtr&lt;Cairo::Context&gt; myContext = myArea.get_window()-&gt;create_cairo_context();\n"
"myContext-&gt;set_source_rgb(1.0, 0.0, 0.0);\n"
"myContext-&gt;set_line_width(2.0);"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4469(para)
msgid ""
"Each <classname>Cairo::Context</classname> is associated with a particular "
"<classname>Gdk::Window</classname>, so the first line of the above example "
"creates a <classname>Gtk::DrawingArea</classname> widget and the second line "
"uses its associated <classname>Gdk::Window</classname> to create a "
"<classname>Cairo::Context</classname> object. The final two lines change the "
"graphics state of the context."
msgstr ""

#: C/gtkmm-tutorial-in.xml:4478(para)
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 <ulink url=\"http://www."
"cairographics.org/cairomm/\">cairomm</ulink> API documentation."
msgstr ""

#: C/gtkmm-tutorial-in.xml:4510(para)
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 ""

#: C/gtkmm-tutorial-in.xml:4516(programlisting)
#, no-wrap
msgid ""
"void doSomething(Cairo::RefPtr&lt;Cairo::Context&gt; context, int x)\n"
"{\n"
"    context-&gt;save();\n"
"    // change graphics state\n"
"    // peform drawing operations\n"
"    context-&gt;restore();\n"
"}"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4493(para)
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>. <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4527(title)
msgid "Drawing Straight Lines"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4536(para)
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 ""

#: C/gtkmm-tutorial-in.xml:4528(para)
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. <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4551(para)
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 ""

#: C/gtkmm-tutorial-in.xml:4563(para)
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 ""

#: C/gtkmm-tutorial-in.xml:4572(para)
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 ""

#: C/gtkmm-tutorial-in.xml:4582(title) C/gtkmm-tutorial-in.xml:4679(title)
msgid "Drawing Area - Lines"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4590(para)
msgid ""
"This program contains a single class, <classname>MyArea</classname>, which "
"is a subclass of <classname>Gtk::DrawingArea</classname> and contains an "
"<methodname>on_expose_event()</methodname> member function. This method is "
"called whenever the image in the drawing area needs to be redrawn. This "
"function is passed a pointer to a <classname>GdkEventExpose</classname> "
"structure which defines the area that needs to be redrawn. We use these "
"values to create a rectangle path in Cairo (using the <methodname>rectangle()"
"</methodname> function) and then <methodname>clip()</methodname> to this "
"path. The <methodname>clip()</methodname> function sets a clip region. The "
"current clip region affects all drawing operations by effectively masking "
"out any changes to the surface that are outside the current clip region. "
"This allows us to limit our redrawing to only the area that needs to be "
"redrawn. 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 ""

#: C/gtkmm-tutorial-in.xml:4614(title)
msgid "Drawing with relative coordinates"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4615(para)
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 ""

#: C/gtkmm-tutorial-in.xml:4621(title)
msgid "Line styles"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4622(para)
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 ""

#: C/gtkmm-tutorial-in.xml:4628(para)
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 ""

#: C/gtkmm-tutorial-in.xml:4635(title)
msgid "Different join types in Cairo"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4640(para)
msgid ""
"The line join style is set using the function <methodname>Cairo::Context::"
"set_line_join()</methodname>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:4644(para)
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 ""

#: C/gtkmm-tutorial-in.xml:4654(para)
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 ""

#: C/gtkmm-tutorial-in.xml:4662(title)
msgid "Drawing Curved Lines"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4663(para)
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 ""

#: C/gtkmm-tutorial-in.xml:4674(para)
msgid ""
"This simple application draws a curve with Cairo and displays the control "
"points for each end of the curve."
msgstr ""

#: C/gtkmm-tutorial-in.xml:4686(para)
msgid ""
"The only difference between this example and the straight line example is in "
"the <methodname>on_expose_event()</methodname> function, but there are a few "
"new concepts and functions introduced here, so let's examine them briefly."
msgstr ""

#: C/gtkmm-tutorial-in.xml:4692(para)
msgid ""
"Note that we clip to the area that needs re-exposing just as we did in the "
"last example. After clipping, however, 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 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 ""

#: C/gtkmm-tutorial-in.xml:4702(para)
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 draw 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 ""

#: C/gtkmm-tutorial-in.xml:4720(title)
msgid "Drawing Arcs and Circles"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4721(para)
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."
msgstr ""

#: C/gtkmm-tutorial-in.xml:4742(programlisting)
#, 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 ""

#: C/gtkmm-tutorial-in.xml:4735(para)
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 "
"in the box given by <varname>x</varname>, <varname>y</varname>, "
"<varname>width</varname>, <varname>height</varname>: <placeholder-1/> Note "
"that this contradicts the <ulink url=\"http://www.cairographics.org/manual/"
"cairo-Paths.html#cairo-arc\">advice given in the official Cairo "
"documentation</ulink>, but it seems to work."
msgstr ""

#: C/gtkmm-tutorial-in.xml:4754(para)
msgid ""
"Here's an example of a simple program that draws an arc, a circle and an "
"ellipse into a drawing area."
msgstr ""

#: C/gtkmm-tutorial-in.xml:4759(title)
msgid "Drawing Area - Arcs"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4768(para)
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_expose_event()</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 ""

#: C/gtkmm-tutorial-in.xml:4776(para)
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 ""

#: C/gtkmm-tutorial-in.xml:4785(para)
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 ""

#: C/gtkmm-tutorial-in.xml:4798(title)
msgid "Drawing counter-clockwise"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4799(para)
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 ""

#: C/gtkmm-tutorial-in.xml:4811(title)
msgid "Drawing Text"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4813(title)
msgid "Drawing Text with Pango"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4814(para)
msgid ""
"Text is drawn via Pango Layouts. The easiest way to create a "
"<classname>Pango::Layout</classname> is to use "
"<methodname>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>draw_layout</"
"methodname> method of <classname>Gdk::Drawable</classname>, which takes a "
"<classname>Gdk::GC</classname> object, an x-position, a y-position and the "
"layout itself. TODO: Update this section for Cairo instead of Gdk::GC."
msgstr ""

#: C/gtkmm-tutorial-in.xml:4836(title)
msgid "Drawing Images"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4838(title)
msgid "Drawing Images with Gdk"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4839(para)
msgid ""
"There are a couple of drawing methods for putting image data into a drawing "
"area. <methodname>draw_pixmap()</methodname> can copy the contents of a "
"<classname>Gdk::Drawable</classname> (the window of a drawing area is one) "
"into the drawing area. There is also <methodname>draw_bitmap()</methodname> "
"for drawing a two-color image into the drawing area, and "
"<methodname>draw_image()</methodname> for drawing an image with more than "
"two colors."
msgstr ""

#: C/gtkmm-tutorial-in.xml:4848(para)
msgid ""
"For all of these methods, the first argument is the <classname>Gdk::GC</"
"classname>. The second argument is the object of the appropriate type to "
"copy in: <classname>Gdk::Drawable</classname>, <classname>Gdk::Bitmap</"
"classname>, <classname>Gdk::Image</classname>. The next two arguments are "
"the x and y points in the image to begin copying from. Then come the x and y "
"points in the drawing area to copy to. The final two arguments are the width "
"and height of the area to copy."
msgstr ""

#: C/gtkmm-tutorial-in.xml:4859(para)
msgid ""
"There is also a method for drawing from a <classname>Gdk::Pixbuf</"
"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 ""

#: C/gtkmm-tutorial-in.xml:4866(para)
msgid ""
"Probably the most common way of creating <classname>Gdk::Pixbuf</classname>s "
"is to use <methodname>Gdk::Pixbuf::create_from_file()</methodname>, which "
"can read an image file, such as a png file into a pixbuf ready for rendering."
msgstr ""

#: C/gtkmm-tutorial-in.xml:4873(para)
msgid ""
"The <classname>Gdk::Pixbuf</classname> can be rendered with "
"<methodname>render_to_drawable</methodname>, which takes quite a few "
"parameters. The <methodname>render_to_drawable</methodname> is a member of "
"<classname>Gdk::Pixbuf</classname> rather than <classname>Gdk::Drawable</"
"classname>, which is unlike the <methodname>draw_*</methodname> functions "
"described earlier. As such, its first parameter is the drawable to render "
"to. The second parameter is still the <classname>Gdk::GC</classname>. The "
"next two parameters are the point in the pixbuf to start drawing from. This "
"is followed by the point in the drawable to draw it at, and by the width and "
"height to actually draw (which may not be the whole image, especially if "
"you're only responding to an expose event for part of the window). Finally, "
"there are the dithering parameters. If you use Gdk::RGB_DITHER_NONE as the "
"dither type, then the dither offset parameters can both be 0."
msgstr ""

#: C/gtkmm-tutorial-in.xml:4890(para)
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 expose event handler! It's just "
"shown here to keep it all together)"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4895(programlisting)
#, no-wrap
msgid ""
"bool myarea::on_expose_event(GdkEventExpose* ev)\n"
"{\n"
"Glib::RefPtr&lt;Gdk::Pixbuf&gt; image = Gdk::Pixbuf::create_from_file(\"myimage.png\");\n"
"image-&gt;render_to_drawable(get_window(), get_style()-&gt;get_black_gc(),\n"
"0, 0, 100, 80, image-&gt;get_width(), image-&gt;get_height(), // draw the whole image (from 0,0 to the full width,height) at 100,80 in the window\n"
"Gdk::RGB_DITHER_NONE, 0, 0);\n"
"return true;\n"
"}"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4922(title)
msgid "Example Application: Creating a Clock with Cairo"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4923(para)
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 ""

#: C/gtkmm-tutorial-in.xml:4935(para)
msgid ""
"As before, almost all of the interesting stuff is done in the expose event "
"handler <methodname>on_expose_event()</methodname>. Before we dig into the "
"expose event handler, notice that the constructor for the <classname>Clock</"
"classname> widget connects a handler function <methodname>onSecondElapsed()</"
"methodname> to a timer with a timeout period of 1000 milliseconds (1 "
"second). This means that <methodname>onSecondElapsed()</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 ""

#: C/gtkmm-tutorial-in.xml:4946(para)
msgid ""
"Now let's take a look at the code that performs the actual drawing. The "
"first section of <methodname>on_expose_event()</methodname> should be pretty "
"familiar by now as it's mostly 'boilerplate' code for getting the "
"<classname>Gdk::Window</classname>, creating a <classname>Cairo::Context</"
"classname>, and clipping to the area that we want to re-draw. 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 ""

#: C/gtkmm-tutorial-in.xml:4959(para)
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 than our next lines don't go "
"outside the outline of the clock."
msgstr ""

#: C/gtkmm-tutorial-in.xml:4971(para)
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 ""

#: C/gtkmm-tutorial-in.xml:4983(para)
msgid ""
"<classname>Gtk::Widget</classname> has several methods and signals which are "
"prefixed with \"drag_\". These are used for Drag and Drop."
msgstr ""

#: C/gtkmm-tutorial-in.xml:4988(title)
msgid "Sources and Destinations"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4989(para)
msgid ""
"Things are dragged from <literal>sources</literal> to be dropped on "
"<literal>destinations</literal>. Each source and destination has infomation "
"about the data formats that it can send or receive, provided by "
"<classname>Gtk::TargetEntry</classname> items. A drop destination will only "
"accept a dragged item if they both share a compatible <classname>Gtk::"
"TargetEntry</classname> item. Appropriate signals will then be emitted, "
"telling the signal handlers which <classname>Gtk::TargetEntry</classname> "
"was used."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5002(para)
msgid "target: A name, such as \"STRING\""
msgstr ""

#: C/gtkmm-tutorial-in.xml:5003(para)
msgid ""
"info: An identifier which will be sent to your signals to tell you which "
"TargetEntry was used."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5004(para)
msgid "flags: TODO"
msgstr ""

#: C/gtkmm-tutorial-in.xml:4999(para)
msgid ""
"<classname>Gtk::TargetEntry</classname> objects contain this information: "
"<placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5012(para)
msgid ""
"<classname>Widgets</classname> can be identified as sources or destinations "
"using these <classname>Gtk::Widget</classname> methods:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5016(programlisting)
#, no-wrap
msgid ""
"void drag_source_set(const ArrayHandle_TargetEntry&amp; targets,\n"
"      GdkModifierType start_button_mask, GdkDragAction actions);"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5021(para)
msgid ""
"<literal>targets</literal> is a container of <classname>Gtk::TargetEntry</"
"classname> (<classname>std::list&lt;Gtk::TargetEntry&gt;</classname> or "
"<classname>std::vector&lt;Gtk::TargetEntry&gt;</classname>, for instance) "
"elements."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5030(para)
msgid ""
"<literal>start_button_mask</literal> is an ORed combination of values, which "
"specify which modifier key or mouse button must be pressed to start the drag."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5037(para)
msgid ""
"<literal>actions</literal> is an ORed combination of values, which specified "
"which Drag and Drop operations will be possible from this source - for "
"instance, copy, move, or link. The user can choose between the actions by "
"using modifier keys, such as <keycap>Shift</keycap> to change from "
"<literal>copy</literal> to <literal>move</literal>, and this will be shown "
"by a different cursor."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5048(programlisting)
#, no-wrap
msgid ""
"void drag_dest_set(const ArrayHandle_TargetEntry&amp; targets,\n"
"    GtkDestDefaults flags, GdkDragAction actions);"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5053(para)
msgid ""
"<literal>flags</literal> is an ORed combination of values which indicates "
"how the widget will respond visually to Drag and Drop items."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5059(para)
msgid ""
"<literal>actions</literal> indicates the Drag and Drop actions which this "
"destination can receive - see the description above."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5069(para)
msgid ""
"When a drop destination 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>drag_dest_set()</methodname> and <methodname>drag_source_set()"
"</methodname>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5080(title) C/gtkmm-tutorial-in.xml:5201(title)
msgid "Copy"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5084(para)
msgid "<literal>drag_begin</literal>: Provides DragContext."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5085(para)
msgid ""
"<literal>drag_motion</literal>: Provides DragContext and coordinates. You "
"can call the drag_status() method of the DragContext to indicate which "
"target will be accepted."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5086(para)
msgid ""
"<literal>drag_get</literal>: Provides <literal>info</literal> about the "
"dragged data format, and a <literal>GtkSelectionData</literal> structure, in "
"which you should put the requested data."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5087(para)
msgid "<literal>drag_drop</literal>: Provides DragContext and coordinates."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5088(para)
msgid "<literal>drag_end</literal>: Provides DragContext."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5081(para)
msgid ""
"The source widget will emit these signals, in this order: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5095(para)
msgid ""
"<literal>drag_data_received</literal>: Provides <literal>info</literal> "
"about the dragged data format, and a <literal>GtkSelectionData</literal> "
"structure which contains the dropped data. You should call the "
"<methodname>drag_finish()</methodname> method of the <literal>DragContext</"
"literal> to indicate whether the operation was successful."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5091(para)
msgid ""
"The destination widget will emit this signal, after the source destination "
"has emitted the <literal>drag_get</literal> signal: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5110(title)
msgid "Move"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5113(para)
msgid ""
"<literal>drag_delete</literal>: Gives the source the opportunity to delete "
"the original data if that's appropriate."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5111(para)
msgid ""
"During a <literal>move</literal>, the source widget will also emit this "
"signal: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5119(title)
msgid "Link"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5120(para)
msgid "TODO: Find an example or documentation."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5125(title)
msgid "DragContext"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5126(para)
msgid ""
"The drag and drop signals provide a DragContext, which contains some "
"information about the drag and drop operation and can be used to influence "
"the process. For instance, you can discover the source widget, or change the "
"drag and drop icon, by using the <methodname>set_icon()</methodname> "
"methods. More importantly, you should call the <methodname>drag_finish()</"
"methodname> method from your <literal>drag_data_received</literal> signal "
"handler to indicate whether the drop was successful."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5139(para)
msgid ""
"Here is a very simple example, demonstrating a drag and drop <literal>Copy</"
"literal> operation:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5150(para)
msgid "There is a more complex example in examples/dnd."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5159(title)
msgid "The Clipboard"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5160(para)
msgid ""
"Simple text copy-paste functionality is provided for free by widgets such as "
"Gtk::Entry and Gtk::TextView, 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 ""

#: C/gtkmm-tutorial-in.xml:5162(para)
msgid ""
"<classname>Gtk::Clipboard</classname> is a singleton. You can get the one "
"and only instance with <methodname>Gtk::Clipboard::get()</methodname>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5167(para)
msgid ""
"So your application doesn't need to wait for clipboard operations, "
"particularly between the time when the user chooses Copy and then later "
"chooses Paste, most <classname>Gtk::Clipboard</classname> methods take "
"<classname>sigc::slot</classname>s which specify callback methods. When "
"<classname>Gtk::Clipboard</classname> is ready, it will call these methods, "
"either providing the requested data, or asking for data."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5179(title)
msgid "Targets"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5180(para)
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>target</literal>s."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5184(para)
msgid ""
"For instance, gedit can supply and receive the <literal>\"UTF8_STRING\"</"
"literal> target, so you can paste data into gedit from any application that "
"supplies that target. Or two different image editing applications might "
"supply and receive a variety of image formats as targets. As long as one "
"application can receive one of the targets that the other supplies then you "
"will be able to copy data from one to the other."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5188(para)
msgid ""
"A target 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. <classname>Gtk::Clipboard</"
"classname> provides overloads that allow you to specify the format in more "
"detail if necessary."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5197(para)
msgid ""
"The <link linkend=\"chapter-draganddrop\">Drag and Drop</link> API uses the "
"same mechanism. You should probably use the same data targets and formats "
"for both Clipboard and Drag and Drap operations."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5202(para)
msgid ""
"When the user asks to copy some data, you should tell the "
"<classname>Clipboard</classname> what targets are available, and provide the "
"callback methods that it can use to get the data. At this point you should "
"store a copy of the data, to be provided when the clipboard calls your "
"callback method in repsonse to a paste."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5211(programlisting)
#, no-wrap
msgid ""
"Glib::RefPtr&lt;Gtk::Clipboard&gt; refClipboard = Gtk::Clipboard::get();\n"
"\n"
"//Targets:\n"
"std::list&lt;Gtk::TargetEntry&gt; listTargets;\n"
"listTargets.push_back( Gtk::TargetEntry(\"example_custom_target\") );\n"
"listTargets.push_back( Gtk::TargetEntry(\"UTF8_STRING\") );\n"
"\n"
"refClipboard-&gt;set( listTargets,\n"
"    sigc::mem_fun(*this, &amp;ExampleWindow::on_clipboard_get),\n"
"    sigc::mem_fun(*this, &amp;ExampleWindow::on_clipboard_clear) );"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5222(para)
msgid ""
"Your callback will then provide the store data when the user chooses to "
"paste the data. For instance:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5224(programlisting)
#, no-wrap
msgid ""
"void ExampleWindow::on_clipboard_get(\n"
"    Gtk::SelectionData&amp; selection_data, guint info)\n"
"{\n"
"  const Glib::ustring target = selection_data.get_target();\n"
"\n"
"  if(target == \"example_custom_target\")\n"
"    selection_data.set(\"example_custom_target\", m_ClipboardStore);\n"
"}"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5232(para)
msgid ""
"The <literal>ideal</literal> example below can supply more than one "
"clipboard target."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5236(para)
msgid ""
"The clear callback allows you to free the memory used by your stored data "
"when the clipboard replaces its data with something else."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5242(title)
msgid "Paste"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5243(para)
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 ""

#: C/gtkmm-tutorial-in.xml:5248(programlisting)
#, no-wrap
msgid ""
"refClipboard-&gt;request_contents(\"example_custom_target\",\n"
"    sigc::mem_fun(*this, &amp;ExampleWindow::on_clipboard_received) );"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5251(para)
msgid "Here is an example callback method:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5253(programlisting)
#, no-wrap
msgid ""
"void ExampleWindow::on_clipboard_received(\n"
"    const Gtk::SelectionData&amp; selection_data)\n"
"{\n"
"  Glib::ustring clipboard_data = selection_data.get_data_as_string();\n"
"  //Do something with the pasted data.\n"
"}"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5261(title)
msgid "Discovering the available targets"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5262(para)
msgid ""
"To find out what targets are currently available on the "
"<classname>Clipboard</classname> for pasting, call the "
"<methodname>request_targets()</methodname> method, specifying a method to be "
"called with the information. For instance:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5268(programlisting)
#, no-wrap
msgid ""
"refClipboard-&gt;request_targets( sigc::mem_fun(*this,\n"
"    &amp;ExampleWindow::on_clipboard_received_targets) );"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5271(para)
msgid ""
"In your callback, compare the list of available targets with those that your "
"application supports for pasting. You could enable or disable a Paste menu "
"item, depending on whether pasting is currently possible. For instance:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5274(programlisting)
#, no-wrap
msgid ""
"void ExampleWindow::on_clipboard_received_targets(\n"
"  const Glib::StringArrayHandle&amp; targets_array)\n"
"{\n"
"  // Get the list of available clipboard targets:\n"
"  std::list&lt;std::string&gt; targets = targets_array;\n"
"\n"
"  const bool bPasteIsPossible =\n"
"    std::find(targets.begin(), targets.end(),\n"
"      example_target_custom) != targets.end();\n"
"\n"
"  // Enable/Disable the Paste button appropriately:\n"
"  m_Button_Paste.set_sensitive(bPasteIsPossible);\n"
"}"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5293(title) C/gtkmm-tutorial-in.xml:5690(title)
msgid "Simple"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5294(para)
msgid ""
"This example allows copy and pasting of application-specific data, using the "
"standard text target. 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 ""

#: C/gtkmm-tutorial-in.xml:5302(title)
msgid "Clipboard - Simple"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5312(title)
msgid "Ideal"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5315(simpara)
msgid ""
"Defines a custom clipboard target, though the format of that target is still "
"text."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5316(simpara)
msgid ""
"It supports pasting of 2 targets - both the custom one and a text one that "
"creates an arbitrary text representation of the custom data."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5317(simpara)
msgid ""
"It uses <methodname>request_targets()</methodname> and disables the Paste "
"button if it can't use anything on the clipboard"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5313(para)
msgid "This is like the simple example, but it <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5322(title)
msgid "Clipboard - Ideal"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5338(title)
msgid "Printing"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5341(para)
msgid ""
"Printing support is available in <application>gtkmm</application> version "
"2.10 and later."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5344(para)
msgid ""
"At the application development level, <application>gtkmm</application>'s "
"printing API provides dialogs that are consistent across applications and "
"allows us 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 ""

#: C/gtkmm-tutorial-in.xml:5350(title)
msgid "PrintOperation"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5352(para)
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 ""

#: C/gtkmm-tutorial-in.xml:5369(para)
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 ""

#: C/gtkmm-tutorial-in.xml:5379(para)
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 ""

#: C/gtkmm-tutorial-in.xml:5393(para)
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 ""

#: C/gtkmm-tutorial-in.xml:5402(para)
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 ""

#: C/gtkmm-tutorial-in.xml:5388(para)
msgid ""
"For each page that needs to be rendered, the following signals are emitted: "
"<placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5417(para)
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 ""

#: C/gtkmm-tutorial-in.xml:5427(para)
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::"
"PrintOperationResult</literal> may indicate that an error occurred. In any "
"case you probably want to notify the user about the final status."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5437(para)
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 ""

#: C/gtkmm-tutorial-in.xml:5363(para)
msgid ""
"The <methodname>PrintOperation::run()</methodname> method starts the print "
"loop, during which various signals are emitted: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5459(title)
msgid "Page setup"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5461(para)
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 ""

#: C/gtkmm-tutorial-in.xml:5471(para)
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 ""

#: C/gtkmm-tutorial-in.xml:5475(programlisting)
#, no-wrap
msgid ""
"\n"
"//Within a class that inherits from Gtk::Window and keeps m_refPageSetup and m_refSettings as members...\n"
"Glib::RefPtr&lt;Gtk::PageSetup&gt; new_page_setup = Gtk::run_page_setup_dialog(*this, m_refPageSetup, m_refSettings);\n"
"m_refPageSetup = new_page_setup;\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5474(para) C/gtkmm-tutorial-in.xml:5539(para)
#: C/gtkmm-tutorial-in.xml:9319(para)
msgid "For instance, <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5486(para)
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 ""

#: C/gtkmm-tutorial-in.xml:5498(title)
msgid "Rendering text"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5500(para)
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 ""

#: C/gtkmm-tutorial-in.xml:5515(para)
msgid ""
"See <link linkend=\"sec-printing-example-simple\">an example</link> of "
"exactly how this can be done."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5523(title)
msgid "Asynchronous operations"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5525(para)
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 ""

#: C/gtkmm-tutorial-in.xml:5532(para)
msgid ""
"<methodname>run()</methodname> may return "
"<literal>PRINT_OPERATION_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 ""

#: C/gtkmm-tutorial-in.xml:5540(programlisting)
#, no-wrap
msgid ""
"\n"
"// in class ExampleWindow's method...\n"
"Glib::RefPtr&lt;PrintOperation&gt; op = PrintOperation::create();\n"
"// ...set up op...\n"
"op-&gt;signal_done().connect(sigc::bind(sigc::mem_fun(*this, &amp;ExampleWindow::on_printoperation_done), op));\n"
"// run the op\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5550(programlisting)
#, no-wrap
msgid ""
"\n"
"void ExampleWindow::on_printoperation_done(Gtk::PrintOperationResult result, const Glib::RefPtr&lt;PrintOperation&gt;&amp; op)\n"
"{\n"
"  if (result == Gtk::PRINT_OPERATION_RESULT_ERROR)\n"
"    //notify user\n"
"  else if (result == Gtk::PRINT_OPERATION_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(*this, &amp;ExampleWindow::on_printoperation_status_changed), op));\n"
"}\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5549(para)
msgid ""
"Second, check for an error and connect to the <literal>status_changed</"
"literal> signal. For instance: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5565(programlisting)
#, no-wrap
msgid ""
"\n"
"void ExampleWindow::on_printoperation_status_changed(const Glib::RefPtr&lt;PrintFormOperation&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 ""

#: C/gtkmm-tutorial-in.xml:5564(para)
msgid "Finally, check the status. For instance, <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5581(title)
msgid "Export to PDF"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5585(programlisting)
#, no-wrap
msgid ""
"\n"
"Glib::RefPtr&lt;Gtk::PrintOperation&gt; op = Gtk::PrintOperation::create();\n"
"// ...set up op...\n"
"op-&gt;set_export_filename(\"test.pdf\");\n"
"Gtk::PrintOperationResult res = op-&gt;run(Gtk::PRINT_OPERATION_ACTION_EXPORT);\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5582(para)
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, <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5597(title)
msgid "Extending the print dialog"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5604(para)
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 ""

#: C/gtkmm-tutorial-in.xml:5614(para)
msgid ""
"Get the data from the widgets in the <literal>custom_widget_apply</literal> "
"signal handler."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5599(para)
msgid "You may add a custom tab to the print dialog: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5629(programlisting)
#, no-wrap
msgid ""
"\n"
"Gtk::Widget* CustomPrintOperation::on_create_custom_widget()\n"
"{\n"
"  set_custom_tab_label(\"My custom tab\");\n"
"\n"
"  Gtk::HBox* hbox = new Gtk::HBox(false, 8);\n"
"  hbox-&gt;set_border_width(6);\n"
"\n"
"  Gtk::Label* label = Gtk::manage(new Gtk::Label(\"Enter some text: \"));\n"
"  hbox-&gt;pack_start(*label, false, false);\n"
"  label-&gt;show();\n"
"\n"
"  hbox-&gt;pack_start(m_Entry, false, false);\n"
"  m_Entry.show();\n"
"\n"
"  return hbox;\n"
"}\n"
"\n"
"void CustomPrintOperation::on_custom_widget_apply(Gtk::Widget* /* widget */)\n"
"{\n"
"  Glib::ustring user_input = m_Entry.get_text();\n"
"  //...\n"
"}\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5622(para)
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: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5656(para)
msgid "The example in examples/book/printing/advanced demonstrates this."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5663(title)
msgid "Preview"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5669(programlisting)
#, no-wrap
msgid ""
"\n"
"// in a class that inherits from Gtk::Window...\n"
"Glib::RefPtr&lt;PrintOperation&gt; op = PrintOperation::create();\n"
"// ...set up op...\n"
"op-&gt;run(Gtk::PRINT_OPERATION_ACTION_PREVIEW, *this);\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5665(para)
msgid ""
"The native GTK+ print dialog has a preview button, but you may also start a "
"preview directly from an application: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5677(para)
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 behaviour and provide a custom preview dialog. See the example "
"located in /examples/book/printing/advanced."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5692(para)
msgid ""
"The following example demonstrates how to print some input from a user "
"interface. 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 ""

#: C/gtkmm-tutorial-in.xml:5700(title)
msgid "Printing - Simple"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5715(title)
msgid "Recently Used Documents"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5717(para) C/gtkmm-tutorial-in.xml:5873(para)
msgid ""
"Recent Files support is available in <application>gtkmm</application> "
"version 2.10 and later"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5720(para)
msgid ""
"<application>gtkmm</application> provides an easy way to manage recently "
"used documents. The classes involved in implementing this functionality are "
"<classname>RecentManager</classname>, <classname>RecentChooserDialog</"
"classname>, <classname>RecentChooserMenu</classname>, "
"<classname>RecentChooserWidget</classname>, and <classname>RecentFilter</"
"classname>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5729(para)
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 ""

#: C/gtkmm-tutorial-in.xml:5737(title)
msgid "RecentManager"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5738(para)
msgid ""
"<classname>RecentManager</classname> acts as the central database of "
"recently used files. You use this class to register new files, remove files "
"from the list, or look up recently used files."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5743(para)
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 ""

#: C/gtkmm-tutorial-in.xml:5750(title)
msgid "Adding Items to the List of Recent Files"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5751(para)
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 ""

#: C/gtkmm-tutorial-in.xml:5755(programlisting)
#, no-wrap
msgid ""
"Glib::RefPtr&lt;Gtk::RecentManager&gt; recent_manager = Gtk::RecentManager::get_default();\n"
"recent_manager-&gt;add_item(uri);"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5757(para)
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 ""

#: C/gtkmm-tutorial-in.xml:5765(para)
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 ""

#: C/gtkmm-tutorial-in.xml:5771(para)
msgid ""
"<varname>app_name</varname>: The name of the application that registered the "
"resource"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5775(para)
msgid ""
"<varname>description</varname>: A short description of the resource as a UTF-"
"8 encoded string"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5779(para)
msgid ""
"<varname>display_name</varname>: The name of the resource to be used for "
"display as a UTF-8 encoded string"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5783(para)
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 ""

#: C/gtkmm-tutorial-in.xml:5789(para)
msgid ""
"<varname>is_private</varname>: Whether this resource should be visible only "
"to applications that have registered it or not"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5793(para)
msgid "<varname>mime_type</varname>: The MIME type of the resource"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5796(para)
msgid ""
"In addition to adding items to the list, you can also look up items from the "
"list and modify or remove items."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5802(title)
msgid "Looking up Items in the List of Recent Files"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5803(para)
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, the <classname>RecentInfo</classname> object "
"will be invalid. <classname>RecentInfo</classname> provides an "
"implementation for <methodname>operator bool()</methodname> which can be "
"used to test for validity. For example:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5814(programlisting)
#, no-wrap
msgid ""
"Gtk::RecentInfo info = recent_manager-&gt;lookup_item(uri);\n"
"if (info)\n"
"{\n"
"  // item was found\n"
"}"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5819(para)
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 above. FIXME - add "
"cross-reference."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5825(para)
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 can be assigned to any standard C++ container (e.g. <classname>std::"
"vector</classname>, <classname>std::list</classname>, etc) and contains a "
"list of all recently-used files up to a user-defined limit (FIXME: what's "
"the default limit?). The following code demonstrates how you might get a "
"list of recently-used files:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5836(programlisting)
#, no-wrap
msgid "std::vector&lt;Gtk::RecentInfo&gt; info_list = recent_manager-&gt;get_items();"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5837(para)
msgid ""
"The limit on the number of items returned can be set by <methodname>set_limit"
"()</methodname>, and queried with <methodname>get_limit()</methodname>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5844(title)
msgid "Modifying the List of Recent Files"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5845(para)
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 ""

#: C/gtkmm-tutorial-in.xml:5852(para)
msgid ""
"In addition to changing a file's URI, you can also remove items from the "
"list, either one at a time or by clearint them all at once. The former is "
"accomplished with <methodname>remove_item()</methodname>, the latter with "
"<methodname>purge_items()</methodname>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5859(para)
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 ""

#: C/gtkmm-tutorial-in.xml:5871(title)
msgid "RecentChooser"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5876(para)
msgid ""
"<classname>RecentChooser</classname> is an interface that can be implemented "
"by widgets displaying the list of recently used files. <application>gtkmm</"
"application> provides three built-in implementations for choosing recent "
"files: <classname>RecentChooserWidget</classname>, "
"<classname>RecentChooserDialog</classname>, and "
"<classname>RecentChooserMenu</classname>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5884(para)
msgid ""
"<classname>RecentChooserWidget</classname> is a simple widget for displaying "
"a list of recently used files. <classname>RecentChooserWidget</classname> is "
"the basic building block for <classname>RecentChooserDialog</classname>, but "
"you can embed it into your user interface if you want to."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5891(para)
msgid ""
"The last class that implements the <classname>RecentChooser</classname> "
"interface is <classname>RecentChooserMenu</classname>. This class allows you "
"to list recently used files as a menu."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5897(title)
msgid "Simple RecentChooserWidget example"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5898(para)
msgid ""
"Shown below is a simple example of how to use the "
"<classname>RecentChooserDialog</classname> class in a program. This simple "
"program has a menubar with a \"Recent Files Dialog\" menu item. When you "
"select this menu item, a dialog pops up showing the list of recently used "
"files."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5906(para)
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 ""

#: C/gtkmm-tutorial-in.xml:5913(para)
msgid ""
"After selecting the <guimenuitem>Recent Files Dialog</guimenuitem> menu "
"item, you should see something similar to the following window."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5922(para)
msgid ""
"The constructor for <classname>ExampleWindow</classname> creates the menu "
"using <classname>UIManager</classname> (see <xref linkend=\"chapter-menus-"
"and-toolbars\"/> for more information). It then adds the menu and the "
"toolbar to the window."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5930(title)
msgid "Filtering Recent Files"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5931(para)
msgid ""
"For any of the <classname>RecentChooser</classname> classes, if you don't "
"wish to display all of the items in the list of recent files, you can filter "
"the list to show only those that you want. You can filter the list with the "
"help of the <classname>RecentFilter</classname> class. This class allows you "
"to filter recent files by their name (<methodname>add_pattern()</"
"methodname>), their mime type (<methodname>add_mime_type()</methodname>), "
"the application that registered them (<methodname>add_application()</"
"methodname>), or by a custom filter function (<methodname>add_custom()</"
"methodname>). It also provides the ability to filter based on how long ago "
"the file was modified and which groups it belongs to."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5944(para)
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>RecentChooser::add_filter()</methodname> function."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5954(title)
msgid "Plugs and Sockets"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5956(title)
msgid "Overview"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5957(para)
msgid ""
"From time to time, it may be useful to be able to embed a widget from "
"another application within your application. <application>gtkmm</"
"application> allows you to do this with the <classname>Gtk::Socket</"
"classname> and <classname>Gtk::Plug</classname> classes. It is not "
"anticipated that very many applications will need this functionality, but in "
"the rare case that you need to display a widget that is running in a "
"completely different process, these classes can be very helpful."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5966(para)
msgid ""
"The communication between a <classname>Socket</classname> and a "
"<classname>Plug</classname> follows the XEmbed protocol. This protocol has "
"also been implemented in other toolkits (e.g. Qt), which allows the same "
"level of integration when embedding a Qt widget in GTK+ or vice versa."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5972(para)
msgid ""
"The way that <classname>Sockets</classname> and <classname>Plugs</classname> "
"work together is through their window ids. Both a <classname>Socket</"
"classname> and a <classname>Plug</classname> have IDs that can be retrieved "
"with their <methodname>get_id()</methodname> member functions. The use of "
"these IDs will be explained below in <xref linkend=\"sec-connecting-plugs-"
"sockets\"/>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5981(title)
msgid "Sockets"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5982(para)
msgid ""
"A <classname>Socket</classname> is a special kind of container widget that "
"provides the ability to embed widgets from one process into another process "
"in a way that is transparent to the user."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5989(title)
msgid "Plugs"
msgstr ""

#: C/gtkmm-tutorial-in.xml:5990(para)
msgid ""
"A <classname>Plug</classname> is a special kind of Window that can be "
"plugged into a <classname>Socket</classname>. Besides the normal properties "
"and methods of <classname>Gtk::Window</classname>, a <classname>Plug</"
"classname> provides a constructor that takes the ID of a <classname>Socket</"
"classname>, which will automatically embed the <classname>Plug</classname> "
"into the <classname>Socket</classname> that matches that ID."
msgstr ""

#: C/gtkmm-tutorial-in.xml:5999(para)
msgid ""
"Since a <classname>Plug</classname> is just a special type of "
"<classname>Gtk::Window</classname> class, you can add containers or widgets "
"to it like you would to any other window."
msgstr ""

#: C/gtkmm-tutorial-in.xml:6006(title)
msgid "Connecting Plugs and Sockets"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6007(para)
msgid ""
"After a <classname>Socket</classname> or <classname>Plug</classname> object "
"is realized, you can obtain its ID with its <methodname>get_id()</"
"methodname> function. This ID can then be shared with other processes so "
"that other processes know how to connect to eachother."
msgstr ""

#: C/gtkmm-tutorial-in.xml:6018(para)
msgid ""
"Create a <classname>Socket</classname> object in one process and pass the ID "
"of that <classname>Socket</classname> to another process so that it can "
"create a <classname>Plug</classname> object by specifying the given "
"<classname>Socket</classname> ID in its constructor. There is no way to "
"assign a <classname>Plug</classname> to a particular <classname>Socket</"
"classname> after creation, so you must pass the <classname>Socket</"
"classname> ID to the <classname>Plug</classname>'s constructor."
msgstr ""

#: C/gtkmm-tutorial-in.xml:6031(para)
msgid ""
"Create a <classname>Plug</classname> independantly from any particular "
"<classname>Socket</classname> and pass the ID of the <classname>Plug</"
"classname> to other processes that need to use it. The ID of the "
"<classname>Plug</classname> can be associated with a particular "
"<classname>Socket</classname> object using the <methodname>Socket::add_id()</"
"methodname> function. This is the approach used in the example below."
msgstr ""

#: C/gtkmm-tutorial-in.xml:6014(para)
msgid "There are two basic strategies that can be used: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6046(title)
msgid "Plugs and Sockets Example"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6047(para)
msgid ""
"The following is a simple example of using sockets and plugs. The method of "
"communication between processes is deliberately kept very simple: The "
"<classname>Plug</classname> writes its ID out to a text file named "
"<filename>plug.id</filename> and the process with the socket reads the ID "
"from this files. In a real program, you may want to use a more sophisticated "
"method of inter-process communication."
msgstr ""

#: C/gtkmm-tutorial-in.xml:6056(para)
msgid ""
"This example creates two executable programs: <filename>socket</filename> "
"and <filename>plug</filename>. The idea is that <filename>socket</filename> "
"has an application window that will embed a widget from the <filename>plug</"
"filename> program. The way this example is designed, <filename>plug</"
"filename> must be running first before starting <filename>socket</filename>. "
"To see the example in action, execute the following commands in order from "
"within the example directory:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6065(para)
msgid ""
"Start the <filename>plug</filename> program and send it to the background "
"(or just use a different terminal)."
msgstr ""

#: C/gtkmm-tutorial-in.xml:6069(screen)
#, no-wrap
msgid "$ ./plug &amp;"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6070(para)
msgid "After which you should see something like the following:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6073(screen)
#, no-wrap
msgid "The window ID is: 69206019"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6074(para)
msgid "Then start the <filename>socket</filename> program:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6075(screen)
#, no-wrap
msgid "$ ./socket"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6076(para)
msgid ""
"After starting <filename>socket</filename>, you should see the following "
"output in the terminal:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6080(screen)
#, no-wrap
msgid ""
"I've been embedded.\n"
"A plug was added"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6082(para)
msgid ""
"The first line of output is from <filename>plug</filename>, after it has "
"been notified that it has been embedded inside of a <classname>Socket</"
"classname>. The second line was emitted by <filename>socket</filename> in "
"response to its <methodname>plug_added</methodname> signal. If everything "
"was done as described above, the <filename>socket</filename> window should "
"look roughly like the following:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6094(para)
msgid ""
"If for some reason the <classname>Socket</classname> couldn't attach the "
"<classname>Plug</classname>, the window would look something like this:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6105(title)
msgid "Timeouts, I/O and Idle Functions"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6108(title)
msgid "Timeouts"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6110(para)
msgid ""
"You may be wondering how to make <application>gtkmm</application> do useful "
"work while it's idling along (well, sleeping actually) in <methodname>Gtk::"
"Main::run()</methodname>. Happily, you have several options. Using the "
"following methods you can create a timeout method that will be called every "
"few milliseconds."
msgstr ""

#: C/gtkmm-tutorial-in.xml:6118(programlisting)
#, no-wrap
msgid ""
"\n"
"sigc::connection Glib::SignalTimeout::connect(const sigc::slot&lt;bool&gt;&amp; slot, unsigned int interval, int priority = Glib::PRIORITY_DEFAULT);\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6123(para)
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 ""

#: C/gtkmm-tutorial-in.xml:6133(programlisting)
#, no-wrap
msgid ""
"\n"
"my_connection.disconnect();\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6145(programlisting)
#, no-wrap
msgid ""
"\n"
"bool MyCallback() { std::cout &lt;&lt; \"Hello World!\\n\" &lt;&lt; std::endl; return true; }\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6138(para)
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: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6151(para)
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 ""

#: C/gtkmm-tutorial-in.xml:6157(para)
msgid "Here's an example of this technique:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6166(title)
msgid "Monitoring I/O"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6168(para)
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 ""

#: C/gtkmm-tutorial-in.xml:6176(programlisting)
#, no-wrap
msgid ""
"\n"
"sigc::connection Glib::SignalInput::connect(const sigc::slot&lt;bool,Glib::IOCondition&gt;&amp; slot,\n"
"                                    int fd, Glib::IOCondition condition,\n"
"                                    int priority = Glib::PRIORITY_DEFAULT);\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6183(para)
msgid ""
"The first argument is a slot you wish to have called when then 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 ""

#: C/gtkmm-tutorial-in.xml:6193(para)
msgid ""
"Glib::IO_IN - Call your method when there is data ready for reading on your "
"file descriptor."
msgstr ""

#: C/gtkmm-tutorial-in.xml:6201(para)
msgid ""
"Glib::IO_OUT - Call your method when the file descriptor is ready for "
"writing."
msgstr ""

#: C/gtkmm-tutorial-in.xml:6209(para)
msgid ""
"Glib::IO_PRI - Call your method when the file descriptor has urgent data to "
"be read."
msgstr ""

#: C/gtkmm-tutorial-in.xml:6216(para)
msgid ""
"Glib::IO_ERR - Call your method when an error has occurred on the file "
"descriptor."
msgstr ""

#: C/gtkmm-tutorial-in.xml:6223(para)
msgid ""
"Glib::IO_HUP - Call your method when hung up (the connection has been broken "
"usually for pipes and sockets)."
msgstr ""

#: C/gtkmm-tutorial-in.xml:6230(para)
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 ""

#: C/gtkmm-tutorial-in.xml:6237(programlisting)
#, no-wrap
msgid ""
"\n"
"bool input_callback(Glib::IOCondition condition);\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6242(para)
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)."
msgstr ""

#: C/gtkmm-tutorial-in.xml:6249(para)
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 ""

#: C/gtkmm-tutorial-in.xml:6263(title)
msgid "Idle Functions"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6265(para)
msgid ""
"If you want to specify a method that gets called when nothing else is "
"happening, use the following:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6270(programlisting)
#, no-wrap
msgid ""
"\n"
"sigc::connection  Glib::SignalIdle::connect(const sigc::slot&lt;bool&gt;&amp; slot, int priority = Glib::PRIORITY_DEFAULT_IDLE);\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6275(para)
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 ""

#: C/gtkmm-tutorial-in.xml:6285(programlisting)
#, no-wrap
msgid ""
"\n"
"bool idleFunc();\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6290(para)
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 ""

#: C/gtkmm-tutorial-in.xml:6297(para)
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 ""

#: C/gtkmm-tutorial-in.xml:6305(para)
msgid ""
"Try executing the example and increasing the system load. The upper progress "
"bar will increase steadily; the lower one will slow down."
msgstr ""

#: C/gtkmm-tutorial-in.xml:6315(title)
msgid "Memory management"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6321(title)
msgid "Normal C++ memory management"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6323(para)
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 ""

#: C/gtkmm-tutorial-in.xml:6335(para)
msgid "Here are some examples of normal C++ memory management:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6338(title)
msgid "Class Scope widgets"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6340(para)
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 ""

#: C/gtkmm-tutorial-in.xml:6347(para)
msgid ""
"The primary disadvantages of using class scope widgets are revealing the "
"class implementation rather than the class interface in the class header. "
"Class scope widgets also require Automatic widgets in class scope suffer the "
"same disadvantages as any other class scope automatic variable."
msgstr ""

#: C/gtkmm-tutorial-in.xml:6355(programlisting)
#, no-wrap
msgid ""
"\n"
"#include &lt;gtkmm/button.h&gt;\n"
"class Foo\n"
"{\n"
"private:\n"
"  Gtk::Button theButton;\n"
"  // will be destroyed when the Foo object is destroyed\n"
"};\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6368(title)
msgid "Function scope widgets"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6376(programlisting)
#, no-wrap
msgid ""
"\n"
"{\n"
"  Gtk::Button aButton;\n"
"  aButton.show();\n"
"  ...\n"
"  kit.run();\n"
"}\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6370(para)
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. <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6388(title)
msgid "Dynamic allocation with new and delete"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6390(para)
msgid ""
"Although, in most cases, the programmer will prefer to allow containers to "
"automatically destroy their children using <function>manage()</function> "
"(see below), the programmer is not required to use <function>manage()</"
"function>. The traditional <literal>new</literal> and <literal>delete</"
"literal> operators may also be used."
msgstr ""

#: C/gtkmm-tutorial-in.xml:6400(programlisting)
#, no-wrap
msgid ""
"\n"
"Gtk::Button* pButton = new Gtk::Button(\"Test\");\n"
"\n"
"// do something useful with pButton\n"
"\n"
"delete pButton;\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6398(para)
msgid ""
"<placeholder-1/> Here, the programmer deletes pButton to prevent a memory "
"leak."
msgstr ""

#: C/gtkmm-tutorial-in.xml:6415(title)
msgid "Managed Widgets"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6417(para)
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, first create it with <function>manage()</function> and pack it "
"into its container with <methodname>add()</methodname>. Now, the widget will "
"be destroyed whenever its container is destroyed."
msgstr ""

#: C/gtkmm-tutorial-in.xml:6427(title)
msgid "Dynamic allocation with manage() and add()"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6429(para)
msgid ""
"<application>gtkmm</application> provides the <function>manage()</function> "
"function and <methodname>add()</methodname> methods to create and destroy "
"widgets. Every widget except a top-level window must be added or packed into "
"a container in order to be displayed. The <function>manage()</function> "
"function marks a packed widget so that when the widget is added to a "
"container, the container becomes responsible for deleting the widget."
msgstr ""

#: C/gtkmm-tutorial-in.xml:6439(programlisting)
#, no-wrap
msgid ""
"\n"
"MyWidget::MyWidget()\n"
"{\n"
"  Gtk::Button* pButton = manage(new Gtk::Button(\"Test\"));\n"
"  add(*pButton); //add aButton to MyWidget\n"
"}\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6438(para)
msgid ""
"<placeholder-1/> Now, when objects of type <classname>MyWidget</classname> "
"are destroyed, the button will also be deleted. It is no longer necessary to "
"delete pButton to free the button's memory; its deletion has been delegated "
"to the <classname>MyWidget</classname> object."
msgstr ""

#: C/gtkmm-tutorial-in.xml:6453(para)
msgid ""
"<application>gtkmm</application> also provides the <methodname>set_manage()</"
"methodname> method for all widgets. This can be used to generate the same "
"result as <function>manage()</function>, but is more tedious:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6459(para)
msgid "foo.add( (w=new Gtk::Label(\"Hello\"), w-&gt;set_manage(), &amp;w) );"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6463(para)
msgid "is the same as"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6467(para)
msgid "foo.add( manage(new Gtk::Label(\"Hello\")) );"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6471(para)
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. For instance, your top-level Window might "
"just be an instance in your <function>main()</function> function.."
msgstr ""

#: C/gtkmm-tutorial-in.xml:6483(title)
msgid "Shared resources"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6485(para)
msgid ""
"Some objects, such as <classname>Gdk::Pixmap</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>RefPtr&lt;&gt;</classname> smartpointer."
msgstr ""

#: C/gtkmm-tutorial-in.xml:6497(programlisting)
#, no-wrap
msgid ""
"\n"
"Glib::RefPtr&lt;Gdk::Bitmap&gt; bitmap = Gdk::Bitmap::create(window, data, width, height);\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6494(para)
msgid ""
"Objects such as <classname>Gdk::Bitmap</classname> can only be instantiated "
"with a <methodname>create()</methodname> function. For instance, "
"<placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6506(programlisting)
#, no-wrap
msgid ""
"\n"
"if(bitmap)\n"
"{\n"
"  int depth = bitmap-&gt;get_depth().\n"
"}\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6502(para)
msgid ""
"You have no way of getting a bare <classname>Gdk::Bitmap</classname>. In the "
"example, <varname>bitmap</varname> is a smart pointer, so you can do this, "
"much like a normal pointer: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6514(para)
msgid ""
"When <varname>bitmap</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 ""

#: C/gtkmm-tutorial-in.xml:6522(programlisting)
#, no-wrap
msgid ""
"\n"
"Glib::RefPtr&lt;Gdk::Bitmap&gt; bitmap2 = bitmap.\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6520(para)
msgid ""
"If you copy a <classname>RefPtr</classname>, for instance <placeholder-1/> , "
"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 ""

#: C/gtkmm-tutorial-in.xml:6530(para)
msgid ""
"See the <link linkend=\"chapter-refptr\">appendix</link> for detailed "
"information about RefPtr."
msgstr ""

#: C/gtkmm-tutorial-in.xml:6535(para)
msgid "Bjarne Stroustrup, \"The C++ Programming Language\" - section 14.4.2"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6538(para)
msgid "Nicolai M. Josuttis, \"The C++ Standard Library\" - section 4.2"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6531(para)
msgid ""
"If you wish to learn more about smartpointers, you might look in these "
"books: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6549(title)
msgid "Glade and Gtk::Builder"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6550(para)
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 <application>Glade</application> 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 ""

#: C/gtkmm-tutorial-in.xml:6563(simpara)
msgid "Less C++ code is required."
msgstr ""

#: C/gtkmm-tutorial-in.xml:6564(simpara)
msgid "UI changes can be seen more quickly, so UIs are able to improve."
msgstr ""

#: C/gtkmm-tutorial-in.xml:6565(simpara)
msgid "Designers without programming skills can create and edit UIs."
msgstr ""

#: C/gtkmm-tutorial-in.xml:6560(para)
msgid "This has the following advantages: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6569(para)
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 ""

#: C/gtkmm-tutorial-in.xml:6576(title)
msgid "Loading the .glade file"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6581(programlisting)
#, no-wrap
msgid ""
"\n"
"Glib::RefPtr&lt;Gtk::Builder&gt; builder = Gtk::Builder::create_from_file(\"basic.glade\");\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6577(para)
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, "
"<placeholder-1/> This will instantiate the windows defined in the .glade "
"file, though they will not be shown immediately unless you have specified "
"that via the <guilabel>Properties</guilabel> window in <application>Glade</"
"application>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:6590(programlisting)
#, no-wrap
msgid ""
"\n"
"Glib::RefPtr&lt;Gtk::Builder&gt; builder = Gtk::Builder::create_from_file(\"basic.glade\", \"treeview_products\");\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6589(para)
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, "
"<placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6598(title)
msgid "Accessing widgets"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6606(programlisting)
#, no-wrap
msgid ""
"\n"
"Gtk::Dialog* pDialog = 0;\n"
"builder-&gt;get_widget(\"DialogBasic\", pDialog);\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6600(para)
msgid ""
"To access a widget, for instance to <methodname>show()</methodname> a "
"dialog, use the <methodname>get_widget()</methodname> method, providing the "
"widget's name. This name should be specified in the <application>Glade</"
"application> Properties window. If the widget could not be found, or is of "
"the wrong type, then the pointer will be set to 0. <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6612(para)
msgid ""
"<application>Gtk::Builder</application> 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 ""

#: C/gtkmm-tutorial-in.xml:6618(para)
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 ""

#: C/gtkmm-tutorial-in.xml:6627(para)
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. So, if you get only a child widget from "
"<application>Gtk::Builder</application>, instead of a whole window, then you "
"must either put it in a <classname>Container</classname> or delete it. "
"<classname>Windows</classname> (such as <classname>Dialogs</classname>) "
"cannot be managed because they have no parent container, so you must delete "
"them at some point."
msgstr ""

#: C/gtkmm-tutorial-in.xml:6641(para)
msgid ""
"This simple example shows how to load a <application>Glade</application> "
"file at runtime and access the widgets with <application>Gtk::Builder</"
"application>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:6654(title)
msgid "Using derived widgets"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6655(para)
msgid ""
"You can use <application>Glade</application> to layout your own custom "
"widgets derived from <application>gtkmm</application> widget classes. This "
"keeps your code organized and encapsulated. Of course you won't see the "
"exact appearance and properties of your derived widget in "
"<application>Glade</application>, but you can specify its location and child "
"widgets and the properties of its <application>gtkmm</application> base "
"class."
msgstr ""

#: C/gtkmm-tutorial-in.xml:6664(programlisting)
#, no-wrap
msgid ""
"\n"
"DerivedDialog* pDialog = 0;\n"
"builder-&gt;get_widget_derived(\"DialogBasic\", pDialog);\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6663(para)
msgid ""
"Use <methodname>Gtk::Builder::get_widget_derived()</methodname> like so: "
"<placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6670(para)
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::"
"Dialog</classname> typedefs <classname>BaseObjectType</classname> as "
"<type>GtkDialog</type>, for instance)."
msgstr ""

#: C/gtkmm-tutorial-in.xml:6680(programlisting)
#, no-wrap
msgid ""
"\n"
"DerivedDialog::DerivedDialog(BaseObjectType* cobject, const Glib::RefPtr&lt;Gtk::Builder&gt;&amp; builder)\n"
": Gtk::Dialog(cobject)\n"
"{\n"
"}\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6677(para)
msgid ""
"You must call the base class's constructor in the initialization list, "
"providing the C pointer. For instance, <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6692(programlisting)
#, no-wrap
msgid ""
"\n"
"DerivedDialog::DerivedDialog(BaseObjectType* cobject, const Glib::RefPtr&lt;Gtk::Builder&gt;&amp; builder)\n"
": Gtk::Dialog(cobject),\n"
"  m_builder(builder),\n"
"  m_pButton(0)\n"
"{\n"
"  //Get the Glade-instantiated Button, and connect a signal handler:\n"
"  m_builder-&gt;get_widget(\"quit_button\", m_pButton);\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 ""

#: C/gtkmm-tutorial-in.xml:6688(para)
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, <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6710(para)
msgid ""
"This example shows how to load a <application>Glade</application> file at "
"runtime and access the widgets via a derived class."
msgstr ""

#: C/gtkmm-tutorial-in.xml:6723(title)
msgid "Internationalization and Localization"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6725(para)
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 ""

#: C/gtkmm-tutorial-in.xml:6731(para)
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 ""

#: C/gtkmm-tutorial-in.xml:6737(para)
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 ""

#: C/gtkmm-tutorial-in.xml:6745(para)
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 ""

#: C/gtkmm-tutorial-in.xml:6753(para)
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 tramslation, and substitute "
"the translated text at runtime."
msgstr ""

#: C/gtkmm-tutorial-in.xml:6761(title)
msgid "Preparing your project"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6764(para)
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 <application>Glade</"
"application> files, into standard <application>gettext</"
"application><filename>.pot/.po</filename> files."
msgstr ""

#: C/gtkmm-tutorial-in.xml:6775(para)
msgid ""
"We also assume that you are using autotools (e.g. <application>automake</"
"application> and <application>autoconf</application>) to build your project, "
"and that you are using <ulink url=\"http://svn.gnome.org/viewcvs/gnome-"
"common/trunk/autogen.sh?view=markup\"><literal>./autogen.sh</literal> from "
"<application>gnome-common</application></ulink>, which, among other things, "
"takes care of some <application>intltool</application> initialization."
msgstr ""

#: C/gtkmm-tutorial-in.xml:6788(para)
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 ""

#: C/gtkmm-tutorial-in.xml:6798(para)
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 ""

#: C/gtkmm-tutorial-in.xml:6807(programlisting)
#, no-wrap
msgid ""
"# keep this file sorted alphabetically, one language code per line\n"
"de\n"
"ja"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6810(para)
msgid ""
"(In addition, you'd have the files <literal>ja.po</literal> and <literal>de."
"po</literal> in your <literal>po</literal> directory which contain the "
"German and Japanese translations, respectively.)"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6817(para)
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 ""

#: C/gtkmm-tutorial-in.xml:6826(programlisting)
#, no-wrap
msgid ""
"src/main.cc\n"
"src/other.cc"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6829(para)
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 "
"<application>Glade</application> UI files, xml, <ulink url=\"http://"
"standards.freedesktop.org/desktop-entry-spec/latest/\">.desktop files</"
"ulink> and several more. So, if you have designed some of the application UI "
"in <application>Glade</application> then also add your <filename>.glade</"
"filename> files to the list in <literal>POTFILES.in</literal>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:6842(para)
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 ""

#: C/gtkmm-tutorial-in.xml:6849(programlisting)
#, 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_GLIB_GNU_GETTEXT\n"
"\n"
"PROGRAMNAME_LOCALEDIR=[${datadir}/locale]\n"
"AC_SUBST(PROGRAMNAME_LOCALEDIR)"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6860(para)
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 ""

#: C/gtkmm-tutorial-in.xml:6871(para)
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 ""

#: C/gtkmm-tutorial-in.xml:6878(programlisting)
#, no-wrap
msgid ""
"INTLTOOL_FILES = intltool-extract.in \\\n"
"                 intltool-merge.in \\\n"
"                 intltool-update.in"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6876(para)
msgid "Define <literal>INTLTOOL_FILES</literal> as: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6884(para)
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 commands will be included in the source tarball."
msgstr ""

#: C/gtkmm-tutorial-in.xml:6894(programlisting)
#, no-wrap
msgid ""
"DISTCLEANFILES = ... intltool-extract \\\n"
"                 intltool-merge \\\n"
"                 intltool-update \\\n"
"                 po/.intltool-merge-cache"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6892(para)
msgid "Update your <literal>DISTCLEANFILES</literal>: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6867(para)
msgid "In the top-level Makefile.am: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6903(para)
msgid ""
"In your <literal>src/Makefile.am</literal>, update your "
"<literal>AM_CPPFLAGS</literal> to add the following preprocessor macro "
"definition:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6908(programlisting)
#, no-wrap
msgid "AM_CPPFLAGS = ... -DPROGRAMNAME_LOCALEDIR=\\\"${PROGRAMNAME_LOCALEDIR}\\\""
msgstr ""

#: C/gtkmm-tutorial-in.xml:6909(para)
msgid ""
"This macro will be used when you initialize <literal>gettext</literal> in "
"your source code."
msgstr ""

#: C/gtkmm-tutorial-in.xml:6916(title)
msgid "Marking strings for translation"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6918(para)
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 ""

#: C/gtkmm-tutorial-in.xml:6926(para)
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 ""

#: C/gtkmm-tutorial-in.xml:6938(programlisting)
#, no-wrap
msgid "display_message(\"Getting ready for i18n.\");"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6940(programlisting)
#, no-wrap
msgid "display_message(_(\"Getting ready for i18n.\"));"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6932(para)
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: <placeholder-1/> with: <placeholder-2/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6951(programlisting)
#, no-wrap
msgid "xgettext -a -o my-strings --omit-header *.cc *.h"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6943(para)
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: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6958(programlisting)
#, no-wrap
msgid ""
"bindtextdomain(GETTEXT_PACKAGE, PROGRAMNAME_LOCALEDIR);\n"
"bind_textdomain_codeset(GETTEXT_PACKAGE, \"UTF-8\");\n"
"textdomain(GETTEXT_PACKAGE);"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6954(para)
msgid ""
"Finally, to let you program use the translation for the current locale, add "
"this code to the beginning of your <filename>main.cc</filename> file, to "
"initialize gettext. <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6964(title)
msgid "How gettext works"
msgstr ""

#: C/gtkmm-tutorial-in.xml:6966(para)
msgid ""
"<application>intltool</application> / <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 <literal>msmerge</"
"literal> script is used to update the <filename>localename.po</filename> "
"files from the regenerated <filename>.pot</filename> file."
msgstr ""

#: C/gtkmm-tutorial-in.xml:6980(para)
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 ""

#: C/gtkmm-tutorial-in.xml:6987(para)
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 ""

#: C/gtkmm-tutorial-in.xml:6999(title)
msgid "Testing and adding translations"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7006(programlisting)
#, no-wrap
msgid "intltool-update --pot"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7001(para)
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: "
"<placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7009(para)
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 ""

#: C/gtkmm-tutorial-in.xml:7022(para)
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."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7032(title)
msgid "Resources"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7041(ulink)
msgid "Internationalizing GNOME applications"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7048(ulink)
msgid "Intltool README"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7054(ulink)
msgid "How to use GNOME CVS as a Translator"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7060(ulink)
msgid "gettext manual"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7066(literal)
msgid "gtkmm_hello"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7066(ulink) C/gtkmm-tutorial-in.xml:7072(ulink)
msgid "<placeholder-1/> example package"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7072(literal)
msgid "gnomemm_hello"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7034(para)
msgid ""
"More information about what lies behind the internationalization and "
"localization process is presented and demonstrated in: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7082(title)
msgid "Expecting UTF8"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7083(para)
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 ""

#: C/gtkmm-tutorial-in.xml:7090(para)
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 ""

#: C/gtkmm-tutorial-in.xml:7098(title)
msgid "Glib::ustring and std::iostreams"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7099(para)
msgid ""
"TODO: This section is not clear - it needs to spell things out more clearly "
"and obviously."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7115(programlisting)
#, no-wrap
msgid ""
"std::ostringstream output;\n"
"output.imbue(std::locale(\"\")); // use the user's locale for this stream\n"
"output &lt;&lt; percentage &lt;&lt; \" % done\";\n"
"label-&gt;set_text(Glib::locale_to_utf8(output.str()));"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7100(para)
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::"
"ustrings</classname> 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>: <placeholder-"
"1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7125(title)
msgid "Pitfalls"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7127(para)
msgid ""
"There are a few common mistakes that you would discover eventually yourself. "
"But this section might help you to avoid them."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7130(title)
msgid "Same strings, different semantics"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7132(para)
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 ""

#: C/gtkmm-tutorial-in.xml:7136(para)
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 ""

#: C/gtkmm-tutorial-in.xml:7146(programlisting)
#, 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 ""

#: C/gtkmm-tutorial-in.xml:7152(title)
msgid "Composition of strings"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7154(para)
msgid ""
"C programmers use <function>sprintf()</function> to compose and concatenate "
"strings. C++ favours 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 ""

#: C/gtkmm-tutorial-in.xml:7161(para)
msgid "For instance, this code would be problematic:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7163(programlisting)
#, 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 ""

#: C/gtkmm-tutorial-in.xml:7168(para)
msgid ""
"So you should either avoid this situation or revert to the C-style "
"<function>sprintf()</function>. One possible solution is the <ulink url="
"\"http://www.cs.auc.dk/~olau/compose/\">compose library</ulink> which "
"supports syntax such as:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7175(programlisting)
#, no-wrap
msgid "label.set_text(compose(_(\"Really delete %1 now?\"), filename));"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7179(title)
msgid "Assuming the displayed size of strings"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7181(para)
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 ""

#: C/gtkmm-tutorial-in.xml:7185(title)
msgid "Unusual words"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7187(para)
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 ""

#: C/gtkmm-tutorial-in.xml:7193(title)
msgid "Using non-ASCII characters in strings"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7195(para)
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 ""

#: C/gtkmm-tutorial-in.xml:7201(para)
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 charactger."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7209(title)
msgid "Getting help with translations"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7211(para)
msgid ""
"If your program is free software, there is a whole <literal>GNOME</literal> "
"subproject devoted to helping you make translations, the <ulink url=\"http://"
"developer.gnome.org/projects/gtp/\"><literal>GNOME</literal> Translation "
"Project</ulink>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7216(para)
msgid ""
"The way it works is that you contact the gnome-i18n mailing list to find out "
"how the translators can access your <filename>po/</filename> subdirectory, "
"and to add your project to the big <ulink url=\"http://developer.gnome.org/"
"projects/gtp/status/\">status tables</ulink>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7223(para)
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 ""

#: C/gtkmm-tutorial-in.xml:7235(para)
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 ""

#: C/gtkmm-tutorial-in.xml:7247(title) C/gtkmm-tutorial-in.xml:7336(title)
msgid "Custom Widgets"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7249(para)
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 behaviour. But you might occasionally find that no "
"suitable starting point already exists. In this case, you can implement a "
"widget from scratch."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7251(title)
msgid "Custom Containers"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7254(para)
msgid ""
"<methodname>on_size_request()</methodname>: Calculate the minimum height and "
"width needed by the container."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7255(para)
msgid ""
"<methodname>on_size_allocate()</methodname>: Position the child widgets, "
"given the height and width that the container has actually been given."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7256(para)
msgid ""
"<methodname>forall_vfunc()</methodname>: Call the same callback for each of "
"the children."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7257(para)
msgid "<methodname>on_add()</methodname>:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7258(para)
msgid "<methodname>on_remove()</methodname>:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7259(para)
msgid ""
"<methodname>child_type_vfunc()</methodname>: Return what type of child can "
"be added."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7252(para)
msgid ""
"When deriving from <classname>Gtk::Container</classname>, you should "
"override the following virtual methods: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7263(para)
msgid ""
"The <methodname>on_size_request()</methodname> and "
"<methodname>on_size_allocate()</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>on_size_request()</"
"methodname> might report the maximum of their widths and the sum of their "
"heights. 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 ""

#: C/gtkmm-tutorial-in.xml:7275(para)
msgid ""
"<methodname>on_size_allocate()</methodname>, however, receives the actual "
"height and width that the parent container has decided to give to your "
"widget. This might be more than the minimum, 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. "
"Its your container, so you decide. Don't forget to call "
"<methodname>set_allocation()</methodname> inside your "
"<methodname>on_size_allocate()</methodname> implementation to actually use "
"the allocated space that has been offered by the parent container."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7286(para)
msgid ""
"Unless your container is a top-level window that derives from "
"<classname>Gtk::Window</classname>, you should also call <methodname>Gtk::"
"Container::set_flags(Gtk::NO_WINDOW)</methodname> in your constructor. "
"Otherwise, your container will appear in its own window, regardless of what "
"container you put it in. And unless your container draws directly onto the "
"underlying <classname>Gdk::Window</classname>, you should probably call "
"<methodname>set_redraw_on_allocate(false)</methodname> to improve "
"performance."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7296(para)
msgid ""
"By overriding <methodname>forall_vfunc()</methodname> you can allow "
"applications to operate on all of the container's child widgets. For "
"instance, <methodname>show_all_children()</methodname> uses this to find all "
"the child widgets and show them."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7301(para)
msgid ""
"Although your container might have its own method to set the child widgets, "
"you should still provide an implementation for the virtual <methodname>on_add"
"()</methodname> and <methodname>on_remove()</methodname> methods from the "
"base class, so that the add() and remove() methods will do something "
"appropriate if they are called."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7307(para)
msgid ""
"Your implementation of the <methodname>child_type_vfunc()</methodname> "
"method should report the type of widget that may be added to your container, "
"if it is not yet full. This is usually <methodname>Gtk::Widget::get_type()</"
"methodname> to indicate that the container may contain any class derived "
"from <classname>Gtk::Widget</classname>. If the container may not contain "
"any more widgets, then this method should return <literal>G_TYPE_NONE</"
"literal>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7319(para)
msgid ""
"This example implements a container with two child widgets, one above the "
"other. Of course, in this case it would be far simpler just to use a "
"<classname>Gtk::VBox</classname>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7324(title)
msgid "Custom Container"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7337(para)
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 ""

#: C/gtkmm-tutorial-in.xml:7345(para)
msgid "This example implements a widget which draws a Penrose triangle."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7348(title)
msgid "Custom Widget"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7364(title)
msgid "Recommended Techniques"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7366(para)
msgid ""
"This section is simply a gathering of wisdom, general style guidelines and "
"hints for creating <application>gtkmm</application> applications."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7370(para)
msgid ""
"Use GNU <application>autoconf</application> and <application>automake</"
"application>! They are your friends :) <application>Automake</application> "
"examines C files, determines how they depend on each other, and generates a "
"<filename>Makefile</filename> so the files can be compiled in the correct "
"order. <application>Autoconf</application> permits automatic configuration "
"of software installation, handling a large number of system quirks to "
"increase portability.."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7380(para)
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 ""

#: C/gtkmm-tutorial-in.xml:7385(para)
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 uses 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 ""

#: C/gtkmm-tutorial-in.xml:7394(title)
msgid "Application Lifetime"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7395(para)
msgid ""
"Most applications will have only one <classname>Window</classname>, or only "
"one main window. These applications can use the <methodname>Gtk::Main::run"
"(Gtk::Window&amp;)</methodname> overload. It shows the window and returns "
"when the window has been hidden. This might happen when the user closes the "
"window, or when your code decides to <methodname>hide()</methodname> the "
"window. You can prevent the user from closing the window (for instance, if "
"there are unsaved changes) by overriding <methodname>Gtk::Window::"
"on_delete_event()</methodname>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7403(para)
msgid "Most of our examples use this technique."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7407(title)
msgid "Using a <application>gtkmm</application> widget"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7409(para)
msgid ""
"Our examples all tend to have the same structure. They follow these steps "
"for using a <classname>Widget</classname>:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7418(para)
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> in your code. Even when using the widget via a "
"pointer, it's still probably best to make that pointer a member variable of "
"a container class so that you can access it later."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7429(para)
msgid ""
"Set the attributes of the widget. If the widget has no default constructor, "
"then you will need to initialize the widget in the initalizer list of your "
"container class's constructor."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7435(para)
msgid "Connect any signals you wish to use to the appropriate handlers."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7441(para)
msgid ""
"Pack the widget into a container using the appropriate call, e.g. "
"<methodname>Gtk::Container::add()</methodname> or <methodname>pack_start()</"
"methodname>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7449(para)
msgid "Call <methodname>show()</methodname> to display the widget."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7458(para)
msgid ""
"<methodname>Gtk::Widget::show()</methodname> lets <application>gtkmm</"
"application> know that we have finished setting the attributes of the "
"widget, and that it is ready to be displayed. You can use <methodname>Gtk::"
"Widget::hide()</methodname> to make it disappear again. The order in which "
"you show the widgets is not important, but we do suggest that you show the "
"top-level window last; this way, the whole window will appear with its "
"contents already drawn. Otherwise, the user will first see a blank window, "
"into which the widgets will be gradually drawn."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7472(title)
msgid "Contributing"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7474(para)
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 ""

#: C/gtkmm-tutorial-in.xml:7480(para)
msgid ""
"Ideally, we would like you to <ulink url=\"http://www.gtkmm.org/bugs.shtml"
"\">provide a patch</ulink> to the <filename>docs/tutorial/C/gtkmm-tutorial-"
"in.xml</filename> file. This file is currently in the <literal>gtkmm-"
"documentation</literal> module in GNOME git."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7486(para)
msgid ""
"If you do decide to contribute, please post your contribution to the "
"<application>gtkmm</application> mailing list at <ulink url=\"mailto:gtkmm-"
"list@gnome.org\">&lt;gtkmm-list@gnome.org&gt;</ulink>. 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 ""

#: C/gtkmm-tutorial-in.xml:7498(title)
msgid "The RefPtr smartpointer"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7499(para)
msgid ""
"<classname>Glib::RefPtr</classname> is a smartpointer. Specifically, it is a "
"reference-counting smartpointer. You might be familiar with <literal>std::"
"auto_ptr&lt;&gt;</literal>, which is also a smartpointer, but <literal>Glib::"
"RefPtr&lt;&gt;</literal> is much simpler, and more useful. We expect a "
"future version of the C++ Standard Library to contain a reference-counting "
"shared smartpointer, and a future version of <application>gtkmm</"
"application> might possibly use that instead."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7509(para)
msgid ""
"A smartpointer acts much like a normal pointer. Here are a few examples."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7512(title)
msgid "Copying"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7513(para)
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 ""

#: C/gtkmm-tutorial-in.xml:7519(programlisting)
#, no-wrap
msgid ""
"\n"
"Glib::RefPtr&lt;Gdk::Bitmap&gt; refBitmap = Gdk::Bitmap::create(window,\n"
"data, width, height);\n"
"Glib::RefPtr&lt;Gdk::Bitmap&gt; refBitmap2 = refBitmap;\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7525(para)
msgid ""
"Of course this means that you can store <classname>RefPtrs</classname> in "
"standard containers, such as <classname>std::vector</classname> or "
"<classname>std::list</classname>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7530(programlisting)
#, no-wrap
msgid ""
"\n"
"std::list&lt; Glib::RefPtr&lt;Gdk::Pixmap&gt; &gt; listPixmaps;\n"
"Glib::RefPtr&lt;Gdk::Pixmap&gt; refPixmap = Gdk::Pixmap::create(window,\n"
"width, height, depth);\n"
"listPixmaps.push_back(refPixmap);\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7539(title)
msgid "Dereferencing"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7540(para)
msgid ""
"You can dereference a smartpointer with the -&gt; operator, to call the "
"methods of the underlying instance, just like a normal pointer."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7544(programlisting)
#, no-wrap
msgid ""
"\n"
"Glib::RefPtr&lt;Gdk::Bitmap&gt; refBitmap = Gdk::Bitmap::create(window,\n"
"data, width, height);\n"
"int depth = refBitmap-&gt;get_depth();\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7550(para)
msgid ""
"But unlike most smartpointers, you can't use the * operator to access the "
"underlying instance."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7554(programlisting)
#, no-wrap
msgid ""
"\n"
"Glib::RefPtr&lt;Gdk::Bitmap&gt; refBitmap = Gdk::Bitmap::create(window,\n"
"data, width, height);\n"
"Gdk::Bitmap* underlying = *refBitmap; //Syntax error - will not compile.\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7562(title)
msgid "Casting"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7563(para)
msgid ""
"You can cast <classname>RefPtrs</classname> to base types, just like normal "
"pointers."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7568(programlisting)
#, no-wrap
msgid ""
"\n"
"Glib::RefPtr&lt;Gtk::TreeStore&gt; refStore = Gtk::TreeStore::create(columns);\n"
"Glib::RefPtr&lt;Gtk::TreeModel&gt; refModel = refStore;\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7573(para)
msgid ""
"This means that any method which takes a <type>const Glib::RefPtr&lt;"
"BaseType&gt;</type> argument can also take a <type>const Glib::RefPtr&lt;"
"DerivedType&gt;</type>. The cast is implicit, just as it would be for a "
"normal pointer."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7577(para)
msgid ""
"You can also cast to a derived type, but the syntax is a little different "
"than with a normal pointer."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7581(programlisting)
#, no-wrap
msgid ""
"\n"
"Glib::RefPtr&lt;Gtk::TreeStore&gt; refStore =\n"
"Glib::RefPtr&lt;Gtk::TreeStore&gt;::cast_dynamic(refModel);\n"
"Glib::RefPtr&lt;Gtk::TreeStore&gt; refStore2 =\n"
"Glib::RefPtr&lt;Gtk::TreeStore&gt;::cast_static(refModel);\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7591(title)
msgid "Checking for null"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7592(para)
msgid ""
"Just like normal pointers, you can check whether a <classname>RefPtr</"
"classname> points to anything."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7597(programlisting)
#, no-wrap
msgid ""
"\n"
"Glib::RefPtr&lt;Gtk::TreeModel&gt; refModel = m_TreeView.get_model();\n"
"if(refModel)\n"
"{\n"
"  int cols_count = refModel-&gt;get_n_columns();\n"
"  ...\n"
"}\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7606(para)
msgid ""
"But unlike normal pointers, <classname>RefPtr</classname>s are automatically "
"initialized to null so you don't need to remember to do that yourself."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7613(title)
msgid "Constness"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7614(para)
msgid ""
"The use of the <literal>const</literal> keyword in C++ is not always clear. "
"You might not realise 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 ""

#: C/gtkmm-tutorial-in.xml:7620(para)
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 ""

#: C/gtkmm-tutorial-in.xml:7627(para)
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 ""

#: C/gtkmm-tutorial-in.xml:7642(title)
msgid "Connecting signal handlers"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7643(para)
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 ""

#: C/gtkmm-tutorial-in.xml:7653(para)
msgid "Here's an example of a signal handler being connected to a signal:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7658(programlisting)
#, 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"
"main()\n"
"{\n"
"    Gtk::Button button(\"Hello World\");\n"
"    button.signal_clicked().connect(sigc::ptr_fun(&amp;on_button_clicked));\n"
"}\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7674(para)
msgid ""
"There's rather a lot to think about in this (non-functional) code. First "
"let's identify the parties involved:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7682(para)
msgid "The signal handler is <methodname>on_button_clicked()</methodname>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7688(para)
msgid ""
"We're hooking it up to the <classname>Gtk::Button</classname> object called "
"<varname>button</varname>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7695(para)
msgid ""
"When the Button emits its <literal>clicked</literal> signal, "
"<methodname>on_button_clicked()</methodname> will be called."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7703(para)
msgid "Now let's look at the connection again:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7708(programlisting)
#, no-wrap
msgid ""
"\n"
"    ...\n"
"    button.signal_clicked().connect(sigc::ptr_fun(&amp;on_button_clicked));\n"
"    ...\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7715(para)
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 ""

#: C/gtkmm-tutorial-in.xml:7722(para)
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 ""

#: C/gtkmm-tutorial-in.xml:7731(para)
msgid "Here's a slightly larger example of slots in action:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7736(programlisting)
#, no-wrap
msgid ""
"\n"
"void on_button_clicked();\n"
"\n"
"class some_class\n"
"{\n"
"    void on_button_clicked();\n"
"};\n"
"\n"
"some_class some_object;\n"
"\n"
"main()\n"
"{\n"
"    Gtk::Button button;\n"
"    button.signal_clicked().connect( sigc::ptr_fun(&amp;on_button_clicked) );\n"
"    button.signal_clicked().connect( sigc::mem_fun(some_object, &amp;some_class::on_button_clicked) );\n"
"}\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7755(para)
msgid ""
"The first call to <methodname>connect()</methodname> is just like the one we "
"saw last time; nothing new here."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7758(para)
msgid ""
"The next is more interesting. <function>sigc::mem_fun()</function> is called "
"with two arguments. The first argument is <parameter>some_object</"
"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, in this case "
"<methodname>some_object.on_button_clicked()</methodname>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7768(para)
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 ""

#: C/gtkmm-tutorial-in.xml:7775(para)
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 ""

#: C/gtkmm-tutorial-in.xml:7787(title)
msgid "Writing signal handlers"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7789(para)
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 ""

#: C/gtkmm-tutorial-in.xml:7796(programlisting)
#, no-wrap
msgid ""
"\n"
"Glib::SignalProxy1&lt;bool, Gtk::DirectionType&gt; signal_focus()\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7801(para)
msgid ""
"Other than the signal's name (<literal>focus</literal>), two things are "
"important to note here: the number following the word "
"<classname>SignalProxy</classname> at the beginning (1, in this case), and "
"the types in the list (<type>bool</type> and <type>Gtk::DirectionType</"
"type>). The number indicates how many arguments the signal handler should "
"have; the first type, <type>bool</type>, is the type that the signal handler "
"should return; and the next type, <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 ""

#: C/gtkmm-tutorial-in.xml:7813(para)
msgid ""
"The same principles apply for signals which have more arguments. Here's one "
"with three (taken from <filename>&lt;gtkmm/editable.h&gt;</filename>):"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7819(programlisting)
#, no-wrap
msgid ""
"\n"
"Glib::SignalProxy3&lt;void, const Glib::ustring&amp;, int, int*&gt; signal_insert_text()\n"
"\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7825(para)
msgid ""
"It follows the same form. The number 3 at the end of the type's name "
"indicates that our signal handler will need three arguments. The first type "
"in the type list 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 ""

#: C/gtkmm-tutorial-in.xml:7834(programlisting)
#, no-wrap
msgid ""
"\n"
"void on_insert_text(const Glib::ustring&amp; text, int length, int* position);\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7841(title)
msgid "Disconnecting signal handlers"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7843(para)
msgid ""
"Let's take another look at a Signal's <literal>connect</literal> method:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7848(programlisting)
#, no-wrap
msgid ""
"\n"
"sigc::signal&lt;void,int&gt;::iterator signal&lt;void,int&gt;::connect( const sigc::slot&lt;void,int&gt;&amp; );\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7853(para)
msgid ""
"Notice that the return value is of type <classname>sigc::signal&lt;void,"
"int&gt;::iterator</classname>. This can be implicitely converted into a "
"<classname>sigc::connection</classname> which in turn can be used to control "
"the connection. By keeping a connection object you can disconnect its "
"associated signal handler using the method <methodname>sigc::connection::"
"disconnect()</methodname>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7864(title)
msgid "Overriding default signal handlers"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7866(para)
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 ""

#: C/gtkmm-tutorial-in.xml:7873(para)
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 ""

#: C/gtkmm-tutorial-in.xml:7880(para)
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 ""

#: C/gtkmm-tutorial-in.xml:7885(para)
msgid ""
"<application>gtkmm</application> classes are designed with overriding in "
"mind; they contain virtual member methods specifically intended to be "
"overridden."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7890(para)
msgid "Let's look at an example of overriding:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7895(programlisting)
#, no-wrap
msgid ""
"\n"
"#include &lt;gtkmm/button.h&gt;\n"
"\n"
"class OverriddenButton : public Gtk::Button\n"
"{\n"
"protected:\n"
"    virtual void on_clicked();\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 ""

#: C/gtkmm-tutorial-in.xml:7914(para)
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 ""

#: C/gtkmm-tutorial-in.xml:7925(para)
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 signals, 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 ""

#: C/gtkmm-tutorial-in.xml:7939(title)
msgid "Binding extra arguments"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7947(programlisting)
#, no-wrap
msgid ""
"\n"
"m_button1.signal_clicked().connect( sigc::bind&lt;Glib::ustring&gt;( sigc::mem_fun(*this, &amp;HelloWorld::on_button_clicked), \"button 1\") );\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7954(programlisting)
#, no-wrap
msgid ""
"\n"
"virtual void on_button_clicked(Glib::ustring data);\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7940(para)
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, which you will "
"encounter later. <placeholder-1/> 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: <placeholder-2/> Of course, a normal \"clicked\" signal "
"handler would have no arguments."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7959(para)
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 ""

#: C/gtkmm-tutorial-in.xml:7971(title)
msgid "X Event signals"
msgstr ""

#: C/gtkmm-tutorial-in.xml:7972(para)
msgid ""
"The <classname>Widget</classname> class has some special signals which "
"correspond to the underlying X-Windows events. These are suffixed by "
"<literal>_event</literal>; for instance, <methodname>Widget::"
"signal_button_pressed_event()</methodname>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7978(para)
msgid ""
"You might occasionally find it useful to handle X 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 "
"<literal>button_pressed_event</literal> if you needed this information. X "
"events are also often used to handle key-presses."
msgstr ""

#: C/gtkmm-tutorial-in.xml:7987(para)
msgid ""
"These 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 ""

#: C/gtkmm-tutorial-in.xml:7992(para)
msgid ""
"Handling an X event doesn't affect the Widget's other signals. If you handle "
"<literal>button_pressed_event</literal> 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 ""

#: C/gtkmm-tutorial-in.xml:7999(para)
msgid ""
"Note also that not all widgets recieve all X events by default. To receive "
"additional X events, you can use <methodname>Gtk::Widget::set_events()</"
"methodname> before showing the widget, or <methodname>Gtk::Widget::add_events"
"()</methodname> after showing the widget. However, some widgets must first "
"be placed inside an <classname>EventBox</classname> widget. See the <link "
"linkend=\"chapter-widgets-without-xwindows\">Widgets Without X-Windows</"
"link> chapter."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8008(programlisting)
#, no-wrap
msgid ""
"\n"
"bool on_button_press(GdkEventButton* event);\n"
"Gtk::Button button(\"label\");\n"
"button.signal_button_press_event().connect( sigc::ptr_fun(&amp;on_button_press) );\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8006(para)
msgid "Here's a simple example: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8014(para)
msgid ""
"When the mouse is over the button and a mouse button is pressed, "
"<methodname>on_button_press()</methodname> will be called."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8019(para)
msgid ""
"<type>GdkEventButton</type> is a structure containing the event's "
"parameters, such as the coordinates of the mouse pointer at the time the "
"button was pressed. There are several different types of <type>GdkEvent</"
"type> structures for the various events."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8027(title)
msgid "Signal Handler sequence"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8029(programlisting)
#, no-wrap
msgid ""
"\n"
"button.signal_button_press_event().connect( sigc::ptr_fun(&amp;on_mywindow_button_press), false );\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8028(para)
msgid ""
"By default, your signal handlers are called after any previously-connected "
"signal handlers. However, this can be a problem with the X Event signals. "
"For instance, the existing signal handlers, or the default signal handler, "
"might return true to stop other signal handlers from being called. To "
"specify that your signal handler should be called before the other signal "
"handlers, so that will always be called, you can specify <literal>false</"
"literal> for the optional <literal>after</literal> parameter. For instance, "
"<placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8043(title)
msgid "Creating your own signals"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8044(para)
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 ""

#: C/gtkmm-tutorial-in.xml:8050(para)
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 ""

#: C/gtkmm-tutorial-in.xml:8061(programlisting)
#, no-wrap
msgid ""
"\n"
"sigc::signal&lt;void, bool int&gt; signal_something;\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8057(para)
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: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8069(programlisting)
#, no-wrap
msgid ""
"\n"
"class Server\n"
"{\n"
"public:\n"
"  //signal accessor:\n"
"  typedef sigc::signal&lt;void, bool, int&gt; type_signal_something;\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 ""

#: C/gtkmm-tutorial-in.xml:8065(para)
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: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8091(programlisting)
#, no-wrap
msgid ""
"\n"
"server.signal_something().connect(\n"
"  sigc::mem_fun(client, &amp;Client::on_server_something) );\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8088(para)
msgid ""
"You can then connect to the signal using the same syntax used when "
"connecting to <application>gtkmm</application> signals. For instance, "
"<placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8099(para)
msgid "This is a full working example that defines and uses custom signal."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8113(title)
msgid "Comparison with other signalling systems"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8114(para)
msgid ""
"TODO: Rewrite this paragraph and talk about Qt's moc. (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 ""

#: C/gtkmm-tutorial-in.xml:8128(para)
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 ""

#: C/gtkmm-tutorial-in.xml:8134(para)
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 ""

#: C/gtkmm-tutorial-in.xml:8142(para)
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 ""

#: C/gtkmm-tutorial-in.xml:8153(title)
msgid "<application>gtkmm</application> and Win32"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8154(para)
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 ""

#: C/gtkmm-tutorial-in.xml:8159(para)
msgid ""
"<application>gtkmm</application> currently works with the <ulink url="
"\"http://mingw.org/\">MingW/GCC3.4 compiler</ulink> and Microsoft Visual C++ "
"2005 or later (including the freely available express editions) on the "
"Windows platform. There is an <ulink url=\"ftp://ftp.gnome.org/pub/GNOME/"
"binaries/win32/gtkmm\"> installer</ulink> available for gtkmm on Microsoft "
"Windows. Refer to <ulink url=\"http://live.gnome.org/gtkmm/MSWindows/\"> "
"http://live.gnome.org/gtkmm/MSWindows</ulink> for instructions how to use it."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8171(title)
msgid "Building <application>gtkmm</application> on Win32"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8172(para)
msgid ""
"Please see <ulink url=\"http://live.gnome.org/gtkmm/MSWindows/BuildingGtkmm"
"\">http://live.gnome.org/gtkmm/MSWindows/BuildingGtkmm</ulink> for "
"instructions on how to build gtkmm on Windws."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8179(title)
msgid "Working with gtkmm's Source Code"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8180(para)
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 to 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 ""

#: C/gtkmm-tutorial-in.xml:8187(para)
msgid ""
"The easiest way to do this is using <ulink url=\"http://library.gnome.org/"
"devel/jhbuild/unstable/\">jhbuild</ulink>. <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 jhbuild 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 <ulink url=\"http://library.gnome.org/devel/jhbuild/unstable/"
"\">jhbuild manual</ulink>. If you need assistance using "
"<application>jhbuild</application>, you should ask for help on the <ulink "
"url=\"http://mail.gnome.org/mailman/listinfo/gnome-love\">gnome-love mailing "
"list</ulink>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8202(para)
msgid ""
"Note that to build <application>gtkmm</application> from git, you'll often "
"need to build all 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 ""

#: C/gtkmm-tutorial-in.xml:8210(title)
msgid "Setting up jhbuild"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8211(para)
msgid ""
"To set up <application>jhbuild</application>, follow the basic installation "
"instructions from the <ulink url=\"http://library.gnome.org/devel/jhbuild/"
"unstable/\">jhbuild manual</ulink>. After you've have installd "
"<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: <command>$ cp sample.jhbuildrc ~/.jhbuildrc</command>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8226(programlisting)
#, no-wrap
msgid "moduleset = 'gnome-2.30'"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8221(para)
msgid ""
"The <application>gtkmm</application> module is defined in the GNOME "
"moduleset (i.e. <filename>gnome-2.xx.modules</filename>, so edit your "
"<filename>.jhbuildrc</filename> file and set your moduleset setting to the "
"latest version of GNOME like so: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8232(programlisting)
#, no-wrap
msgid "modules = [ 'gtkmm', ]"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8228(para)
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: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8234(para)
msgid ""
"You can build all GNOME C++ modules by setting the <varname>modules</"
"varname> variable to the meta-package named <literal>meta-gnome-c++</"
"literal> or build all of the core GNOME modules with <literal>meta-gnome-"
"desktop</literal>. The <varname>modules</varname> variable specifies which "
"modules that 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 ""

#: C/gtkmm-tutorial-in.xml:8245(title)
msgid "Setting a prefix"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8246(para)
msgid ""
"By default, <application>jhbuild</application>'s configuration is configured "
"to install all software built with <application>jhbuild</application> under "
"the <filename>/opt/gnome2</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 ""

#: C/gtkmm-tutorial-in.xml:8260(title)
msgid ""
"Installing and Using the git version of <application>gtkmm</application>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8261(para)
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>$ jhbuild bootstrap\n"
"$ jhbuild sanitycheck</screen>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8272(title)
msgid ""
"Installing <application>gtkmm</application> with <application>jhbuild</"
"application>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8273(para)
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 ""

#: C/gtkmm-tutorial-in.xml:8280(para)
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 than 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 ""

#: C/gtkmm-tutorial-in.xml:8291(title)
msgid "Using the git version of <application>gtkmm</application>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8292(para)
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> 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 ""

#: C/gtkmm-tutorial-in.xml:8306(para)
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 ""

#: C/gtkmm-tutorial-in.xml:8323(title)
msgid "Wrapping C Libraries with gmmproc"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8324(para)
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 ""

#: C/gtkmm-tutorial-in.xml:8329(para)
msgid ""
"This involves a variety of tools, some of them crufty, but it does at least "
"work, and has been used successfully by several projects."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8334(title)
msgid "The build structure"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8335(para)
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>. 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 mm-common module. To get started, it helps a "
"lot to pick an existing binding module as an example to look at."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8342(para)
msgid ""
"For instance, let's pretend that we are wrapping a C library called "
"libexample. It provides a <classname>GObject</classname>-based API with "
"types named, for instance, <classname>ExampleThing</classname> and "
"<classname>ExampleStuff</classname>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8348(title)
msgid "Copying the skeleton project"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8353(programlisting)
#, no-wrap
msgid ""
"\n"
"  $ git clone git://git.gnome.org/mm-common\n"
"  $ cp -a mm-common/skeletonmm libsomethingmm\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8350(para)
msgid ""
"Typically our wrapper library would be called libsomethingmm. We can start "
"by copying the <ulink url=\"http://git.gnome.org/cgit/mm-common/tree/"
"skeletonmm\">skeleton source tree</ulink> from the mm-common module. "
"<placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8363(para)
msgid "<filename>libsomethingmm</filename>: The top-level directory."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8365(para)
msgid ""
"<filename>libsomething</filename>: Contains the main include file and the "
"pkg-config .pc file."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8367(para)
msgid "<filename>src</filename>: Contains .hg and .ccg source files."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8368(para)
msgid ""
"<filename>libsomethingmm</filename>: Contains generated and hand-written .h "
"and .cc files."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8370(para)
msgid ""
"<filename>private</filename>: Contains generated <filename>*_p.h</filename> "
"files."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8358(para)
msgid ""
"This provides a directory structure for the source .hg and .ccg files and "
"the generated .h and .cc files, with <filename>filelist.am</filename> "
"Automake include files that can specify the various files in use, in terms "
"of generic Automake variables. The directory structure usually looks like "
"this, after we have renamed the directories appropriately: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8382(programlisting)
#, 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 ""

#: C/gtkmm-tutorial-in.xml:8380(para)
msgid ""
"As well as renaming the directories, we should rename some of the source "
"files. For instance: <placeholder-1/> A number of the skeleton files must "
"still be filled in with project-specific content later."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8389(para)
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 ""

#: C/gtkmm-tutorial-in.xml:8395(title)
msgid "Modifying build files"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8397(para)
msgid ""
"Now we edit the files to adapt them to 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 Automake and Autoconf files."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8401(para)
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 ""

#: C/gtkmm-tutorial-in.xml:8405(para)
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 ""

#: C/gtkmm-tutorial-in.xml:8410(title)
msgid "configure.ac"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8413(para)
msgid ""
"The <function>AC_CONFIG_SRCDIR()</function> line must mention a file in our "
"source tree. We can edit this later if we don't yet know the names of any of "
"the files that we will create."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8416(para)
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 ""

#: C/gtkmm-tutorial-in.xml:8421(para)
msgid ""
"The <function>AC_CONFIG_HEADERS()</function> line is used to generate two or "
"more configuration header files. The first header file in the list contains "
"all configuration macros which are set during the configure run. The "
"remaining headers in the list contain only a subset of configuration macros "
"and their corresponding <filename>configh.h.in</filename> file will not be "
"autogenerated. The reason for this separation is that the namespaced "
"configuration headers are installed with your library and define publically "
"visible macros."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8429(para)
msgid ""
"The <function>AC_SUBST([SOMETHINGMM_MODULES], ['...'])</function> line may "
"need to be modified to check for the correct dependencies."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8431(para)
msgid ""
"The <function>AC_CONFIG_FILES()</function> block must mention the correct "
"directory names, as described above."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8411(para)
msgid "In <filename>configure.ac</filename>, <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8438(title)
msgid "Makefile.am files"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8441(para) C/gtkmm-tutorial-in.xml:8459(para)
msgid ""
"In <filename>skeleton/skeletonmm/Makefile.am</filename> we must mention the "
"correct names in the generic variables that are used elsewhere in the build "
"system:"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8446(varname)
msgid "binding_name"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8447(para)
msgid "The name of the library, such as libsomethingmm."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8451(varname)
msgid "wrap_init_flags"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8452(para)
msgid ""
"Additional command-line flags passed to the <filename>generate_wrap_init.pl</"
"filename> script, such as the C++ namespace and the parent directory prefix "
"of include files."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8464(varname)
msgid "lib_LTLIBRARIES"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8465(para)
msgid ""
"This variable must mention the correct library name, and this library name "
"must be used to form the <varname>_SOURCES</varname>, <varname>_LDFLAGS</"
"varname>, and <varname>_LIBADD</varname> variable names. It is permissible "
"to use variables substituted by <filename>configure</filename> like "
"<varname>@SOMETHINGMM_API_VERSION@</varname> as part of the variable names."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8474(varname)
msgid "AM_CPPFLAGS"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8475(para)
msgid "The command line options passed to the C preprocessor."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8479(varname)
msgid "AM_CXXFLAGS"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8480(para)
msgid "The command line options passed to the C++ compiler."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8439(para)
msgid ""
"Next we must adapt the various <filename>Makefile.am</filename> files: "
"<placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8490(title)
msgid "Creating .hg and .ccg files"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8491(para)
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 ""

#: C/gtkmm-tutorial-in.xml:8495(para)
msgid ""
"We must mention all of our <filename>.hg</filename> and <filename>.ccg</"
"filename> files in the <filename>skeleton/src/filelist.am</filename> file, "
"typically in the <varname>files_hg</varname> variable."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8499(para)
msgid ""
"Any additional non-generated <filename>.h</filename> and <filename>.cc</"
"filename> source files may be placed in <filename>skeleton/skeletonmm/</"
"filename> and listed in <filename>skeleton/skeletonmm/filelist.am</"
"filename>, typically in the <varname>files_extra_h</varname> and "
"<varname>files_extra_cc</varname> variables."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8505(para)
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 ""

#: C/gtkmm-tutorial-in.xml:8512(title)
msgid "Generating the .defs files."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8516(para)
msgid "objects (GObjects, widgets, interfaces, boxed-types and plain structs)"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8517(para)
msgid "functions"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8518(para)
msgid "enums"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8519(para)
msgid "signals"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8520(para)
msgid "properties"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8521(para)
msgid "vfuncs"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8513(para)
msgid ""
"The <filename>.defs</filename> file are text files, in a lisp format, that "
"describe the API of a C library, including its <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8530(filename)
msgid "gtk.defs"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8531(para)
msgid "Includes the other files."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8534(filename)
msgid "gtk_methods.defs"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8535(para)
msgid "Objects and functions."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8538(filename)
msgid "gtk_enums.defs"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8539(para)
msgid "Enumerations."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8542(filename)
msgid "gtk_signals.defs"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8543(para)
msgid "Signals and properties."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8546(filename)
msgid "gtk_vfuncs.defs"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8547(para)
msgid "vfuncs (function pointer member fields in structs), written by hand."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8524(para)
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: "
"<placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8553(title)
msgid "Generating the methods .defs"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8557(programlisting)
#, no-wrap
msgid ""
"\n"
"$ ./h2def.py /usr/include/gtk-2.0/gtk/*.h &gt; gtk_methods.defs\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8554(para)
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 pygobject's <filename>codegen</filename> directory. For instance, "
"<placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8564(title)
msgid "Generating the enums .defs"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8568(programlisting)
#, no-wrap
msgid ""
"\n"
"$ ./enum.pl /usr/include/gtk-2.0/gtk/*.h &gt; gtk_enums.defs\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8565(para)
msgid ""
"This <filename>.defs</filename> file describes enum types and their possible "
"values. It is generated by the <filename>enum.pl</filename> script which you "
"can find in glibmm's <filename>tools</filename> directory. For instance, "
"<placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8575(title)
msgid "Generating the signals and properties .defs"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8580(programlisting)
#, no-wrap
msgid ""
"\n"
"$ cd tools/extra_defs_gen\n"
"$ ./generate_extra_defs &gt; gtk_signals.defs\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8576(para)
msgid ""
"This <filename>.defs</filename> file describes signals and properties. It is "
"generated by the special <filename>extra_defs</filename> utility that is in "
"every wrapping project, such as <filename>gtkmm/tools/extra_defs_gen/</"
"filename>. For instance <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8585(para)
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>codegen/extradefs/"
"generate_extra_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>codegen/Makefile.am</"
"filename> file should also mention the new source filename."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8594(programlisting)
#, no-wrap
msgid ""
"\n"
"#include &lt;libsomething.h&gt;\n"
"\n"
"int main(int, char**)\n"
"{\n"
"  something_init();\n"
"\n"
"  std::cout &lt;&lt; get_defs(EXAMPLE_TYPE_SOMETHING)\n"
"            &lt;&lt; get_defs(EXAMPLE_TYPE_THING);\n"
"  return 0;\n"
"}\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8592(para)
msgid ""
"Then edit the <filename>.cc</filename> file to specify the correct types. "
"For instance, your <function>main()</function> function might look like "
"this: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8610(title)
msgid "Writing the vfuncs .defs"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8620(title)
msgid "The .hg and .ccg files"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8621(para)
msgid ""
"The .hg and .ccg source files are very much like .h anc .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 ""

#: C/gtkmm-tutorial-in.xml:8634(programlisting)
#, no-wrap
msgid ""
"\n"
"#include &lt;gtkmm/bin.h&gt;\n"
"#include &lt;gtkmm/stockid.h&gt;\n"
"_DEFS(gtkmm,gtk)\n"
"_PINCLUDE(gtkmm/private/bin_p.h)\n"
"\n"
"namespace Gtk\n"
"{\n"
"\n"
"class Button : public Bin\n"
"{\n"
"  _CLASS_GTKOBJECT(Button,GtkButton,GTK_BUTTON,Gtk::Bin,GtkBin)\n"
"public:\n"
"\n"
"  _CTOR_DEFAULT\n"
"  explicit Button(const Glib::ustring&amp; label, bool mnemonic = false);\n"
"  explicit Button(const StockID&amp; stock_id);\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 ""

#: C/gtkmm-tutorial-in.xml:8629(para)
msgid ""
"A .hg file will typically include some headers and then declare a class, "
"using some macros to add API or behaviour to this class. For instance, "
"gtkmm's <filename>button.hg</filename> looks roughly like this: <placeholder-"
"1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8669(function)
msgid "_DEFS()"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8670(para)
msgid ""
"Specifies the destination directry for generated sources, and the name of "
"the main .defs file that <command>gmmproc</command> should parse."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8673(function)
msgid "_PINCLUDE()"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8674(para)
msgid ""
"Tells <command>gmmproc</command> to include a header from the generated "
"private/button_p.h file."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8677(function)
msgid "_CLASS_GTKOBJECT()"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8678(para)
msgid ""
"Tells <command>gmmproc</command> to add some typedefs, constructors, and "
"standard methods to this class, as appropriate when wrapping a GtkObject-"
"derived type."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8681(term)
msgid ""
"<function>_WRAP_METHOD()</function>, <function>_WRAP_SIGNAL()</function>, "
"and <function>_WRAP_PROPERTY()</function>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8684(para)
msgid "Add methods to wrap parts of the C API."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8666(para)
msgid "The macros in this example do the following: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8691(programlisting)
#, no-wrap
msgid ""
"\n"
"$ cd gtk/src\n"
"$ /usr/lib/glibmm-2.4/proc/gmmproc -I ../../tools/m4 --defs . button . ./../gtkmm\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8688(para)
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: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8696(para)
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 ""

#: C/gtkmm-tutorial-in.xml:8699(para)
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 ""

#: C/gtkmm-tutorial-in.xml:8704(para)
msgid "The macros are explained in more detail in the following sections."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8707(title)
msgid "m4 Conversions"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8714(programlisting)
#, no-wrap
msgid ""
"\n"
"_CONVERSION(`GtkTreeView*',`TreeView*',`Glib::wrap($3)')\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8708(para)
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. gmmproc takes this "
"information from an .m4 file in your <literal>tools/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 functon. For instance, "
"this tells gmmproc how to convert a GtkTreeView pointer to a Gtk::TreeView "
"pointer: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8719(para)
msgid ""
"<literal>$3</literal> will be replaced by the parameter name when this "
"conversion is used by gmmproc."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8726(programlisting)
#, 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 ""

#: C/gtkmm-tutorial-in.xml:8723(para)
msgid ""
"Some extra macros make this easier and consistent. Look in gtkmm's .m4 files "
"for examples. For instance: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8736(title)
msgid "Class macros"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8737(para)
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 ""

#: C/gtkmm-tutorial-in.xml:8742(para)
msgid ""
"Other macros, such as <function>_WRAP_METHOD()</function> and "
"<function>_SIGNAL()</function> may only be used after a call to a "
"<function>_CLASS_*</function> macro."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8747(title)
msgid "_CLASS_GOBJECT"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8748(para) C/gtkmm-tutorial-in.xml:8838(para)
msgid ""
"This macro declares a wrapper for a type that is derived from "
"<classname>GObject</classname>, but which is not derived from "
"<classname>GtkObject</classname>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8751(function)
msgid ""
"_CLASS_GOBJECT( C++ class, C class, C casting macro, C++ base class, C base "
"class )"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8753(programlisting)
#, no-wrap
msgid ""
"\n"
"_CLASS_GOBJECT(AccelGroup, GtkAccelGroup, GTK_ACCEL_GROUP, Glib::Object, GObject)\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8752(para)
msgid "For instance, from <filename>accelgroup.hg</filename>: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8760(title)
msgid "_CLASS_GTKOBJECT"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8761(para)
msgid ""
"This macro declares a wrapper for a type that is derived from "
"<classname>GtkObject</classname>, such as a widget or dialog."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8763(function)
msgid ""
"_CLASS_GTKOBJECT( C++ class, C class, C casting macro, C++ base class, C "
"base class )"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8765(programlisting)
#, no-wrap
msgid ""
"\n"
"_CLASS_GTKOBJECT(Button, GtkButton, GTK_BUTTON, Gtk::Bin, GtkBin)\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8764(para) C/gtkmm-tutorial-in.xml:9052(para)
#: C/gtkmm-tutorial-in.xml:9083(para)
msgid "For instance, from <filename>button.hg</filename>: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8772(title)
msgid "_CLASS_BOXEDTYPE"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8773(para)
msgid ""
"This macro declares a wrapper for a non-<classname>GObject</classname> "
"struct, registered with <function>g_boxed_type_register_static()</function>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8776(function)
msgid ""
"_CLASS_BOXEDTYPE( C++ class, C class, new function, copy function, free "
"function )"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8778(programlisting)
#, no-wrap
msgid ""
"\n"
"_CLASS_BOXEDTYPE(Color, GdkColor, NONE, gdk_color_copy, gdk_color_free)\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8777(para)
msgid "For instance, for <classname>Gdk::Color</classname>: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8785(title)
msgid "_CLASS_BOXEDTYPE_STATIC"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8786(para)
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 ""

#: C/gtkmm-tutorial-in.xml:8790(function)
msgid "_CLASS_BOXEDTYPE_STATIC( C++ class, C class )"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8792(programlisting)
#, no-wrap
msgid ""
"\n"
"_CLASS_BOXEDTYPE_STATIC(Rectangle, GdkRectangle)\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8791(para)
msgid ""
"For instance, for <classname>Gdk::Rectangle</classname>: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8799(title)
msgid "_CLASS_OPAQUE_COPYABLE"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8800(para)
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 ""

#: C/gtkmm-tutorial-in.xml:8803(function)
msgid ""
"_CLASS_OPAQUE_COPYABLE( C++ class, C class, new function, copy function, "
"free function )"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8805(programlisting)
#, no-wrap
msgid ""
"\n"
"_CLASS_OPAQUE_COPYABLE(Region, GdkRegion, gdk_region_new, gdk_region_copy, gdk_region_destroy)\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8804(para)
msgid "For instance, for <classname>Gdk::Region</classname>: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8812(title)
msgid "_CLASS_OPAQUE_REFCOUNTED"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8813(para)
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 ""

#: C/gtkmm-tutorial-in.xml:8816(function)
msgid ""
"_CLASS_OPAQUE_COPYABLE( C++ class, C class, new function, ref function, "
"unref function )"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8818(programlisting)
#, no-wrap
msgid ""
"\n"
"_CLASS_OPAQUE_REFCOUNTED(Coverage, PangoCoverage, pango_coverage_new, pango_coverage_ref, pango_coverage_unref)\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8817(para)
msgid ""
"For instance, for <classname>Pango::Coverage</classname>: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8825(title)
msgid "_CLASS_GENERIC"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8826(para)
msgid ""
"This macro can be used to wrap structs which don't fit into any specialized "
"category."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8828(function)
msgid "_CLASS_GENERIC( C++ class, C class )"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8830(programlisting)
#, no-wrap
msgid ""
"\n"
"_CLASS_GENERIC(AttrIter, PangoAttrIterator)\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8829(para)
msgid ""
"For instance, for <classname>Pango::AttrIter</classname>: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8837(title)
msgid "_CLASS_INTERFACE"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8842(function)
msgid ""
"_CLASS_INTERFACE( C++ class, C class, C casting macro, C interface struct, "
"Base C++ class (optional), Base C class (optional) )"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8845(programlisting)
#, no-wrap
msgid ""
"\n"
"  _CLASS_INTERFACE(CellEditable, GtkCellEditable, GTK_CELL_EDITABLE, GtkCellEditableIface)\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8843(para)
msgid ""
"For instance, from <filename>celleditable.hg</filename>: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8852(programlisting)
#, no-wrap
msgid ""
"\n"
"  _CLASS_INTERFACE(LoadableIcon, GLoadableIcon, G_LOADABLE_ICON, GLoadableIconIface, Icon, GIcon)\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8849(para)
msgid ""
"Two extra parameters are optional, for the case that the interface derives "
"from another interface, which should be the case when the GInterface has "
"another GInterface as a prerequisitite. For instance, from "
"<filename>loadableicon.hg</filename>: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8862(title)
msgid "Constructor macros"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8863(para)
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 gtkmm must actually instantiate derived "
"GTypes, and the <function>*_new()</function> C functions are meant only as "
"convenience functions for C programmers."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8878(programlisting)
#, no-wrap
msgid ""
"\n"
"class ActionGroup : public Glib::Object\n"
"{\n"
"  _CLASS_GOBJECT(ActionGroup, GtkActionGroup, GTK_ACTION_GROUP, Glib::Object, GObject)\n"
"\n"
"protected:\n"
"  _WRAP_CTOR(ActionGroup(const Glib::ustring&amp; name = Glib::ustring()), gtk_action_group_new)\n"
"\n"
"public:\n"
"  _WRAP_CREATE(const Glib::ustring&amp; name = Glib::ustring())\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8873(para)
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: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8892(title)
msgid "_CTOR_DEFAULT"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8893(para)
msgid "This macro creates a default constructor with no arguments."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8898(title)
msgid "_WRAP_CTOR"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8899(para)
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 ""

#: C/gtkmm-tutorial-in.xml:8908(title)
msgid "Hand-coding constructors"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8917(programlisting)
#, 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 ""

#: C/gtkmm-tutorial-in.xml:8909(para)
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>: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8929(title)
msgid "Method macros"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8932(title)
msgid "_WRAP_METHOD"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8933(para)
msgid "This macro generates the C++ method to wrap a C function."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8934(function)
msgid "_WRAP_METHOD( C++ method signature, C function name)"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8936(programlisting)
#, no-wrap
msgid ""
"\n"
"_WRAP_METHOD(void set_text(const Glib::ustring&amp; text), gtk_entry_set_text)\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8935(para)
msgid "For instance, from <filename>entry.hg</filename>: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8940(para)
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 ""

#: C/gtkmm-tutorial-in.xml:8949(term)
msgid "refreturn"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8951(para)
msgid ""
"Do an extra reference() on the return value, in case the C function does not "
"provide a reference."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8956(term)
msgid "errthrow"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8958(para)
msgid "Use the last GError* parameter of the C function to throw an exception."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8963(term)
msgid "deprecated"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8965(para)
msgid ""
"Puts the generated code in #ifdef blocks. Text about the deprecation can be "
"specified as an optional parameter."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8971(term)
msgid "constversion"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8973(para)
msgid ""
"Just call the non-const version of the same function, instead of generating "
"almost duplicate code."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8946(para) C/gtkmm-tutorial-in.xml:9060(para)
msgid "There are some optional extra arguments: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8981(para)
msgid ""
"Objects used via <classname>RefPtr</classname>: Pass the <classname>RefPtr</"
"classname> as a const reference. For instance, <code>const Glib::RefPtr&lt;"
"Gtk::Action&gt;&amp; action</code>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8985(para)
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::Action&gt;&amp; action</code>."
msgstr ""

#: C/gtkmm-tutorial-in.xml:8990(para)
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 an appropriate intermediate "
"type, such as <classname>Glib::ListHandle</classname> or <classname>Glib::"
"SListHandle</classname>. These are templates, so you can specify the item "
"type. For instance, <code>Glib::ListHandle&lt; Glib::RefPtr&lt;Action&gt; "
"&gt;</code>. Existing typedefs exist for some common list types. You may "
"need to define a Traits type to specify how the C and C++ types should be "
"converted."
msgstr ""

#: C/gtkmm-tutorial-in.xml:9009(programlisting)
#, no-wrap
msgid "#m4 _CONVERSION(`GSList*', `Glib::SListHandle&lt;Widget*&gt;', `$2($3, Glib::OWNERSHIP_NONE)')"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9001(para)
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: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:8979(para)
msgid ""
"Though it's usually obvious what C++ types should be used in the C++ method, "
"here are some hints: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9015(title)
msgid "_WRAP_METHOD_DOCS_ONLY"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9016(para)
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 ""

#: C/gtkmm-tutorial-in.xml:9020(function)
msgid "_WRAP_METHOD_DOCS_ONLY(C function name)"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9022(programlisting)
#, no-wrap
msgid ""
"\n"
"_WRAP_METHOD_DOCS_ONLY(gtk_container_remove)\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9021(para)
msgid "For instance, from <filename>container.hg</filename>: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9029(title)
msgid "_IGNORE()"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9030(para)
msgid ""
"<command>gmmproc</command> will warn you on stdout about functions that you "
"have forgotten to wrap, helping to ensure that you are wrapping the complete "
"API. Buf if you don't want to wrap some functions or if you chose to hand-"
"code some methods then you can use the _IGNORE() macro the make "
"<command>gmmproc</command> stop complaining."
msgstr ""

#: C/gtkmm-tutorial-in.xml:9035(function)
msgid "_IGNORE(C function name 1, C function name2, etc)"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9037(programlisting)
#, no-wrap
msgid ""
"\n"
"_IGNORE(gtk_button_box_set_spacing, gtk_button_box_get_spacing,\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9036(para)
msgid "For instance, from <filename>buttonbox.hg</filename>: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9044(title)
msgid "_WRAP_SIGNAL"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9045(para)
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 ""

#: C/gtkmm-tutorial-in.xml:9051(function)
msgid "_WRAP_SIGNAL( C++ signal handler signature, C signal name)"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9053(programlisting)
#, no-wrap
msgid ""
"\n"
"_WRAP_SIGNAL(void clicked(),\"clicked\")\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9057(para)
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 ""

#: C/gtkmm-tutorial-in.xml:9063(term)
msgid "no_default_handler"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9065(para)
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."
msgstr ""

#: C/gtkmm-tutorial-in.xml:9077(title)
msgid "_WRAP_PROPERTY"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9078(para)
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 ""

#: C/gtkmm-tutorial-in.xml:9082(function)
msgid "_WRAP_PROPERTY(C property name, C++ type)"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9084(programlisting)
#, no-wrap
msgid ""
"\n"
"_WRAP_PROPERTY(\"label\", Glib::ustring)\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9093(title)
msgid "Other macros"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9095(title)
msgid "_WRAP_ENUM"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9096(para)
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 ""

#: C/gtkmm-tutorial-in.xml:9099(programlisting)
#, no-wrap
msgid ""
"\n"
"_WRAP_ENUM(WindowType, GdkWindowType)\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9098(para)
msgid "For instance, from <filename>widget.hg</filename>: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9103(para)
msgid ""
"If the enum is not a <classname>GType</classname>, you must pass a third "
"parameter NO_GTYPE. 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 regeistered as GTypes."
msgstr ""

#: C/gtkmm-tutorial-in.xml:9108(programlisting)
#, no-wrap
msgid ""
"\n"
"_WRAP_ENUM(IconLookupFlags, GtkIconLookupFlags)\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9107(para)
msgid "For example: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9115(title)
msgid "_WRAP_GERROR"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9116(para)
msgid ""
"This macro generates a C++ exception class, derived from Glib::Error, with a "
"Code enum and a code() method. You must specify the desired C++ name, the "
"name of the corresponding C enum, and the prefix for the C enum values."
msgstr ""

#: C/gtkmm-tutorial-in.xml:9119(para)
msgid ""
"This exception can then be thrown by methods which are generated from "
"_WRAP_METHOD() with the errthrow option."
msgstr ""

#: C/gtkmm-tutorial-in.xml:9121(programlisting)
#, no-wrap
msgid ""
"\n"
"_WRAP_GERROR(PixbufError, GdkPixbufError, GDK_PIXBUF_ERROR)\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9120(para)
msgid "For instance, from <filename>pixbuf.hg</filename>: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9128(title)
msgid "_MEMBER_GET / _MEMBER_SET"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9129(para)
msgid ""
"Use these macro 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 ""

#: C/gtkmm-tutorial-in.xml:9133(function)
msgid "_MEMBER_GET(C++ name, C name, C++ type, C type)"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9134(function)
msgid "_MEMBER_SET(C++ name, C name, C++ type, C type)"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9137(programlisting)
#, no-wrap
msgid "_MEMBER_GET(x, x, int, int)"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9135(para)
msgid "For example, in <filename>rectangle.hg</filename>: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9141(title)
msgid "_MEMBER_GET_PTR / _MEMBER_SET_PTR"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9142(para)
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 ""

#: C/gtkmm-tutorial-in.xml:9147(function)
msgid "_MEMBER_GET_PTR(C++ name, C name, C++ type, C type)"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9148(function)
msgid "_MEMBER_SET_PTR(C++ name, C name, C++ type, C type)"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9150(programlisting)
#, no-wrap
msgid ""
"\n"
"_MEMBER_GET_PTR(vbox, vbox, VBox*, GtkWidget*)\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9149(para)
msgid "For example, in <filename>dialog.hg</filename>: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9156(title)
msgid "_MEMBER_GET_GOBJECT / _MEMBER_SET_GOBJECT"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9157(para)
msgid ""
"Use this macro to provide getters and setters for a data member that is a "
"<classname>GObject</classname> type that must be referenced before being "
"returned."
msgstr ""

#: C/gtkmm-tutorial-in.xml:9162(function)
msgid "_MEMBER_GET_GOBJECT(C++ name, C name, C++ type, C type)"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9163(function)
msgid "_MEMBER_SET_GOBJECT(C++ name, C name, C++ type, C type)"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9165(programlisting)
#, no-wrap
msgid ""
"\n"
"_MEMBER_GET_GOBJECT(offscreen_pixmap, offscreen_pixmap, Gdk::Pixmap, GdkPixmap*)\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9164(para)
msgid "For example, in <filename>progress.hg</filename>: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9172(title)
msgid "Basic Types"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9173(para)
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 ""

#: C/gtkmm-tutorial-in.xml:9178(title)
msgid "Basic Type equivalents"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9180(segtitle)
msgid "C type"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9181(segtitle)
msgid "C++ type"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9182(type)
msgid "gboolean"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9182(type)
msgid "bool"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9183(type)
msgid "gint"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9183(type)
msgid "int"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9184(type)
msgid "guint"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9185(type)
msgid "gdouble"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9185(type)
msgid "double"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9186(type)
msgid "gunichar"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9187(type)
msgid "gchar*"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9187(classname)
msgid "std::string"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9187(seg)
msgid "<placeholder-1/> (or <placeholder-2/> for filenames)"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9194(title)
msgid "Hand-coded source files"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9195(para)
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>Makefile.am</filename> in the <varname>files_extra_h</"
"varname> and <varname>files_extra_cc</varname> variables."
msgstr ""

#: C/gtkmm-tutorial-in.xml:9205(title)
msgid "Initialization"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9214(programlisting)
#, no-wrap
msgid ""
"\n"
"void init()\n"
"{\n"
"  Gtk::Main::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 ""

#: C/gtkmm-tutorial-in.xml:9206(para)
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: <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9222(para)
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>init()</function> "
"function appears in the correct C++ namespace."
msgstr ""

#: C/gtkmm-tutorial-in.xml:9231(title)
msgid "Problems in the C API."
msgstr ""

#: C/gtkmm-tutorial-in.xml:9232(para)
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 ""

#: C/gtkmm-tutorial-in.xml:9234(title)
msgid "Unable to predeclare structs"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9236(programlisting)
#, no-wrap
msgid ""
"\n"
"typedef struct _ExampleWidget ExampleWidget;\n"
"\n"
"struct _ExampleWidget\n"
"{\n"
"  ...\n"
"};\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9235(para)
msgid ""
"By convention, structs are declared in glib/GTK+-style headers like so: "
"<placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9245(para)
msgid ""
"The extra typedef allows the struct to be used in a header without including "
"its full defintion, 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 ""

#: C/gtkmm-tutorial-in.xml:9248(programlisting)
#, 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 ""

#: C/gtkmm-tutorial-in.xml:9254(programlisting)
#, 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 ""

#: C/gtkmm-tutorial-in.xml:9246(para)
msgid ""
"This compiler error might look like this: <placeholder-1/> or this: "
"<placeholder-2/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9259(para)
msgid ""
"This is easy to correct in the C library, so do send a patch to the relevant "
"maintainer."
msgstr ""

#: C/gtkmm-tutorial-in.xml:9263(title)
msgid "Lack of properties"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9270(programlisting)
#, 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 ""

#: C/gtkmm-tutorial-in.xml:9264(para)
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, <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9277(para)
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 ""

#: C/gtkmm-tutorial-in.xml:9281(para)
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 ""

#: C/gtkmm-tutorial-in.xml:9289(programlisting)
#, 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 ""

#: C/gtkmm-tutorial-in.xml:9286(para)
msgid ""
"Another workaround is to add a <function>*_construct()</function> function "
"that the C++ constructor can call after instantiating its own type. For "
"instance, <placeholder-1/>"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9305(para)
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 ""

#: C/gtkmm-tutorial-in.xml:9313(title)
msgid "Documentation"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9314(para)
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 ""

#: C/gtkmm-tutorial-in.xml:9317(title)
msgid "Reusing C documentation"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9318(para)
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 and therefore have "
"source code comments formatted for gtk-doc and some extra documentation in ."
"tmpl files. The docextract_to_xml.py script, from pygobject's codegen "
"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 ""

#: C/gtkmm-tutorial-in.xml:9321(programlisting)
#, no-wrap
msgid "./docextract_to_xml.py -s /gnome/head/cvs/gtk+/gtk/ -s /gnome/head/cvs/gtk+/docs/reference/gtk/tmpl/ &gt; gtk_docs.xml\n"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9324(para)
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."
msgstr ""

#: C/gtkmm-tutorial-in.xml:9333(title)
msgid "Documentation build structure"
msgstr ""

#: C/gtkmm-tutorial-in.xml:9334(para)
msgid ""
"If you copied the skeleton source tree in mm-common and substituted the "
"placeholder text, then you will already have suitable <filename>Makefile.am</"
"filename> and <filename>Doxyfile.in</filename> files. With the mm-common "
"build setup, the list of Doxygen input files is not defined in the Doxygen "
"configuration file, but passed along from <command>make</command> to the "
"standard input of <command>doxygen</command>. The input file list is defined "
"by the <varname>doc_input</varname> variable in the <filename>Makefile.am</"
"filename> file."
msgstr ""

#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2
#: C/gtkmm-tutorial-in.xml:0(None)
msgid "translator-credits"
msgstr ""
"sweord <sweord@msn.com>, 2004\n"
"Tao Wang <dancefire@gmail.com>, 2010"

#~ msgid ""
#~ "Note that the <classname>XPMLabelBox</classname> class can be used to "
#~ "place XPMs and labels into any widget that can be a container."
#~ msgstr ""
#~ "请注意，<classname>XPMLabelBox</classname> 类可以用于将 XPM 和标签放置到任"
#~ "何容器组件。"
