On 9/12/14 10:17 AM, "Justin Mclean" <jus...@classsoftware.com> wrote: >>and with the SDK locale example the new locales don't seem to be >>included. > >Compiling the loader to specify all of the locales fixed this issue. >Looks like a SDK bug to me. I just took a quick look at ResourceManager. I do not see any support for sub apps with different locale chains.
> >The 3rd issue with the Callout not working is also a SDK bug, in >particular this line in the CallOut arrow skin constructor > >var applicationDPI:Number = >Application(FlexGlobals.topLevelApplication).applicationDPI; > >This assumes that the top level Application is an s:Application not can't >be mx:Application. Callout used to be mobile-only, IIRC. I'll bet the authors did not think mobile apps would be aggregated up into other apps. Too bad we didn't see that when we moved it out of mobile. > >Choices are: >1. Remove example >2. Leave broken example in there, code example does work standalone. >3. Change TourDeFlex to use s:Application. Would break any existing >example that assumes mx:Application is the top level - no idea one exists >or not. >4. Fix SDK bug and make new SDK release, then release TourDeFlex What about: 5. Add public applicationDPI property to Explorer. Otherwise, I would choose 1 (or 4 if you have the time and energy). -Alex
