Brightness control for all the monitors detected by ddcutil This tool uses ddcutil as backend for communication with your display. Read setup instructions from: https://github.com/daitj/gnome-display-brightness-ddcutil/blob/master/README.md
Note: Binary files aren't shown on the web site. To see all files, please download the extension zipfile.
Version | Status |
---|---|
54 | Active |
53 | Active |
52 | Active |
51 | Active |
50 | Active |
49 | Active |
48 | Active |
47 | Active |
46 | Active |
45 | Rejected |
44 | Active |
43 | Active |
42 | Inactive |
41 | Inactive |
40 | Inactive |
39 | Rejected |
38 | Inactive |
37 | Inactive |
36 | Inactive |
35 | Inactive |
34 | Inactive |
33 | Inactive |
32 | Inactive |
31 | Active |
30 | Active |
29 | Inactive |
28 | Inactive |
27 | Inactive |
26 | Rejected |
25 | Inactive |
24 | Inactive |
23 | Inactive |
22 | Inactive |
21 | Inactive |
20 | Inactive |
19 | Rejected |
18 | Rejected |
17 | Rejected |
16 | Inactive |
15 | Inactive |
14 | Inactive |
13 | Inactive |
12 | Inactive |
11 | Inactive |
10 | Inactive |
9 | Rejected |
8 | Rejected |
7 | Inactive |
6 | Inactive |
5 | Rejected |
4 | Inactive |
3 | Inactive |
2 | Inactive |
1 | Inactive |
1. Please use `console.*` instead of `log()`: https://gjs.guide/extensions/upgrading/gnome-shell-45.html#logging 2. All of those timeout functions supported on 45 (line 41-79 convenienceExt.js). Please remove them. 3. Also null out `this.settings` in disable: https://gjs.guide/extensions/review-guidelines/review-guidelines.html#destroy-all-objects 4. `destroy()` not `destory()`: - line 135 extenision.js - line 272, 358 indicator.js 5. Shouldn't be `console.log()`, should be `console.debug()` (line 197-200 extension.js). 6. Timeout should be removed on disable (line 148 and 544 extension.js): https://gjs.guide/extensions/review-guidelines/review-guidelines.html#remove-main-loop-sources
I do not have GNOME 45, running I relying on a pull request by contributors and their feedbacks. I have fixed most of these issues, once I get feedbacks from the contributors I will upload a new version. 5. By default extension won't output anything to log, you need to enable it peferences for `brightnessLog` to work. How does console.debug work in normal session, what are the steps to enable debug mode, I guess if I replace console.log with console.debug, I need to add that step also in my issue template. 6. for line 148, the clearInterval in line 128 should remove the timeout, do I need to do something else also?
5. `console.debug()` only show up in the logs if the debug mode is enabled (`G_MESSAGES_DEBUG=all` or enabled GLib log debug). So, You can use `console.log()` if users have controls over the logs in your extension's settings. 6. Missed that. It's ok then.