On Wed, 2013-10-30 at 15:34 +0100, Dirk Van Haerenborgh wrote:
> Also, Glib::Interface is not as flexible as GTypeInterface, in that it
> does not allow casting any Glib::Object to an interface instance
Can you show an example of this in C, and an example of how you'd like
to do the same thing in
That's indeed what I ended up doing.
Nevertheless, I think there's a lot of power in the GObject system
concerning runtime type information that is currently lost when using the
mm bindings.
Most importantly, there seem to be no wrappers for GParamSpec at all. Also,
Glib::Interface is not as flexi
You may at least use glibmm's .defs-generating code for this as
inspiration:
https://git.gnome.org/browse/glibmm/tree/tools/extra_defs_gen/generate_extra_defs.cc
--
Murray Cumming
murr...@murrayc.com
www.murrayc.com
www.openismus.com
___
gtkmm-list mai
W dniu 25.10.2013 09:55, Dirk Van Haerenborgh pisze:
Hi,
I'm working on an application that has to generate a user interface
based on the properties of a given object (a Gst::Element).
Since I cannot know upfront what properties are installed on the object
class, I'm looking for an alternative t
Hi,
I'm working on an application that has to generate a user interface based
on the properties of a given object (a Gst::Element).
Since I cannot know upfront what properties are installed on the object
class, I'm looking for an alternative to the Glib C API
'g_object_class_list_properties' funct
