>This causes a stack overflow inside the Binding/Watch infrastructure.
Really? Didn't expect that one. I never use inline renderers if I can
help it! I suspect it'll need to be value={parent.data} or maybe
owner.data ... again, I hate inline renderers.
>If I take out the mx:Component lines, it fails to compile because
>NumericStepper is not an Factory, is that why you suggest creating a
Factory
>for it ?
Yeah, the itemEditor property takes an IFactory. The main reason for
setting it in actionscript like that is so you can set the
initialization properties (max, min, etc). It defaults to new
ClassFactory( mx.controls.TextInput).
Gk.
