Skip to content

Conversation

@sh41
Copy link
Contributor

@sh41 sh41 commented Dec 18, 2025

Loving the Widget, but I found that I needed to disable/enable after every restart due to the ExperimentalSettings flag not being available in the project config when the StatusBarManager starts up.

This PR registers a backgroup startup activity that only runs after the project (including the application) settings have loaded.

It also moves the settings watcher into this class to keep the Factory "pure". When the experimental status of the widget moves to production, the startup activity is still useful for the settings watcher.

Lastly, and purely because I wasted an hour wondering why the widget wasn't working after a sandbox reset, I've defaulted the widget to display as soon as the experimental setting is enabled. Looking at the comments, I think the setting was originally at project level, but it is now at application level, and it makes sense to me that if I enable it in Experimental Settings, it should immediately appear in the status bar.

@sh41 sh41 force-pushed the fix/widget-startup branch from c4bbc10 to 8a5ae52 Compare December 18, 2025 22:09
Previously the Widget would need to be disabled/enabled after every restart due to the ExperimentalSettings flag not being available in memory when the StatusBarManager starts up.

This registers a startup activity that only runs after the project (including the application level settings) have loaded.

It also moves the settings watcher into this class to keep the Factory "pure".

Lastly, default the widget to display as soon as the experimental setting is enabled. I think the setting used to be at project level, but it is now at application level, and it makes sense to me that if I enable it in Experimental Settings, it should immediately appear in the status bar.
@sh41 sh41 force-pushed the fix/widget-startup branch from f3b488b to e8673a0 Compare December 20, 2025 09:34
@sh41 sh41 mentioned this pull request Dec 22, 2025
@joshuataylor
Copy link
Collaborator

Ah! Yes, a couple of quirks these were from the merge that happened where I changed the scope.

Thanks for this!

@joshuataylor joshuataylor merged commit d1e605c into KronicDeth:main Jan 6, 2026
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