Hi guys - for getting and setting the position of a gdkmm window we have
Gdk::Window::get_position() and Gdk::Window::move(). However, if I'm
reading the documentation correctly, these use co-ordinates that are
relative to its parent window. For getting a window's screen
co-ordinates we can
Hi;
On 26 June 2015 at 08:37, John Emmas john...@tiscali.co.uk wrote:
Hi guys - for getting and setting the position of a gdkmm window we have
Gdk::Window::get_position() and Gdk::Window::move(). However, if I'm
reading the documentation correctly, these use co-ordinates that are
relative to
So, I just tried to use the memory profiler in glib, and I crashes
really early because the gobject constructor (gobject_init_ctor) calls
g_malloc before main() is reached.
This means g_mem_set_vtable() is impossible to use. I don't necessarily
think this is all that bad. Honestly we should never
Yeah, we've all been sort of aware of this for some time. I've abused
it to the fact where I know that malloc and g_new / free and g_free
will *always* be the same since a specific glib version.
I think removing all the code is fine.
On Fri, Jun 26, 2015 at 8:38 PM, Alexander Larsson
On Fri, Jun 26, 2015 at 8:50 PM, Jasper St. Pierre jstpie...@mecheye.net
wrote:
Yeah, we've all been sort of aware of this for some time. I've abused
it to the fact where I know that malloc and g_new / free and g_free
will *always* be the same since a specific glib version.
I think removing
