Releases: bp2008/MonitorControl
Releases · bp2008/MonitorControl
MonitorControl 2.1
MonitorControl 2.0.1
Version 2.0.1
- Fixed a bug where Accidental Wake Prevention's GUI dialogs could crash the app if they were commanded to close while the forms were still loading.
MonitorControl 2.0
Version 2.0
- Accidental Wake Prevention has been revised:
- Instead of an explicit number of inputs being required in 10 seconds, there is now a "wakefulness" progress bar which slowly moves towards empty if no inputs are happening. Inputs cause it to move towards full. The monitors will go back to sleep if the progress bar reaches empty, otherwise the monitors will stay on if the progress bar reaches full.
- The progress bar now appears at the center of all monitors instead of just one.
- Hotkey-triggered sleep now operates via the Accidental Wake Prevention mechanism so that you get immediate feedback that the hotkey worked, but still have opportunity to cancel it in case the hotkey was pressed accidentally.
MonitorControl 1.11.1
Version 1.11.1
- Fixed bug where "delayed monitor off commands" failed to trigger again after a partial wake timeout.
MonitorControl 1.11
Version 1.11
- Added Hotkey support.
- Fixed bugs in storing multi-line command lists.
- Added additional command list: "Additional commands to run 9 seconds after turning monitors OFF, if state is still OFF".
- Log file names now use two-digit month numbers.
MonitorControl 1.9
Version 1.9
- Added the ability to run additional commands when turning monitors on or off.
- This was implemented to run the LGTV Companion app with command line flags to turn an LG TV's screen on or off to match the monitor output state. I find that this is a better interaction than having LGTV Companion app manage the TV on its own (because it can get the TV's power state out of sync with the signal state).
MonitorControl 1.8
Version 1.8
- "Prevent Accidental Wakeup" now allows fine-grained control of the number of input events that will be required to fully wake the screen. (default: 8 events if setting was previously enabled, otherwise 1).
- When turning a screen off, the off command is now sent every 5 seconds for one minute (or until an input event is received) in order to help prevent spontaneous wakeups due to OS bugs or misbehaving 3rd-party software.
MonitorControl 1.7
Version 1.7
Bugfix
- Fixed bug where the "Start Program Automatically" function caused the app to close 3 days after automatic startup.
- This was because the default configuration of a Task Scheduler task has the task end if it is still running 3 days after startup (WHY IS THIS THE DEFAULT BEHAVIOR, MICROSOFT!!?).
Quality of Life
-
When synced with a remote machine, local activity will no longer have a lasting effect on monitor on/off state.
- Added a checkbox to restore previous functionality where local input overrides the synchronized state until the next remote state change.
-
Added "Prevent Accidental Wakeup" setting to prevent spurious inputs from leaving screens on when nobody is actually using the computer.
-
When opening the configuration GUI, the form now appears near the mouse cursor.
Other changes
- Explicitly set several of the Task Scheduler settings that were previously left at defaults.
MonitorControl 1.6
Version 1.6
- The app now requires administrator privilege. This was the true problem with unreliable waking of monitors: if the focused window was elevated, this app ran with lower permissions so it could not move the mouse. Simple as that.
- Task Scheduler is now used to register the app for automatic startup because it supports starting the app as administrator. The old registry method did start the app as administrator. This setting is migrated automatically upon first launch of version 1.6.
- Added mousemove command to perform simple relative mouse movements for testing purposes.
MonitorControl 1.4
Version 1.4
- Added the ability to synchronize monitor on/off state with a another computer running MonitorControl. Both computers should be running version 1.4 or newer.
- The internal monitor status flag is now set to "on" when user input is detected after turning off the monitors. This was critical to support synchronization with another MonitorControl program.