You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flex.apache.org by "Morten Gorm Madsen (JIRA)" <ji...@apache.org> on 2015/06/16 10:34:01 UTC
[jira] [Created] (FLEX-34890) BusyIndicator very power consuming
Morten Gorm Madsen created FLEX-34890:
-----------------------------------------
Summary: BusyIndicator very power consuming
Key: FLEX-34890
URL: https://issues.apache.org/jira/browse/FLEX-34890
Project: Apache Flex
Issue Type: Bug
Components: Spark: BusyIndicator
Affects Versions: Apache Flex 4.14.1
Reporter: Morten Gorm Madsen
Due to some hack fixing another problem, the state is always rotatingState which makes the component rotate behind the scenes when used in non-modal popups. Bad for power consumption on mobile devices!
See BusyIndicator.as:computeEffectiveVisibility().
// Treat all pop ups as if they were visible. This is to
// fix a bug where the BusyIndicator does not spin when it
// is inside modal popup. The problem is in we do not get
// an event when the modal window is made visible in
// PopUpManagerImpl.fadeInEffectEndHandler(). When the modal
// window is made visible, setVisible() is passed "true" so
// as to not send an event. When do get events when the
// non-modal windows are popped up. Only modal windows are
// a problem.
// The downside of this fix is BusyIndicator components that are
// inside of hidden, non-modal, popup windows will paint themselves
// on a timer.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)