On Thu, Sep 11, 2014 at 11:41:17PM +0100, Thomas Adam wrote: > On Thu, Sep 11, 2014 at 11:30:40PM +0100, Dominik Vogt wrote: > > Yes, this looks good now. With that fix I can now debug the > > buttons placement problem. It turns out that the module window > > ends up at y = -61 instead of y = screen height - 61. That sounds > > like with the XRandR patch, negative coordinates are now taken > > literally. Coordinates actually schould mean: > > > > x/+x -> 0 + x > > +-x -> 0 - x > > -x/-+x -> screen size - window size - x > > --x -> screen size - window size + x > > > > Since the Move command works fine, it's possibly caused by > > MvwmButtons' parsing of the geometry option. > > Are you looking into this, or would you like me to? ISTR that > MvwmButtons will try calling libs/FScreen.c:FScreenParseGeometry() -- > it's entirely possible that's returning a slightly different value now.
I'm not looking into it because you know that new code better. Ciao Dominik ^_^ ^_^ -- Dominik Vogt
