physical screen boundaries
How would a module determine the boundaries between physical screens? EdgeMoveResistance snapping seems to know about it, so the data is in there somewhere. For example, if I have two monitors 1600x1200 and 1920x1200, querying X11 about the screen dimensions seems to give me the full 3520x1200. I'd like to know about the implicit barrier at x=1600. -- Jason Weber
Re: physical screen boundaries
On Fri, Oct 08, 2010 at 10:04:18AM -0700, Jason Weber wrote: How would a module determine the boundaries between physical screens? EdgeMoveResistance snapping seems to know about it, so the data is in there somewhere. For example, if I have two monitors 1600x1200 and 1920x1200, querying X11 about the screen dimensions seems to give me the full 3520x1200. I'd like to know about the implicit barrier at x=1600. Assuming you are talking about Xinerama screens, fvwm sends the modules a packet whenever the screen layout changes. The packet string is XineramaConfig. Upon receiving such a packet, a module wopuld call the function FScreenConfigureModule() which stores the module configuration is structures that can be accessed by the other helper functions in libs/FScreen.[ch]. For example, with FScreenGetScrRect() you can find out about the geometry of the given Xinerama screen. Ciao Dominik ^_^ ^_^ -- Dominik Vogt
Re: physical screen boundaries
Jason Weber baboon.im...@gmail.com writes: How would a module determine the boundaries between physical screens? EdgeMoveResistance snapping seems to know about it, so the data is in there somewhere. For example, if I have two monitors 1600x1200 and 1920x1200, querying X11 about the screen dimensions seems to give me the full 3520x1200. I'd like to know about the implicit barrier at x=1600. Perhaps $[vp.width]/$[vp.height] will work. I'm only using one monitor. Thomas, I notice there is no fvwm2 man page for the unstable branch. I may get time to look but not right now.
Re: physical screen boundaries
Thomas Adam tho...@xteddy.org writes: On Fri, Oct 08, 2010 at 01:33:56PM -0400, des...@verizon.net wrote: Jason Weber baboon.im...@gmail.com writes: How would a module determine the boundaries between physical screens? EdgeMoveResistance snapping seems to know about it, so the data is in there somewhere. For example, if I have two monitors 1600x1200 and 1920x1200, querying X11 about the screen dimensions seems to give me the full 3520x1200. I'd like to know about the implicit barrier at x=1600. Perhaps $[vp.width]/$[vp.height] will work. I'm only using one monitor. Thomas, I notice there is no fvwm2 man page for the unstable branch. I may get time to look but not right now. Err, do you mean on the website or built as part of ./configure make sudo make install -- only for unstable, that will just be fvwm. It's generated from the not-so-lovely XML sources -- and IIRC, the man page is always built, but you would need to pass an option to ./configure to get the HTML documentation. I mean it's missing from the website: http://fvwm.org/documentation/manpages/unstable/ Unless I'm blind...
Re: physical screen boundaries
On Fri, Oct 08, 2010 at 04:06:52PM -0400, des...@verizon.net wrote: Thomas Adam tho...@xteddy.org writes: On Fri, Oct 08, 2010 at 01:33:56PM -0400, des...@verizon.net wrote: Jason Weber baboon.im...@gmail.com writes: How would a module determine the boundaries between physical screens? EdgeMoveResistance snapping seems to know about it, so the data is in there somewhere. For example, if I have two monitors 1600x1200 and 1920x1200, querying X11 about the screen dimensions seems to give me the full 3520x1200. I'd like to know about the implicit barrier at x=1600. Perhaps $[vp.width]/$[vp.height] will work. I'm only using one monitor. Thomas, I notice there is no fvwm2 man page for the unstable branch. I may get time to look but not right now. Err, do you mean on the website or built as part of ./configure make sudo make install -- only for unstable, that will just be fvwm. It's generated from the not-so-lovely XML sources -- and IIRC, the man page is always built, but you would need to pass an option to ./configure to get the HTML documentation. I mean it's missing from the website: http://fvwm.org/documentation/manpages/unstable/ Unless I'm blind... No, your eyesight's fine. I've regenerated the whole lot -- which is what I thought I did when I released 2.5.31, but maybe I was too drunk to remember? :P Either way, the index.php file looks more correct now, so if it still looks odd, let me know. Kindly, -- Thomas Adam -- Deep in my heart I wish I was wrong. But deep in my heart I know I am not. -- Morrissey (Girl Least Likely To -- off of Viva Hate.)
