❦ 20 octobre 2012 13:06 CEST, Uli Schlachter <[email protected]> :
>>> Could you try making the window floating and see where its corner ends up?
>>> If it
>>> moves outside of the visible space, awesome considers it to be on screen 1.
>>> Just
>>> because "nowhere" isn't a good answer. ;-)
>>>
>>> (Yes, eventually all of this should be replaced with some more complicated
>>> magic. For example using the center of the window instead of its corner. Or
>>> doing more math and see where most of its area is...)
>>
>> I didn't try, but maybe attaching a signal to `property::screen` and
>> restoring the original screen would do the trick. The question is: how
>> to get the original screen?
>
> Uhm. You don't. I guess you would need to save each client and their screen
> in a
> lua table to be able to figure out the old one.
Yes, that's cumbersome. This does not happen to me too often so I won't
try to implement this myself.
> But with your approach, how would you move clients between screens when you
> actually want to do that?
Explicit changes by the user would be allowed. There are not many places
where the user request an application to migrate to another screen. A
global variable could kept the fact that the user requested a change and
any change will be allowed for one second.
--
Use the good features of a language; avoid the bad ones.
- The Elements of Programming Style (Kernighan & Plauger)
--
To unsubscribe, send mail to [email protected].
