Skip to content

keep queued startup enable and disable commands - #46

Merged
JamesLinYJ merged 1 commit into
mainfrom
cursor/startup-toggle-queue
Nov 9, 2026
Merged

JamesLinYJ merged 1 commit into
mainfrom
cursor/startup-toggle-queue

Conversation

@JamesLinYJ

@JamesLinYJ JamesLinYJ commented Nov 3, 2026 •

Copy link
Copy Markdown
Owner

Summary

Startup enable and disable clicks are no longer latest-wins. While the startup worker is busy, every accepted toggle is queued with its entry id and run in that order.

  • A later refresh does not erase queued toggles, and a toggle is not dropped when a refresh is already pending.
  • Immediately before each registry or startup-folder write, the worker re-reads the entry and compares it with the identity the page already stored. A missing or different entry skips that command and reports the existing missing failure.
  • The page still posts no new strings, menus, or window messages. Dropping the worker does not join it on the UI thread.

Test plan

  • Unit test: two different pending toggles both survive a merge, and a refresh does not erase them. A toggle also survives when a refresh is already pending. A mismatched or missing identity is the existing missing failure.
  • cargo fmt --all -- --check
  • cargo check, cargo clippy, and cargo test — not run to completion here. The default target is x86_64-pc-windows-msvc, and resource compilation stops because llvm-rc is not installed. It was not installed for this change. Linking the Windows test binary also needs link.exe, which this Linux environment does not have.
Open in Web Open in Cursor 

Loading
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