Well I tried your code in flex sdk 4.6 and could not include <mx:states> as it 
is deprecated.
But replacing <ms:states> with <s:states> works like a butter.
Please refer to the code below:

<?xml version="1.0" encoding="utf-8"?>
<s:Application xmlns:fx="http://ns.adobe.com/mxml/2009" 
<!-- Place non-visual elements (e.g., services, value objects) here -->
<s:State id="sparkState1" name="sparkState1" />
<s:State id="sparkState2" name="sparkState2" />
<mx:Button includeIn="sparkState1" label="MX Component" />
<mx:Button includeIn="sparkState2" label="MX Component 2" />

Flex 3 states can be used with spark component
Please refer to the attach blog: http://blog.benstucki.net/?p=56

Rishi Tandon

 From: bu4fred <fred.se...@adventistcare.org>
To: flexcoders@yahoogroups.com 
Sent: Tuesday, February 7, 2012 12:39 AM
Subject: [flexcoders] Flex 3 -> 4 migration and s:States

I'm migrating a flex 3.0 application to 4.0 (or 4.5, doesn't matter much) and I 
want to use the new state features of includeIn and excludeFrom.  I have a user 
defined base class in mxml and i inherit from that for my 'working' classes.  I 
have this code in my baseclass

<mx:TitleWindow xmlns:fx="http://ns.adobe.com/mxml/2009"; 

<s:State id="Oct2010" name="Oct2010"/>
<s:State name="Oct2011"/>
<s:State name="Apr2012"/>
. . .

------------- working class contains -----------------------------
<mx:FormItem  includeIn="Apr2012">
---- and the error is --------------------------------------------

State 'Apr2012' was referenced without being declared.  A.mxml  line 66 
/MdsClientBeta1/src/sections    Flex Problem

------------------- comments ------------------------
I tried s:states rather than mx:states but it could not resolve name
Must s:states be used only in s: components or can they be used in mx 


Reply via email to