-
-
Notifications
You must be signed in to change notification settings - Fork 275
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues with dual-screen setup and copyToAll #797
Comments
|
It's broken, and I don't think it's "fixable". I wanted to work on a replacement but didn't get to it yet. |
I think
is key here. AFAIK, this is something that would need to be done on the compositor side. |
Uppon further testing it turns out, that this issue only applies to floating windows. Any "normal" window remains on the same screen. Is there some way of using this? |
Probably not, unless https://hackage.haskell.org/package/xmonad-contrib-0.17.1/docs/XMonad-Layout-Monitor.html does what you want. Or you're willing to |
`windows` generates mappings one screen at a time, starting with the current. Tracking the windows it's already generated mappings for, it excludes them from the tiles under consideration, hence supporting window duplication in a first-biased manner. This allows the current screen to win against any contenders and keep duplicated tiles within reach. However, it neglects to extend this treatment to floats; they end up mapped in a last-biased manner. Consequently, duplicated floats become very slippery, escaping to any inactive screen they can. This change rectifies that issue. See: xmonad/xmonad-contrib#797
`windows` generates mappings one screen at a time, starting with the current. Tracking the windows it's already generated mappings for, it excludes them from the tiles under consideration, hence supporting window duplication in a first-biased manner. This allows the current screen to win against any contenders and keep duplicated tiles within reach. However, it neglects to extend this treatment to floats; they end up mapped in a last-biased manner. Consequently, duplicated floats become very slippery, escaping to any inactive screen they can. This change rectifies that issue. See: xmonad/xmonad-contrib#797
`windows` generates mappings one screen at a time, starting with the current. Tracking the windows it's already generated mappings for, it excludes them from the tiles under consideration, hence supporting window duplication in a first-biased manner. This allows the current screen to win against any contenders and keep duplicated tiles within reach. However, it neglects to extend this treatment to floats; they end up mapped in a last-biased manner. Consequently, duplicated floats become very slippery, escaping to any inactive screen they can. This change rectifies that issue. See: xmonad/xmonad-contrib#797
Hi,
as stated in the title, if copyToAll from
XMonad.Actions.CopyWindow
(xmonad version 0.17.1) is used on a setup with two screens, it just doesnt work.If the copyToAll command is called, the selected window moves to the other (inactive) screen. When trying to switch screens, the window moves to the new inactive screen. It seems to work somehow, since the window is always visible (just on the wrong screen) independend from to workspace. I tested it with my second screen turned off and it worked as expected.
Is there a way for the copied window to either stay on the screen it originated from or to always be on the active screen?
The text was updated successfully, but these errors were encountered: