Skip to content

Releases: Crozzers/screen_brightness_control

v0.6

27 Dec 18:18

Choose a tag to compare

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, XRandr and DDCUtil classes now have the get_display_info method
  • Monitor class added
  • list_monitors and list_monitors_info functions added. The command line -l argument also works
  • The XBacklight class remains unchanged due to the fact that the display command line argument doesn't work
  • Each linux class now has executable attribute which is the path to the executable that it calls (eg: XRandr.executable = 'xrandr')

Removed:

  • The methods dictionary in the linux submodule

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 None is added to the output instead of nothing. Output length should now always match length of list_monitors()

v0.6.2

  • Merged commit from @drojf in issue #5, fixing fade_brightness

v0.5

25 Nov 18:36

Choose a tag to compare

  • 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 Monitor class on Windows
  • display kwarg 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_serials as 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

15 Nov 00:24

Choose a tag to compare

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 display kwarg to allow users to specify which display they wish to control. Also added to command line args
  • Added --verbose command 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_value kwarg

Special thanks to lcharles for raising issue #1 and making me aware that DDC/CI commands existed

v0.4.1

  • Added method kwarg 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 function list_monitors (Windows only), add a command line option for this and add a function in the windows module called list_monitors_with_method, which returns list of pairs of display names and their methods
  • Fixed the XRandr.get_brightness function returning the wrong type

v0.3

04 Oct 15:41

Choose a tag to compare

Changes:

  • You can now call this module from the command line! Use python -m screen_brightness_control --help to get the available commands
  • Fixed fade_brightness not working when running in a new thread on Windows
  • Removed raw_value kwargs for linux as they were not really useful
  • Deprecated max_value kwarg

V0.3.1:

  • Updated FAQ section of README

v0.2.0 + Patches

23 Aug 00:52

Choose a tag to compare

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 False upon failure but they raise a ScreenBrightnessError. This was an effort to unify the various exceptions that get raised (wmi.x_wmi on Windows, FileNotFoundError and PermissionError on Linux)
  • get_brightness and set_brightness accept a new kwarg verbose_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 the ScreenBrightnessError

v0.2.1:

  • Fixed get_brightness attribute 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_brightness will 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

16 Aug 19:53

Choose a tag to compare

v0.1.7 Changes:

  • Made some type conversions in set_brightness ever so slightly more reliable
  • Added max_value kwarg to get_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

13 Aug 17:05

Choose a tag to compare

Added a new function called fade_brightness which does exactly what it says on the tin

A bunch more quick fixes

26 Jul 22:59

Choose a tag to compare

Fixed package dependencies for Windows
Fixed set_brightness force and raw_value kwargs
Fixed some other small bugs

Quick Fix 2

26 Jul 19:39

Choose a tag to compare

Fixed a bug in the get_brightness function and updated the version number

Quick Fix 1

26 Jul 19:22

Choose a tag to compare

Fixed setup.py to correctly format the README.md for PyPi