Releases: Crozzers/screen_brightness_control
Releases · Crozzers/screen_brightness_control
v0.6
This release focused on bringing the Linux side of the library up to speed with the Windows side of things.
Changes for Linux:
- Support for using ddcutil to control desktop monitors
- The
Light,XRandrandDDCUtilclasses now have theget_display_infomethod Monitorclass addedlist_monitorsandlist_monitors_infofunctions added. The command line-largument also works- The
XBacklightclass remains unchanged due to the fact that the display command line argument doesn't work - Each linux class now has
executableattribute which is the path to the executable that it calls (eg:XRandr.executable = 'xrandr')
Removed:
- The
methodsdictionary in thelinuxsubmodule
v0.6.1
- Improved the way monitor manufacturers are processed
- Fixed the CLI not working with single monitors
- Fixed CLI not working with xbacklight
- Fixed some inaccurate docstrings
- If a monitor's brightness method fails
Noneis added to the output instead of nothing. Output length should now always match length oflist_monitors()
v0.6.2
v0.5
- Fixed issue #3 where if you turned a monitor off and on again the module might behave weirdly
- Sped up the import speed of the module
- Added
Monitorclass on Windows displaykwarg can now be a string on Linux
Special thanks to lcharles for raising PR #2 and issue #3
v0.5.1
- Removed
screen_brightness_control.windows.WMI.get_display_serialsas it wasn't useful - Re-wrote most docstrings to be able to provide full documentation for the project, which is now hosted on https://crozzers.github.io/screen_brightness_control. I will add to it as I go
v0.4
Added:
- Added support for DDC/CI commands in Windows, meaning that most desktop monitors can now also be controlled using this package
- Added an XRandr method for Linux. The module attempts to call Xrandr before XBacklight and after Light
- Added the
displaykwarg to allow users to specify which display they wish to control. Also added to command line args - Added
--verbosecommand line arg, which increases the verbosity of any error messages
Changed:
- Re-structured the module to allow for easier upgrades/changes in the future
- Improved error formatting
Removed:
- Removed the
max_valuekwarg
Special thanks to lcharles for raising issue #1 and making me aware that DDC/CI commands existed
v0.4.1
- Added
methodkwarg to brightness methods so that you can choose how the brightness is adjusted. On windows the options are'wmi'and'vcp'and on linux they are'light', 'xrandr'and'xbacklight' - Added method command line arg
- Merged pull request from
lcharles#2 to add top-level functionlist_monitors(Windows only), add a command line option for this and add a function in the windows module calledlist_monitors_with_method, which returns list of pairs of display names and their methods - Fixed the
XRandr.get_brightnessfunction returning the wrong type
v0.3
Changes:
- You can now call this module from the command line! Use
python -m screen_brightness_control --helpto get the available commands - Fixed
fade_brightnessnot working when running in a new thread on Windows - Removed
raw_valuekwargs for linux as they were not really useful - Deprecated
max_valuekwarg
V0.3.1:
- Updated FAQ section of README
v0.2.0 + Patches
This release would have been v0.1.8 but that is less than 0.1.72 which should have been obvious to me.
Changes:
- Functions no longer return
Falseupon failure but they raise aScreenBrightnessError. This was an effort to unify the various exceptions that get raised (wmi.x_wmion Windows,FileNotFoundErrorandPermissionErroron Linux) get_brightnessandset_brightnessaccept a new kwargverbose_error=False. This controls the level of detail in the exceptions raised.get_brightness(max_value=True)will only return 100 if the brightness can actually be retrieved. Otherwise it raises theScreenBrightnessError
v0.2.1:
- Fixed
get_brightnessattribute errors for Windows - The Windows version will now set the brightness for ALL wmi brightness methods (not just the first one)
- If there are multiple brightness methods then
get_brightnesswill return a list of brightness values - Added a copy of the MIT license to the files
v0.2.2
- Updated README with an FAQ section
- Minor adjustment to
fade_brightness
v0.1.7 Update + Patches
v0.1.7 Changes:
- Made some type conversions in
set_brightnessever so slightly more reliable - Added
max_valuekwarg toget_brightness - Fixed a logic error in
get_brightness - Fixed rounding error in
get_brightness
Patch 1:
- Removed debug print statements
Patch 2:
- Fixed not returning false upon failure on Windows
- If fade_brightness cannot set the brightness it exits the for loop
v0.1.6
A bunch more quick fixes
Fixed package dependencies for Windows
Fixed set_brightness force and raw_value kwargs
Fixed some other small bugs
Quick Fix 2
Fixed a bug in the get_brightness function and updated the version number
Quick Fix 1
Fixed setup.py to correctly format the README.md for PyPi