Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Add ScheduleAfterChildren()-API to Containers #802
Planned to make an osu pr with at least the chat fix once this is in. Can't immediately think of a good use case within the framework, but I imagine callbacks post-layout will be a thing in more places.…
On 8 Jun 2017 7:25 a.m., "Dean Herbert" ***@***.***> wrote: Is there an osu-level PR to move such things over? I would've thought there was at least one potential usage in the framework for this... — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#802 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEshB6rXATij6DxIoY1S7ez0ol-maAxmks5sB4W4gaJpZM4NzPRD> .
Adding a scheduler specifically for scrollToEnd feels very wrong. Just add a single internal state for that instead?
I mean there's so many other scenarios where scrollToEnd won't work too (if new content appears when a ScrollContainer is off-screen it won't work etc.) to the point we probably want a permanent
management of keeping a scroll position should be the
Regarding UpdateAfterChildren(): While using the framework I've encountered situations where the literal action, ie "let my children update, then update me" is necessary to get the right order of operations, where this wasn't purely related to just sizes not getting invalidated.
I can imagine similar situations where I will want to use ScheduleAfterChildren() because I need to do an action of a similar kind - but schedule it to the next frame - even though the only use-case I currently have in my own code is making sure that a ScrollContainer properly scrolls to its end.