THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1157 - Clients messed up after adding another monitor
User who did this - Joss Wright (tealeaf)

----------
The only way I've been able to deal with this has been to move each client 
between screens manually, which causes it to be picked up correctly.

As of now, my disgusting solution to this has been to bind a key to a function 
that moves each client to the other screen then back again. It's not pretty, it 
won't work for more than 2 monitors, but it's doing the job for me. (I only 
need to use it when I plug my laptop in at work or when I get home, so I can 
put up with a bit of hideousness.)

Snippet from my rc.lua:

   -- Problem with windows not being mapped correctly on multiple monitors 
after an xrandr
   -- This can be fixed by moving each client to the other screen and back
    awful.key({ modkey, "Control" },            "d",     
      function () 
         for i, c in pairs( client.get() ) do
            awful.client.movetoscreen( c )
            awful.client.movetoscreen( c )
         end
      end)
----------

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1157#comment3675

You are receiving this message because you have requested it from the Flyspray 
bugtracking system.  If you did not expect this message or don't want to 
receive mails in future, you can change your notification settings at the URL 
shown above.

--
To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.

Reply via email to