Variant.this
- this(GVariant* gVariant, bool ownedRef)
- this(VariantType childType, Variant[] children)
- this(bool value)
- this(ubyte value)
- this(Variant key, Variant value)
- this(double value)
- this(VariantType elementType, void* elements, size_t nElements, size_t elementSize)
- this(VariantType type, Bytes bytes, bool trusted)
- this(VariantType type, ubyte[] data, bool trusted, GDestroyNotify notify, void* userData)
- this(short value)
- this(int value)
- this(long value)
- this(VariantType childType, Variant child)
- this(string format, void** app)
- this(string string_)
- this(string[] strv)
- this(Variant[] children)
- this(ushort value)
- this(uint value)
- this(ulong value)
- this(string formatString, string[] endptr, void** app)
- this(Variant value)
glib Variant Variant
constructorsfunctionsstatic functionsvariables
This function is intended to be used by libraries based on glib.Variant that want to provide Variant.new-like functionality to their users.
The API is more general than Variant.new to allow a wider range of possible uses.
format_string must still point to a valid format string, but it only needs to be nul-terminated if endptr is NULL. If endptr is non-NULL then it is updated to point to the first character past the end of the format string.
app is a pointer to a va_list The arguments, according to format_string, are collected from this va_list and the list is left pointing to the argument following the last.
Note that the arguments in app must be of the correct width for their types specified in format_string when collected into the va_list See the [GVariant varargs documentation][gvariant-varargs].
These two generalisations allow mixing of multiple calls to Variant.newVa and Variant.getVa within a single actual varargs call by the user.
The return value will be floating if it was a newly created GVariant instance (for example, if the format string was "(ii)"). In the case that the format_string was '*', '?', 'r', or a format starting with '@' then the collected glib.Variant pointer will be returned unmodified, without adding any additional references.
In order to behave correctly in all cases it is necessary for the calling function to Variant.refSink the return result before returning control to the user that originally provided the pointer. At this point, the caller will have their own full reference to the result. This can also be done by adding the result to a container, or by passing it to another Variant.new call.