Anatomy of a bug fix: MAME Debugger GUI

[@andrewdunbar828]

not only for your amusement, for your amusement and edification

[@Torbjorn.Lindgren]

IMHO your final simpler solution for resizing is the "correct" one, in fact I'd argue it's generally considered bad UI design to limit max window size if not absolutely necessary. Fixed max window sizes really only make sense for "one size only" windows which has a fixed layout and can't handle any resizing. Even if it breaks their custom scroll-bar sizing slightly.

[@CocoTownRetro]

Yes, actually I do agree that letting the user pick the size of the window is almost always better than the product deciding what the range of acceptable sizes is. However, the problem with my final fix is, what if the user makes the window narrow? They will expect that they can horizontally scroll through all of the text. But, while that worked in my first fix, that no longer works in the second fix. The logic that determines the horizontal scrollable extent needs to know the number of characters in the longest line. And with the second fix, that's back to being just some constant number, which will sometimes be too small. It just so happened that the code which set the window’s maximum size was also dependent on that value, and I was just trying to play nice with the existing windows sizing code.

[@Wormetti]

I had to laugh at this part 19:09. Next time, debugging the Microsoft debugger, so you can debug the MAME debugger, so you can debug your game.

[@andrewdunbar828]

I promise to subscribe if this happens!

[@CocoTownRetro]

Hmm, the source for VS Code is up on github, so I suppose I could.... NO! No, not getting caught up in another nested rabbit hole.

[@Ashe_S_]

Okay but everyone talks to themselves in the first person plural right? We're all "we" on the inside?

[@CocoTownRetro]

I know I am.

[@andrewdunbar828]

you forgot nondeterministic nonsense