From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: To: 9fans@cse.psu.edu Subject: Re: [9fans] cooked mouse mode. Date: Fri, 14 Jan 2005 13:57:48 +0000 From: rog@vitanuova.com In-Reply-To: <004101c4f9d5$4a45dfa0$0200000a@urjc1> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: 2f445696-eace-11e9-9e20-41e7f4b1d025 > We wanted to make explicit to choose between cooked events or raw events, no > to expose the two interfaces at the same time, which may get applications > into a kludge. You must choose cooked or raw, not being able to see both at > the same time. just IMHO, i'd say that having the same channel produce two different types of event is at least as open to confusion as having a new channel and ignoring the old one. by setting cooked mode, you are essentially changing the type of the channel. in the future you might wish cooked mode events to contain other fields (for instance a "click count" to cope with more than double mouse clicks), in which case your suggested interface would not be sufficient - you'd have to change the definition of the Mouse structure, which doesn't seem right. i'm not objecting to putting the declarations in mouse.h in the slightest; just that i don't think it's necessary to alter the old interface. doing it this way also opens the possibility of having various different kinds of mouse cookery without affecting the original interface or code in the slightest. cheers, rog.