home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.apollo
- Path: sparky!uunet!cs.utexas.edu!sdd.hp.com!apollo.hp.com!netnews
- From: ganek@apollo.hp.com (Dan Ganek)
- Subject: Re: Favourite DOMAIN/OS features (or mis-features)
- Sender: usenet@apollo.hp.com (Usenet News)
- Message-ID: <BrsrGA.DL8@apollo.hp.com>
- Date: Wed, 22 Jul 1992 15:38:34 GMT
- References: <1992Jul20.093747.12417@wam.umd.edu> <Brozvu.5uu@apollo.hp.com> <1992Jul22.063333.4659@wam.umd.edu>
- Nntp-Posting-Host: menage_a_trois.ch.apollo.hp.com
- Organization: Hewlett-Packard Corporation, Chelmsford, MA
- Lines: 54
-
- >>> Recent versions of GPR have the mouse handling screwed up. Try playing
- >>> "star wars" on a DN3500 to see what I mean.
- >>
- >>HUh??? Explain, please.
- >
- >The easist way to see what's going in is to play Revenaugh's Star Wars on
- >a DN580 and then try it on a DN3500. The difference should be immediately
- >noticable. The 3500 (and other newer models) buffer the mouse input
- >"incorrectly".
- >
- >The problem is that gpr_$cond_event_wait will return a gpr_$no_event
- >even when there is still mouse information in the buffer. Graphics-intensive
- >programs such as Star Wars therefore have the response to mouse input
- >lagging behind the actual mouse movements. The program believes that it
- >
-
- First, where can I get a copy of the program? For investigation purpose
- only, of course :-)
-
- Second, keeping in mind that I haven't seen the code nor do I have ANY
- idea of the expertise of the author, but this sound like the classic
- mistake that EVERYONE seems to make when first using eventcounts. (Yours
- truely included). i.e.
-
- instead of the correct sequence, or some CYCLIC variation thereof
-
- REPEAT
- ec2_$wait(..);
- ec2_$read(..);
- xxx_$cond_event_wait(...);
- process_event(...);
- UNTIL tired;
-
- the programmer uses something like::
-
- REPEAT
- ec2_$wait(..);
- xxx_$cond_event_wait(...);
- {an event can be queued HERE before the ec2_$read but after the cond_event_wait}
- ec2_$read(..);
- process_event(...);
- UNTIL tired;
-
- On slower machines or machines with less memory , i.e. a 580,
- the probability of queueing an event is significantly less.
-
- There is no difference in input event processing on any of the
- machine types.
-
- /dan ganek
- ganek@apollo.hp.com
-
-
-
-