Hi,
Thanks for the replies... Amy - I've tried wrapping my e4x in a trace
statement inside the Expression panel but that didn't seem to help me :(
Valdor, I seem to be able to look at basic variables when I trace now - I'm
right-clicking the variable from the Variables panel, adding it as an
Expression and it's there.
I'm trying to look at the "data" variable which is XML with children() so I
edit the expression as data.children() and click ok but get the error...
I then try XML(data).children() but no joy either.
Mmmmm... It'd be great if i can on the fly edit expressions without having
to create new variables and recompile...
Nick
2010/1/6 valdhor <valdhorli...@embarqmail.com>
>
>
> I use this all the time.
>
> Generally, I am only interested in a few variable values and it is a pain
> to have to open the variables pane full screen and then navigate around to
> see what each of the variable values are (especially if they are in multiple
> instances).
>
> So, what I do is right click on the variable I want to watch (inside my
> code) and select Watch("Variable Name"). This adds it to the watch
> expression pane and when I hit a breakpoint, the values I want to look at
> are right there. I can then resume or step through and watch them change.
>
> One other thing that is useful is the path to a nested variable. For
> example, I clicked on an item in the variables pane and added it as a watch
> expression. I then right clicked on the expression and selected "Edit Watch
> Expression". I can now copy and paste that into my code and know that it
> will work.
>
> Anyway, how did you get the variable into the Expressions panel? Also, what
> type of variable is it? There has to be a reason you get a "Can't Evaluate"
> message.
>
>
> --- In flexcoders@yahoogroups.com <flexcoders%40yahoogroups.com>, Nick
> Middleweek <n...@...> wrote:
> >
> > Hi,
> >
> > Has anyone managed to get this "what seems to 'could' be a wonderfull
> tool"
> > working?
> >
> > i just get a message in red saying something like "Cant evaluate"
> >
> >
> > Thanks for any pointers...
> > Nick
> >
>
>
