On Tue, 2013-02-26 at 17:03 -0500, Owen Taylor wrote:
> On Tue, 2013-02-26 at 15:30 +0100, Alexander Larsson wrote:
> > I don't really see any way to solve this generically. But maybe we can
> > somehow limit our baseline support so that this works? For instance,
> > we could always request the nau
On ons, 2013-02-27 at 21:22 +0900, Tristan Van Berkom wrote:
> > How do we assign 5 pixels above the baseline based on this? All we can
> > do is give the child more total height (via gtk_widget_size_allocate),
> > we have in general no control of where that height will go. The child
> > might be e
On Wed, Feb 27, 2013 at 8:44 PM, Alexander Larsson wrote:
> On ons, 2013-02-27 at 17:47 +0900, Tristan wrote:
>
>> Ah, I think I understand your question better now.
>>
>> Use a natural allocation process similar to
>> gtk_distribute_natural_allocation():
>> http://git.gnome.org/browse/gtk+/tree/g
On ons, 2013-02-27 at 17:47 +0900, Tristan wrote:
> Ah, I think I understand your question better now.
>
> Use a natural allocation process similar to
> gtk_distribute_natural_allocation():
> http://git.gnome.org/browse/gtk+/tree/gtk/gtksizerequest.c#n599
>
> Instead of looping over widget size
On Tue, 2013-02-26 at 21:05 +0100, Alexander Larsson wrote:
> On tis, 2013-02-26 at 10:58 -0500, Matthias Clasen wrote:
> > On Tue, Feb 26, 2013 at 9:30 AM, Alexander Larsson wrote:
> >
> > > Ideas wanted...
> >
> > I think you basically have to split the height that is returned for
> > minimal
On Tue, 2013-02-26 at 15:30 +0100, Alexander Larsson wrote:
> I don't really see any way to solve this generically. But maybe we can
> somehow limit our baseline support so that this works? For instance,
> we could always request the naural size for baseline aligned widgets
> and never grow them? W
On ons, 2013-02-27 at 01:18 +0900, Tristan wrote:
> My thoughts are that, when performing get_preferred_height_for_width(),
> you need some virtual allocation logic like such that is found in
> gtkbox.c (when we are requesting in the 'uncomfortable/opposing'
> orientation):
>
> a.) Calculate ho
On tis, 2013-02-26 at 10:58 -0500, Matthias Clasen wrote:
> On Tue, Feb 26, 2013 at 9:30 AM, Alexander Larsson wrote:
>
> > Ideas wanted...
>
> I think you basically have to split the height that is returned for
> minimal or natural size into an overlength/underlength pair. Then you
> can sum th
On Tue, 2013-02-26 at 15:30 +0100, Alexander Larsson wrote:
> One of the main layout features we're badly missing atm is baseline
> alignment. I spent some time looking at this recently but I bumped
> into some problems. I'd like to bring this up for discussion in the
> hope that we might figure ou
On Tue, Feb 26, 2013 at 9:30 AM, Alexander Larsson wrote:
> Ideas wanted...
I think you basically have to split the height that is returned for
minimal or natural size into an overlength/underlength pair. Then you
can sum them up separately in containers that support baseline
alignment. In conta
One of the main layout features we're badly missing atm is baseline
alignment. I spent some time looking at this recently but I bumped
into some problems. I'd like to bring this up for discussion in the
hope that we might figure out a solution to my problems.
First, let me define what i mean by ba
11 matches
Mail list logo
