Tiling and window manager for GNOME Please report bugs/issues on https://github.com/forge-ext/forge/issues
Note: Binary files aren't shown on the web site. To see all files, please download the extension zipfile.
| Version | Status |
|---|---|
| 84 | Active |
| 83 | Active |
| 82 | Rejected |
| 81 | Inactive |
| 80 | Inactive |
| 79 | Rejected |
| 78 | Inactive |
| 77 | Active |
| 76 | Rejected |
| 75 | Active |
| 74 | Rejected |
| 73 | Rejected |
| 72 | Active |
| 71 | Active |
| 70 | Inactive |
| 69 | Inactive |
| 68 | Active |
| 67 | Active |
| 66 | Inactive |
| 65 | Inactive |
| 64 | Inactive |
| 63 | Inactive |
| 62 | Inactive |
| 61 | Inactive |
| 60 | Inactive |
| 59 | Inactive |
| 58 | Inactive |
| 57 | Inactive |
| 56 | Inactive |
| 55 | Inactive |
| 54 | Inactive |
| 53 | Inactive |
| 52 | Inactive |
| 51 | Inactive |
| 50 | Inactive |
| 49 | Inactive |
| 48 | Inactive |
| 47 | Inactive |
| 46 | Inactive |
| 45 | Inactive |
| 44 | Inactive |
| 43 | Inactive |
| 42 | Inactive |
| 41 | Inactive |
| 40 | Inactive |
| 39 | Inactive |
| 38 | Active |
| 37 | Inactive |
| 36 | Inactive |
| 35 | Active |
| 34 | Inactive |
| 33 | Inactive |
| 32 | Inactive |
| 31 | Rejected |
| 30 | Inactive |
| 29 | Rejected |
| 28 | Rejected |
| 27 | Inactive |
| 26 | Inactive |
| 25 | Inactive |
| 24 | Inactive |
| 23 | Inactive |
| 22 | Inactive |
| 21 | Inactive |
| 20 | Inactive |
| 19 | Inactive |
| 18 | Inactive |
| 17 | Inactive |
| 16 | Inactive |
| 15 | Rejected |
| 14 | Rejected |
| 13 | Inactive |
| 12 | Inactive |
| 11 | Inactive |
| 10 | Inactive |
| 9 | Inactive |
| 8 | Inactive |
| 7 | Rejected |
| 6 | Rejected |
| 5 | Inactive |
| 4 | Inactive |
| 3 | Inactive |
| 2 | Inactive |
| 1 | Rejected |
Added session-mode unlock-dialog - and referenced the recommended pattern from GJS docs. For this extension, the tree data structure needs to be persisted in memory during lock screen. Otherwise, users need to re-arrange their windows every single time it locks.
Ok but, `unlock-dialog` doesn't mean the extension won't get disabled. When users lock the screen: 1. All extensions get disabled to rebase (including extensions with `unlock-dialog`). 2. Extensions with `unlock-dialog` get enabled. Is that what you want?
Based on my testing - when the screen gets locked, it only ran the remove indicator and disable keybindings functions. The windows had been preserved. So I think it is working correctly? When logging out or disabling in Extensions Manager it is complete disabled. Based on the GJS docs: Like standard extensions, the extension will be enabled when the user logs in and logs out, but won't be disabled when the screen locks. I followed the review guidelines to implement: https://gjs.guide/extensions/review-guidelines/review-guidelines.html#session-modes
You shouldn't monitor the session mode changes. Instead, you shouldn't add indicator and key bindings on `enable()` (when session mode is `unlock-dialog`). Anyway, I don't think this is a good approach for what you wanna achieve. The `unlock-dialog` has been introduced for extensions modifying unlock dialog. when you use `unlock-dialog` in session modes, it means: **the extension will be disabled and then re-enabled in lock.**
Forge