Surprising wxAuiNotebook split behaviour (Issue #26081)
rudolfwalter
rudolfwalter created an issue (wxWidgets/wxWidgets#26081)Description
When dragging the tabs of a wxAuiNotebook into a split state, multiple behaviours are possible:
A. There is only one pane (ie, no split), the new pane will take up half of the total width. The old pane shrinks to take the remaining half.
B. There are multiple panes, the new pane will take up a small amount of width. The rightmost pane shrinks enough to allow this. If the rightmost pane is not large enough, the one to the left of it will also shrink, etc.
C. There are multiple panes, the new pane will take up the same amount of width as the destination pane. Existing panes shrink like (B) above.
The above is mostly okay, but there are unexpected details:
1. If the rightmost pane is not large enough to yield sufficient space, it gets resized to zero. The user might think they lost their tabs. Ideally, there should be some minimum size (perhaps configurable).
1a. If then one starts resizing a pane, suddenly things snap into a new arrangement of widths. Perhaps the widths are calculated differently in multiple places? In some cases the result is reminiscent of behaviour (A), so maybe there is overlap with that too?
2. It is not intuitive to me why some drag destinations allow only behaviour (B), others allow only (C), and still others allow both (B) and (C).
2a. I'm not sure if behaviour (C) can make sense if the destination is larger than 50%. Currently it is allowed regardless.
3. Behaviour (A) seems generally useful: perhaps it should be possible to split a pane halfway even if there are multiple ones already.
Here is a screen capture showing some of the above:
https://github.com/user-attachments/assets/d312ee95-28b6-4a43-a999-a9a6565eac37
Platform and version information
- wxWidgets version: 3.3.0 and 3.3 master
- wxWidgets port: wxMSW
- OS: Windows 11 25H2
- other: 150% DPI
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
VZ
vadz left a comment (wxWidgets/wxWidgets#26081)Thanks for reporting this, the problem (1) is indeed pretty bad so I'll fix at least this.
For the rest, I'm not really sure what the correct/best behaviour would be. Do you already know this, by chance, e.g. do we have anything (MSVS, VS Code, ...) to compare with?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.