Indeed alex, I tested the spark busyIndicator but in a mx application. Sorry for the false alarm
Dany Dany Dhondt archeme...@mac.com | Mobile +32 496 251 455 > Op 14-jan.-2015, om 18:57 heeft Alex Harui <aha...@adobe.com> het volgende > geschreven: > > Could you be using mx:Application instead of any of the other Application > classes? > > -Alex > > From: Dany Dhondt <archeme...@mac.com<mailto:archeme...@mac.com>> > Reply-To: "dev@flex.apache.org<mailto:dev@flex.apache.org>" > <dev@flex.apache.org<mailto:dev@flex.apache.org>> > Date: Wednesday, January 14, 2015 at 5:08 AM > To: "dev@flex.apache.org<mailto:dev@flex.apache.org>" > <dev@flex.apache.org<mailto:dev@flex.apache.org>> > Subject: [4.14] BusyIndicator skin applicationDPI > > Hi All, > > I've installed the latest sdk build to test if the BusyIndicator skin issue > was solved. > The skin itself is found but FlexGlobals.topLevelApplication.applicationDPI > is not found/doesn't exist > > Could it be a configuration issue? Anyone had this error? > > ================ > > > protected functionget applicationDPI():Number > > { > > return FlexGlobals.topLevelApplication.applicationDPI; > > } > > > ================ > > > > at spark.skins::ActionScriptSkinBase/get > applicationDPI()[C:\Jenkins\workspace\flex-sdk_release-candidate\frameworks\projects\spark\src\spark\skins\ActionScriptSkinBase.as:180] > > at > spark.skins.spark::BusyIndicatorSkin()[C:\Jenkins\workspace\flex-sdk_release-candidate\frameworks\projects\spark\src\spark\skins\spark\BusyIndicatorSkin.as:64] > > ... > > > -Dany >
