Giter Site home page Giter Site logo

Comments (3)

LGUG2Z avatar LGUG2Z commented on June 24, 2024

The behaviour when dragging a window container onto an empty monitor workspace is clear for me; it should be appended to that (empty) workspace.

I'm not sure what the defeat behaviour should be when dragging to another monitor with an already populated workspace. Should the window being dragged be swapped with the window it ends up over (ie. across monitors)? Or should the window just be appended (or prepended) to the focused workspace of the target monitor?

Open to suggestions for defining the default behaviour.

from komorebi.

da-rth avatar da-rth commented on June 24, 2024

@LGUG2Z we could define behaviour similar to that of SwayWM:

  • dragging a (source) window onto the left or right side of another (destination) window will split the destination window, placing the source window tiled to the left or right of the destination window

  • dragging a source window into the center area of another destination window will swap that window with the source window

SwayWM actually displays a coloured rectangle guide above the destination window (where the source window is being dragged to) in order to show which action will be taken:

swaywm_example.mp4

So when dragging over a window, you would split the destination window into 5 sections and decide the action based on which section the cursor lands in when releasing the mouse:

example

I do think a visual rectangle guide would be very useful if this were to be implemented

from komorebi.

LGUG2Z avatar LGUG2Z commented on June 24, 2024

The way that Sway handles this is very elegant. I think being able to do this also depends to some extend on what I mentioned in this issue, in order to be able to resolve sibling nodes, parent nodes and child nodes quickly and easily for any layout: #59 (comment)

In order to have this case handled in a minimal way until then, when dragging a window between monitors to a destination monitor that already contains 1+ visible window containers, I will have the source window container inserted at the index of the window container the mouse drags ends on the destination monitor/workspace.

For the Sway-like zones, let's create a new issue from your comment that can be tracked as a feature request.

from komorebi.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.