[
https://issues.apache.org/jira/browse/FLEX-33868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13813357#comment-13813357
]
Maurice Amsellem edited comment on FLEX-33868 at 11/4/13 10:29 PM:
-------------------------------------------------------------------
My two cents: most of the issues you have raised are motivated by performance
on mobile platforms and I am assuming this one as well.
As far as I know, setting showBusyCursor=true on mobile is pointless as there
is no mouse and no mouse pointer.
Even worse, when you set "showBusyCursor", the "hourglass" cursor is displayed
at random places, which does not look very "mobile".
Better to use "BusyIndicator" or anything else to show that something is in
progress (and of course setting showBusyCursor to false).
was (Author: mamsellem):
My two cents: most of the issues you have raised are motived by performance on
mobile platforms and I am assuming this one as well.
As far as I know, setting showBusyCursor=true on mobile is pointless as there
is no mouse and no mouse pointer.
Even worse, when you set "showBusyCursor", the "hourglass" cursor is displayed
at random places, which does not very pretty.
Better to use "BusyIndicator" or anything else to show that something is in
progress (and of course setting showBusyCursor to false).
> 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
(v6.1#6144)
