X.H.FadeInactive: Better support for multi monitor setups

Hi, I have added fadeInactiveCurrentWSLogHook which given a rationale fades all windows that are not active. However unlike fadeInactiveLogHook, then it only does it for the current active workspace which makes it much easier to read the content on the other screens. Most of the code is courtesy of Morten Brøns-Pedersen. This is my first official patch, hope it is done correctly. -- Reenberg

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On Fri, Mar 30, 2012 at 15:45:55 GMT, Jesper Reenberg wrote:
I have added fadeInactiveCurrentWSLogHook which given a rationale fades all windows that are not active. However unlike fadeInactiveLogHook, then it only does it for the current active workspace which makes it much easier to read the content on the other screens.
Out of curiosity, what happens if you continually switch between windows on a single workspace? With the current fade hook, the factor keeps getting multiplied (switching focus between windows A and B when C exists makes C fade to nothing after lots of switches). If that's fixed, it should probably be ported back to fadeInactive as well (a different patch if so). - --Ben -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCgAGBQJPdk1eAAoJEKaxavVX4C1X51YQAJskdx03avQS8uodiljeoTmS cpZ/YFGru9i5sIPbnJsONzBpmHHDXNPoQGsrTX+ez7gLgnZ7x/J8c7V1ECq+Pg5R 0MDqwK7/e/3FXh++Weh//SXP3TcQx/KKFbPHsov/712JOp0o36Jb3W44zEmeB0OV +o13sjnsouIW/LcxDxLXkeJyxH1usn2y9pmawM1i9W4wfhVZdBQvq1UBaDVpcB8G y5eoklG4guE8msPu56T0K4wwWhtR8lDm0omxUpEqCiuGPtmd6DBxg9QyExlHEaK1 qOPiUvunJSTRBZLAVcudhXs8Sz50gb8LGXVBegX5Y/rLpgqqhA403R4XraE5CwXX 6ZTTm6zSfj7JwyZNV4bst1NVsSNAfEXqARVY0gCWKN0fKbtoaCL2LvNOUxR2fX6M f/OBCMtKJDVTh598dXAiBjiga7dUWUj4QbuH9lwLVNVJekMc7h+mGyiiT2tAZGC9 M3c8iyU5sfLpeagQ18zu9nNyEh5udHyLljxfrhg+2R+ndyZsM3+NI5igo98Od7Of SoVyqnGyVuSIIr5d1ah6PSWr034sF1MM/slAqMWxvgpLJrYqpmoVg0DpSYbr5jri vc5JfE1v9vxImJIO3c/pZRSbkxXYpUMqCpQ0cMDCcDwz09JntaiusSxNMgOxS8A1 E7tP+BcCBwQ08EOdIOKb =RLtE -----END PGP SIGNATURE-----

On 31 March 2012 02:27, Ben Boeckel
Out of curiosity, what happens if you continually switch between windows on a single workspace? With the current fade hook, the factor keeps getting multiplied (switching focus between windows A and B when C exists makes C fade to nothing after lots of switches).
I have never experienced that, an I must say that I got borred after a minute trying to replicate what you mention, without any noticeable effect (Only switching between window A and B, window C didn't get more transparent). I don't see (from a quick look) any way that the code would allow the opacity to change if lots of switches happen.
If that's fixed, it should probably be ported back to fadeInactive as well (a different patch if so).
It is implemented the exact same way as fadeInactiveLogHook (using "fadeOutLogHook . fadeIf"). -- Reenberg

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On Sat, Mar 31, 2012 at 21:28:24 GMT, Jesper Reenberg wrote:
--===============4195939976883571922== Content-Type: multipart/alternative; boundary=20cf302ef74c4eeaab04bc90a4a4
--20cf302ef74c4eeaab04bc90a4a4 Content-Type: text/plain; charset=ISO-8859-1
On 31 March 2012 02:27, Ben Boeckel
wrote: Out of curiosity, what happens if you continually switch between windows on a single workspace? With the current fade hook, the factor keeps getting multiplied (switching focus between windows A and B when C exists makes C fade to nothing after lots of switches).
I have never experienced that, an I must say that I got borred after a minute trying to replicate what you mention, without any noticeable effect (Only switching between window A and B, window C didn't get more transparent). I don't see (from a quick look) any way that the code would allow the opacity to change if lots of switches happen.
Where/how did you use the fading hooks? I have mine in the logHook. Mind posting the code/diff? - --Ben -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCgAGBQJPl0GfAAoJEKaxavVX4C1XiE4QAOgJTgazZjCRTI/5czRj9x+n ke6hKI4JT2srXvUSBF00GMyHEkenneokhwahGuoBTKWIQ5apSKG+0OctPCeM7LFE wW/GT7zw6pfU4ImsZe7D8Mgjfj8+I7lL63eMP+9sCvB9Dp7zLrygGn3ZEHC+UNZz Mij1Ya7VG8ryXkcioz8YrbWcTeAD0jqXTQ4+IJEf8+j+sqNoEXq8ZsTkQp5YtRZ7 bxPQNQJP00FsvVsbe+7SGgGVJYm6ZyvYcG53PZmgOv3aZKsJtavbKC6RE8slIfpa bjOM2cSF8xNho37JTrHlRs1qG0mkmkvnDKx7LEA/7e6cHBN6nZ9ouvIULlNChDJ8 1BVVxyOFHyL6zEddVbfzhsqVQQIlXD6KRNpilJAQrzztiaxU9DDQw+tSmV/xaGR0 LjxGqUUFpYIJEcjPnHKJiiVUn/OsTmmYwt88wT18MRNabPp/rOhQhzFx5pAucaBq Jdlp5tKSdpyxwO/JAflXc8hLj/Hna1nYclQOvThJlsazWxzzVM6DOsH81Du8bC1q OIPS7DWCsSshC+aR9PZdUWj3mMTHHe8kflEJygUgrcJTjVwxL1Uzt3aRXlbwq3Pk VERWqCth55cPRz0L/pTuHQg54rUzP5r2hO6A7do8srtmAOAdPw5YrfFYa+T8Y/cA uzIif3uENNRZyCQ7yb7K =ZTns -----END PGP SIGNATURE-----

On 25 April 2012 02:31, Ben Boeckel
I have never experienced that, an I must say that I got borred after a minute trying to replicate what you mention, without any noticeable effect (Only switching between window A and B, window C didn't get more transparent). I don't see (from a quick look) any way that the code would allow the opacity to change if lots of switches happen.
Where/how did you use the fading hooks? I have mine in the logHook. Mind posting the code/diff?
I have mine setup as a logHook aswell. , logHook = do -- Sets transparancy on non focues windows. fadeInactiveCurrentWSLogHook 0.7 -- fadeInactiveLogHook 1 -- fadeInactiveLogHook 0.7 -- Fix SWING applications. >> setWMName "LG3D" The comments are old code which I haven't removed yet. I used it before, when I had to switch off the fading when hooking on a projector. -- Reenberg
participants (2)
-
Ben Boeckel
-
Jesper Reenberg