I agree that they should be able to fail silently, but they also stop the execution of that specific method at that point....that's what's bothering me about it.... I can remember getting errors thrown about in the past indeed.
Ralph. On 2/4/07, Ralf Bokelberg <[EMAIL PROTECTED]> wrote:
Bindings must be able to fail silently. Otherwise we would see a lot of exceptions during the initialization phase. Therefore these exceptions are catched by the flex framework. Last time i looked into it, there is a debug flag you can set, to see the failing bindings. I just looked at the online docs and can't find it. Maybe it has been removed with 2.01? Cheers, Ralf. On 2/4/07, Ralph Hauwert <[EMAIL PROTECTED]> wrote: > > Hi All, > > I just spent about an hour trying to figure out why one of my methods > was not executing. > After a while I figured out it was only half executing. It would just > stop at one of my BindingUtils.bindSetter calls. Turns out that during > a quick cleanup I had deleted the value I was binding to in my host > object. > > Now of course, that's not handy, but what bothers me is that there are > no errors thrown, and the method execution is broken off at that > point, without any debug warnings popping up what-so-ever. That the > errors are not thrown at compile time is logical, but that it fails > silently at runtime amazed me..... > > What's this all about ? > > -- > Ralph Hauwert > -- Ralf Bokelberg <[EMAIL PROTECTED]> Flex & Flash Consultant based in Cologne/Germany Phone +49 (0) 221 530 15 35
-- Ralph Hauwert FlashCoder
