Package ch.bailu.gtk.gobject
Klasse TypePlugin
java.lang.Object
ch.bailu.gtk.type.Type
ch.bailu.gtk.type.Pointer
ch.bailu.gtk.gobject.Object
ch.bailu.gtk.type.PropertyHolder
ch.bailu.gtk.type.Interface
ch.bailu.gtk.gobject.TypePlugin
- Alle implementierten Schnittstellen:
PointerInterface
An interface that handles the lifecycle of dynamically loaded types.
The GObject type system supports dynamic loading of types.
It goes as follows:
1. The type is initially introduced (usually upon loading the module
the first time, or by your main application that knows what modules
introduces what types), like this:
```c
new_type_id = g_type_register_dynamic (parent_type_id,
"TypeName",
new_type_plugin,
type_flags);
```
where `new_type_plugin` is an implementation of the
`GTypePlugin` interface.
2. The type's implementation is referenced, e.g. through
[func@GObject.TypeClass.ref] or through [func@GObject.type_create_instance]
(this is being called by [ctor@GObject.Object.new]) or through one of the above
done on a type derived from `new_type_id`.
3. This causes the type system to load the type's implementation by calling
[method@GObject.TypePlugin.use] and [method@GObject.TypePlugin.complete_type_info]
on `new_type_plugin`.
4. At some point the type's implementation isn't required anymore, e.g. after
[method@GObject.TypeClass.unref] or [func@GObject.type_free_instance]
(called when the reference count of an instance drops to zero).
5. This causes the type system to throw away the information retrieved
from [method@GObject.TypePlugin.complete_type_info] and then it calls
[method@GObject.TypePlugin.unuse] on `new_type_plugin`.
6. Things may repeat from the second step.
So basically, you need to implement a `GTypePlugin` type that
carries a use_count, once use_count goes from zero to one, you need
to load the implementation to successfully handle the upcoming
[method@GObject.TypePlugin.complete_type_info] call. Later, maybe after
succeeding use/unuse calls, once use_count drops to zero, you can
unload the implementation again. The type system makes sure to call
[method@GObject.TypePlugin.use] and [method@GObject.TypePlugin.complete_type_info]
again when the type is needed again.
[class@GObject.TypeModule] is an implementation of `GTypePlugin` that
already implements most of this except for the actual module loading and
unloading. It even handles multiple registered types per module.
The GObject type system supports dynamic loading of types.
It goes as follows:
1. The type is initially introduced (usually upon loading the module
the first time, or by your main application that knows what modules
introduces what types), like this:
```c
new_type_id = g_type_register_dynamic (parent_type_id,
"TypeName",
new_type_plugin,
type_flags);
```
where `new_type_plugin` is an implementation of the
`GTypePlugin` interface.
2. The type's implementation is referenced, e.g. through
[func@GObject.TypeClass.ref] or through [func@GObject.type_create_instance]
(this is being called by [ctor@GObject.Object.new]) or through one of the above
done on a type derived from `new_type_id`.
3. This causes the type system to load the type's implementation by calling
[method@GObject.TypePlugin.use] and [method@GObject.TypePlugin.complete_type_info]
on `new_type_plugin`.
4. At some point the type's implementation isn't required anymore, e.g. after
[method@GObject.TypeClass.unref] or [func@GObject.type_free_instance]
(called when the reference count of an instance drops to zero).
5. This causes the type system to throw away the information retrieved
from [method@GObject.TypePlugin.complete_type_info] and then it calls
[method@GObject.TypePlugin.unuse] on `new_type_plugin`.
6. Things may repeat from the second step.
So basically, you need to implement a `GTypePlugin` type that
carries a use_count, once use_count goes from zero to one, you need
to load the implementation to successfully handle the upcoming
[method@GObject.TypePlugin.complete_type_info] call. Later, maybe after
succeeding use/unuse calls, once use_count drops to zero, you can
unload the implementation again. The type system makes sure to call
[method@GObject.TypePlugin.use] and [method@GObject.TypePlugin.complete_type_info]
again when the type is needed again.
[class@GObject.TypeModule] is an implementation of `GTypePlugin` that
already implements most of this except for the actual module loading and
unloading. It even handles multiple registered types per module.
-
Verschachtelte Klassen - Übersicht
Von Klasse geerbte verschachtelte Klassen/Schnittstellen ch.bailu.gtk.gobject.Object
Object.OnBindingTransformFunc, Object.OnDestroyNotify, Object.OnDuplicateFunc, Object.OnNotify, Object.OnToggleNotify, Object.OnWeakNotify
-
Feldübersicht
Von Klasse geerbte Felder ch.bailu.gtk.gobject.Object
SIGNAL_ON_NOTIFY
-
Konstruktorübersicht
Konstruktoren -
Methodenübersicht
Modifizierer und TypMethodeBeschreibungvoid
completeInterfaceInfo
(long instance_type, long interface_type, InterfaceInfo info) Calls the @complete_interface_info function from the
#GTypePluginClass of @plugin.void
completeTypeInfo
(long g_type, TypeInfo info, TypeValueTable value_table) Calls the @complete_type_info function from the #GTypePluginClass of @plugin.static ClassHandler
static int
static long
static TypeSystem.TypeSize
static long
static TypeSystem.TypeSize
void
unuse()
Calls the @unuse_plugin function from the #GTypePluginClass of
@plugin.void
use()
Calls the @use_plugin function from the #GTypePluginClass of
@plugin.Von Klasse geerbte Methoden ch.bailu.gtk.type.PropertyHolder
getBooleanProperty, getIntProperty, getObjectProperty, getStringProperty, getStrProperty, setBooleanProperty, setIntProperty, setObjectProperty, setStringProperty, setStrProperty
Von Klasse geerbte Methoden ch.bailu.gtk.gobject.Object
addToggleRef, bindProperty, bindProperty, bindPropertyFull, bindPropertyFull, bindPropertyWithClosures, bindPropertyWithClosures, compatControl, connect, connect, disconnect, disconnect, dupData, dupData, dupQdata, forceFloating, freezeNotify, get, get, getData, getData, getProperty, getProperty, getQdata, interfaceFindProperty, interfaceInstallProperty, isFloating, notify, notify, notifyByPspec, onNotify, ref, refSink, removeToggleRef, replaceData, replaceData, replaceQdata, runDispose, set, set, setData, setData, setDataFull, setDataFull, setProperty, setProperty, setQdata, setQdataFull, stealData, stealData, stealQdata, takeRef, thawNotify, unref, watchClosure, weakRef, weakUnref
Von Klasse geerbte Methoden ch.bailu.gtk.type.Pointer
asCPointer, cast, connectSignal, disconnectSignals, disconnectSignals, equals, hashCode, throwIfNull, throwNullPointerException, toString, unregisterCallbacks, unregisterCallbacks
Von Klasse geerbte Methoden ch.bailu.gtk.type.Type
asCPointer, asCPointer, asCPointerNotNull, asJnaPointer, asJnaPointer, asPointer, asPointer, cast, cast, throwIfNull
Von Klasse geerbte Methoden java.lang.Object
clone, finalize, getClass, notify, notifyAll, wait, wait, wait
Von Schnittstelle geerbte Methoden ch.bailu.gtk.type.PointerInterface
asCPointerNotNull, asJnaPointer, asPointer, isNotNull, isNull
-
Konstruktordetails
-
TypePlugin
-
-
Methodendetails
-
getClassHandler
-
completeInterfaceInfo
public void completeInterfaceInfo(long instance_type, long interface_type, @Nonnull InterfaceInfo info) Calls the @complete_interface_info function from the
#GTypePluginClass of @plugin. There should be no need to use this
function outside of the GObject type system itself.- Parameter:
instance_type
- the #GType of an instantiatable type to which the interface is addedinterface_type
- the #GType of the interface whose info is completedinfo
- the #GInterfaceInfo to fill in
-
completeTypeInfo
public void completeTypeInfo(long g_type, @Nonnull TypeInfo info, @Nonnull TypeValueTable value_table) Calls the @complete_type_info function from the #GTypePluginClass of @plugin.
There should be no need to use this function outside of the GObject
type system itself.- Parameter:
g_type
- the #GType whose info is completedinfo
- the #GTypeInfo struct to fill invalue_table
- the #GTypeValueTable to fill in
-
unuse
public void unuse()Calls the @unuse_plugin function from the #GTypePluginClass of
@plugin. There should be no need to use this function outside of
the GObject type system itself. -
use
public void use()Calls the @use_plugin function from the #GTypePluginClass of
@plugin. There should be no need to use this function outside of
the GObject type system itself. -
getTypeID
public static long getTypeID() -
getParentTypeID
public static long getParentTypeID() -
getTypeSize
-
getParentTypeSize
-
getInstanceSize
public static int getInstanceSize()
-