[ 
https://issues.apache.org/jira/browse/FLEX-33860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13842784#comment-13842784
 ] 

kevin godell commented on FLEX-33860:
-------------------------------------

I didn't get that double gap anymore on ios7 when using air 4 beta with my 
temporary workaround. I place a public function in my viewnavigatorapplication 
and called it from the view that requests a fullscreen change like so:
public function setStageDisplayState(stageDisplayState:String):void
{
if (stage != null) {
if (stage.displayState != stageDisplayState) {
switch (stageDisplayState) {
case StageDisplayState.NORMAL :
stage.displayState = stageDisplayState;
if (IS_IOS7 == true && getStyle('osStatusBarHeight') != 20) {
setStyle('osStatusBarHeight', 20);
}
break;
case StageDisplayState.FULL_SCREEN :
case StageDisplayState.FULL_SCREEN_INTERACTIVE :
stage.displayState = stageDisplayState;
if (IS_IOS7 == true && getStyle('osStatusBarHeight') != 0) {
setStyle('osStatusBarHeight', 0);
}
break;
}
}
}
}
I know the function contained more than it should, but i was debugging.
And from the view it is called :
FlexGlobals.topLevelApplication.setStageDisplayState(StageDisplayState.NORMAL);

> Support For iOS7 status bar
> ---------------------------
>
>                 Key: FLEX-33860
>                 URL: https://issues.apache.org/jira/browse/FLEX-33860
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: Mobile: ActionBar
>    Affects Versions: Apache Flex 4.11.0
>         Environment: iOS 7
>            Reporter: Keith Lee
>             Fix For: Apache Flex 4.12.0
>
>
> iOS 7 now runs everything in full screen, with the status bar being 
> transparent, so mobile Flex applications now need a 20px padding at the top 
> in order for action bar text to not be obscured by the status bar text and 
> symbols.
> * handle the case when  softkeyboardBehavior = "pan" and screen in scrolled 
> for SKB



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Reply via email to