Same here... I am wondering whether its VISTA related (which I am
running on my box)? Basically, if there is a trigger for a runtime
error, such as e.g. referencing a null pointer, the function with the
culprit will stop executing, but the rest will continue... makes
debugging kind of tedious...
DataBinding is funny like that.
Once it fails it stop execute any further in the code block.
I think at this stage it may be worth writing our own versions of
databinding that handle as we wish.
On 02/04/2007, at 4:11 PM, iko_knyphausen wrote:
Same here... I am wondering whether its VISTA
Hm, how about data binding that is done declarative - meaning in curly
braces... there is no code block per se?
--- In flexcoders@yahoogroups.com, Bjorn Schultheiss
[EMAIL PROTECTED] wrote:
DataBinding is funny like that.
Once it fails it stop execute any further in the code block.
I think
Where you change the value that is being Binded to.
eg.
mx:Text text={model.text} /
// in a command or equivalent
model.text = param1;
model.otherVal = param2;
If binding throws an error on line1 of the command, it can prevent
line 2 from executing
On 02/04/2007, at 4:33 PM,
Ok, got you...
I have another post out there regarding binding problems...
http://tech.groups.yahoo.com/group/flexcoders/message/70163
http://tech.groups.yahoo.com/group/flexcoders/message/70163
Maybe you know an answer to that one too ;-) (praying)
Thx
--- In flexcoders@yahoogroups.com,
I read it earlier.
Its hard to say exactly why it fails.
There are a few ways it can happen. But i dont think there is a limit
to the amount of bindings in an application.
You can use the debugger to see when databinding fails. Usually you
will eventually step into the databinding error
6 matches
Mail list logo
