Hi,
> Glib::RefPtr m_pixbuf =
> Gdk::Pixbuf::create_from_file (Glib::build_filename
> (DATADIR, "picture.svg"), 130, 130);
> Is it normal that this code that ran perfectly in past now produces an
> abortion in runtime ?
> With a message like,
> terminate called after throwing an i
Hi guys,
Please, consider this line,
Glib::RefPtr m_pixbuf =
Gdk::Pixbuf::create_from_file (Glib::build_filename (DATADIR,
"picture.svg"), 130, 130);
Is it normal that this code that ran perfectly in past now produces an
abortion in runtime ?
With a message like,
terminate called
Thanks, that's the answer I was looking for.
In my view, libstdc++ is not different from any other library - just
like you view API refs of GNOME libraries in Devhelp, you can view the
standard C++ library's docs - for exactly the same reason and with the
same convenience.
I'm creating a template
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
