Hey guys, say I have the following:
[Bindable]
public function get foo() : Foo {...}
public function set foo(v : Foo) : Void {...}
When I'm single-stepping through something that calls obj.foo =
fooInstance() the debugger tells me I'm in "set foo", but highlights "get
foo". Now I understand why this is happening, due to the compile-time voodoo
required for the generic [Bindabe] tag, but for newbs this would probably be
fairly intimidating.
It'd be really good if there was some sort of metadata included when
compiling debug versions that flags a specific method as compile-time
generated in the debugger stack trace or something along those lines.
Or a compile-time warning telling you to put [Bindable] on set rather than
get, despite it being counter-intuitive (does it even work?).
Maybe a compile-time warning telling you you're better off using the event=
form of [Bindable] when using get/set, which I assume doesn't require any
compile-time hijinks?
Just having the debugger smart enough to recognise these generated functions
and do something more appropriate. If you step into a [Bindable] setter you
end up single stepping through code you can't see on screen until it calls
set _generatedFooName() or whatever it happens to be that contains your
actual code. Confusing to say the least!
Maybe another window showing the .as intermediary code that's generated
between mxml and swf?
-J
--
"Therefore, send not to know For whom the bell tolls. It tolls for thee."
:: Josh 'G-Funk' McDonald
:: 0437 221 380 :: [EMAIL PROTECTED]
