| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
It makes no sense to use the size of the icon to tell GTK+ about our
preferred width/height: what we really care about is the size of our
parent, since we're filling it anyway.
taken from:
https://git.gnome.org/browse/gnome-panel/commit/?h=gnome-3-0&id=e870aaa
|
|
|
|
|
|
|
|
gdk_window_set_geometry_hints accept 0 as flags when geometry is null
return 1px width/height while image is not loadded
|
|
|
|
Based on gnome-panel commit: 8a942d16378f62015f302357e0e5b6f61b5713b3
From: Vincent Untz <[email protected]>
|
|
gtk_widget_render_icon()
Based on gnome-panel commit: 6f13318fa892afde6ff35b6784217121481e3963
From: Carlos Garcia Campos <[email protected]>
|
|
Even tough it works it makes taking code (eg StyleContext)
from gnome-panel much easier.
Also fixes a bug where applets are not drawn when moved/added.
|
|
Based on gnome-panel commit: ee0fcd193030b433b5aa1785a864f89e25345f01
From: Carlos Garcia Campos <[email protected]>
In the process make button_widget_{draw,expose} a little more readable.
|
|
We need to add a child to the button to get the right allocation of the
pixbuf. When the button is created without a pixbuf,
get_preferred_width/height are called the first time when the widget is
allocated and 0x0 size is cached by gtksizerequest. Since the widget
doesn't change its size when a pixbuf is set, gtk_widget_queue_resize()
always uses the cached values instead of calling
get_preferred_width_height() again. So the actual size, based on pixbuf
size, is never used. We are overriding the draw() method, so having a
child doesn't affect the widget rendering anyway.
Taken from gnome-panel commit: 0b8ace11087855d741cdeed97dc839db50319ae8
from: Carlos Garcia Campos <[email protected]>
|
|
|
|
|
|
|
|
|
|
|
