As ridiculously stupid as it was, I found that providing a "blank" skin for the navigation buttons worked quite well :-)
<mx:DateChooser xmlns:mx="http://www.adobe.com/2006/mxml" enabled="false" alpha="1" showToday="false" rollOverColor="#FFFFFF" yearNavigationEnabled="false" dayNames="[ 'S', 'M', 'T', 'W', 'T', 'F', 'S' ]" firstDayOfWeek="0" nextMonthDisabledSkin="{InvisibleSkin}" nextMonthDownSkin="{InvisibleSkin}" nextMonthOverSkin="{InvisibleSkin}" nextMonthUpSkin="{InvisibleSkin}" prevMonthDisabledSkin="{InvisibleSkin}" prevMonthDownSkin="{InvisibleSkin}" prevMonthOverSkin="{InvisibleSkin}" prevMonthUpSkin="{InvisibleSkin}" disabledColor="#000000"> <mx:Script> <![CDATA[ [Embed(source="DateChooserSkins.swf", symbol="Invisible")] [Bindable] public var InvisibleSkin:Class; ]]> </mx:Script> </mx:DateChooser> The "Invisible" symbol is simply a blank movieclip symbol in Flash. This makes for nice calendar display component, where we don't want user input. HTH, Brendan On 10/5/06, Jay Araujo <[EMAIL PROTECTED]> wrote:
How do I go about doing this? I can think of: 1) Creating a DateChooserMonthArrowSkin class to render the Arrow invisible ? ( Un-elegant ? ) 2) Subclassing DateChooser component to overwrite all navigation functionality ? ( Time consuming? ) Sorry to think this outloud but, why is it so hard for Adobe to come up with a allowNavigation="false" attribute? Regards, J.