Skip to content

screensheild.js: Listen to changes to allow floating setting#13624

Merged
mtwebster merged 1 commit intolinuxmint:masterfrom
JosephMcc:screensaver-settings-1
Mar 8, 2026
Merged

screensheild.js: Listen to changes to allow floating setting#13624
mtwebster merged 1 commit intolinuxmint:masterfrom
JosephMcc:screensaver-settings-1

Conversation

@JosephMcc
Copy link
Contributor

We were only reading this setting at creation time and not updating on settings changes. The timer to start widgets floating also wasn't getting started on first show.

@mtwebster
Copy link
Member

Why don't we just check it in activate() (instead of at startup) - then we don't really need a listener.

@JosephMcc
Copy link
Contributor Author

Sure, I can do that. Is there a reason one way is better than the other?

We were only reading this setting at creation time. Instead read it on each
activation in case the value changed. The timer to start widgets floating
also wasn't getting started on first show.
@JosephMcc JosephMcc force-pushed the screensaver-settings-1 branch from ed742bb to 65aa531 Compare March 8, 2026 17:22
@JosephMcc
Copy link
Contributor Author

Done. Updated and force pushed.

@mtwebster
Copy link
Member

Just so you don't need a signal handler - the setting will never change while the screensaver's active.

@mtwebster mtwebster merged commit 5dbfa5c into linuxmint:master Mar 8, 2026
4 of 5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants