Complex UIs for inputs/outputs/bottom tend to blend together so it's userfult to be able to define a separator between those child-UIs easily.
I was wondering whether to only pass &mut egui::Ui for simplicity, but in the end I think it's better to provide a more capable API consistent with other methods considering that there's basically no cost to that, even if I don't see a specific use-case right now.
Complex UIs for inputs/outputs/bottom tend to blend together so it's userfult to be able to define a separator between those child-UIs easily.
I was wondering whether to only pass
&mut egui::Uifor simplicity, but in the end I think it's better to provide a more capable API consistent with other methods considering that there's basically no cost to that, even if I don't see a specific use-case right now.Also, fixed a missing doc comment.