You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by "Alex Harui (JIRA)" <ji...@apache.org> on 2012/11/05 20:16:12 UTC
[jira] [Updated] (FLEX-33165) RTE on Scroller when rotating device
in mobile simulator
[ https://issues.apache.org/jira/browse/FLEX-33165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Harui updated FLEX-33165:
------------------------------
Labels: EasyFix (was: )
Try adding null check and if there are downstream problems, remove EasyFix label
> RTE on Scroller when rotating device in mobile simulator
> --------------------------------------------------------
>
> Key: FLEX-33165
> URL: https://issues.apache.org/jira/browse/FLEX-33165
> Project: Apache Flex
> Issue Type: Bug
> Components: Spark: Scroller
> Affects Versions: Adobe Flex SDK 4.6 (Release)
> Reporter: Maurice Amsellem
> Priority: Minor
> Labels: EasyFix
>
> When rotating the mobile simulator (Menu Device>Rotate left or right), I get the following error:
> {code}
> Error #1056: Cannot create property null on spark.components.DataGroup.
> at spark.components::Scroller/http://www.adobe.com/2006/flex/mx/internal::snapElement()[E:\dev\4.y\frameworks\projects\spark\src\spark\components\Scroller.as:1571]
> at spark.components::Scroller/checkScrollPosition()[E:\dev\4.y\frameworks\projects\spark\src\spark\components\Scroller.as:1750]
> at spark.components::Scroller/handleSizeChange()[E:\dev\4.y\frameworks\projects\spark\src\spark\components\Scroller.as:1766]
> at spark.components::Scroller/handleSizeChangeOnUpdateComplete()[E:\dev\4.y\frameworks\projects\spark\src\spark\components\Scroller.as:2048]
> {code}
> In Scroller:1571 viewport[scrollProperty] = snapScrollPosition;
> scrollProperty is null, which trigger the RTE.
> Scroller belongs to a spark:List with HorizontalLayout and verticalScrollPolicy style is set to ScrollPolicy.OFF.
> also, the RTE does not seem to occur on the real device, but maybe it is just swallowed...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira