>
> this weekend i wrote a plugin for ulatencyd which tries to get the pid
> of the window in focus so the program can get scheduled with more cpu
> slots then other programs. I don't want to flame on X11, but it is
> 1. Terrible to do. Even with root permissions you need workarounds just
> to conn
The major problem with PropertyNotify events, or with having generalized
properties of any kind, is that they are too much like polled interrupts rather
than vectored interrupts. You get the event, but you then have to poll to see
which thing changed.
Also, the protocol design seems to be more
I expect Wayland will add a "attach this blob of data to this
window+key" similar to X window properties, for IPC to the compositor
and other software.
The question is whether software is going to be required to keep these
things up to date for information that Wayland must know anyway.
Requi
On 01/18/2011 01:00 AM, Marty Jack wrote:
> Concerning what is going to be done in Wayland, we are not to the
> point of designing these parts quite yet. I am confident there will
> ultimately be mechanisms since people will want to write desktop
> environments over Wayland.
I know that wayland
This is (a) really the wrong place to complain about the X Window System and
(b) this mechanism has all been in place and stable and heavily used for many
years and is not likely to change in any significant way.
Concerning what is going to be done in Wayland, we are not to the point of
designi
Hi,
this weekend i wrote a plugin for ulatencyd which tries to get the pid
of the window in focus so the program can get scheduled with more cpu
slots then other programs. I don't want to flame on X11, but it is
1. Terrible to do. Even with root permissions you need workarounds just
to connect.
2.
