Path: utzoo!attcan!uunet!husc6!spdcc!bloom-beacon!WSL.DEC.COM!haynes From: haynes@WSL.DEC.COM Newsgroups: comp.windows.x Subject: Re: xset m accl. theres. and XNextEvent (MotionNotify) Message-ID: <8806291927.AA15530@gilroy.dec.com> Date: 29 Jun 88 19:27:50 GMT Sender: daemon@bloom-beacon.MIT.EDU Organization: The Internet Lines: 31 Huh, it seems to me the server does mouse compression for you. Wrong. When the server sees the mouse device move, it sends out a mouse motion event. It (normally) has no way of knowing if the client is ready for that mouse event yet, or whether it's just adding another event to the client's input queue. Having the client do it is stupid. Wrong. It is sometimes, maybe usually stupid, but not always. With a slow client and a fast server the server could easily swamp the client with mouse motion events. Only the client is in a position to decide if it is "stupid" to compress. Every windowing system I have used does this by default Congratulations. Do you use X? If so, wrong again. There are two queues here, the mouse device driver queue, and the client input queue. The server can, and does, compress the mouse device driver queue, but it has no way of compressing the client input queue. That must be done on the client side, and that's what I was talking about. read the manual carefuly. "The bookful blockhead, ignorantly read, With loads of learned lumber in his head." -- Alexander Pope, "An Essay on Criticism" -- Charles