Fixed/committed in develop branch -----Message d'origine----- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : jeudi 27 février 2014 14:08 À : dev@flex.apache.org Objet : RE: RC1/RC2 iOS possible issue
Or more simply, by testing stage.displayState at initialization. Maurice -----Message d'origine----- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : jeudi 27 février 2014 13:57 À : dev@flex.apache.org Objet : RE: RC1/RC2 iOS possible issue Checked my code: FullScreenEvent.FULL_SCREEN / FULL_SCREEN_INTERACTIVE are handled to set the os bar height to 0 (in Application class). However, this event is not sent initially when the app is set to full screen in the descriptor. So it has to be handled manually by reading the value of fullScreen in the AIR descriptor. Maurice -----Message d'origine----- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : jeudi 27 février 2014 13:13 À : dev@flex.apache.org Objet : RE: RC1/RC2 iOS possible issue Tested with SDK 4.12 RC2, AIR 4.0, and <fullScreen>true</fullScreen> iOS 6 => app displays in full screen iOS7 => the status bar is not displayed (OK), but there is a blank space, because of the osStatusBarHeight. I understand the problem: osStatusBarHeight should be ignored when fullScreen is set. My bad. I will fixed that immediately, so that it can be included in the next RC. Maurice -----Message d'origine----- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : jeudi 27 février 2014 13:01 À : dev@flex.apache.org Objet : RE: RC1/RC2 iOS possible issue I am checking with iOS6 and iOS7. Maurice -----Message d'origine----- De : Justin Mclean [mailto:jus...@classsoftware.com] Envoyé : jeudi 27 février 2014 11:44 À : dev@flex.apache.org Objet : RC1/RC2 iOS possible issue HI, >From the linkedin Apache Flex group: "The issue described by Simon Gladman in RC1 is still present in RC2: when compiling with Flex 4.12 iOS Apps don't correctly fill the whole screen when fullscreen is set to true in the descriptor file." Anyone confirm this is an issue or not? Or is it just you need to use the latest version of AIR? Thanks Justin
