Using States and the includeIn-property for UI-elements inside my mxml-composide-component

Question

Hi,
unfortunatly I am looking for a way to use States in a mxml-component. I’m working with the flash builder 4.6 (means as3).
Because this did not work when I did use the normal mxml tags for the states inside my VGroup-composite-component, I added a creationComplete-Handler in the Script part of my component in which I instanciated the states and the states-Array via as3. I copied
this of an internet- article from 2006 that was already dealing with
as3, but at that time the States were part of the mx-namespace. How ever when I wrote: newState1: State= new State(); my development environment did not know the class State. Did I forgot to import anything or to use a namespace in my Script block ? I imported the AS3 Finite State Machine from meekgeek.com.
But these states have no name-property insted they got a key-property, but this did not work either though I imported correct and did use the correct namespace. I did not find any State-class-description at Adobe's doku either. All I’m trying to do is to use the standard State-includeIn-properties of UI-Components inside
my mxml-composide-componend. I’d be much obliged if You may help me in this point.
Best regards,
Timan Bracht

Answer 1

Thanks for the answers so far.
I can show now the correct KmLimit on the field, thanks to a javabean method, so this problem is solved - even I don't know why on hell it does not show it automatically, since I did give to it literal/expression default value in the attribute properties of the transient field; but never mind.
The current problem: we use a task flow, that shows an input form to enter new records. This form has a LOV, from where I get a value from, which will be then saved once the submit button has been pressed.
So far, so good.
I enter some values in the input fields. If now I save the record, it will be saved, and all the form fields reset to null. Perfect.
But. If I don't press the save button, instead I pick another value from the LOV list, the values of the input fields does not reset to null, instead, they remain with the last entered value.
It does not seem there's more to change in the task flow properties that would reset the fields automatically.
So we're stuck with this issue, the fields remain filled, even if I do set it to null. The value is really null - I set it to null with fieldName.setValue(null) and show it in the console with fieldName.getValue() - but the form still shows the old value in the field.
Any help is greatly appreciated,
Sergio.