RE: movetoscreen - still not having much luck...
Studied awful.client.lua... --- Move a client to a screen. Default is next screen, cycling. -- @param c The client to move. -- @param s The screen number, default to current + 1. function client.movetoscreen(c, s) screen = screen or require(awful.screen) local sel = c or capi.client.focus if sel then local sc = capi.screen.count() if not s then s = sel.screen + 1 end if s sc then s = 1 elseif s 1 then s = sc end sel.screen = s screen.focus(s) end end Tried to do the same to see what was happening... awful.key({ modkey, }, o, function (c) local iScreen = c.screen + 1 if iScreen screen.count() then iScreen = 1 end c.screen = iScreen awful.screen.focus(iScreen) local sNum = string.format(-= %d, %d, %d =-, c.screen, iScreen, screen.count()) naughty.notify({ text = sNum }) end), Client still wouldn't change screens! Notify from screen 1 was -= 1, 2, 2 =- Notify from screen 2 was -= 2, 1, 2 =- What I did see was that the mouse focus actually worked as expected (moved to the other screen) One Confused Dave awesome v3.4.11 (Pickapart) • Build: Apr 2 2012 18:39:18 for x86_64 by gcc version 4.6.3 (buildd@crested) • D-Bus support: ✔ -Original Message- From: David Sorkovsky [mailto:davidsorkov...@hotmail.com] Sent: Friday, 21 February 2014 7:02 PM To: awesome@naquadah.org Cc: 'Maxim Bulatov' Subject: RE: movetoscreen G'Day Maxim all, Dual monitors both working well with Awesome - like the independence, but sometimes I use the RHS for my laptop and want to move apps to the LHS at that time. Wondering if there is something I needed to setup in Awesome? xrandr on LHS... Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192 VGA1 disconnected (normal left inverted right x axis y axis) HDMI1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 531mm x 299mm 1920x1080 60.0*+ 1680x1050 60.0 1600x900 60.0 1280x1024 75.0 60.0 1280x960 60.0 1280x800 59.8 1152x864 75.0 1280x720 60.0 1024x768 75.1 60.0 1024x576 60.0 832x62474.6 800x60075.0 60.3 640x48075.0 60.0 720x40070.1 DP1 disconnected (normal left inverted right x axis y axis) HDMI2 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis) Xrandr on RHS... Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192 VGA1 disconnected (normal left inverted right x axis y axis) HDMI1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 531mm x 299mm 1920x1080 60.0*+ 1680x1050 60.0 1600x900 60.0 1280x1024 75.0 60.0 1280x960 60.0 1280x800 59.8 1152x864 75.0 1280x720 60.0 1024x768 75.1 60.0 1024x576 60.0 832x62474.6 800x60075.0 60.3 640x48075.0 60.0 720x40070.1 DP1 disconnected (normal left inverted right x axis y axis) HDMI2 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis) Xorg.conf... # Manually adjusted/combined from the below... # X.org Configured # nvidia-xconfig: X configuration file generated by nvidia-xconfig # nvidia-xconfig: version 304.116 (buildmeister@swio-display-x86-rhel47-01) Mon Oct 28 21:46:08 PDT 2013 Section ServerLayout Identifier Layout Screen 0 Screen0 0 0 Screen 1 Screen2 RightOf Screen0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Section Files # ModulePath /usr/lib/xorg/modules # FontPath /usr/share/fonts/X11/misc # FontPath /usr/share/fonts/X11/cyrillic # FontPath /usr/share/fonts/X11/100dpi/:unscaled # FontPath /usr/share/fonts/X11/75dpi/:unscaled # FontPath /usr/share/fonts/X11/Type1 # FontPath /usr/share/fonts/X11/100dpi # FontPath /usr/share/fonts/X11/75dpi # FontPath /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType # FontPath built-ins EndSection Section Module # Load dbe # Load dri2 # Load record # Load extmod # Load dri # Load glx EndSection Section InputDevice Identifier Keyboard0 Driver kbd EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto
Re: movetoscreen - still not having much luck...
Hi, On 23.02.2014 09:13, David Sorkovsky wrote: [...] Dual monitors both working well with Awesome - like the independence, but sometimes I use the RHS for my laptop and want to move apps to the LHS at that time. Wondering if there is something I needed to setup in Awesome? xrandr on LHS... Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192 VGA1 disconnected (normal left inverted right x axis y axis) HDMI1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 531mm x 299mm 1920x1080 60.0*+ 1680x1050 60.0 1600x900 60.0 1280x1024 75.0 60.0 1280x960 60.0 1280x800 59.8 1152x864 75.0 1280x720 60.0 1024x768 75.1 60.0 1024x576 60.0 832x62474.6 800x60075.0 60.3 640x48075.0 60.0 720x40070.1 DP1 disconnected (normal left inverted right x axis y axis) HDMI2 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis) Xrandr on RHS... Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192 VGA1 disconnected (normal left inverted right x axis y axis) HDMI1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 531mm x 299mm 1920x1080 60.0*+ 1680x1050 60.0 1600x900 60.0 1280x1024 75.0 60.0 1280x960 60.0 1280x800 59.8 1152x864 75.0 1280x720 60.0 1024x768 75.1 60.0 1024x576 60.0 832x62474.6 800x60075.0 60.3 640x48075.0 60.0 720x40070.1 DP1 disconnected (normal left inverted right x axis y axis) HDMI2 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis) Welcome to 1987. You have two different protocol screens. They are completely independent. They only share the keyboard and the mouse. That's it. This does especially mean that you cannot move windows between screens. (This is a limitation of X11!) People were unhappy and Xinerama was invented and included in X11R6v4.0. This makes multiple screens look to the X11 protocol like a single, big one. Since from the protocol's point of view there is now just a single screen, windows can now move around freely. (At least I think that this is what's going on, since you are giving us two times the same xrandr output and claim that it is for the different screens...) Xorg.conf... # Manually adjusted/combined from the below... # X.org Configured # nvidia-xconfig: X configuration file generated by nvidia-xconfig # nvidia-xconfig: version 304.116 (buildmeister@swio-display-x86-rhel47-01) Mon Oct 28 21:46:08 PDT 2013 Section ServerLayout Identifier Layout Screen 0 Screen0 0 0 Screen 1 Screen2 RightOf Screen0 Yeah, zaphod mode, not Xinerama. InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection [...] Cheers, Uli -- alanc I think someone had a Xprint version of glxgears at one point, but benchmarking how many GL pages you can print per second was deemed too silly to merge -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
RE: movetoscreen - still not having much luck...
Tried it - Just added Option Xinerama 1 to my layout - Solved I can work with that! Thanks Uki Regards Dave -Original Message- From: Uli Schlachter [mailto:psyc...@znc.in] Sent: Sunday, 23 February 2014 9:00 PM To: awesome@naquadah.org Subject: Re: movetoscreen - still not having much luck... Hi, On 23.02.2014 09:13, David Sorkovsky wrote: [...] Dual monitors both working well with Awesome - like the independence, but sometimes I use the RHS for my laptop and want to move apps to the LHS at that time. Wondering if there is something I needed to setup in Awesome? xrandr on LHS... Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192 VGA1 disconnected (normal left inverted right x axis y axis) HDMI1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 531mm x 299mm 1920x1080 60.0*+ 1680x1050 60.0 1600x900 60.0 1280x1024 75.0 60.0 1280x960 60.0 1280x800 59.8 1152x864 75.0 1280x720 60.0 1024x768 75.1 60.0 1024x576 60.0 832x62474.6 800x60075.0 60.3 640x48075.0 60.0 720x40070.1 DP1 disconnected (normal left inverted right x axis y axis) HDMI2 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis) Xrandr on RHS... Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192 VGA1 disconnected (normal left inverted right x axis y axis) HDMI1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 531mm x 299mm 1920x1080 60.0*+ 1680x1050 60.0 1600x900 60.0 1280x1024 75.0 60.0 1280x960 60.0 1280x800 59.8 1152x864 75.0 1280x720 60.0 1024x768 75.1 60.0 1024x576 60.0 832x62474.6 800x60075.0 60.3 640x48075.0 60.0 720x40070.1 DP1 disconnected (normal left inverted right x axis y axis) HDMI2 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis) Welcome to 1987. You have two different protocol screens. They are completely independent. They only share the keyboard and the mouse. That's it. This does especially mean that you cannot move windows between screens. (This is a limitation of X11!) People were unhappy and Xinerama was invented and included in X11R6v4.0. This makes multiple screens look to the X11 protocol like a single, big one. Since from the protocol's point of view there is now just a single screen, windows can now move around freely. (At least I think that this is what's going on, since you are giving us two times the same xrandr output and claim that it is for the different screens...) Xorg.conf... # Manually adjusted/combined from the below... # X.org Configured # nvidia-xconfig: X configuration file generated by nvidia-xconfig # nvidia-xconfig: version 304.116 (buildmeister@swio-display-x86-rhel47-01) Mon Oct 28 21:46:08 PDT 2013 Section ServerLayout Identifier Layout Screen 0 Screen0 0 0 Screen 1 Screen2 RightOf Screen0 Yeah, zaphod mode, not Xinerama. InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection [...] Cheers, Uli -- alanc I think someone had a Xprint version of glxgears at one point, but benchmarking how many GL pages you can print per second was deemed too silly to merge -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org. -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
RE: movetoscreen
MonitorMonitor0 SubSection Display Viewport 0 0 Depth 1 EndSubSection SubSection Display Viewport 0 0 Depth 4 EndSubSection SubSection Display Viewport 0 0 Depth 8 EndSubSection SubSection Display Viewport 0 0 Depth 15 EndSubSection SubSection Display Viewport 0 0 Depth 16 EndSubSection SubSection Display Viewport 0 0 Depth 24 # Modes 1920x1080 EndSubSection EndSection Section Screen Identifier Screen2 Device Card2 MonitorMonitor2 SubSection Display Viewport 0 0 Depth 1 EndSubSection SubSection Display Viewport 0 0 Depth 4 EndSubSection SubSection Display Viewport 0 0 Depth 8 EndSubSection SubSection Display Viewport 0 0 Depth 15 EndSubSection SubSection Display Viewport 0 0 Depth 16 EndSubSection SubSection Display Viewport 0 0 Depth 24 # Modes 1920x1080 EndSubSection EndSection -Original Message- From: Maxim Bulatov [mailto:dvenum...@gmail.com] Sent: Friday, 21 February 2014 1:05 PM To: David Sorkovsky Subject: Re: movetoscreen I had same problem with separated screen. I could not move mouse between screens. Solution was easier to reconfigure xorg. Now, I have one big virtual screen from two videocards in system and two screen on the awesome wm level. Show your xrandr output and xorg config options and describe your hardware environment. On Thu, Feb 20, 2014 at 10:00:54PM +1100, David Sorkovsky wrote: I'm not having much luck with... awful.key({ modkey, }, o, awful.client.movetoscreen ), awful.key({ modkey, Shift }, F1, function (c) awful.client.movetoscreen(c, 1) end), awful.key({ modkey, Shift }, F2, function (c) awful.client.movetoscreen(c, 2) end), All that happens on any keypress is that the mouse jumps to the top left corner of the current window Regards Dave -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org. -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: movetoscreen
/lib/xorg/modules # FontPath /usr/share/fonts/X11/misc # FontPath /usr/share/fonts/X11/cyrillic # FontPath /usr/share/fonts/X11/100dpi/:unscaled # FontPath /usr/share/fonts/X11/75dpi/:unscaled # FontPath /usr/share/fonts/X11/Type1 # FontPath /usr/share/fonts/X11/100dpi # FontPath /usr/share/fonts/X11/75dpi # FontPath /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType # FontPath built-ins EndSection Section Module # Load dbe # Load dri2 # Load record # Load extmod # Load dri # Load glx EndSection Section InputDevice Identifier Keyboard0 Driver kbd EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/input/mice Option ZAxisMapping 4 5 6 7 EndSection Section Monitor Identifier Monitor0 VendorName Unknown ModelName Unknown #HorizSync 28.0 - 33.0 #VertRefresh 43.0 - 72.0 #Option DPMS EndSection Section Monitor Identifier Monitor2 VendorName Unknown ModelName Unknown #HorizSync 28.0 - 33.0 #VertRefresh 43.0 - 72.0 #Option DPMS EndSection Section Device ### Available Driver options are:- ### Values: i: integer, f: float, bool: True/False, ### string: String, freq: f Hz/kHz/MHz, ### percent: f% ### [arg]: arg optional #Option DRI # [bool] #Option ColorKey# i #Option VideoKey# i #Option FallbackDebug # [bool] #Option Tiling # [bool] #Option LinearFramebuffer # [bool] #Option Shadow # [bool] #Option SwapbuffersWait # [bool] #Option TripleBuffer# [bool] #Option XvMC# [bool] #Option XvPreferOverlay # [bool] #Option DebugFlushBatches # [bool] #Option DebugFlushCaches# [bool] #Option DebugWait # [bool] #Option HotPlug # [bool] #Option RelaxedFencing # [bool] #Option BufferCache # [bool] Identifier Card0 Driver intel BusID PCI:0:2:0 # VendorName Intel EndSection Section Device Identifier Card2 Driver nvidia BusID PCI:1:0:0 # VendorName NVIDIA Corporation EndSection Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 SubSection Display Viewport 0 0 Depth 1 EndSubSection SubSection Display Viewport 0 0 Depth 4 EndSubSection SubSection Display Viewport 0 0 Depth 8 EndSubSection SubSection Display Viewport 0 0 Depth 15 EndSubSection SubSection Display Viewport 0 0 Depth 16 EndSubSection SubSection Display Viewport 0 0 Depth 24 #Modes 1920x1080 EndSubSection EndSection Section Screen Identifier Screen2 Device Card2 MonitorMonitor2 SubSection Display Viewport 0 0 Depth 1 EndSubSection SubSection Display Viewport 0 0 Depth 4 EndSubSection SubSection Display Viewport 0 0 Depth 8 EndSubSection SubSection Display Viewport 0 0 Depth 15 EndSubSection SubSection Display Viewport 0 0 Depth 16 EndSubSection SubSection Display Viewport 0 0 Depth 24 #Modes 1920x1080 EndSubSection EndSection -Original Message- From: Maxim Bulatov [mailto:dvenum...@gmail.com] Sent: Friday, 21 February 2014 1:05 PM To: David Sorkovsky Subject: Re: movetoscreen I had same problem with separated screen. I could not move mouse between screens. Solution was easier to reconfigure xorg. Now, I have one big virtual screen from two videocards in system and two screen on the awesome wm level. Show your xrandr output and xorg config options and describe your hardware environment. On Thu, Feb 20, 2014 at 10:00:54PM +1100, David Sorkovsky wrote: I'm not having much luck with... awful.key({ modkey, }, o, awful.client.movetoscreen ), awful.key({ modkey, Shift }, F1, function (c) awful.client.movetoscreen(c, 1) end), awful.key({ modkey, Shift }, F2, function (c) awful.client.movetoscreen(c, 2) end), All that happens on any keypress
movetoscreen
I'm not having much luck with... awful.key({ modkey, }, o, awful.client.movetoscreen ), awful.key({ modkey, Shift }, F1, function (c) awful.client.movetoscreen(c, 1) end), awful.key({ modkey, Shift }, F2, function (c) awful.client.movetoscreen(c, 2) end), All that happens on any keypress is that the mouse jumps to the top left corner of the current window Regards Dave
Re: movetoscreen
I had same problem with separated screen. I could not move mouse between screens. Solution was easier to reconfigure xorg. Now, I have one big virtual screen from two videocards in system and two screen on the awesome wm level. Show your xrandr output and xorg config options and describe your hardware environment. On Thu, Feb 20, 2014 at 10:00:54PM +1100, David Sorkovsky wrote: I'm not having much luck with... awful.key({ modkey, }, o, awful.client.movetoscreen ), awful.key({ modkey, Shift }, F1, function (c) awful.client.movetoscreen(c, 1) end), awful.key({ modkey, Shift }, F2, function (c) awful.client.movetoscreen(c, 2) end), All that happens on any keypress is that the mouse jumps to the top left corner of the current window Regards Dave -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
[awesome bugs] #449 - movetoscreen does nothing
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - J.R. (thedoctor) Attached to Project - awesome Summary - movetoscreen does nothing Task Type - Bug Report Category - Core Status - Unconfirmed Assigned To - Operating System - All Severity - Low Priority - Normal Reported Version - git/master Due in Version - Undecided Due Date - Undecided Details - Function movetoscreen has no effect other than moving the mouse to the upper left corner of the current screen. Focused window should move to another screen. Nvidia card with two separate X screens (not clones) with different resolutions, if that helps. More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=detailstask_id=449 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.