Version 1.5.0 - Final

I've moved on from GNOME. I've merged the CPU temperature monitor/warning from the dev branch in the condition it was in when I stopped work. It had performed fine in the time I used it but the code wasn't as clean as I'd like. At this point GNOME 50 was just released and the extension worked in the testing I did in the testing environment.

Version 1.4.1 - Refactor

All new bugs!

Version 1.4.0 - New feature: Fix occasionally missing wallpaper on the lockscreen

As long as I've been using GNOME, the wallpaper on the lockscreen has come and gone at random. Now, the user can explicitly force the desktop wallpaper to load with the standard blur and brightness. If you're interested in more customization you'll want to use another extension and if you do you should probably disable this feature, but otherwise all it does is take the wallpaper and load it (while accommodating light/dark variants).

There's also now a toggle for enabling customizing the lockscreen clock font whereas before it was always being modified, you just had the option of resetting to default font.

Version 1.3.0 - New feature: Workspace indicator now works with PaperWM's visible workspaces

This isn't a new feature per se, but it's new-ish in that the workspace indicator now smartly adapts to PaperWM's use of unique workspaces per monitor. The hacky workaround of hiding a defined workspace has been removed.

Worth noting is that PaperWM keeps workspaces associated with the monitor it's on when you create a window so if you try to switch to a workspace that you created on another monitor it will move that monitor to the workspace, not bring it over to the main monitor. You'll have to use PaperWM's keybind shortcuts to move a workspace to a different stack, but PaperWM users should be used to this workflow.

Version 1.2.5 - Correct two try-catch blocks

Fixed

• Added back two old try-catch blocks without a descriptive error message, now they're fixed.

Version 1.2.4 - Abandoning EGO submission & more try-catches

Fixed

• The comments are a lot cleaner and more uniform now, describing every method throughout. Prefs modules were always okay but now they're a little better too.
• Removed ADDED some try-catch blocks that Just Perfection feels are indicative of AI code. It turns out I use these error messages way more than I thought and missed them too much. While this precludes EGO submission, for now it is what it is.
• Refactored lockscreenUnblank.js and while it's still based on the logic of Unblank Lockscreen, the structure of the code is now easier for me to read and maintain.
• Added a note in the README in case anyone has expectations of competence. That should never have been the case, the logo is a Q vomiting, but it's a little more explicit now.

Version 1.2.3 - Added handling for extension-added title bar context menu items in prefs

Fixed

• The module always handled extension-added menu items properly but in cleaning up comments and labeling the prefs modules for easy searching I found that it wasn't accounted for in the preferences. Now such items can be added with the Add... button.
• As mentioned, the comments are cleaner and more uniform.
• Removed some try-catch blocks that Just Perfection feels are indicative of AI code.

Version 1.2.2 - Better documents & preferences

Fixed

• Made module options disable in preferences when the feature is disabled

Added

• Images and videos to the README

Version 1.2.1 - Added descriptive console log error messages

Fixed

• Cleaned up code for the Google Calendar feature so that it's less likely to leak.

Added

• Console error messages for anything that fails to load

Version 1.2.0 - New feature: Have the event button open that day in Google Calendar

Did you know the Event Button, which is in the date menu below the calendar and displays the selected date and any events for that day, when clicked does not take the user to that day in the calendar that it opens? It's true, even with the default GNOME Calendar application as the MIME type handler for text/calendar, it will always lead to the current day even though that application has a way to go to the correct date with a properly formed URI.

Now I want to be fair, this is a recent problem having been brought to the attention of the maintainers in 2019 so it's understandable it hasn't been addressed. But while this temporary situation exists, you can now salve the pain with this feature that simply fixes the problem.

Well, fixes the problem if you use Google Calendar.

Which I do. So it fixes the problem for me.