On Fri, Mar 28, 2014 at 01:19:42PM +0900, Jiachen Yang wrote:
> Hello Everyone,
> 
> I am new to qtile, using it on my laptop for just 2 months.
> My workstation is running AwesomeWM version 3.4 for about 2 years, and I am
> considering switch to qtile on the workstation.
> This workstation has a setup with 2 ATI graph cards and 4 monitors. I have
> give a try to Xinerama and/or Xrandr in the last 2 years for several times,
> and found that I can not work with Xinerama or Xrandr for many technical
> reasons. Therefore I used a multiple X screen setup, which has a limitation
> on moving windows between screens. With a tiling WM, I found this
> acceptable (comparing to using only 2 monitors with Xrandr).
> 
> The main motivation to switching from AwesomeWM to Qtile is that, AwesomeWM
> 3.5 removed the support for multiple X screens, and the upstream refused to
> fix that (
> https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1069). And I
> can not manage to hack the source code of AwesomeWM, while qtile's python
> code is much more understandable for me.
> 
> I looked into libqtile's source code, and found that xcbq.py already has
> the true Screen support, while manager.py only manage the default screen.
> 
> Therefore I want to ask, is it possible (or easy) to hack qtile to manage
> all the screens (not the PseudoScreen by Xinerama or Xrandr) and handle the
> input events correctly? There may be multiple root windows or other details
> I don't know.

It is probably possible, although you'd need to change most of the
code to figure out which display things are running on and send the
commands to the appropriate display. You wouldn't be able to move
windows across displays, so I'm not sure there's much to be gained
there over simply running two instances of qtile (which should work
just fine).

\t

-- 
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].
For more options, visit https://groups.google.com/d/optout.

Reply via email to