[PATCH] Xi: check all handlers before applying property changes.
simon.thum at gmx.de
Thu Oct 9 06:42:50 PDT 2008
Peter Hutterer wrote:
> right now, the properties are documented in the header files that define their
> names. They should eventually be added to the man pages, once they settle down
> a bit.
Fine, I'll be including a header.
> So based on the current implementation (the one that is in master), what's
> your concrete proposal then? Just leave it an beat up anyone trying to
> double-handle a property? Not that I would be opposed to that, but it's likely
> going to be me who's going to be beaten up :)
OK, I'm summing up:
One non-ignoring handler is invoked at max. For this we have to
differentiate the RC.
'beat me up'
When a handler is invoked, it may decide to call a new function which
allows it to pass through to handlers AFTER itself. A logical complement
would be the ability to register handlers at head and tail.
That way, the one who double-handles a prop isn't just in charge, he's
also in control. Which increases chances he won't screw it, or at least
he can do something about it (short of hackery).
I admit you can do more awkward stuff like this, but a 'evil' driver
isn't something to protect from anyway.
How does that sound?
More information about the xorg