Fix some documentation typos

svn path=/trunk/; revision=7707
This commit is contained in:
Matthias Clasen 2008-11-28 23:53:13 +00:00
parent a44f5f6aaa
commit db830dd381
6 changed files with 30 additions and 13 deletions

View File

@ -1,3 +1,13 @@
2008-11-28 Matthias Clasen <mclasen@redhat.com>
Bug 559452 GObject Reference Manual (typo)
Bug 559462 GObject Reference Manual (typo)
Bug 559517 GObject Reference Manual (typo)
* gobject/tut_howto.xml:
* gobject/tut_gsignal.xml:
* gobject/tut_gobject.xml: Fix typos, found by Andrew Feren.
2008-11-28 Matthias Clasen <mclasen@redhat.com>
* gio/gio-sections.txt: Add g_app_info_get_commandline

View File

@ -725,7 +725,7 @@ g_object_set (G_OBJECT (foo),
<para>
These high level functions have one drawback - they don't provide a return result.
One should pay attention to the argument types and ranges when using them.
A know source of errors is to e.g. pass a gfloat instead of a gdouble and thus
A known source of errors is to e.g. pass a gfloat instead of a gdouble and thus
shifting all subsequent parameters by four bytes. Also forgetting the terminating
NULL will lead to unexpected behaviour.
</para>

View File

@ -501,7 +501,7 @@ void g_signal_emit_by_name (gpointer instance,
<para>
This completely optional filtering mechanism is mainly used as an optimization for signals
which are often emitted for many different reasons: the clients can filter out which events they are
interested into before the closure's marshalling code runs. For example, this is used extensively
interested in before the closure's marshalling code runs. For example, this is used extensively
by the <emphasis>notify</emphasis> signal of GObject: whenever a property is modified on a GObject,
instead of just emitting the <emphasis>notify</emphasis> signal, GObject associates as a detail to this
signal emission the name of the property modified. This allows clients who wish to be notified of changes

View File

@ -319,7 +319,7 @@ G_DEFINE_TYPE (MamanBar, maman_bar, G_TYPE_OBJECT);
static void
maman_bar_init (MamanBar *self)
{
self->private = MAMAN_BAR_GET_PRIVATE (self);
self->priv = MAMAN_BAR_GET_PRIVATE (self);
/* initialize all public and private members to reasonable default values. */

View File

@ -1,3 +1,10 @@
2008-11-28 Matthias Clasen <mclasen@redhat.com>
Bug 559456 GObject Reference Manual (typo)
* gsignal.c (g_signal_newv): Fix a typo in the docs, pointed out
by Andrew Feren
2008-11-03 Matthias Clasen <mclasen@redhat.com>
Bug 555935 Clear the mechanism of overwriting properties

View File

@ -1480,19 +1480,19 @@ signal_add_class_closure (SignalNode *node,
* g_signal_newv:
* @signal_name: the name for the signal
* @itype: the type this signal pertains to. It will also pertain to
* types which are derived from this type.
* types which are derived from this type
* @signal_flags: a combination of #GSignalFlags specifying detail of when
* the default handler is to be invoked. You should at least specify
* %G_SIGNAL_RUN_FIRST or %G_SIGNAL_RUN_LAST.
* @class_closure: The closure to invoke on signal emission; may be %NULL.
* @accumulator: the accumulator for this signal; may be %NULL.
* @accu_data: user data for the @accumulator.
* the default handler is to be invoked. You should at least specify
* %G_SIGNAL_RUN_FIRST or %G_SIGNAL_RUN_LAST
* @class_closure: The closure to invoke on signal emission; may be %NULL
* @accumulator: the accumulator for this signal; may be %NULL
* @accu_data: user data for the @accumulator
* @c_marshaller: the function to translate arrays of parameter values to
* signal emissions into C language callback invocations.
* signal emissions into C language callback invocations
* @return_type: the type of return value, or #G_TYPE_NONE for a signal
* without a return value.
* @n_params: the length of @param_types.
* @param_types: an array types, one for each parameter.
* without a return value
* @n_params: the length of @param_types
* @param_types: an array of types, one for each parameter
*
* Creates a new signal. (This is usually done in the class initializer.)
*