Hi Gina, > I am new to Flex and Actionscript, and only started > prototyping for our new project (a UI application on a J2EE > server) a week ago. It's been a fun learning this technology > and the Cairngorm framework does present a very neat > framework that suits our purpose well.
Good to hear Cairngorm is working for you... > 1. I have a button whose face is completely occupied by a > .gif image. When the button is disabled, it is expected that > the image will be grayed out in addition to having a flat > appearance. Do I need to swap the image file references > whenever the image is enabled/disabled, or is there a better > way of achieving the same effect in Flex? We've used something like this in previous projects, with 4 different PNG files for the different button skins: <mx:Button xmlns:mx="http://www.macromedia.com/2003/mxml"; falseUpSkin="@Embed('images/button_default.png')" falseDownSkin="@Embed('images/button_down.png')" falseOverSkin="@Embed('images/button_hover.png')" falseDisabledSkin="@Embed('images/button_disabled.png')" color="white" disabledColor="white"/> We would typically save that as a superclass, eg MyButton.mxml and then just use <namespace:MyButton /> instead of <mx:Button> when we want one of our skinned buttons. > > 2. Another button I have is meant to be a toggle button so I > used the syntax: > <mx:Button label="Is" toggle="true" selected="true" /> But > this does not have the toggled effect - it looks exactly the > same whether I set "toggle" property to true or not. I > thought it should be quite straightforward so please suggest > what's my blindspot! > Can't see that you're missing anything ... try with the above skins, and see how you get on ? Best, Steven -- Steven Webster Technical Director iteration::two This e-mail and any associated attachments transmitted with it may contain confidential information and must not be copied, or disclosed, or used by anyone other than the intended recipient(s). If you are not the intended recipient(s) please destroy this e-mail, and any copies of it, immediately. Please also note that while software systems have been used to try to ensure that this e-mail has been swept for viruses, iteration::two do not accept responsibility for any damage or loss caused in respect of any viruses transmitted by the e-mail. Please ensure your own checks are carried out before any attachments are opened.
