Thanks for your reply and the pictures!
And to explain my impression: often feature requests are not followed up on, even after being implemented, but noticeable frustration/disappointment from the user part is expressed while requesting. Given the effort necessary to implement/design things, it creates frustration in me as well (which I usually don't share and thought I should start to do).
And no worries about raising questions, they help.
T.BugReporter wrote: ↑
07 Jul 2019 09:41
Maël wrote: ↑
16 Jun 2019 09:02
So, MDI child windows were tiled horizontally and they should resize automatically to fit the main window width, but never get smaller than necessary to completely show all data (hex and text) for the current BytesPerRow setting?
Or, should every MDI child have exactly the width necessary to fit the data (according to BytesPerRow), no matter how large the main window is?
I think either one would work for me.
In more technical terms, this would mean it works like now, but instead of showing a scrollbar, each window would remain as large as necessary, to not need a horizontal scrollbar. So I could use the scrollbar computation code, to determine the necessary window width.
There would still be limits to this, as windows are limited by screen size, and BytesPerRow can cause larger "content" than would fit on a screen.
A possible name could be: "Fit to content width". Technically, it should be "Fit to content width (if possible)", but that would be too long and still not say what the conditions are.
I could compute the window size constraints based on BytesPerRow, as long as the "Fit to content width" option is enabled.
The already existing "Fit to window width" option would form a radio group with the "Fit to content width" option, so only one of them could be enabled at any time (or none of the two). In the options dialog there would also be a global "Fit to content width" option that applies to all windows.
Now the only issue I can see that remains, would be with the upcoming UTF-8 support. It is not clear how large a window needs to be (to show the content without a scrollbar), before having rendered the relevant part of the file. Each line can have a different width, as characters don't have a fixed width anymore, and several bytes could just result in an average width character.
The only option I could see would be to assume the maximum text line width possible for the current ByterPerRow setting. That could mean wasted horizontal space / a lot of blank space.
Any other ideas?