v1.0.13: fix cross-folder timer stop
Remove onWillDisappear cache pruning so buttons in other folders remain in settingsCache — previously navigating away deleted their entries, causing the stop-other-timers loop to miss them on next key press. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -1,4 +1,4 @@
|
||||
const CURRENT_VERSION = "1.0.12";
|
||||
const CURRENT_VERSION = "1.0.13";
|
||||
const GITEA_BASE = "https://gitea.pdmarf.co.uk/pdm/stream_deck_notion_timer/raw/branch/master";
|
||||
const SIGNING_PUBLIC_KEY = `-----BEGIN PUBLIC KEY-----
|
||||
MCowBQYDK2VwAyEAN7ko8TUpuPzPAJuKAZCRjV0c4ZSlou5d9pUAF6o12b4=
|
||||
@@ -97,10 +97,6 @@ function buttonTitle(projectName: string): string {
|
||||
class TimerToggle extends SingletonAction<TimerSettings> {
|
||||
private settingsCache = new Map<string, TimerSettings>();
|
||||
|
||||
async onWillDisappear(ev: WillAppearEvent<TimerSettings>): Promise<void> {
|
||||
this.settingsCache.delete(ev.action.id);
|
||||
}
|
||||
|
||||
async onWillAppear(ev: WillAppearEvent<TimerSettings>): Promise<void> {
|
||||
this.settingsCache.set(ev.action.id, ev.payload.settings);
|
||||
const { activeEntryId, projectName } = ev.payload.settings;
|
||||
|
||||
Reference in New Issue
Block a user