W3C home > Mailing lists > Public > public-mbui@w3.org > January 2014

Abstract User Interface Models - questions on event structure [Honeywell Internal]

From: Hickman, Steve (AdvTech) <Steve.Hickman@honeywell.com>
Date: Wed, 22 Jan 2014 01:30:42 +0000
To: "public-mbui@w3.org" <public-mbui@w3.org>
Message-ID: <EA5676973A55CA4BA5D3F921E9FB1C172773084B@de08ex3003.global.ds.honeywell.com>
Classification: Honeywell Internal
The 05 Nov 2013 Working Draft is spartan.  In particular, there isn't enough description of the event structure to understand how they differ. Can someone explain this in more detail?  It seems to me that all events trigger something unless they are ignored. It might be a change in a display (selecting or deselecting a visual element, changing a value in a visual element, etc.) or it might trigger something else.  So how is a "TriggerEvent" something unique?

Steve Hickman
System Architect, Flight Deck of the Future

This message classified as Honeywell Internal by Hickman, Steve (AdvTech) on Tuesday, January 21, 2014 at 5:30:42 PM.
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 Wednesday, 22 January 2014 01:31:15 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:58:26 UTC