flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Piotr Zarzycki (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLEX-34712) Callout loses anchor to CalloutButton while callout open and screen rotates
Date Fri, 09 Jan 2015 21:25:34 GMT

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

Piotr Zarzycki commented on FLEX-34712:
---------------------------------------

Hi [~kevin.godell]

I have commented your post on dev forum with some suggestions to your fix. Please try it once
yo will have some time and let us know. :)

Best,
Piotr

> Callout loses anchor to CalloutButton while callout open and screen rotates 
> ----------------------------------------------------------------------------
>
>                 Key: FLEX-34712
>                 URL: https://issues.apache.org/jira/browse/FLEX-34712
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: Mobile: Callout / CalloutButton
>    Affects Versions: Apache Flex 4.14.0
>         Environment: windows 7, flashbuilder 4.6, flex 4.14, air 15
>            Reporter: kevin godell
>         Attachments: calloutButtonCalloutPositionOnResize.fxp
>
>
> When debugging on android device, rotating device from landscape to portrait and then
back again causes callout to lose its positioning to the calloutbutton. It works good on the
simulator, but on the device, it seems that the positioning is called before the screen finishes
rotating. Tested on 3 different android devices with android 2.3.6, 4.2.2, and 4.4.
> workaround: patching callout.as 
> in systemManager_resizeHandler, change invalidatePosition() to callLater(invalidatePosition).
This gives the necessary delay to allow the popup to position itself in the correct location.
It looks a little buggy as it moves from the old position to the new position, but atleast
it gets to the right spot.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message