Optionalproperties: Partial<GioUnix.DesktopAppInfo.ConstructorProps>Internal$signalsCompile-time signal type information.
This instance property is generated only for TypeScript type checking. It is not defined at runtime and should not be accessed in JS code.
Static$gtypeAdds a content type to the application information to indicate the application is capable of opening files with the given content type.
a string.
TRUE on success, FALSE on error.
Obtains the information whether the Gio.AppInfo can be deleted. See Gio.AppInfo.delete.
TRUE if appinfo can be deleted
Checks if a supported content type can be removed from an application.
TRUE if it is possible to remove supported content types from a given appinfo, FALSE if not.
SignalconnectSignalconnect_Tries to delete a Gio.AppInfo.
On some platforms, there may be a difference between user-defined Gio.AppInfos which can be deleted, and system-wide ones which cannot. See Gio.AppInfo.can_delete.
TRUE if appinfo has been deleted
SignalemitChecks if two Gio.AppInfos are equal.
Note that the check may not compare each individual field, and only does an identity check. In case detecting changes in the contents is needed, program code must additionally compare relevant fields.
the second Gio.AppInfo.
TRUE if appinfo1 is equal to appinfo2. FALSE otherwise.
Gets the user-visible display name of the
‘additional application actions’
specified by action_name.
This corresponds to the Name key within the keyfile group for the
action.
the name of the action as from GioUnix.DesktopAppInfo.list_actions
the locale-specific action name
Looks up a boolean value in the keyfile backing info.
The key is looked up in the Desktop Entry group.
the key to look up
the boolean value, or FALSE if the key is not found
Gets the categories from the desktop file.
The unparsed Categories key from the desktop file; i.e. no attempt is made to split it by ; or validate it.
Gets the commandline with which the application will be started.
a string containing the appinfo’s commandline, or NULL if this information is not available
Gets a human-readable description of an installed application.
a string containing a description of the application appinfo, or NULL if none.
Gets the display name of the application. The display name is often more descriptive to the user than the name itself.
the display name of the application for appinfo, or the name if no display name is available.
Gets the executable’s name for the installed application.
This is intended to be used for debugging or labelling what program is going to be run. To launch the executable, use Gio.AppInfo.launch and related functions, rather than spawning the return value from this function.
a string containing the appinfo’s application binaries name
When info was created from a known filename, return it.
In some situations such as a GioUnix.DesktopAppInfo returned
from GioUnix.DesktopAppInfo.new_from_keyfile, this function
will return NULL.
The full path to the file for info, or NULL if not known.
Gets the ID of an application. An id is a string that identifies the application. The exact format of the id is platform dependent. For instance, on Unix this is the desktop file id from the xdg menu specification.
Note that the returned ID may be NULL, depending on how the appinfo has
been constructed.
a string containing the application’s ID.
A desktop file is hidden if the
Hidden key
in it is set to True.
TRUE if hidden, FALSE otherwise.
Looks up a localized string value in the keyfile backing info
translated to the current locale.
The key is looked up in the Desktop Entry group.
the key to look up
a newly allocated string, or NULL if the key is not found
Gets the installed name of the application.
the name of the application for appinfo.
Gets the value of the
NoDisplay key
which helps determine if the application info should be shown in menus. See
G_KEY_FILE_DESKTOP_KEY_NO_DISPLAY and Gio.AppInfo.should_show.
The value of the NoDisplay key
Checks if the application info should be shown in menus that list available
applications for a specific name of the desktop, based on the
OnlyShowIn
and NotShowIn
keys.
desktop_env should typically be given as NULL, in which case the
XDG_CURRENT_DESKTOP environment variable is consulted. If you want
to override the default mechanism then you may specify desktop_env,
but this is not recommended.
Note that Gio.AppInfo.should_show for info will include this check
(with NULL for desktop_env) as well as additional checks.
a string specifying a desktop name
TRUE if the info should be shown in desktop_env according to the OnlyShowIn and NotShowIn keys, FALSE otherwise.
Retrieves the StartupWMClass field from info. This represents the
WM_CLASS property of the main window of the application, if launched
through info.
the startup WM class, or NULL if none is set in the desktop file.
Looks up a string value in the keyfile backing info.
The key is looked up in the Desktop Entry group.
the key to look up
a newly allocated string, or NULL if the key is not found
Looks up a string list value in the keyfile backing info.
The key is looked up in the Desktop Entry group.
the key to look up
a NULL-terminated string array or NULL if the specified key cannot be found. The array should be freed with GLib.strfreev.
Retrieves the list of content types that app_info claims to support.
If this information is not provided by the environment, this function
will return NULL.
This function does not take in consideration associations added with Gio.AppInfo.add_supports_type, but only those exported directly by the application.
a list of content types.
Returns whether key exists in the Desktop Entry group
of the keyfile backing info.
the key to look up
TRUE if the key exists
Launches the application. Passes files to the launched application
as arguments, using the optional context to get information
about the details of the launcher (like what screen it is on).
On error, error will be set accordingly.
To launch the application without arguments pass a NULL files list.
Note that even if the launch is successful the application launched can fail to start if it runs into problems during startup. There is no way to detect this.
Some URIs can be changed when passed through a GFile (for instance unsupported URIs with strange formats like mailto:), so if you have a textual URI you want to pass in as argument, consider using Gio.AppInfo.launch_uris instead.
The launched application inherits the environment of the launching process, but it can be modified with Gio.AppLaunchContext.setenv and Gio.AppLaunchContext.unsetenv.
On UNIX, this function sets the GIO_LAUNCHED_DESKTOP_FILE
environment variable with the path of the launched desktop file and
GIO_LAUNCHED_DESKTOP_FILE_PID to the process id of the launched
process. This can be used to ignore GIO_LAUNCHED_DESKTOP_FILE,
should it be inherited by further processes. The DISPLAY,
XDG_ACTIVATION_TOKEN and DESKTOP_STARTUP_ID environment
variables are also set, based on information provided in context.
a list of Gio.File objects
the launch context
TRUE on successful launch, FALSE otherwise.
Activates the named application action.
You may only call this function on action names that were returned from GioUnix.DesktopAppInfo.list_actions.
Note that if the main entry of the desktop file indicates that the
application supports startup notification, and launch_context is
non-NULL, then startup notification will be used when activating the
action (and as such, invocation of the action on the receiving side
must signal the end of startup notification when it is completed).
This is the expected behaviour of applications declaring additional
actions, as per the
desktop file specification.
As with Gio.AppInfo.launch there is no way to detect failures that occur while using this function.
the name of the action as from GioUnix.DesktopAppInfo.list_actions
Launches the application. This passes the uris to the launched application
as arguments, using the optional context to get information
about the details of the launcher (like what screen it is on).
On error, error will be set accordingly. If the application only supports
one URI per invocation as part of their command-line, multiple instances
of the application will be spawned.
To launch the application without arguments pass a NULL uris list.
Note that even if the launch is successful the application launched can fail to start if it runs into problems during startup. There is no way to detect this.
a list of URIs to launch.
the launch context
TRUE on successful launch, FALSE otherwise.
This function performs the equivalent of Gio.AppInfo.launch_uris, but is intended primarily for operating system components that launch applications. Ordinary applications should use Gio.AppInfo.launch_uris.
If the application is launched via GSpawn, then spawn_flags, user_setup
and user_setup_data are used for the call to GLib.spawn_async.
Additionally, pid_callback (with pid_callback_data) will be called to
inform about the PID of the created process. See
GLib.spawn_async_with_pipes for information on certain parameter
conditions that can enable an optimized posix_spawn()
code path to be used.
If application launching occurs via some other mechanism (for example, D-Bus
activation) then spawn_flags, user_setup, user_setup_data,
pid_callback and pid_callback_data are ignored.
List of URIs
GLib.SpawnFlags, used for each process
a GLib.SpawnChildSetupFunc, used once for each process.
Callback for child processes
TRUE on successful launch, FALSE otherwise.
Equivalent to GioUnix.DesktopAppInfo.launch_uris_as_manager but allows you to pass in file descriptors for the stdin, stdout and stderr streams of the launched process.
If application launching occurs via some non-spawn mechanism (e.g. D-Bus
activation) then stdin_fd, stdout_fd and stderr_fd are ignored.
List of URIs
GLib.SpawnFlags, used for each process
a GLib.SpawnChildSetupFunc, used once for each process.
Callback for child processes
file descriptor to use for child’s stdin, or -1
file descriptor to use for child’s stdout, or -1
file descriptor to use for child’s stderr, or -1
TRUE on successful launch, FALSE otherwise.
Async version of Gio.AppInfo.launch_uris.
The callback is invoked immediately after the application launch, but it
waits for activation in case of D-Bus–activated applications and also provides
extended error information for sandboxed applications, see notes for
Gio.AppInfo.launch_default_for_uri_async.
a list of URIs to launch.
the launch context
Async version of Gio.AppInfo.launch_uris.
The callback is invoked immediately after the application launch, but it
waits for activation in case of D-Bus–activated applications and also provides
extended error information for sandboxed applications, see notes for
Gio.AppInfo.launch_default_for_uri_async.
a list of URIs to launch.
the launch context
a Gio.AsyncReadyCallback to call when the request is done
Async version of Gio.AppInfo.launch_uris.
The callback is invoked immediately after the application launch, but it
waits for activation in case of D-Bus–activated applications and also provides
extended error information for sandboxed applications, see notes for
Gio.AppInfo.launch_default_for_uri_async.
a list of URIs to launch.
the launch context
Optionalcallback: AsyncReadyCallback<GioUnix.DesktopAppInfo> | nulla Gio.AsyncReadyCallback to call when the request is done
Finishes a Gio.AppInfo.launch_uris_async operation.
the async result
TRUE on successful launch, FALSE otherwise.
Returns the list of ‘additional application actions’ supported on the desktop file, as per the desktop file specification.
As per the specification, this is the list of actions that are
explicitly listed in the Actions key of the Desktop Entry group.
a list of strings, always non-NULL
Removes a supported type from an application, if possible.
a string.
TRUE on success, FALSE on error.
Sets the application as the default handler for the given file extension.
a string containing the file extension (without the dot).
TRUE on success, FALSE on error.
Sets the application as the default handler for a given type.
the content type.
TRUE on success, FALSE on error.
Sets the application as the last used application for a given type. This will make the application appear as first in the list returned by Gio.AppInfo.get_recommended_for_type, regardless of the default application for that content type.
the content type.
TRUE on success, FALSE on error.
Checks if the application info should be shown in menus that list available applications.
TRUE if the appinfo should be shown, FALSE otherwise.
Checks if the application accepts files as arguments.
TRUE if the appinfo supports files.
Checks if the application supports reading files and directories from URIs.
TRUE if the appinfo supports URIs.
Virtualvfunc_Adds a content type to the application information to indicate the application is capable of opening files with the given content type.
a string.
Virtualvfunc_Obtains the information whether the Gio.AppInfo can be deleted. See Gio.AppInfo.delete.
Virtualvfunc_Checks if a supported content type can be removed from an application.
Virtualvfunc_Tries to delete a Gio.AppInfo.
On some platforms, there may be a difference between user-defined Gio.AppInfos which can be deleted, and system-wide ones which cannot. See Gio.AppInfo.can_delete.
Virtualvfunc_Creates a duplicate of a Gio.AppInfo.
Virtualvfunc_Checks if two Gio.AppInfos are equal.
Note that the check may not compare each individual field, and only does an identity check. In case detecting changes in the contents is needed, program code must additionally compare relevant fields.
the second Gio.AppInfo.
Virtualvfunc_Gets the commandline with which the application will be started.
Virtualvfunc_Gets a human-readable description of an installed application.
Virtualvfunc_Gets the display name of the application. The display name is often more descriptive to the user than the name itself.
Virtualvfunc_Gets the executable’s name for the installed application.
This is intended to be used for debugging or labelling what program is going to be run. To launch the executable, use Gio.AppInfo.launch and related functions, rather than spawning the return value from this function.
Virtualvfunc_Virtualvfunc_Gets the ID of an application. An id is a string that identifies the application. The exact format of the id is platform dependent. For instance, on Unix this is the desktop file id from the xdg menu specification.
Note that the returned ID may be NULL, depending on how the appinfo has
been constructed.
Virtualvfunc_Gets the installed name of the application.
Virtualvfunc_Retrieves the list of content types that app_info claims to support.
If this information is not provided by the environment, this function
will return NULL.
This function does not take in consideration associations added with Gio.AppInfo.add_supports_type, but only those exported directly by the application.
Virtualvfunc_Launches the application. Passes files to the launched application
as arguments, using the optional context to get information
about the details of the launcher (like what screen it is on).
On error, error will be set accordingly.
To launch the application without arguments pass a NULL files list.
Note that even if the launch is successful the application launched can fail to start if it runs into problems during startup. There is no way to detect this.
Some URIs can be changed when passed through a GFile (for instance unsupported URIs with strange formats like mailto:), so if you have a textual URI you want to pass in as argument, consider using Gio.AppInfo.launch_uris instead.
The launched application inherits the environment of the launching process, but it can be modified with Gio.AppLaunchContext.setenv and Gio.AppLaunchContext.unsetenv.
On UNIX, this function sets the GIO_LAUNCHED_DESKTOP_FILE
environment variable with the path of the launched desktop file and
GIO_LAUNCHED_DESKTOP_FILE_PID to the process id of the launched
process. This can be used to ignore GIO_LAUNCHED_DESKTOP_FILE,
should it be inherited by further processes. The DISPLAY,
XDG_ACTIVATION_TOKEN and DESKTOP_STARTUP_ID environment
variables are also set, based on information provided in context.
a list of Gio.File objects
the launch context
Virtualvfunc_Launches the application. This passes the uris to the launched application
as arguments, using the optional context to get information
about the details of the launcher (like what screen it is on).
On error, error will be set accordingly. If the application only supports
one URI per invocation as part of their command-line, multiple instances
of the application will be spawned.
To launch the application without arguments pass a NULL uris list.
Note that even if the launch is successful the application launched can fail to start if it runs into problems during startup. There is no way to detect this.
a list of URIs to launch.
the launch context
Virtualvfunc_Async version of Gio.AppInfo.launch_uris.
The callback is invoked immediately after the application launch, but it
waits for activation in case of D-Bus–activated applications and also provides
extended error information for sandboxed applications, see notes for
Gio.AppInfo.launch_default_for_uri_async.
a list of URIs to launch.
the launch context
a Gio.AsyncReadyCallback to call when the request is done
Virtualvfunc_Finishes a Gio.AppInfo.launch_uris_async operation.
the async result
Virtualvfunc_Removes a supported type from an application, if possible.
a string.
Virtualvfunc_Sets the application as the default handler for the given file extension.
a string containing the file extension (without the dot).
Virtualvfunc_Sets the application as the default handler for a given type.
the content type.
Virtualvfunc_Sets the application as the last used application for a given type. This will make the application appear as first in the list returned by Gio.AppInfo.get_recommended_for_type, regardless of the default application for that content type.
the content type.
Virtualvfunc_Checks if the application info should be shown in menus that list available applications.
Virtualvfunc_Checks if the application accepts files as arguments.
Virtualvfunc_Checks if the application supports reading files and directories from URIs.
Staticget_Gets all applications that implement interface.
An application implements an interface if that interface is listed in
the Implements line of the desktop file of the application.
the name of the interface
StaticnewStaticnew_Staticnew_StaticsearchSearches desktop files for ones that match search_string.
The return value is an array of strvs. Each strv contains a list of
applications that matched search_string with an equal score. The
outer list is sorted by score so that the first strv contains the
best-matching applications, and so on.
The algorithm for determining matches is undefined and may change at
any time.
None of the search results are subjected to the normal validation
checks performed by GioUnix.DesktopAppInfo.new (for example,
checking that the executable referenced by a result exists), and so it is
possible for GioUnix.DesktopAppInfo.new to return NULL when passed
an app ID returned by this function. It is expected that calling code will
do this when subsequently creating a GioUnix.DesktopAppInfo for
each result.
the search string to use
Staticset_Sets the name of the desktop that the application is running in.
This is used by Gio.AppInfo.should_show and
GioUnix.DesktopAppInfo.get_show_in to evaluate the
OnlyShowIn
and NotShowIn
keys.
Should be called only once; subsequent calls are ignored.
a string specifying what desktop this is
Creates a binding between source_property on source and target_property
on target.
Whenever the source_property is changed the target_property is
updated using the same value. For instance:
g_object_bind_property (action, "active", widget, "sensitive", 0);
Will result in the "sensitive" property of the widget GObject.Object instance to be updated with the same value of the "active" property of the action GObject.Object instance.
If flags contains GObject.BindingFlags.BIDIRECTIONAL then the binding will be mutual:
if target_property on target changes then the source_property on source
will be updated as well.
The binding will automatically be removed when either the source or the
target instances are finalized. To remove the binding without affecting the
source and the target you can just call g_object_unref() on the returned
GObject.Binding instance.
Removing the binding by calling g_object_unref() on it must only be done if
the binding, source and target are only used from a single thread and it
is clear that both source and target outlive the binding. Especially it
is not safe to rely on this if the binding, source or target can be
finalized from different threads. Keep another reference to the binding and
use g_binding_unbind() instead to be on the safe side.
A GObject.Object can have multiple bindings.
the property on source to bind
the target GObject.Object
the property on target to bind
flags to pass to GObject.Binding
the GObject.Binding instance representing the binding between the two GObject.Object instances. The binding is released whenever the GObject.Binding reference count reaches zero.
Creates a binding between source_property on source and target_property
on target, allowing you to set the transformation functions to be used by
the binding.
This function is the language bindings friendly version of
g_object_bind_property_full(), using GClosures instead of
function pointers.
the property on source to bind
the target GObject.Object
the property on target to bind
flags to pass to GObject.Binding
a GObject.Closure wrapping the transformation function from the source to the target, or null to use the default
a GObject.Closure wrapping the transformation function from the target to the source, or null to use the default
the GObject.Binding instance representing the binding between the two GObject.Object instances. The binding is released whenever the GObject.Binding reference count reaches zero.
Blocks a handler of an instance so it will not be called during any signal emissions
Handler ID of the handler to be blocked
Disconnects a handler from an instance so it will not be called during any future or currently ongoing emissions of the signal it has been connected to.
Handler ID of the handler to be disconnected
This function is intended for GObject.Object implementations to re-enforce
a [floating][floating-ref] object reference. Doing this is seldom
required: all GInitiallyUnowneds are created with a floating reference
which usually just needs to be sunken by calling g_object_ref_sink().
Increases the freeze count on object. If the freeze count is
non-zero, the emission of "notify" signals on object is
stopped. The signals are queued until the freeze count is decreased
to zero. Duplicate notifications are squashed so that at most one
GObject.Object::notify signal is emitted for each property modified while the
object is frozen.
This is necessary for accessors that modify multiple properties to prevent premature notification while the object is still being modified.
Gets a named field from the objects table of associations (see g_object_set_data()).
name of the key for that association
the data if found, or null if no such data exists.
Gets a property of an object.
The value can be:
In general, a copy is made of the property contents and the caller is responsible for freeing the memory by calling GObject.Value.unset.
Note that GObject.Object.get_property is really intended for language bindings, GObject.Object.get is much more convenient for C programming.
The name of the property to get
Return location for the property value. Can be an empty GObject.Value initialized by G_VALUE_INIT (auto-initialized with expected type since GLib 2.60), a GObject.Value initialized with the expected property type, or a GObject.Value initialized with a transformable type
This function gets back user data pointers stored via
g_object_set_qdata().
A GLib.Quark, naming the user data pointer
The user data pointer set, or null
Gets n_properties properties for an object.
Obtained properties will be set to values. All properties must be valid.
Warnings will be emitted and undefined behaviour may result if invalid
properties are passed in.
the names of each property to get
the values of each property to get
Checks whether object has a [floating][floating-ref] reference.
true if object has a floating reference
Emits a "notify" signal for the property property_name on object.
When possible, eg. when signaling a property change from within the class
that registered the property, you should use g_object_notify_by_pspec()
instead.
Note that emission of the notify signal may be blocked with
g_object_freeze_notify(). In this case, the signal emissions are queued
and will be emitted (in reverse order) when g_object_thaw_notify() is
called.
the name of a property installed on the class of object.
Emits a "notify" signal for the property specified by pspec on object.
This function omits the property name lookup, hence it is faster than
g_object_notify().
One way to avoid using g_object_notify() from within the
class that registered the properties, and using g_object_notify_by_pspec()
instead, is to store the GParamSpec used with
g_object_class_install_property() inside a static array, e.g.:
typedef enum
{
PROP_FOO = 1,
PROP_LAST
} MyObjectProperty;
static GParamSpec *properties[PROP_LAST];
static void
my_object_class_init (MyObjectClass *klass)
{
properties[PROP_FOO] = g_param_spec_int ("foo", NULL, NULL,
0, 100,
50,
G_PARAM_READWRITE | G_PARAM_STATIC_STRINGS);
g_object_class_install_property (gobject_class,
PROP_FOO,
properties[PROP_FOO]);
}
and then notify a change on the "foo" property with:
g_object_notify_by_pspec (self, properties[PROP_FOO]);
the GObject.ParamSpec of a property installed on the class of object.
Increases the reference count of object.
Since GLib 2.56, if GLIB_VERSION_MAX_ALLOWED is 2.56 or greater, the type
of object will be propagated to the return type (using the GCC typeof()
extension), so any casting the caller needs to do on the return type must be
explicit.
the same object
Increase the reference count of object, and possibly remove the
[floating][floating-ref] reference, if object has a floating reference.
In other words, if the object is floating, then this call "assumes ownership" of the floating reference, converting it to a normal reference by clearing the floating flag while leaving the reference count unchanged. If the object is not floating, then this call adds a new normal reference increasing the reference count by one.
Since GLib 2.56, the type of object will be propagated to the return type
under the same conditions as for g_object_ref().
object
Releases all references to other objects. This can be used to break reference cycles.
This function should only be called from object system implementations.
Sets multiple properties of an object at once. The properties argument should be a dictionary mapping property names to values.
Object containing the properties to set
Each object carries around a table of associations from strings to pointers. This function lets you set an association.
If the object already had an association with that name, the old association will be destroyed.
Internally, the key is converted to a GLib.Quark using g_quark_from_string().
This means a copy of key is kept permanently (even after object has been
finalized) — so it is recommended to only use a small, bounded set of values
for key in your program, to avoid the GLib.Quark storage growing unbounded.
name of the key
data to associate with that key
Sets a property on an object.
The name of the property to set
The value to set the property to
Remove a specified datum from the object's data associations, without invoking the association's destroy handler.
name of the key
the data if found, or null if no such data exists.
This function gets back user data pointers stored via
g_object_set_qdata() and removes the data from object
without invoking its destroy() function (if any was
set).
Usually, calling this function is only required to update
user data pointers with a destroy notifier, for example:
void
object_add_to_user_list (GObject *object,
const gchar *new_string)
{
// the quark, naming the object data
GQuark quark_string_list = g_quark_from_static_string ("my-string-list");
// retrieve the old string list
GList *list = g_object_steal_qdata (object, quark_string_list);
// prepend new string
list = g_list_prepend (list, g_strdup (new_string));
// this changed 'list', so we need to set it again
g_object_set_qdata_full (object, quark_string_list, list, free_string_list);
}
static void
free_string_list (gpointer data)
{
GList *node, *list = data;
for (node = list; node; node = node->next)
g_free (node->data);
g_list_free (list);
}
Using g_object_get_qdata() in the above example, instead of
g_object_steal_qdata() would have left the destroy function set,
and thus the partial string list would have been freed upon
g_object_set_qdata_full().
A GLib.Quark, naming the user data pointer
The user data pointer set, or null
Stops a signal's emission by the given signal name. This will prevent the default handler and any subsequent signal handlers from being invoked.
Name of the signal to stop emission of
Reverts the effect of a previous call to
g_object_freeze_notify(). The freeze count is decreased on object
and when it reaches zero, queued "notify" signals are emitted.
Duplicate notifications for each property are squashed so that at most one GObject.Object::notify signal is emitted for each property, in the reverse order in which they have been queued.
It is an error to call this function when the freeze count is zero.
Unblocks a handler so it will be called again during any signal emissions
Handler ID of the handler to be unblocked
Decreases the reference count of object. When its reference count
drops to 0, the object is finalized (i.e. its memory is freed).
If the pointer to the GObject.Object may be reused in future (for example, if it is
an instance variable of another object), it is recommended to clear the
pointer to null rather than retain a dangling pointer to a potentially
invalid GObject.Object instance. Use g_clear_object() for this.
Virtualvfunc_the constructed function is called by g_object_new() as the
final step of the object creation process. At the point of the call, all
construction properties have been set on the object. The purpose of this
call is to allow for object initialisation steps that can only be performed
after construction properties have been set. constructed implementors
should chain up to the constructed call of their parent class to allow it
to complete its initialisation.
Virtualvfunc_Virtualvfunc_the dispose function is supposed to drop all references to other
objects, but keep the instance otherwise intact, so that client method
invocations still work. It may be run multiple times (due to reference
loops). Before returning, dispose should chain up to the dispose method
of the parent class.
Virtualvfunc_instance finalization function, should finish the finalization of
the instance begun in dispose and chain up to the finalize method of the
parent class.
Virtualvfunc_Virtualvfunc_Emits a "notify" signal for the property property_name on object.
When possible, eg. when signaling a property change from within the class
that registered the property, you should use g_object_notify_by_pspec()
instead.
Note that emission of the notify signal may be blocked with
g_object_freeze_notify(). In this case, the signal emissions are queued
and will be emitted (in reverse order) when g_object_thaw_notify() is
called.
Virtualvfunc_the generic setter for all properties of this type. Should be
overridden for every type with properties. If implementations of
set_property don't emit property change notification explicitly, this will
be done implicitly by the type system. However, if the notify signal is
emitted explicitly, the type system will not emit it a second time.
This function essentially limits the life time of the closure to
the life time of the object. That is, when the object is finalized,
the closure is invalidated by calling g_closure_invalidate() on
it, in order to prevent invocations of the closure with a finalized
(nonexisting) object. Also, g_object_ref() and g_object_unref() are
added as marshal guards to the closure, to ensure that an extra
reference count is held on object during invocation of the
closure. Usually, this function will be called on closures that
use this object as closure data.
GObject.Closure to watch
Static_Staticcompat_Staticfind_Staticinstall_Staticinstall_the id for the new property
the GObject.ParamSpec for the new property
Staticinterface_Find the GObject.ParamSpec with the given name for an
interface. Generally, the interface vtable passed in as g_iface
will be the default vtable from g_type_default_interface_ref(), or,
if you know the interface has already been loaded,
g_type_default_interface_peek().
any interface vtable for the interface, or the default vtable for the interface
name of a property to look up.
Staticinterface_Add a property to an interface; this is only useful for interfaces
that are added to GObject-derived types. Adding a property to an
interface forces all objects classes with that interface to have a
compatible property. The compatible property could be a newly
created GObject.ParamSpec, but normally
g_object_class_override_property() will be used so that the object
class only needs to provide an implementation and inherits the
property description, default value, bounds, and so forth from the
interface property.
This function is meant to be called from the interface's default
vtable initialization function (the class_init member of
GObject.TypeInfo.) It must not be called after after class_init has
been called for any object types implementing this interface.
If pspec is a floating reference, it will be consumed.
any interface vtable for the interface, or the default vtable for the interface.
the GObject.ParamSpec for the new property
Staticinterface_Lists the properties of an interface.Generally, the interface
vtable passed in as g_iface will be the default vtable from
g_type_default_interface_ref(), or, if you know the interface has
already been loaded, g_type_default_interface_peek().
any interface vtable for the interface, or the default vtable for the interface
Staticlist_StaticnewvStaticoverride_the new property ID
the name of a property registered in a parent class or in an interface of this class.
GioUnix.DesktopAppInfo is an implementation of Gio.AppInfo based on desktop files.
Note that
<gio/gdesktopappinfo.h>belongs to the UNIX-specific GIO interfaces, thus you have to use thegio-unix-2.0.pcpkg-config file or theGioUnix-2.0GIR namespace when using it.