Ideal screen rotation

Rui Miguel Silva Seabra rms at
Sat Nov 7 20:57:25 CET 2009

On Sat, Nov 07, 2009 at 02:23:01PM +0000, Neil Jerram wrote:
> 2009/11/7 Rui Miguel Silva Seabra <rms at>:
> >
> > I'm definitely not following you... I envision the following scenario according
> > to what you say, could you please elaborate on why it wouldn't happen this way?
> My thinking is evolving with this discussion, but my current idea of
> the solution is that the WM controls whether omnewrotate is running
> (or equivalent, but for simplicity let's just say omnewrotate).

Actually, screen rotation *should* be the job of the WM. For me, as a relative
begginer, it was easier to startup with the first rotate.c written by Chris Ball
and step by step improving (for instance, drop fork and link to libxrandr for
better performance, control speed of reading from device, give tolerance, etc.

But if it was the WM, the WM could even do nifty special effects (in graphics
card that would allow it), etc...

OMNewRotate is a hack satisfying one need. To keep it going it needs a smart
way to do it (like DBUS). X properties is probably not so good for this kind
of programs.


> As above, omnewrotate wouldn't actually be running, so wouldn't do this.

If you have two applications handling screen rotation at the same time, then
you're just bound to a disaster fuse.

Either the WM does it (hint for more experienced E developers), or it should
keep it's hands off of it :)

> I hope that helps to clarify what I have in mind!


More information about the community mailing list