[22.02.02 19:05 +0100] Radovan Garabik <-- : > On Fri, Feb 22, 2002 at 07:30:19AM -0600, Thomas Chan wrote: > > > >>> sci-fi ideas (not to be implemented anytime soon): > >>> - timeout for key combination. For example, in certain layout, pressing cx > >>> keys in succession with less then 1 second delay between c and > >>> x would yield LATIN SMALL LETTER C WITH CIRCUMFLEX. > >>> Pressing them with more than 1 second delay would yield two > >>> characters, c and x. > >> > >> I detest time-delay interfaces. Windows in "one-click" mode--hover the > >> mouse to select a file; Mac "click and hold a link to bookmark"--it's > >> extremely frustrating to break flow to suit an interface. For compose, > >> it's even worse--I'm breaking my typing. > > > > This sounded more like an "sticky keys" Accessibility option for > > typists who only have the use of one hand. > > No, it was more like automatic compose, without the need to press > compose first. Believe me, it is nice (I am using yudit a lot).
When I first read about that delay tactic I thought, nice idea. Rethinking about it gave two questions: 1. how does it play together with kbd rate/delay being extra adjustable 2. that means to have an extra config/prog kbd compose_delay a professional typist will go mad to wait 1 second for the next press a user with eagle-tactic would never be able to make a composing > In fact, traditional <Compose> behaves like a sticky key - it could have > been more like shift, to be hold while typing compose sequence > (and it would have the advantage that the system would know when the > composed sequence ends) In that case you would need an additional Compose_Lock, nothing is is more anti-ergonomic than holding a key while typing some others. Just my 2 cents. -- Erika Pacholleck <[EMAIL PROTECTED]> for private replies unhex my last name -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
