2013-07-01, 17:22
b) xvba version does not grab the pointer. you can have XBMC fullscreen on one monitor and move the mouse out. Once the window has lost focus, the keyboard in ungrabbed.
c) you certainly can't launch XBMC standalone when using multiple monitors.
EDIT: of course you can, but makes no sense
we do easier when using correct terms here:
- a display device spans a virtual screen
- an output (Monitor) defines a view to that screen
So having only one screen should work ok (not on NVidia because of tearing). use xrandr an set out outputs leftOf or rightOf the other.
You can run xbmc-xrandr to see the information XBMC gets. (please post this output).
Don't blame Linux I have tested this on AMD and NVidia where it works.
c) you certainly can't launch XBMC standalone when using multiple monitors.
EDIT: of course you can, but makes no sense
we do easier when using correct terms here:
- a display device spans a virtual screen
- an output (Monitor) defines a view to that screen
So having only one screen should work ok (not on NVidia because of tearing). use xrandr an set out outputs leftOf or rightOf the other.
You can run xbmc-xrandr to see the information XBMC gets. (please post this output).
Quote:Really can't see why this should be so hard on Linux
Don't blame Linux I have tested this on AMD and NVidia where it works.