Over the weekend I did some experimenting and came up with this, made somewhat of an attempt to make the underneath settings code actually work but probably not yet.
![[Image: tzOhlDU.png]](https://i.imgur.com/tzOhlDU.png)
While I tried to keep unrelated changes to a minimum, but it has to have some key necessary changes to make it all work, there's a bit of renaming going on you see in the "More" group box as I couldn't resist it in this case. The acceptable implementation of such a thing would probably come in more stages as it operates with different logic, but this what you see here is one branch and one commit, some of the technical nature of this at least in my logic requires quite a bit more than just strictly one new combo box, so the removal and shuffling of some other settings is a good idea to make the change have a practical sense and without non-working builds in between. That's why I demoed it here and not even attempted a PR.
Not worth a serious attempt while Wx is still here, when it's going it should make a big difference. It was a great learning curve on top of that, in many areas for me being very unfamiliar with the code, but the one that I should point out is Wx, Qt and the whole GUI improvements would suffer or slow down just because of Wx presence, I support the speedy removal of Wx, at least prioritization, the arguments against a speedy removal are absolutely valid as well, however everyone could come to an understanding which things have more weight, a valid argument can still have lower weight if a group of people decides it will treat it differently, it would work like this, if Wx is removed quicker, temporairly there would be some loss of overall functionality/quality but that removal might encourage faster than usual completion of Qt, and an earlier beginning of the improvements which change things a lot under the hood not only visually, it's just a tradeoff, and if that sacrifice is worth it, a few weeks of lack of functionality/polish that Wx still has over Qt - but being a total new guy my opinion obviously does not have to be taken with a lot of weight, I don't expect that at all.
EDIT: By just posting this here, not even 30 seconds have passed and I already see the first thing I would change, "Fullscreen - Borderless" should say "Fullscreen - Borderless Auto" because it would still decide the resolution automatically as I meant it from beginning.
Additionally I went over some terminology several times before going with "Adjustable" - the earlier version were ".. User Scalable", ".. User Scaled", ".. User Sizable", "Windowed, Resizable", "Windowed, IR-Bound" etc.
EDIT2: Oh, the key distinction with borderless ofcourse is that it's not exclusive, that means "Fullscreen - Auto" could say "Fullscreen - Exclusive Auto" or "Fullscreen - Auto Exclusive" (and reorder others for consistency) to make it even more clear and accurate.
While I tried to keep unrelated changes to a minimum, but it has to have some key necessary changes to make it all work, there's a bit of renaming going on you see in the "More" group box as I couldn't resist it in this case. The acceptable implementation of such a thing would probably come in more stages as it operates with different logic, but this what you see here is one branch and one commit, some of the technical nature of this at least in my logic requires quite a bit more than just strictly one new combo box, so the removal and shuffling of some other settings is a good idea to make the change have a practical sense and without non-working builds in between. That's why I demoed it here and not even attempted a PR.
Not worth a serious attempt while Wx is still here, when it's going it should make a big difference. It was a great learning curve on top of that, in many areas for me being very unfamiliar with the code, but the one that I should point out is Wx, Qt and the whole GUI improvements would suffer or slow down just because of Wx presence, I support the speedy removal of Wx, at least prioritization, the arguments against a speedy removal are absolutely valid as well, however everyone could come to an understanding which things have more weight, a valid argument can still have lower weight if a group of people decides it will treat it differently, it would work like this, if Wx is removed quicker, temporairly there would be some loss of overall functionality/quality but that removal might encourage faster than usual completion of Qt, and an earlier beginning of the improvements which change things a lot under the hood not only visually, it's just a tradeoff, and if that sacrifice is worth it, a few weeks of lack of functionality/polish that Wx still has over Qt - but being a total new guy my opinion obviously does not have to be taken with a lot of weight, I don't expect that at all.
EDIT: By just posting this here, not even 30 seconds have passed and I already see the first thing I would change, "Fullscreen - Borderless" should say "Fullscreen - Borderless Auto" because it would still decide the resolution automatically as I meant it from beginning.
Additionally I went over some terminology several times before going with "Adjustable" - the earlier version were ".. User Scalable", ".. User Scaled", ".. User Sizable", "Windowed, Resizable", "Windowed, IR-Bound" etc.
EDIT2: Oh, the key distinction with borderless ofcourse is that it's not exclusive, that means "Fullscreen - Auto" could say "Fullscreen - Exclusive Auto" or "Fullscreen - Auto Exclusive" (and reorder others for consistency) to make it even more clear and accurate.