App Layout restore clears Stash tracking after stashRight/stashDown action
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 48/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Tranquilla
- Stack tecnologico
- macos
- Ambito
- desktop
Direzione di ricerca
Start with the provided App Layout restore log and trace the sequence from stashRight/stashDown through cursor tracking to the following manual action. Compare the restore sequence with running the stash shortcut manually. Done means restored stashed windows retain slide-out behavior when the cursor reaches the stash edge.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Description
When restoring an App Layout that contains stashed windows, the windows are moved back into their correct stash positions, but the slide-out behavior no longer works.
Running the same stash keyboard shortcut manually after the layout restore fixes the issue.
It appears the layout restore successfully applies the stash action and starts cursor tracking, but a following manual action clears the stash state.
Environment
- Rectangle Pro: v3.80 (225)
- macOS: 26.5.1 (Build 25F80)
- Hardware: Apple Silicon MacBook Pro
- Display: Samsung Odyssey G95SD (5120x1440)
Steps to reproduce
- Arrange multiple application windows
- Use Rectangle Pro stash shortcuts:
- Stash Right
- Stash Down
- Save the arrangement as an App Layout
- Restore the App Layout
- Move cursor to stash edge
Expected behavior
The restored stashed windows should slide out when hovering over the stash area.
Actual behavior
The windows are moved to the correct stash locations, but they do not slide out.
Running the stash shortcut again on the affected window restores the expected slide-out behavior.
Relevant logs
The log appears to show:
stashRight/stashDown -> cursor tracking starts -> manual action executes -> cursor tracking stops
Rectangle Pro v3.80 (225)
macOS: Version 26.5.1 (Build 25F80)
Model: MacBook Pro Apple Silicon
Display: Odyssey G95SD 5120x1440
2026-06-12T07:44:13-06:00:
Layouts: started layout: Dev - Chat
2026-06-12T07:44:13-06:00:
Layouts: 11 windows, 10 unique PIDs with windows
--- Stash Right example ---
2026-06-12T07:44:13-06:00:
LayoutState: Applying window action
2026-06-12T07:44:13-06:00:
Execute action: stashRight, source: keyboardShortcut
2026-06-12T07:44:13-06:00:
Stashing window ID: ### to location: stashRight
2026-06-12T07:44:13-06:00:
AX position proposed: (5119.0, 30.0), result: (5119.0, 30.0)
2026-06-12T07:44:13-06:00:
Starting cursor tracking (stashed count: 1) ✅
2026-06-12T07:44:13-06:00:
Execute action: manual, source: keyboardShortcut ⁉️
2026-06-12T07:44:13-06:00:
Stopping cursor tracking (menu open: false, stashed count: 0) ‼️
2026-06-12T07:44:13-06:00:
LayoutState: indexAndApply completed,
Windows applied: 1,
Windows stashed: 0,
Windows remaining: 0
--- Stash Down example ---
2026-06-12T07:44:13-06:00:
Execute action: stashDown, source: keyboardShortcut
2026-06-12T07:44:13-06:00:
Stashing window ID: ### to location: stashDown
2026-06-12T07:44:13-06:00:
AX position proposed: (5119.0, 1439.0),
result: (5119.0, 1408.0)
2026-06-12T07:44:13-06:00:
Starting cursor tracking (stashed count: 1) ✅
2026-06-12T07:44:13-06:00:
Execute action: manual, source: keyboardShortcut ⁉️
2026-06-12T07:44:13-06:00:
Stopping cursor tracking (menu open: false, stashed count: 0) ‼️
2026-06-12T07:44:13-06:00:
LayoutState: indexAndApply completed,
Windows applied: 1,
Windows stashed: 0,
Windows remaining: 0
--- Layout completion ---
2026-06-12T07:44:13-06:00:
Layouts: Bringing 1 windows forward for spec: Stash Right
2026-06-12T07:44:13-06:00:
Layouts: Bringing 1 windows forward for spec: Stash Down
2026-06-12T07:44:13-06:00:
Layouts: completed - Total windows applied: 7
Notes
The App Layout appears to save the stash actions correctly because stashRight and stashDown are executed during restore.
The issue appears to happen after the stash action succeeds, when the stash tracking state is cleared before the layout restore completes.
- Lingua principale
- Nessun dato sulla lingua
- Stelle
- 156
- Fork
- 1
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di rxhanson/RectanglePro-Community
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 35/100
rxhanson/RectanglePro-Community#944 · 1 commento ·
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 35/100
rxhanson/RectanglePro-Community#943 · 1 commento ·
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 25/100
rxhanson/RectanglePro-Community#939 · 1 commento ·
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 45/100
rxhanson/RectanglePro-Community#937 · 4 commenti ·
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
rxhanson/RectanglePro-Community#936 · 2 commenti ·
Tutte le issue di rxhanson/RectanglePro-Community
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
Facepunch/sbox-public#12305 ·
I maintainer di solito rispondono entro 5 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
JiaFeiMiao-K-Cat/DiscImageStudio#205 ·
I maintainer di solito rispondono entro 1 giorno
-
bug keep-fresh
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
Flow-Launcher/Flow.Launcher#4744 ·
I maintainer di solito rispondono entro 1 giorno
-
The Browser tab fails with a Wayland error when Open Terminal runs from a Wayland desktop sessionAperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
open-webui/open-terminal#210 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
flyingpie/windows-terminal-quake#419 ·
I maintainer di solito rispondono entro 1 giorno