I am beginning to think this is a deeper issue than I initially thought. Since my apps was originally written for mobile, it has a few mobile components and skins for those components. I simply left them in my desktop versions so that I would have as few changes to make as possible because these are very large apps, and there are three of them. I am beginning to think that if you add ANY mobile components, or perhaps a mobile skin, then the app defaults to a "mobile mentality" for lack of a better word and behave like a mobile application. Here is an small example.
<?xml version="1.0" encoding="utf-8"?> <s:WindowedApplication xmlns:fx="http://ns.adobe.com/mxml/2009"; xmlns:s="library://ns.adobe.com/flex/spark" xmlns:mx="library://ns.adobe.com/flex/mx"> <fx:Style> @namespace s "library://ns.adobe.com/flex/spark"; @namespace mx "library://ns.adobe.com/flex/mx"; s|TextInput { skinClass: ClassReference("spark.skins.mobile.ScrollingStageTextInputSkin"); fontFamily: "Arial, Helvetica, san-serif"; contentBackgroundAlpha: 1; contentBackgroundColor: #FFFFFF; paddingTop:0; paddingBottom:0; } </fx:Style> <s:TextInput width="200" horizontalCenter="0" top="150"/> <s:Button width="200" horizontalCenter="0" top="250"/> </s:WindowedApplication> This is a simple little desktop app that adds a button and a TextInput in it, but I have added the skinClass ScrollingStageTextInputSkin in the CSS for the textInput, which was designed for mobile. To get it to work, you need to add these two swc's: [SDK]/frameworks/libs/mobile/mobilecomponents.swc [SDK]/frameworks/themes/Mobile/mobile.swc If you run this app after adding the code and swc's, the application works, but the button will no longer display an over state, just an up state, and down state. If you simply delete the s|TextInput CSS, then the button behaves exactly as you would expect with all three states demonstrated. Unless you have any other ideas, my early thoughts are that I am going to have to go through each of my apps and meticulously replace all the mobilegrids and other mobile components with their desktop counterparts to get this issue resolved. Any Thoughts??? I would really love to avoid this if there is any other alternative. -- Sent from: http://apache-flex-users.2333346.n4.nabble.com/
