Repository navigation
feat: add optional default app launcher mode (tiling, float, niether) in extension settings - #121
JiruGutema wants to merge 7 commits into
Conversation
Style, active style, position, scroll, empty/occupied, custom labels and border radius.
Super+1-9 switches workspace, Super+Shift+1-9 moves the focused window. Toggle in prefs.
Co-Authored-By: Claude Sonnet 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01F9Wg95qFaK6gVtFX7ACriH
… extension settings
|
Please don't make a major overhaul of an existing feature without first identifying and addressing the issues with it. This PR proposes a major overhaul of the "Floating Window Exceptions" feature, but the existing functionality already seems to be doing its job. What exactly does this PR change or improve? Honestly, I don't see anything significantly better or any meaningful new functionality being introduced. I still appreciate the effort you've put into this, but I feel like this PR doesn't really align with the project's goals or direction. |
Thanks for the feedback. Here's the problem I was trying to solve. I use Vicinae, a launcher that should always float. O-Tiling treats it as a normal window, so each time I open it the screen splits between Vicinae and whatever I was working in. The current exception list is float-only and has to be set up per app by hand, so every new launcher or overlay app hits the same problem. The PR lets each app have its own default mode (tiled, floating or ignored), so a launcher like Vicinae can be set to floating once and never split the screen again. plus, we can add an exception to this. for this is to work, i think we need to edit the configuration by hand. this pr avoids that and lets you to add an exception in the setting itself. |
This pull request introduces a major overhaul of the "Floating Window Exceptions" feature, transforming it into a more flexible and user-friendly "Window Rules" system. Users can now specify how each application or window should open (tiled, floating, or ignored) rather than being limited to floating exceptions. The UI, backend logic, and documentation have all been updated to reflect these changes, and the configuration system now supports live reloading and more granular rule management.
Before:
Untitled.design.mp4
After:
Untitled.design.1.mp4
Setting Page:
