Kulik wrote:What do you think about layoutAfter? Is it worth the hassle? It might speed things up for really long sequential layouts but it complicates things.
On the whole, I think keeping things as simple as possible is the better choice. Though if you want to leave it in, it's fine
Kulik wrote:I will need a new event on CEGUI::Window - EventMarginChanged. Should I split it to EventMarginTopChange, etc? Probably not worth the hassle. I am planning to define margin as 4 UDim, because URect doesn't really fit.
Yeah, I think one new event would be fine here, and four UDims would be ok for storing the margins.
I've been looking into the clipping issue. I've identified at least one definite issue, and some other things that look inconsistent. I've gotten to the point where I'm not especially happy with much of the stuff surrounding these calculations, and so I need to work through it from scratch to ensure that everything is as it should be, and in order to figure out precisely which combinations are causing the issues. None of this has anything to do with the new code; I've reproduced the issues in unmodified CEGUI code - so they have been lurking a while. I was hoping this would be a quick fix, but this is not the case - but on the positive side, at least this issue is found and can be addressed