--- Lyle Johnson <lyle / users.sourceforge.net> wrote:
> 
> I agree with David. If you're creating only a few
> widgets, the user 
> probably won't notice it -- FOX is pretty fast at
> keeping up with 
> changes in layout and so forth. But if it's a lot of
> new widgets you 
> might want to consider a switcher instead for the
> reasons David 
> outlined. There's an example of how to use the
> FXSwitcher widget in the 
> shutter.rb example program.
> 
> 

Hmmm... since I have to have a whole bunch of these,
and users can create or delete them, I don't think
this is really an option... I'd still have a problem
when the user deletes a parameter.

I tried to redefine the getHeight method for my
container, but that didn't seem to have any affect. 
That is, I could call obj.getHeight and it would get
the value from my function, but the parent still sees
the height differently.  Does that make sense?  

Each widget is an FXParameterRow, which is a class I
made to show a key and value... the current
implementation is a GroupBox titled with the key
containing an FXText box with the edittable value...
whew.

I thought of another option though... If I could do
this as an FXList, that should handle all of the size
issues appropriately... however, it doesn't seem like
a widget can be an FXListItem (even with
subclassing)... is this correct?

Anyway, I still think that there should be a way to
tell a container to re-evaluate it's height... and it
should do so automatically after a child gets
destroyed.  Wouldn't that make sense?

Jason