![](Zrzut ekranu - taskbar - 2022-01-23 152652.png)
![](Zrzut ekranu - window - 2022-01-23 152812.png)
screenshot is a bit outdated
Resolutioner is a program for changing primary screen's resolution on triggers.
It could be written as a Windows Service to be above all users and sessions but is not, and instead aims to work by autostarting.
-
CORE
actual resolution setting -
FEAT
handling errors of resolution changing instead of ignoring them -
CORE
saving and loading config on start- does it really work? sometimes it worked sometimes not?
- see about that
Upgrade()
method
-
CORE
trigger: "Now" button -
CORE
trigger: user login- autostart
- trigger: on start
-
IMPR
Hide()
on start, because it seems it shows up in taskbar as window before re-minimized instead of just in status notification icons area from the start -
FEAT
detect when not autostart, and configure with another checkbox whether to then not start minimized -
CORE
trigger: user switch- separate lock/unlock desired/restored
- maybe columns of all SessionSwitchReasons
-
CORE
trigger: user logout -
FEAT
trigger: distinction between logoff and shutdown -
FEAT
change scaling too, i think it's even in DEVMODE -
FEAT
introduce three-state checkboxes/dropdowns to pick the other side for a trigger, or something -
IMPR
don't depend on RawInputLight nuget just forWindows.Win32.UI.WindowsAndMessaging.SYSTEM_METRICS_INDEX
, get that with CsWin32 instead by NativeMethods.txt or somehow
Click "swap" button to swap "for own use" and "to restore" resolutions.
Click fetch buttons on the sides to fetch current screen resolutions into the inputs. If the exact resolution was already in the opposite inputs, resolution will not be inserted and the "swap" button will be assigned focus.
"Config Saved" is checked when the config has not changed since load or since last write. Checking the box triggers write (save).
"Don't do things" will be stored in the config too and will inhibit just the resolution changes.