Re: questions re: aux info, size request

On Sun, 2010-09-12 at 12:53 -0400, Havoc Pennington wrote:
> Hi,
> On Sun, Sep 12, 2010 at 1:33 AM, Tristan Van Berkom
> <tristanvb openismus com> wrote:
> > Ok I see, so we end up with:
> >  - set_size_request() Can be used to increase the minimum request
> I was thinking this should stay backward compatible and allow lowering
> it, fwiw. Though I can't actually come up with a use case, I'm just
> being paranoid.
> btw - have you looked into allowing 0x0 allocations at all? (at 0x0,
> draw() would not be called, I think, so draw() implementations would
> not have to handle 0x0; also, 0x0 would not really work on window
> widgets, but this could be addressed by forcing window widgets to have
> at least a 1x1 minimum size. i.e. replace 1x1 min allocation with a
> 1x1 min request for window widgets only)

Heh, do you mean GtkWindow widgets or GtkWidgets that have their own
GdkWindow ?

I think essentially to allow 0x0 allocations we either need to 
allow GdkWindows to be created at a 0x0 size (currently they
also force >= 1x1 internally)... or we need to add some special casing
code to GtkWidget's to handle their GdkWindows with care at
allocation time (naturally they all just call gdk_window_move_resize()

Probably the former is better than the latter... even if the 
window has to do some hackery and hide itself when there is
a dimension of 0 size.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]