Skip to content

fix: migrate implicit nodes back to main display on display change#23

Merged
typester merged 1 commit intomainfrom
fix/wrong-monitor
Feb 25, 2026
Merged

fix: migrate implicit nodes back to main display on display change#23
typester merged 1 commit intomainfrom
fix/wrong-monitor

Conversation

@typester
Copy link
Owner

When a display temporarily disappears and comes back, set_displays() returned early if no displays were removed, leaving implicit nodes stranded on a non-main display. Now, after handling removed displays, also scan all non-main displays and migrate stray implicit nodes back to main.

When a display temporarily disappears and comes back, set_displays() returned
early if no displays were removed, leaving implicit nodes stranded on a
non-main display. Now, after handling removed displays, also scan all non-main
displays and migrate stray implicit nodes back to main.
@typester typester merged commit 94fc50c into main Feb 25, 2026
2 checks passed
@typester typester deleted the fix/wrong-monitor branch February 25, 2026 18:00
typester pushed a commit that referenced this pull request Feb 25, 2026
🤖 I have created a release *beep* *boop*
---


## [0.1.10](v0.1.9...v0.1.10)
(2026-02-25)


### Bug Fixes

* migrate implicit nodes back to main display on display change
([#23](#23))
([94fc50c](94fc50c))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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.

1 participant