On Friday, 15 May 2020 22:16:22 UTC+2, tcld wrote:
>
>
>
> On Friday, 15 May 2020 21:20:47 UTC+2, Tycho Andersen wrote:
>>
>> On Fri, May 15, 2020 at 10:58:33AM -0700, tcld wrote:
>> > I regularly use xfreerdp to connect to a different machine, and while I
>> am
>> > doing that it is very beneficial to have the xfreerdp-window span
>> multiple
>> > screens.
>> >
>> > Should there already be any way to accomplish something like this,
>> please
>> > let me know.
>> >
>> > I have tried the following two things so far, the third point is just a
>> > theory I don't know how to realize yet:
>> >
>> > 1. Write a custom layout that steals screen space in its
>> > configure-method.
>> > Flaws:
>> > - Sometimes my screen locks and afterwards I can still see the
>> > lockscreen as background on one monitor.
>> > - Other times one application gets in front of the stolen screen
>> > space and it can be difficult to get the multi-monitor window to
>> the top
>> > again.
>> > - Sometimes the bars of the actual screens sit on top of my
>> > mega-window, even though the layout should draw on top of them.
>> > 2. Use the fake_screens variable instead of screens; create one
>> > fake-screen for every screen plus an actual fake-screen spanning all
>> > monitors.
>> > Flaws:
>> > - Very confusing to use.
>> > - I can't click on the bars of the true screens anymore, I guess
>> the
>> > fake-screen is opaque to clicks, even when empty.
>> > 3. Create a custom type of group of which there can only be one
>> > instance. The group can be active on multiple screens (if it isn't,
>> part of
>> > the multiscreen-image is covered), but it doesn't have to be.
>> >
>> > One more thing: I also want to have the standard screens, since the
>> machine
>> > is not exclusively used for RDP-connections. :)
>> >
>> > This is kind of the opposite of what a tiling WM should accomplish, I
>> > guess. But it is nevertheless something I would like to get out of
>> Qtile. I
>> > would very much appreciate ideas of how to tackle this - or a clear
>> > statement that it isn't possible without breaking a leg and an arm.
>>
>> Have you tried floating it across both screens?
>>
>> Tycho
>>
>
> Manually, yes. I have not tried automating it yet, though, so I'll do that
> next.
>
I have tried two things regarding floating now:
Added the following lines in my `@hook.subscribe.client_new`:
if client.match(wmclass='xfreerdp'):
client.floating = True
client.cmd_move_floating(0, 1) # just to make sure there is a little
space to reach the bar, in case the window eats too much focus
With this enabled the window behaved weird, although multi-screening
worked; the window even showed up in a group it didn't belong to (I have
this wm_class auto-moved to a specific group). But, since the
xfreerdp-window knows how much space it wants to occupy, at least I don't
have to hack any sizes into anything. I'll have to give this a more
longterm test next week.
Instead of the above I have also tried to make use of the
`no_reposition_match`-property on the floating layout (very useful for
opening my calendar when clicking the Clock-widget, so the tinkering paid
off either way), but for some reason I couldn't get that to trigger on this
wm_class.
--
You received this message because you are subscribed to the Google Groups
"qtile-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/qtile-dev/bf4f8468-2c69-497d-a1ca-2638be6e5fe4%40googlegroups.com.
