It's the same error I am experiencing when I am trying to make my ListView
ctrl scrolled without using the ScrolledWindow. It works in GTK+2 but really
not in GTK+3.
What I was trying to do is to request it to be smaller or else when the list
gets longer it force its self to show all the list out
It's the same error I am experiencing when I am trying to make my ListView
ctrl scrolled without using the ScrolledWindow. It works in GTK+2 but really
not in GTK+3.
What I was trying to do is to request it to be smaller or else when the list
gets longer it force its self to show all the list
Hi Mike,
On Wed, Apr 16, 2014 at 11:25 PM, mike_s michael.u.santi...@gmail.com
wrote:
It's the same error I am experiencing when I am trying to make my
ListView
ctrl scrolled without using the ScrolledWindow. It works in GTK+2 but
really
not in GTK+3.
What I was trying to do is to request
On Fri, Oct 5, 2012 at 1:57 AM, Steffen Gutmann muib...@yahoo.com wrote:
Hi Tristan!
Right, the bug might have to do more with cropping/scaling support
GtkImage, rather than it's size request.
Filed as [Bug 685506] New: GtkImage and size/space management
Regarding size request:
We add
Hi Tristan!
I suggest you start by filing an enhancement bug against GtkImage for this.
Yes, I can do that. Just to make sure, I file a new bug for component gtk,
severity set to enhancement, and put somethign like Size request of GtkImage
into the title. Is this correct?
If you have a
On Thu, Oct 4, 2012 at 1:46 AM, Steffen Gutmann muib...@yahoo.com wrote:
Hi Tristan!
I suggest you start by filing an enhancement bug against GtkImage for this.
Yes, I can do that. Just to make sure, I file a new bug for component gtk,
severity set to enhancement, and put somethign like
Hi Tristan!
Lets not go around the merry-go-round one more time.
In GTK+3, widgets receive *at least* what they requested in the size
requesting phase.
User facing apis cannot undermine the minimal requirements for the geometry
which a widget has requested.
User facing apis can
On Tue, Oct 2, 2012 at 1:52 AM, Steffen Gutmann muib...@yahoo.com wrote:
Hi Tristan!
Lets not go around the merry-go-round one more time.
In GTK+3, widgets receive *at least* what they requested in the size
requesting phase.
User facing apis cannot undermine the minimal requirements for
When creating a new widget subclass, you end up implementing
get_preferred_height/width. This allows you to specify both a
minimum and a natural size. Then in on_size_allocate() you can
decide to maybe set a clipped or scaled version of your pixbuf to a
GtkImage. When you do it this way, you don't
Lets not go around the merry-go-round one more time.
In GTK+3, widgets receive *at least* what they requested in the size
requesting phase.
User facing apis cannot undermine the minimal requirements for the geometry
which a widget has requested.
User facing apis can however, enforce a minimum
Hi Tristan
I must admit the docs are incorrect about this, it says:
Sets the minimum size of a widget; that is, the widget's size request
will be width by height. You can use this function to force a widget to be
either larger or smaller than it normally would be.
But what it should
Hi,
with GTK2 some applications used to set the minimum size of some widgets using
gtk_widget_set_size_request. E.g. the min size of a GtkImage. This no longer
works with GTK3 and the min size of the GtkImage is that of the underlying
image, e.g. a GdkPixbuf.
There is also a bug report
On 09/28/2012 02:16 AM, Steffen Gutmann wrote:
Hi,
with GTK2 some applications used to set the minimum size of some widgets using
gtk_widget_set_size_request. E.g. the min size of a GtkImage. This no longer
works with GTK3 and the min size of the GtkImage is that of the underlying
image,
13 matches
Mail list logo
