Conversation
Added a new swap feature that allows users to exchange two ready windows, including remote desktop streams, using the Super+Shift+Arrow shortcut. Enhanced the session management to ensure that zone reservations and source assignments are updated correctly during swaps. Updated the documentation to reflect these changes and included new tests to validate the swap functionality.
Updated the content management system to support additional file types in the stream directory, including PowerShell and C# scripts. Improved the validation process to exclude these new types from compilation. Enhanced the installation script to ensure proper installation of these files. Updated documentation to clarify the functionality of the Scenes tab and its controls, including scene saving and restoration processes. Added new tests to validate these features.
Updated the Mac display adapter to utilize native CoreGraphics APIs, ensuring that display modes are preserved and correctly managed during transitions. Enhanced the stream control logic to provide better user feedback for connection states, including reconnect and restore actions. Improved audio handling for native PipeWire clients and added tests to validate these changes. Updated documentation to reflect the new display management features and control options.
* Allow directional moves into empty layout slots * Preserve navigation within stacked layout slots
The rail's header names the workspace until a scene is applied, then the scene with how many apps are placed. Saved scenes are cards like the layout list, with the apps drawn in their zones; the row applies and the delete shows on hover. One ZONES list replaces CONTENT, ZONE and CHANGE TO, with zones named by position. The picker under the selected zone filters as you type and takes the keys: Enter assigns, arrows pick, digits select zones, Esc clears. It shows app icons and groups open windows with their titles, remote desktops, and installed apps. Zone cards show what they hold with icon, name and state, preview a hovered match, offer Change, Clear and Retry, and outline zones that need attention. The catalog lists each app's icon and each saved scene's sources, and skips placeholder window classes. The pane keeps its lists by value so the catalog poll does not rebuild rows.
Bump the manifest to 1.1.0 and date the changelog, adding the Scenes feature, the remote desktop launcher note, and the empty-slot moves. The README's repository map lists the scenes service, its entry point, the navigation module, and the Scenes tab files. RELEASING.md names the 1.1.0 release as the marketplace candidate that supersedes 1ba0f8a.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Promote develop to main as release 1.1.0, per docs/RELEASING.md "Subsequent releases" step 2. The manifest says 1.1.0; the changelog dates the release 2026-09-06.
Since 1.0.1 (1ba0f8a):
Validation: every local CI suite passed on the release preparation (#6); both required checks passed on #5 and #6. After this merge: confirm CI on the resulting main SHA, tag v1.1.0 on it, publish release notes, re-lock main, and update marketplace submission #4893 with the new SHA.