glib/docs/reference/gobject/tmpl/gobject-unused.sgml

<!-- ##### SECTION ./tmpl/closures.sgml:Long_Description ##### -->
<para>

</para>


<!-- ##### SECTION ./tmpl/closures.sgml:See_Also ##### -->
<para>

</para>


<!-- ##### SECTION ./tmpl/closures.sgml:Short_Description ##### -->



<!-- ##### SECTION ./tmpl/closures.sgml:Title ##### -->
Closures


<!-- ##### SECTION ./tmpl/gtypemodule.sgml.sgml:Long_Description ##### -->
<para>

</para>


<!-- ##### SECTION ./tmpl/gtypemodule.sgml.sgml:See_Also ##### -->
<para>

</para>


<!-- ##### SECTION ./tmpl/gtypemodule.sgml.sgml:Short_Description ##### -->



<!-- ##### SECTION ./tmpl/gtypemodule.sgml.sgml:Title ##### -->
gtypemodule.sgml


<!-- ##### SECTION ./tmpl/signals.sgml:Long_Description ##### -->
<para>
The basic concept of the signal system is that of the <emphasis>emission</emphasis>
of a signal.
Signals are introduced per-type and are identified through strings.
Signals introduced for a parent type are availale in derived types as well,
so basically they are a per-type facility that is inherited.
A signal emission mainly involves invocation of a certain set of callbacks in
precisely defined manner. There are two main categories of such callbacks,
per-object
	<footnote><para> Although signals can deal with any kind of type, i'm
	referring to those types as "object types" in the following, simply
	because that is the context most users will encounter signals in.
	</para></footnote>
ones and user provided ones.
The per-object callbacks are most often referred to as "object method
handler" or "default (signal) handler", while user provided callbacks are
usually just called "signal handler".
The object method handler is provided at signal creation time (this most
frequently happens at the end of an object class' creation), while user
provided handlers are frequently connected and disconnected to/from a certain
signal on certain object instances.
</para>
<para>
A signal emission consists of five stages, unless prematurely stopped:
<variablelist>
  <varlistentry><term></term><listitem><para>
	1 - Invocation of the object method handler for %G_SIGNAL_RUN_FIRST signals
  </para></listitem></varlistentry>
  <varlistentry><term></term><listitem><para>
	2 - Invocation of normal user-provided signal handlers (<emphasis>after</emphasis> flag %FALSE)
  </para></listitem></varlistentry>
  <varlistentry><term></term><listitem><para>
	3 - Invocation of the object method handler for %G_SIGNAL_RUN_LAST signals
  </para></listitem></varlistentry>
  <varlistentry><term></term><listitem><para>
	4 - Invocation of user provided signal handlers, connected with an <emphasis>after</emphasis> flag of %TRUE
  </para></listitem></varlistentry>
  <varlistentry><term></term><listitem><para>
	5 - Invocation of the object method handler for %G_SIGNAL_RUN_CLEANUP signals
  </para></listitem></varlistentry>
</variablelist>
The user provided signal handlers are called in the order they were
connected in.
All handlers may prematurely stop a signal emission, and any number of
handlers may be connected, disconnected, blocked or unblocked during
a signal emission.
There are certain criteria for skipping user handlers in stages 2 and 4
of a signal emission.
First, user handlers may be <emphasis>blocked</emphasis>, blocked handlers are omitted
during callback invocation, to return from the "blocked" state, a
handler has to get unblocked exactly the same amount of times
it has been blocked before.
Second, upon emission of a %G_SIGNAL_DETAILED signal, an additional
"detail" argument passed in to g_signal_emit() has to match the detail
argument of the signal handler currently subject to invocation.
Specification of no detail argument for signal handlers (omission of the
detail part of the signal specification upon connection) serves as a
wildcard and matches any detail argument passed in to emission.
</para>


<!-- ##### SECTION ./tmpl/signals.sgml:See_Also ##### -->
<para>

</para>


<!-- ##### SECTION ./tmpl/signals.sgml:Short_Description ##### -->
Signals provide a means for customization of object behaviour and are used
as general purpose notification mechanism.


<!-- ##### SECTION ./tmpl/signals.sgml:Title ##### -->
Signals


<!-- ##### USER_FUNCTION GObjectGetParamFunc ##### -->
<para>

</para>

@object: 
@param_id: 
@value: 
@pspec: 
@trailer: 

<!-- ##### USER_FUNCTION GObjectSetParamFunc ##### -->
<para>

</para>

@object: 
@param_id: 
@value: 
@pspec: 
@trailer: 

<!-- ##### ENUM GSignalType ##### -->
<para>

</para>

@G_SIGNAL_RUN_FIRST: 
@G_SIGNAL_RUN_LAST: 
@G_SIGNAL_RUN_CLEANUP: 
@G_SIGNAL_NO_RECURSE: 
@G_SIGNAL_ACTION: 
@G_SIGNAL_NO_HOOKS: 

<!-- ##### USER_FUNCTION GTypePluginFillInterfaceInfo ##### -->
<para>

</para>

@plugin: 
@interface_type: 
@instance_type: 
@info: 

<!-- ##### USER_FUNCTION GTypePluginFillTypeInfo ##### -->
<para>

</para>

@plugin: 
@g_type: 
@info: 
@value_table: 

<!-- ##### USER_FUNCTION GTypePluginRef ##### -->
<para>

</para>

@plugin: 

<!-- ##### USER_FUNCTION GTypePluginUnRef ##### -->
<para>

</para>

@plugin: 

<!-- ##### STRUCT GTypePluginVTable ##### -->
<para>

</para>

@plugin_ref: 
@plugin_unref: 
@complete_type_info: 
@complete_interface_info: 

<!-- ##### MACRO G_IS_PARAM_VALUE ##### -->
<para>

</para>

@pspec: 
@value: 

<!-- ##### MACRO G_NOTIFY_PRIORITY ##### -->
<para>

</para>


<!-- ##### MACRO G_WARN_INVALID_PARAM_ID ##### -->
<para>

</para>

@object: 
@param_id: 
@pspec: 

<!-- ##### FUNCTION g_object_class_find_param_spec ##### -->
<para>

</para>

@oclass: 
@param_name: 
@Returns: 

<!-- ##### FUNCTION g_object_class_install_param ##### -->
<para>

</para>

@oclass: 
@param_id: 
@pspec: 

<!-- ##### FUNCTION g_object_get_param ##### -->
<para>

</para>

@object: 
@param_name: 
@value: 

<!-- ##### FUNCTION g_object_queue_param_changed ##### -->
<para>

</para>

@object: 
@param_name: 

<!-- ##### FUNCTION g_object_set_param ##### -->
<para>

</para>

@object: 
@param_name: 
@value: 

<!-- ##### FUNCTION g_param_spec_hash_table_insert ##### -->
<para>

</para>

@hash_table: 
@pspec: 
@owner_type: 

<!-- ##### FUNCTION g_param_spec_hash_table_lookup ##### -->
<para>

</para>

@hash_table: 
@param_name: 
@owner_type: 
@try_ancestors: 
@trailer: 
@Returns: 

<!-- ##### FUNCTION g_param_spec_hash_table_new ##### -->
<para>

</para>

@Returns: 

<!-- ##### FUNCTION g_param_spec_hash_table_remove ##### -->
<para>

</para>

@hash_table: 
@pspec: 

<!-- ##### FUNCTION g_signal_type_closure_new ##### -->
<para>

</para>

@itype: 
@struct_offset: 
@Returns: 

<!-- ##### FUNCTION g_signals_destroy ##### -->
<para>

</para>

@itype: 

<!-- ##### FUNCTION g_type_conforms_to ##### -->
<para>

</para>

@type: 
@iface_type: 
@Returns: 

<!-- ##### FUNCTION g_type_instance_conforms_to ##### -->
<para>

</para>

@instance: 
@iface_type: 
@Returns: 

<!-- ##### FUNCTION g_type_is_dynamic ##### -->
<para>

</para>

@type: 
@flags: 
@Returns: 

<!-- ##### FUNCTION g_type_value_conforms_to ##### -->
<para>

</para>

@value: 
@type: 
@Returns: