Skip to content

feat: take peripherals at launch when a marked display is connected - #121

Merged
MegaManSec merged 1 commit into
mainfrom
feat/display-trigger-on-launch
Sep 28, 2026
Merged

MegaManSec merged 1 commit into
mainfrom
feat/display-trigger-on-launch

Conversation

@MegaManSec

Copy link
Copy Markdown
Owner

A marked display that was already connected when Magic Switch started used to be treated as the baseline and never triggered a switch. Now the monitor starts from an empty set and reconciles after the usual debounce, so launching while docked takes the peripherals like a fresh dock.

The existing guards in takeAllPeripheralsIfAway still apply: it's a silent no-op if the peripherals are already here, if Bluetooth is unhealthy, or if a switch is in flight.

Trade-off: restarting the app while docked (e.g. after an update) now pulls peripherals back even if they were deliberately sent to the other Mac.

README updated to match.

A marked display that was already connected when Magic Switch started
used to be treated as the baseline and never triggered a switch. Now the
monitor starts from an empty set and reconciles after the usual debounce,
so launching while docked takes the peripherals like a fresh dock. The
existing guards still apply: nothing happens if they're already here,
Bluetooth is unhealthy, or a switch is in flight.
@MegaManSec
MegaManSec merged commit 829302b into main Sep 28, 2026
2 checks passed
@MegaManSec
MegaManSec deleted the feat/display-trigger-on-launch branch September 28, 2026 17:16
@github-actions

Copy link
Copy Markdown

🎉 This PR is included in version 2.28.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant