Return-Path: X-Original-To: apmail-flex-dev-archive@www.apache.org Delivered-To: apmail-flex-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9DFB5E133 for ; Thu, 31 Jan 2013 18:33:13 +0000 (UTC) Received: (qmail 85660 invoked by uid 500); 31 Jan 2013 18:33:12 -0000 Delivered-To: apmail-flex-dev-archive@flex.apache.org Received: (qmail 85634 invoked by uid 500); 31 Jan 2013 18:33:12 -0000 Mailing-List: contact dev-help@flex.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flex.apache.org Delivered-To: mailing list dev@flex.apache.org Received: (qmail 85622 invoked by uid 99); 31 Jan 2013 18:33:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 Jan 2013 18:33:12 +0000 Date: Thu, 31 Jan 2013 18:33:12 +0000 (UTC) From: "Alex Harui (JIRA)" To: dev@flex.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (FLEX-33375) Button clicked in a Component (Group) causes the component to stay in memory MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/FLEX-33375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Harui resolved FLEX-33375. ------------------------------- Resolution: Not A Problem We would need a complete test case to be sure, but the most likely cause based on the snippet you included is that the button still has keyboard focus. The FocusManager does not try to figure out where else to put focus when the focused item is removed from the display list. It is highly recommended that you call setFocus on some useful component for your users that may not be able to use a mouse, and doing so should allow the view to be garbage collected. Otherwise, please re-open with a small and complete test case. > Button clicked in a Component (Group) causes the component to stay in memory > ---------------------------------------------------------------------------- > > Key: FLEX-33375 > URL: https://issues.apache.org/jira/browse/FLEX-33375 > Project: Apache Flex > Issue Type: Bug > Components: Spark: Button > Environment: air 3.5 mobile > Reporter: Christian Kiefer > Priority: Critical > > Code: > protected function handleLoginClicked(event:MouseEvent):void > { > dispatchEvent(new LoginEvent(LoginEvent.LOGIN, "XYZ", "123")); > } > > ]]> > > enabled="true" > label="test" > height="60" > click="handleLoginClicked(event)"/> > > > Result: > After the login event is dispatched the view/current component (group) gets disposed and removed... > Problem: > clicking the label and the view isn't in memory anymore. > clicking the button causes the view to stay in memory. -- 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