Hello, I already posted on the forums, and talked with Thomas Adam about this. Still, I can't understand what is going on so I will post it here and see what do the fvwm developers think.
Before starting, some conventions: "screen" is a xinerama screen, which in my case spans across two physical devices. "monitor" is a physical display device "root window" is the fvwm root window, which takes the whole screen, as per the "screen" definition above. Now, I read on the man page this: WindowId [id] [(conditions)] | [root [screen]] command And here comes the questions: 1.- is the definition of "screen" above applicable to that command line? 2.- if not, what is that "root [screen]" supposed to do? These two commands do nothing different on my xinerama setup: Key Left A 4 WindowId root 1 WarpToWindow 50 50 Key Right A 4 WindowId root 0 WarpToWindow 50 50 They move the pointer to (50,50) taking as reference the root window, or the whole xinerama screen, if you prefer. So, I can only assume that either the man page or the WindowId/WarpToWindow combo are broken. Another thing is that, if this behaviour is the intended one, then it is missleading because the Move command has also a "screen" parameter, and it works as expected. If you open a FvwmConsole and do All (FvwmConsole) Move screen 0 0 0 All (FvwmConsole) Move screen 1 0 0 All (FvwmConsole) Move screen 0 0 0 You will see how your FvwmConsole moves from one physical monitor to the other. I don't see why this is a good behaviour for windows and not for the mouse pointer. I am not stating the fact that this is a bug or anything because maybe I am missing something. I just think that there is an inconsistency, and I don't understand what the "screen" parameter does in that WindowId/WarpToWindow line Thanks in advance for any response and congratulations for the good work :) -- Jesús Guerrero <[EMAIL PROTECTED]>
