home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!vtserf!vtucs.cc.vt.edu!daves
- From: daves@vtucs.cc.vt.edu (Dave Sisson)
- Newsgroups: comp.lang.pascal
- Subject: TurboVision and CUA (was Re: Turbo Vision Keys?)
- Message-ID: <10411@vtserf.cc.vt.edu>
- Date: 13 Dec 92 17:49:50 GMT
- References: <724065276.AA00687@contrast.wlink.nl>
- Sender: usenet@vtserf.cc.vt.edu
- Organization: Virginia Tech, Blacksburg, VA
- Lines: 32
-
- In article <724065276.AA00687@contrast.wlink.nl> berend@contrast.wlink.nl (Berend de Boer) writes:
- >Not so difficult, but you do, in this way, not conform to the CUA
- >standard which is a serious drawback I think. More and more people are
- >using CUA compliant UIs. But let's show the code:
-
- ...
-
- >1) Do not use the bfDefault flag
- >2) Override the HandleEvent of your dialog.
-
-
- True, my code does not use the bfDefault flag. But when considering
- compliancy to the CUA standard - who wants to use a standard which is
- complicated to use? My extended dialog class makes the first button
- act as if it were the default by being the first button in the TAB order
- that the user would reach by continually pressing the ENTER key. (BTW,
- I plan to post my code to the TurboVision mailing list late Monday morning
- so subscribe soon!)
-
- I agree that the arrow keys should not be overridden
- especially if you want to use histories at all in your code, but the
- changing of the ENTER key is extremely logical. When I have a menu box
- with several input lines in it (see below for a drawing), users get confused
- when they have to use some special key like TAB to move between lines. More
- often than not a user will end up with just the first entry filled in and
- the rest just blank.
-
- --
- Dave Sisson Join the TurboVision mailing list!
-
- Send a message with the body --> SUBSCRIBE TURBVIS My Name
- to listserv@vtvm1.cc.vt.edu today!
-