On Sun, 6 Jan 2013, Rodolfo García Peñas wrote:
What do you think about the idea of the set clip in one of the four corners?
Then, the clip will work with xrandr too.
Do you mean that the clip could only be placed in one of the four corners
and nowhere else? Then I don't think it's a good idea. Unless maybe if the
clip could also be docked like any other appicon. To see why, here's a
screenshot of my dock and clip:
http://goliat.eik.bme.hu/~balaton/wmaker/OS42-WindowMaker_Screenshot.png
(As a curiosity and for comparison I also included a window with OPENSTEP
4.2 running under QEMU.) I use the clip as a desktop specific dock
extension so it's not tied to one of the corners. Maybe a solutions that
could work is to store the clip position with relative coordinates, that
is upper left: +0,+0 upper right: +0,-0 lower right: -0,-0 so always
measure to the closest edge and store that instead of absolute position.
IMO should be:
-------8<------
case ConfigureNotify:
#ifdef HAVE_XRANDR
if (event->xconfigure.window == DefaultRootWindow(dpy))
XRRUpdateConfiguration(event);
#endif
break;
-------8<------
Then why not even:
#ifdef HAVE_XRANDR
case ConfigureNotify:
if (event->xconfigure.window == DefaultRootWindow(dpy))
XRRUpdateConfiguration(event);
break;
#endif
And finally, someone knows whats happends when "XRRUpdateConfiguration" is
called? What function/event is called in wmaker?
Don't know anything about this but the man page says it is a callback to
notify the xlib client side about changes in the screen configuration
which is not done automatically to let clients decide when's the best time
to call this. So no event is generated in wmaker but wmaker should call
this if it gets an "RRScreenChangeNotify, or ConfigureNotify (on the root
window)" according to the docs.
Regards,
BALATON Zoltan
