home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.next.programmer
- Path: sparky!uunet!wupost!uwm.edu!news.bbn.com!micro-heart-of-gold.mit.edu!uw-beaver!news.u.washington.edu!hardy.u.washington.edu!zeno
- From: zeno@hardy.u.washington.edu (Sean T. Lamont)
- Subject: response of view keydown messages
- Message-ID: <1992Jul21.231819.7766@u.washington.edu>
- Sender: news@u.washington.edu (USENET News System)
- Organization: Abstract Software
- References: <92203.164622MKK2@psuvm.psu.edu>
- Date: Tue, 21 Jul 1992 23:18:19 GMT
- Lines: 17
-
-
- I'm running a high-priority timed entry which updates a view. I've
- also got a keydown handler within the view. The odd thing I found is that
- there is a significant delay between the time I press the key and the time it
- is actually registered by the view.
-
- Playing with this some more, I found that if the timed entry specifically
- checks the event queue with NXGetOrPeekEvent(), that it works in a more timely
- manner. It seems the view doesn't know about key events as often as the
- event queue produces them.
-
- Is this normal behavior?
- --
- Sean T. Lamont, Abstract Software | "Don't oppress me, It's
- zeno@u.washington.edu | 'computer of color!' "
- Next Mail............................... | yang.cpac.washington.edu!zebu!zeno
- ----------------"My employers opinions are my own, not yours."-----------------
-