FDB is a good old-fashioned command line debugger.  Should be in the bin folder 
next to MXMLC.  There is a help command

From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Josh 
McDonald
Sent: Monday, September 15, 2008 5:01 PM
To: [email protected]
Subject: Re: [flexcoders] XMLListCollection.AddItemAt() silently fails

Builder's debugger is no good with MXMLC-generated binding code, that's for 
sure :) I'm intrigued by FDB, what's the best place to get started with it?

-Josh
On Tue, Sep 16, 2008 at 9:56 AM, Alex Harui <[EMAIL PROTECTED]<mailto:[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: [email protected]<mailto:[email protected]> 
[mailto:[email protected]<mailto:[email protected]>] On 
Behalf Of Daniel Freiman
Sent: Monday, September 15, 2008 1:59 PM
To: [email protected]<mailto:[email protected]>
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]<mailto:[EMAIL 
PROTECTED]>> wrote:

Maybe setting source[0] triggers change events that refresh source?



From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]<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





--
"Therefore, send not to know For whom the bell tolls. It tolls for thee."

http://flex.joshmcdonald.info/

:: Josh 'G-Funk' McDonald
:: 0437 221 380 :: [EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>

Reply via email to