ASPN ActiveState Programmer Network
ActiveState
/ Home / Perl / PHP / Python / Tcl / XSLT /
/ Safari / My ASPN /
Cookbooks | Documentation | Mailing Lists | Modules | News Feeds | Products | User Groups


Recent Messages
List Archives
About the List
List Leaders
Subscription Options

View Subscriptions
Help

View by Topic
ActiveState
.NET Framework
Open Source
Perl
PHP
Python
Tcl
Web Services
XML & XSLT

View by Category
Database
General
SOAP
System Administration
Tools
User Interfaces
Web Programming
XML Programming


MyASPN >> Mail Archive >> Tcl-core
Tcl-core
[TCLCORE] Re: TIP #158: Distinguish the two 'Enter' keys on Windows
by Benjamin Riefenstahl other posts by this author
Sep 29 2003 5:16PM messages near this date
Re: [TCLCORE] Re: TIP #158: Distinguish the two 'Enter' keys on Windows | Re: [TCLCORE] Re: TIP #158: Distinguish the two 'Enter' keys on Windows
Hi George, all,


>  Benjamin Riefenstahl writes:
> > To summarize my state of information: I think that the "ModX"
> > modifiers are just stand-ins in X11, in case a keyboard has a
> > modifier that is not in the regular list of "Shift", (Num)"Lock"
> > and "Control".  So the "ModX" keys are generic to cover "Alt",
> > "Meta", "Hyper", "Windows", "Option", "Command", "AltGr", just to
> > mention the ones of which I have heard.

George Howlett <gah@[...].com>  writes:
>  There's nothing deeply wrong with the "Mod4" proposal.

The text you quoted from me didn't say there was something wrong with
using "Mod4".


To summarize my position on this:

As I see it, using "Mod4" is suprising behaviour.  If I wanted to use
the keypad enter key, I would check the list of keysyms in the header,
see <KP_Enter>  and try that.  Several people have lately done that and
than asked why this doesn't work on Windows or Mac.

With <KP_Enter>  implemented on Windows and Mac we'd never have any
such discussion again.  With the "Mod4" proposal, we will.  We'd have
to refer programmers to some specific bit of Tk documentation that
discusses this issue.  I prefer something that is obvious to something
that needs new documentation.

The most convincing (for me) argument for the "Mod4" proposal is that
it's more compatible with existing binds to <Return> .  This is
important on Windows, because <Return>  is supposed to invoke the
default button in Windows dialogs, and <KP_Enter>  should have the same
meaning.  But <KP_Enter>  is most likely not bound by some current
Windows-only applications.


As an alternative to "Mod4", [event generate] has been proposed.  I
like that idea.

Implement <KP_Enter>  and add a default binding in the init scripts
like

  bind all <KP_Enter>  {event generate %W <Return>}

That would satisfy the compatibility requirement nicely and in a
straight-forward way.  It would still make Tk on Windows compatible
with X11.

Of course the same could be done with all (or at least most) other
keys on the keypad.


benny



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Tcl-Core mailing list
Tcl-Core@[...].net
https://lists.sourceforge.net/lists/listinfo/tcl-core
Thread:
Benjamin Riefenstahl
=?ISO-8859-1?Q?Fr=E9d=E9ric_Bonnet?=
Benjamin Riefenstahl
George Howlett
Benjamin Riefenstahl
George Howlett
Vince Darley
Joe English
Vince Darley

Privacy Policy | Email Opt-out | Feedback | Syndication
© ActiveState Software Inc. All rights reserved