- From: Hickman, Steve (AdvTech) <Steve.Hickman@honeywell.com>
- Date: Sun, 19 Jan 2014 14:25:05 +0000
- To: "public-pointer-events@w3.org" <public-pointer-events@w3.org>
- Message-ID: <EA5676973A55CA4BA5D3F921E9FB1C172772FCA4@de08ex3003.global.ds.honeywell.com>
Classification: Honeywell Internal A prior thread from 2 April 2013 discussed the addition of a rotation attribute to Pointer event. While I also see a need for specifying "rotation" information, I'm not certain that adding this to a Pointer event is the correct solution. Input devices can have a lot of functionality. If the spec continues to expand to include all possible functionality, the event structures will become unwieldy. Consider this as the equivalent of the CISC vs. RISC debate - do we continue to add more fields to existing events or create smaller, highly focused events, and have the devices generate multiple event types depending on their particular combination of functionality? Some alternative approaches in this case could be: 1) Adding this to "wheel events" since rotation of a knob is essentially the same as rotation of a wheel. In this case, the wheel event would have absolute position as well as delta. 2) Creating a separate absolute rotation event that specifies only absolute wheel position. The advantage here is there is no need to try to figure out which fields in the event are to be used. The event type indicates that. Steve Hickman System Architect, Flight Deck of the Future 480-236-8367 ============================================================================================================================================================================================================ This message classified as Honeywell Internal by Hickman, Steve (AdvTech) on Sunday, January 19, 2014 at 6:25:05 AM. The above classification labels are in accordance with the Honeywell Corporate Classification Policy. The information contained in this electronic message is confidential and intended only for the use of the individual/entity named above, and the information may be privileged. If you, the reader of this message, are not the intended recipient or an employee or agent responsible to deliver this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the sender and delete the original message. ============================================================================================================================================================================================================
Received on Sunday, 19 January 2014 14:25:50 UTC