Releases: Crozzers/screen_brightness_control
Releases · Crozzers/screen_brightness_control
v0.23.0
- Add
allow_duplicates
param tofilter_monitors
and most top-level functions (#34, @BingoWon) - Add
allow_duplicates
kwarg to command line (#35, @BingoWon) - Add ability to stop
fade_brightness
thread before starting new one (#38, @BingoWon) - Add ability to set default configuration values (3db8344)
- Can set default value for
method
andallow_duplicate
kwargs
- Can set default value for
- Smarter interval handling in
fade_brightness
(#36, @BingoWon) - Better handling of monitor identification when using relative brightness values in
set_brightness
(#37, @BingoWon) - Fix XRandr reporting displays on wayland session (b76b82f)
- Remove deprecated behaviour of
Display.fade_brightness
returning the new brightness (8880c65)
v0.22.2
- Removed deprecated top level imports (38e1a85)
- Restrict param types in
EDID.parse
to prevent potentialTypeError
(677ea14) - Fixed some docstrings (7d35446, e91f826)
- Fix
force
kwarg not being propagated inDisplay.fade_brightness
(ffa10a1) - Fix excessive calls to
dxva2.DestroyPhysicalMonitor
(b273777) - Fix potential
UnboundLocalError
inVCP.[get/set]_brightness
(6e411d4) - Port test suite to pytest and expand coverage (89642fc...d7a1567)
v0.22.1
v0.22.0
- Type safety improvements
- Improved debugging in test runner
- TTL cache now deletes all expired data semi-automatically (31957f2)
- Upgrade out of date notice on documentation to redirect to latest version of current document (f786f71)
- Switch from
setup.py
topyproject.toml
- Upgraded release CICD
- Fix filtering list of monitors by method in
filter_monitors
- Fix
TypeError
inMonitor
class constructor when passing unknown monitor in - Fix invalid argument when correcting post-fade brightness in
fade_brightness
- Remove support for identifying displays solely by their model (c8e89dd)
- Remove deprecated
Monitor.__getitem__
behaviour - Dropped Python 3.7 support
- Deprecate
Display.fade_brightness
returning the new brightness. Will returnNone
fromv0.23.0
v0.21.0
- Add new
Display
dataclass to replace oldMonitor
classMonitor
is now deprecated for removal in v0.23.0
- Add ability to disable
--async
flag inlinux.DDCUtil
- Add new type aliases with better descriptions of what they mean (see 5fa542f, 20c3dea)
- Fix not all monitor handles being properly cleaned up in
windows.VCP
- Refactor
fade_brightness
- Remove redundant type info in docstrings (see 0431b53)
- Remove redundant docstrings (see 20c3dea)
- Deprecate
Monitor.__getitem__
behaviour for removal in v0.22.0 - Deprecate using a display's model to identify it. Use the name instead. Will be removed in v0.22.0
- Deprecate unused top-level imports for removal in v0.22.0:
MONITOR_MANUFACTURER_CODES
debug_info
v0.20.0
- Merge #28 Added increment change for --set in command line argument from @ujjukumar
- Add ability to look up method name via
get_methods
- Rework exceptions (see d5f1bdd)
- New exceptions added. Should all be backwards compatible
- Refactor:
windows.get_display_info
- removed massive generic try/except blockshelpers.EDID.parse
- more helpful exceptionsfilter_monitors
- better readability
- More consistent use of "display", "screen" and "monitor" terminology (see 46bfac2)
v0.19.0
v0.18.0
- Add ability to report unsupported displays
- Fix
linux.XRandr
reporting unsupported wayland displays - Merge #24 Patch CVE-2007-4559 from @TrellixVulnTeam
- Remove deprecated
flatten_list
function - Drop Python 3.6 support
v0.17.0
- Log stages of
_debug.info
- Fix
list_monitors_info
not fully respecting method kwarg (#21) - Fix windows fallback monitor info using wrong (non-unique) part of DeviceID
This is not a feature update but I bumped the minor version because that last change can potentially break some code.
If you referred to a monitor using a name like: Acer {e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}
then this release will break that as it changes how monitors are named when a model number is not available.
I suggest running list_monitors
to see what the new names are.