ParamSpec#
- class ParamSpec(*args, **kwargs)#
Subclasses: ParamSpecBoolean, ParamSpecBoxed, ParamSpecChar, ParamSpecDouble, ParamSpecEnum, ParamSpecFlags, ParamSpecFloat, ParamSpecGType, ParamSpecInt, ParamSpecInt64, ParamSpecLong, ParamSpecObject, ParamSpecOverride, ParamSpecParam, ParamSpecPointer, ParamSpecString, ParamSpecUChar, ParamSpecUInt, ParamSpecUInt64, ParamSpecULong, ParamSpecUnichar, ParamSpecValueArray, ParamSpecVariant
GParamSpec encapsulates the metadata required to specify parameters, such as GObject properties.
Parameter names#
A property name consists of one or more segments consisting of ASCII letters
and digits, separated by either the - or _ character. The first
character of a property name must be a letter. These are the same rules as
for signal naming (see signal_new).
When creating and looking up a GParamSpec, either separator can be
used, but they cannot be mixed. Using - is considerably more
efficient, and is the ‘canonical form’. Using _ is discouraged.
Methods#
- class ParamSpec
- 
- do_get_property(pspec)#
- Parameters:
- pspec 
 
 - do_set_property(pspec, value)#
- Parameters:
- pspec 
- value 
 
 
 - get_default_value() Value#
- Gets the default value of - pspecas a pointer to a- Value.- The - Valuewill remain valid for the life of- pspec.- Added in version 2.38. 
 - get_name() str#
- Get the name of a - ParamSpec.- The name is always an “interned” string (as per - intern_string()). This allows for pointer-value comparisons.
 - get_qdata(quark: int) Any | None#
- Gets back user data pointers stored via - set_qdata().- Parameters:
- quark – a - Quark, naming the user data pointer
 
 - get_redirect_target() ParamSpec | None#
- If the paramspec redirects operations to another paramspec, returns that paramspec. Redirect is used typically for providing a new implementation of a property in a derived type while preserving all the properties from the parent type. Redirection is established by creating a property of type - GParamSpecOverride. See- override_property()for an example of the use of this capability.- Added in version 2.4. 
 - classmethod is_valid_name() bool#
- Validate a property name for a - ParamSpec. This can be useful for dynamically-generated properties which need to be validated at run-time before actually trying to create them.- See [canonical parameter names]:obj: - ParamSpec#parameter-namesfor details of the rules for valid names.- Added in version 2.66. 
 - set_qdata(quark: int, data: Any = None) None#
- Sets an opaque, named pointer on a - ParamSpec. The name is specified through a- Quark(retrieved e.g. via- quark_from_static_string()), and the pointer can be gotten back from the- pspecwith- get_qdata(). Setting a previously set user data pointer, overrides (frees) the old pointer set, using- Noneas pointer essentially removes the data stored.- Parameters:
- quark – a - Quark, naming the user data pointer
- data – an opaque user data pointer 
 
 
 - sink() None#
- The initial reference count of a newly created - ParamSpecis 1, even though no one has explicitly called- ref()on it yet. So the initial reference count is flagged as “floating”, until someone calls- g_param_spec_ref (pspec); g_param_spec_sink (pspec);in sequence on it, taking over the initial reference count (thus ending up with a- pspecthat has a reference count of 1 still, but is not flagged “floating” anymore).
 
Virtual Methods#
- class ParamSpec
Fields#
- class ParamSpec
- blurb#
 - flags#
- GParamFlagsflags for this parameter
 - g_type_instance#
- Private - GTypeInstanceportion
 - name#
- Name of this parameter: always an interned string 
 - nick#
 - owner_type#
- GTypetype that uses (introduces) this parameter
 - param_id#
 - qdata#
 - ref_count#
 - value_type#
- The - GValuetype for this parameter