Simple GNOME Shell extension manager in the top panel For support, please report any issues via the homepage link below.
Note: Binary files aren't shown on the web site. To see all files, please download the extension zipfile.
| Version | Status |
|---|---|
| 40 | Active |
| 39 | Rejected |
| 38 | Active |
| 37 | Active |
| 36 | Active |
| 35 | Active |
| 34 | Active |
| 33 | Inactive |
| 32 | Inactive |
| 31 | Active |
| 30 | Active |
| 29 | Active |
| 28 | Active |
| 27 | Active |
| 26 | Inactive |
| 25 | Active |
| 24 | Inactive |
| 23 | Inactive |
| 22 | Rejected |
| 21 | Rejected |
| 20 | Rejected |
| 19 | Active |
| 18 | Rejected |
| 17 | Inactive |
| 16 | Inactive |
| 15 | Inactive |
| 14 | Inactive |
| 13 | Inactive |
| 12 | Inactive |
| 11 | Inactive |
| 10 | Inactive |
| 9 | Rejected |
| 8 | Rejected |
| 7 | Inactive |
| 6 | Rejected |
| 5 | Inactive |
| 4 | Inactive |
| 3 | Inactive |
| 2 | Rejected |
| 1 | Rejected |
As I mentioned in the other extension review, the `gsettings` needs to move to `buildPrefsWidget` (line 10 prefs.js): https://extensions.gnome.org/review/33520 Do you want to fix that and send it again?
Does that matter? The prefs page runs as a standalone process, and the bindings with `Gio.Settings` will be disconnected automatically when the widgets finalize. It should never crash the GNOME Shell. Right? Whatever, maybe the next time.
It doesn't crash GNOME Shell but it remains there after the prefs window is getting closed (not going to be garbage collected). I approve this since you have other extensions like this but please fix it for the next version.
Let the `gsetting` connect to log sth in the global scope, if that so, open the setting window repeatedly to modify the setting, each time the output log is only one or will increase with the number of openings?
1. Do this in `buildPrefsWidget`: ```js gsettings.connect('changed::del-button', () => { log('TEST'); }); ``` 2. Restart GNOME Shell. 3. Open the prefs window and then close it. 4. Open dconf and change the `del-button` value. As you can see the log is happening in the log. Because the global object didn't get destroyed after you closed the prefs window.
Extension List