I'll test that theory out when I have time.  For now I have a workaround.
It'll be interesting to see if there's a substantive difference between the
two.

- Daniel Freiman

On Mon, Sep 15, 2008 at 7:56 PM, Alex Harui <[EMAIL PROTECTED]> wrote:

>    I use FDB to debug XML problems.  I can see instance numbers and other
> properties that the FB debugger filters.  I don't trust the debugger to step
> into binding code.
>
>
>
> *From:* flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] *On
> Behalf Of *Daniel Freiman
> *Sent:* Monday, September 15, 2008 1:59 PM
> *To:* flexcoders@yahoogroups.com
> *Subject:* Re: [flexcoders] XMLListCollection.AddItemAt() silently fails
>
>
>
> Yeah, I've been looking into binding causes, but wouldn't I see that
> happening while stepping through the code?  As far as I can tell this is an
> atomic action (or lack thereof).
>
> - Daniel Freiman
>
> On Mon, Sep 15, 2008 at 4:45 PM, Alex Harui <[EMAIL PROTECTED]> wrote:
>
> Maybe setting source[0] triggers change events that refresh source?
>
>
>
> *From:* flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] *On
> Behalf Of *Daniel Freiman
> *Sent:* Monday, September 15, 2008 12:03 PM
> *To:* flexcoders
> *Subject:* [flexcoders] XMLListCollection.AddItemAt() silently fails
>
>
>
> I have a case where I try to add a node to an empty XMLListCollection and
> addition silently fails.  I step through the code and I find that line 216
> of XMLListAdapater is the line that is failing (it's supposed to assign the
> added node to the first location in the source list but instead nothing
> happens).  Here's the line:
>
> source[0] = length > 0 ? item + source[0] : item;
>
> I can't recreate this bug in any other condition other than the app I'm
> currently developing.  Has anyone else seen this intermitent error?
>
> - Daniel Freiman
>
>
>
>   
>

Reply via email to