--- In flexcoders@yahoogroups.com, Kenneth Sutherland
kenneth.sutherl...@... wrote:
Sorry should have said you should use the 'event.target.id' (in
virtually all cases you can get away with using currentTarget, but if
you want to be guaranteed to be getting the info from whatever
dispatched
--- In flexcoders@yahoogroups.com, Tracy Spratt tr...@... wrote:
And if you do need to just send changed items, put a, isModified property
on the VO and set it when the data is updated..
I have never done anything like it, you think you can maybe, elaborate a little
more? a little example,
Sent: Saturday, May 09, 2009 1:04 PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Re: Sending textinput id
--- In flexcod...@yahoogro mailto:flexcoders%40yahoogroups.com ups.com,
Tracy Spratt tr...@... wrote:
And if you do need to just send changed items, put a, isModified
property
If you use the change event of the text input then the id is at event.target.id
Steve
--- In flexcoders@yahoogroups.com, Gustavo xy...@... wrote:
Hi, I have a form and I would like to add the textinput id to an array so I
know which fields were edited, I trigger the change event on each
Hi Gustavo,
I'm not sure of your implementation, but many times it's easier to
persist a working copy of the data in a value object (VO). Each
property in the object, that is editable in the form, is bound to it's
associated control. When a control changes, update the associated
property in
@yahoogroups.com
Subject: [flexcoders] Re: Sending textinput id
Hi Gustavo,
I'm not sure of your implementation, but many times it's easier to
persist a working copy of the data in a value object (VO). Each
property in the object, that is editable in the form, is bound to it's
associated
6 matches
Mail list logo
