- From: <rob.bull@blackdog.co.uk>
- Date: Thu, 01 Dec 2005 09:30:55 +0000
- To: www-forms@w3.org
- Cc: Mark.Birbeck@x-port.net
Hi Mark, Many thanks for that, I had been assuming that the value-changed event occurred after the DOMFocusOut, but it looks as if I was mistaken. I think that I may have been confused by the case sensitivity of 'value-changed'. It works brillianty for my purpose with FP anyway, TVM, Rob Robert, Just use xforms-value-changed. The 'ing' event used to be for @incremental, but the XForms model doesn't have any notion of the model being in some intermediate state, so there is no concept of data changing, only changed. It was therefore dropped. Regards, Mark Mark Birbeck CEO x-port.net Ltd. e: Mark.Birbeck@x-port.net t: +44 (0) 20 7689 9232 w: http://www.formsPlayer.com/ Download our XForms processor from http://www.formsPlayer.com/ ---------------------------------------------------------------------------- ---- From: www-forms-request@w3.org [mailto:www-forms-request@w3.org] On Behalf Of Robert Bull Sent: 30 November 2005 22:52 To: www-forms@w3.org Subject: value-changing I have probably missed a massive "thread" somewhere along the line, but somehow the removal of the value-changing event between the candidate recommendation and the recommendation seems to have passed me by. I have searched my e-mail archive in vain; has this event been left out of xForms 1.0? Is there anything similar that implementations capture to monitor instance manipulation? RR **************************************************** * This e-mail is for the intended recipient only, * * its contents and the content of any attachments * * is copyright material belonging to HoT Training * * and Consultancy Ltd, and all information herein * * should be treated as Company Confidential * ****************************************************
Received on Thursday, 1 December 2005 09:31:22 UTC