Re: pack or grid (or the other way around)?

On Thu, 16 Jan 2025 11:34:34 +0100, Ralf Fassel wrote:

In addition to what Rich wrote, here is what you *cant* do:
>
 frame .f
 label .f.l1
 label .f.l2
 
 pack .f.l1
 grid .f.l2
 => error: cannot use geometry manager grid inside .f which already has
slaves managed by pack 
>
 grid .f.l2
 pack .f.l1
 => error: cannot use geometry manager pack inside .f which already has
slaves managed by grid 
>
But .f itself can be managed by either grid or pack, regardless of what
you use to pack/grid widgets 'inside' .f

**************************

That is my concern.

.f itself can be managed by either grid or pack, regardless of what
you use to pack/grid widgets 'inside' .f

That's because .f is the parent.

Now suppose someone has an application that uses grid. Everything is
inside one big 'gridded' frame. And suppose my megawidget uses pack.

Or the other way around.

That is my concern.

I still haven't gone back to that code. I guess I will have to run
multiple tests on it and see what happens.

--
Luc

>