flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "OmPrakash Muppirala (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLEX-33868) CursorManagerImpl#setBusyCursor is memory inefficient
Date Tue, 05 Nov 2013 18:06:19 GMT

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

OmPrakash Muppirala commented on FLEX-33868:

Please note that this is existing behavior that we should be careful about changing.  In my
enterprise mobile apps, I don't mind the busy cursor showing up (even it is at a random location)
 If needed, I can always go and fix it to not show in a mobile app. 

> CursorManagerImpl#setBusyCursor is memory inefficient
> -----------------------------------------------------
>                 Key: FLEX-33868
>                 URL: https://issues.apache.org/jira/browse/FLEX-33868
>             Project: Apache Flex
>          Issue Type: Improvement
>          Components: Mobile: Performance, Performance: Framework
>    Affects Versions: Apache Flex 4.11.0
>         Environment: mobile
>            Reporter: Benoit Wiart
>            Assignee: Justin Mclean
>            Priority: Minor
>              Labels: memory, performance
>         Attachments: busycursor.png
> Each time CursorManagerImpl#setBusyCursor is called a new cursor is created.
> setBusyCursor may be called on each remote invocation

This message was sent by Atlassian JIRA

View raw message