waydabber
When HiDPI activation fails and BetterDisplay falls back to LoDPI no notice is given
Experiencing this with Dummy displays mirrored to real displays. BetterDisplay just sort of hangs for a few seconds and then if I check the menu the HiDPI radio button is not selected. A simple flashed overlay notice that doesn't need to be clicked away would be non-obtrusive but helpful.
I'll think about how to handle issues like this. The problem is somewhat complicated - the HiDPI mode appears in the mode list and seems to be valid. The app issues the command to switch to the mode selected, however on Intel (mostly with Intel iGPU) for whatever reason sometimes a HiDPI mode that seems to be valid and available does not actually work and the GPU driver activates a LoDPI mode instead. After the mode change the OS generates a configuration change event which the app receives and refreshes the current mode data based on this event - but since this change is fully event driven (and the event is originated by the system and its cause can be a number of things, not necessary an app induced change), it is not directly connected to the original intent of the user to switch to a HiDPI mode - so there is no clear reason by the app to show a warning or maybe try again switching to the right mode. I could maybe use a timer of course to suppose that the unintended mode change has something to do with the fact that just half a second ago the user initiated a mode change using the app to a different mode and maybe that failed thus a notification could be shown about a possible issue.
Yeah, I see what you mean. It's kind of a wonky thing to code in because it's not really all coming from your app, but it could be useful. I like your hotkey overlays, like the one that comes up when you advance to a one step higher or lower resolution via a hotkey. Looks great!