home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zephyr.ens.tek.com!vice!bobb
- From: bobb@vice.ICO.TEK.COM (Robert Beauchaine)
- Newsgroups: comp.lang.pascal
- Subject: Re: TV Focus in Dialog views
- Message-ID: <10213@vice.ICO.TEK.COM>
- Date: 21 Aug 92 23:31:23 GMT
- References: <10202@vice.ICO.TEK.COM> <1992Aug21.190034.40057@urz.unibas.ch>
- Organization: Tektronix, Inc., Beaverton, OR.
- Lines: 31
-
- In article <1992Aug21.190034.40057@urz.unibas.ch> gysin1@urz.unibas.ch writes:
- >In article <10202@vice.ICO.TEK.COM>, bobb@vice.ICO.TEK.COM (Robert Beauchaine) writes:
- >>
- >> Here's the problem:
- >>
- >
- > Well, I think the only thing you can do is to override the
- >HandleEvent-Method and redefine the function of kbTab and kbShiftTab (and -why
- >not ? - kbEnter). The user is probably already typing in new values and has
- >just to type the Tab-Key or Enter-Key to jump to the next InputLine. If he
- >moves the focus with the mouse, he doesn't need to care for the value, any
- >typing is ignored...
- >
- > For catching positional events, I suppose you should start at the
- >Dialog's event handler that manages the subviews....
- >
-
- Actually, I solved the problem today. Catching the change of
- focus seems to be the correct solution. The one missing part was
- to check the value of the COMMAND parameter passed into the input
- number's valid() function. If COMMAND = cmCancel, don't do the
- validation. Pretty simple, but it gave me fits!
-
- /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
-
- Bob Beauchaine bobb@vice.ICO.TEK.COM
-
- C: The language that combines the power of assembly language with the
- flexibility of assembly language.
-
- Real friends don't let friends use UNIX.
-