Alexander Steitz wrote:
Hi skar,
On Tuesday 17 November 2009 skar wrote:
Matthew Gregory wrote:
Strange,
I am not sure why it would do that, from what you've said it sounds like
this would work for you though:
this.fireDataEvent("changeReadOnly", !!value, !!old);
Don't know why. Anyways, I've used the syntax
this.fireDataEvent("changeReadOnly", {value: value, old: old});
Now, it's working fine and this is a syntax already used in various
qooxdoo modules and that's where I found the idea.
If you fire a data event with
--snip--
this.fireDataEvent("changeReadOnly", value, old);
--snip--
you should get the data from the event like
--snip--
readOnlyListener : function(e)
{
var currentValue = e.getData();
var oldValue = e.getOldData();
}
--snip--
That's how it should work.
Yes, I did that but got true when readonly was changed from false to
true, but getOldData was undefined.
When it's changed from true to false, both getData as well as getOldData
are undefined.
cheers,
skar.
--
--
The life so short, the craft so long to learn.
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
