2009/3/20 <tlaro...@polynum.com>: > On Fri, Mar 20, 2009 at 01:03:12PM +0000, roger peppe wrote: > For my own stuff, having to rewrite the 2 dimensions user interface, I > have created a library running on the terminal that keeps the > definitions of the graphical elements drawn with an identifier (3 > members) giving to the processing unit (remote) a mean to unambiguously > identifies the antecedent for processing.
that's fine for location-based events, e.g. from a mouse, (well, fine for largely static UIs) but still leaves unresolved the issue of how do deal with events that are agnostic about their destination, such as keyboard events. you can't decide which graphical element a key press is destined for until you know the mouse language of your application. acme has both click-to-type and point-to-type - the client would need to know which one to use, otherwise you still have exactly the same ordering problem as before.
