CEGUI (Crazy Eddie's GUI) Forums

So I have a vertical layout container which I'm using to display a list of entries which a user can modify (imagine an Excel sheet). Each entry consists of a row of elements, one of which is a Combobox.

Now, when I initially create my Combobox, I set it's height to be just enough to show the currently selected item in the Combox box. When that combobox is expanded though, I increase it's size to show the selectable options. Since the parent LayoutContainer is listening to changes in size, it ends up pushing all the rows below down, which looks odd. I'd prefer if the layout container did not change size when I did that.

So my question is what is the best way to handle said situation? Should I mute the EventSet when I resize the comboxbox? Or should I unsubscribe from the event itself? Or is there another option?

Thanks for any help!

That's an unfortunate combination of behaviours . Honestly, I always have found it quite weird that the expanded version of the combobox depends on the combobox's original size at all. Maybe it would make more sense if the expanded element acted like a child that ignores its parents clipping in general. But then no parent would clip it at all. Not sure if that is desirable either...

I do not have a suggestion on how to turn the reaction of the parent layoutcontainer off, on any size changes, but yea muting the eventset would be one way to do this. It might have side-effects though.

What if you place the combobox into a defaultwindow (doesnt render anything on its own) , setting it to the size you want and let it have the combobox as child, which may change its size however it wants. For the combobox turn the parent clipping off. Sounds like it could work and it would have less side-effects than muting all events.

Tell me if this worked for you.

Hey Ident,

Thank you for the quick reply and apologies for the late response; I went down the rabbit hole on a new feature and have just now resurfaced.

Wrapping the comboboxes (and their rows) in a Default Window did indeed work. It was an quick replacement since I was already wrapping them in a horizontal layout container (HLC) and I just had to chang one into the other. I'm thinking of adding the HLC I replaced as a child of the Default Window, though I start to worry about the costs of adding so many wrappers (though I guess that is not any different from what the UI is already doing).

Many thanks for the suggestion, Ident!

CEGUI is very efficient, especially if things dont change much it practically costs you almost nothing to have an extra DefaultWindow. This is except for when you might be interacting with the UI, but then again how often do you click per tick