Lines Matching full:para
3 <para>
7 </para>
13 <para>
19 </para>
24 <para>
32 <listitem><para>If your users are a bit accustomed to GTK+ code or any
35 grumpy (not a good thing)</para></listitem>
36 <listitem><para>You must assess the fact that these conventions might
38 were at least partly right. Try to put your ego aside.</para></listitem>
40 </para>
42 <para>
45 <listitem><para>use a dash to separate the prefix from the typename:
47 (this is the convention used by Nautilus and most GNOME libraries).</para></listitem>
48 <listitem><para>use an underscore to separate the prefix from the
50 <filename>maman_bar.c</filename>.</para></listitem>
51 <listitem><para>Do not separate the prefix from the typename:
53 (this is the convention used by GTK+)</para></listitem>
57 </para>
59 <para>
68 </para>
70 <para>
75 <listitem><para>
130 </para></listitem>
131 <listitem><para>
147 </para></listitem>
148 <listitem><para>
199 </para></listitem>
201 <listitem><para>
207 </para></listitem>
209 </para>
211 <para>
216 <listitem><para>
220 </para></listitem>
221 <listitem><para>
228 </para></listitem>
230 </para>
237 <para>
263 </para>
265 <para>
280 </para>
282 <para>
288 </para>
294 <para>
298 </para>
300 <para>
308 </para>
310 <para>
314 </para>
316 <para>
331 </para>
333 <para>
363 </para>
365 <para>
370 </para>
372 <para>
378 </para>
384 <para>
390 </para>
392 <para>
464 </para>
466 <para>
469 </para>
471 <para>
476 </para>
482 <para>
490 <listitem><para>
492 </para></listitem>
493 <listitem><para>
495 </para></listitem>
496 <listitem><para>
498 </para></listitem>
500 </para>
505 <para>
523 </para>
525 <para>There is really nothing scary about this.</para>
531 <para>
565 </para>
567 <para>
575 </para>
577 <para>
581 </para>
583 <para>
623 </para>
629 <para>
670 </para>
672 <para>
686 </para>
688 <para>
700 </para>
707 <para>Chaining up is often loosely defined by the following set of
710 <listitem><para>Parent class A defines a public virtual method named <function>foo</function> and
711 provides a default implementation.</para></listitem>
712 <listitem><para>Child class B re-implements method <function>foo</function>.</para></listitem>
713 <listitem><para>In the method B::foo, the child class B calls its parent class method A::foo.</para></listitem>
717 <listitem><para>You need to change the behaviour of a class without modifying its code. You create
720 </para></listitem>
721 <listitem><para>You are lazy, you have access to the source code of the parent class but you don't want
723 to chain up than to modify the parent to call down.</para></listitem>
724 <listitem><para>You need to implement the Chain Of Responsibility pattern: each object of the inheritance
726 they each handler is run in turn.</para></listitem>
730 </para>
732 <para>
737 <para>
746 </para>
748 </para>
750 <para>The function <function><link linkend="g-type-class-peek-parent">g_type_class_peek_parent</link></function> is used to access the original parent
770 </para>
783 <para>
786 </para>
788 <para>
821 <listitem><para>
825 </para></listitem>
826 <listitem><para>
830 </para></listitem>
831 <listitem><para>
834 </para></listitem>
836 </para>
838 <para>
841 <listitem><para><function>maman_ibaz_get_type</function> registers the
843 </para></listitem>
844 <listitem><para><function>maman_ibaz_base_init</function> is expected
850 instantiation)</para></listitem>
851 <listitem><para><function>maman_ibaz_do_action</function> dereferences
853 </para></listitem>
896 </para>
902 <para>
904 </para>
906 <para>
943 </para>
945 <para>
960 </para>
962 <note><para>Classes can implement multiple interfaces by using multiple
964 to <function>G_DEFINE_TYPE_WITH_CODE</function>.</para></note>
966 <para>
991 </para>
998 <para>
1005 </para>
1007 <para>
1077 </para>
1083 <para>
1090 </para>
1092 <para>
1097 <para>
1099 </para>
1103 <para>
1107 </para>
1128 </para>
1130 <para>
1136 </para>
1138 <para>
1217 </para>
1226 <para>
1232 <para>A Python callback can be connected to any signal on any
1234 </para>
1240 </para>
1245 <para>
1259 </para>
1261 <para>
1293 </para>
1295 <para>
1302 </para>
1304 <para>
1310 </para>
1320 <para>
1327 </para>
1329 <para>
1334 </para>
1336 <para>
1348 </para>
1350 <para>
1378 </para>
1380 <para>
1392 </para>
1394 <para>
1407 </para>
1409 <para>
1419 </para>
1421 <para>
1461 </para>
1476 <para>For many historic reasons related to how the ancestor of GObject used to work in GTK+ 1.x versions,
1479 <para>I personally think that this method is horribly mind-twisting: it adds a new indirection
1488 </para>
1492 </para>
1494 <para>For example, <function><link linkend="g-signal-new">g_signal_new</link></function> can be used to create a signal which uses a default
1500 <para>I would like to point out here that the reason why the default handler of a signal is named everywhere
1503 </para>
1505 </para>
1507 <para>The following code shows the declaration of the <type>MamanFileSimple</type> class structure which contains
1550 <para>GSignal uses this offset to create a special wrapper closure
1552 </para>
1554 </para>
1556 <para>
1564 </para>
1566 <para>If you have doubts about which method to use, I would advise you to use the second one which
1570 </para>
1586 <para>Now that you know how to create signals to which the users can connect easily and at any point in
1591 </para>
1593 <para>
1596 <listitem><para>stop the emission of the signal at anytime</para></listitem>
1597 <listitem><para>override the default handler of the signal if it is stored as a function
1599 as discussed in the previous section).</para></listitem>
1601 </para>
1603 <para>
1609 </para>
1611 <para>
1615 </para>
1617 <para>
1623 </para>
1625 <para>
1628 </para>
1640 <para>
1644 </para>
1646 <para>
1665 </para>
1667 <para>
1694 </para>
1696 <para>
1704 </para>
1706 <para>
1711 </para>
