Spark button event record.

Question

Hi,
I've the issue about record event in automation framework. A mouse events (double click, click, mouseDown) do not recording method which listen the event, i.e. automationManager.addEventListener(AutomationRecordEvent.RECORD, recordHandler, false, 0, true) but events from keyboard such as SPACE or ENTER is successfull recorded.
This is snippet of xml environment files with event for spark button:
<ClassInfo Name="SparkButton" Extends="SparkButtonBase" SupportsTabularData="false">
        <Implementation class="spark.components::Button"/>
        <Events>
            <Event Name="Click"   >
            <Implementation class="flash.events::MouseEvent" Type="click"/>
                <Property Name="triggerEvent"  DefaultValue="1">
                    <PropertyType Type="Enumeration" Codec="event"/>                  
                </Property>
                <Property Name="ctrlKey"  DefaultValue="false">
                  <PropertyType Type="Boolean"/>
                </Property>
                <Property Name="altKey"  DefaultValue="false">
                  <PropertyType Type="Boolean"/>
                </Property>
                <Property Name="shiftKey"  DefaultValue="false">
                  <PropertyType Type="Boolean"/>
                </Property>
            </Event>
            <Event Name="TypeSpark" >
                <Implementation class="flash.events::KeyboardEvent" Type="keyPress"/>
                <Property Name="keyCode" >
                    <PropertyType Type="String" Codec="keyCode" DefaultValue="ENTER"/>               
                </Property>  
            </Event>
      </Events>
</ClassInfo>
In what may be the cause?
Thanks.

Answer 1

The Spark button in this case is not itself toggleable.  You will need to use a ToggleButton.  Spark controls are not the swiss army knives that Flex 3 components were (in order to keep things a bit lighter).
The new Spark skinnable components control their own state internally and the components themselves in turn set the currentState of their associated skin at runtime.  The current state of the component is not (in general) directly controllable via 'currentState'.
Regards,
Corey