"The GType API is the foundation of the GObject system. It provides the facilities for registering and managing all fundamental data types, user-defined object and interface types." - GObject documentation
1 2 3 4 5
The name of a
GType system supports inheritance and interfaces, enabling the
psuedo-object-oriented system known as
GObject. However, they
also encompass all fundamental (primitive) types.
GType is considered a
transparent-type in RGtk2,
since you may specify one as either the type name or the numeric value
retrieved from some API function like
GType system obviously names primitive types different from the
corresponding types in R, but this is automatically taken care of for
you, so you can use R type names (ie, "character", "logical", etc) when
GType. This means that
gTypeFromName is not
that useful to the RGtk2 programmer.
All R objects representing external RGtk2 objects have their hierarchy
stored in the
class attribute. Everything descends from
"RGtkObject", then, for example, "GObject", etc. The types do not
necessarily correspond to
GTypes, but they do for all
GObjects and others. Thus,
gTypeGetAncestors is also of
little use unless one is working with pure
gTypeGetAncestors returns a vector of type names from which
gTypeGetInterfaces names the interfaces implemented by
gTypeFromName retrieves the numeric value of a type from its
gTypeGetClass returns the class instance for the type, for
gTypeGetSignals returns a list of signal ids with names for the
signals supported by the type.
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.