Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 2523D200BC8 for ; Wed, 23 Nov 2016 22:48:53 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 23973160AFD; Wed, 23 Nov 2016 21:48:53 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 43DDE160AEC for ; Wed, 23 Nov 2016 22:48:52 +0100 (CET) Received: (qmail 43298 invoked by uid 500); 23 Nov 2016 21:48:51 -0000 Mailing-List: contact users-help@flex.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@flex.apache.org Delivered-To: mailing list users@flex.apache.org Received: (qmail 43282 invoked by uid 99); 23 Nov 2016 21:48:51 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Nov 2016 21:48:51 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id A25B2180226 for ; Wed, 23 Nov 2016 21:48:50 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.713 X-Spam-Level: *** X-Spam-Status: No, score=3.713 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, NUMERIC_HTTP_ADDR=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URI_HEX=1.313] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id WYhNQVr2wBZU for ; Wed, 23 Nov 2016 21:48:48 +0000 (UTC) Received: from mail-io0-f175.google.com (mail-io0-f175.google.com [209.85.223.175]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id DC7365F23D for ; Wed, 23 Nov 2016 21:48:47 +0000 (UTC) Received: by mail-io0-f175.google.com with SMTP id j65so47900980iof.0 for ; Wed, 23 Nov 2016 13:48:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=Fc2V8gwlr81ZYInUGFFcfAQpPs5A5fU6o0PGAWAzd4E=; b=wBCYu85sD5MIBLGu2NiEMbmKBcrTe6kToESVlAKtc95DZky5IgguIlClwHKoK0baPu dwyx9Zy3wHIOrmfyZuibAYJ87Ype8EdM4i/2kKtZXT3MRdWmZwLRGkRCwq4u/pIRAECi 5XoBmoHwk/nN2zj4RVYEQKRsk3xRvyHXJIBGje9oR1oZ3h479gv4sEn1xRaWwWJGKAEa ImXa1SJtc/sh5l0L7ECIbUIE8DqTDqJxug06NJu4Lwhy/w0n61kKsDpwCc7AXIHgRS1R xqUC3bFW/NWzoMkM4Xo6nyE258l3opvmYWgj42Eld5aEP6/7Xr8Q0tfN43glg8eTptKv 3a9g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=Fc2V8gwlr81ZYInUGFFcfAQpPs5A5fU6o0PGAWAzd4E=; b=Ht4oLi2bIUMUMDXNPFsJ5U4dDLWoNi/Jznu4Vl8AXg2kCAhsFRLpRHuDBsYQqOh9Y1 WnZnWavaQzuIz3cYyQHyF45GadWC6FcdKCdAnX+Ab5IvG5P6+es36UVU1U2JbkvCYzsa L4tc3tM5tkiMtak58Dbn20sPYzQosXiTJ7OVzjq6OFx3f8ZHjWDZCxrYjskwUZQjosVD DRmqS/V5Jth0FxLd4zm6a4I6Fs3kk0OolUshjz2vicx2+WPYZKlKfOOkyDpcSarLKpWn xsBV1HJzhDEGWKSdurPHWSvUU+BGQ4sMZzjVChsXFyvb2CcCEdIALXk97ND8qDv4TyhF gV0Q== X-Gm-Message-State: AKaTC01AsKXeUpziIGF5QUcD8he8XjhZiTHrKrH/wsy1Bqv1GaCGtg7nj8fHd2EIxDClCX4Y2yXV5H5288jjGg== X-Received: by 10.36.58.129 with SMTP id m123mr5008830itm.7.1479937718367; Wed, 23 Nov 2016 13:48:38 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.197.66 with HTTP; Wed, 23 Nov 2016 13:48:37 -0800 (PST) Received: by 10.107.197.66 with HTTP; Wed, 23 Nov 2016 13:48:37 -0800 (PST) In-Reply-To: <1479883681036-14202.post@n4.nabble.com> References: <1479883681036-14202.post@n4.nabble.com> From: flex capacitor Date: Wed, 23 Nov 2016 15:48:37 -0600 Message-ID: Subject: Re: Event Fired When A Transition is Complete? To: users@flex.apache.org Content-Type: multipart/alternative; boundary=001a11441222fe3c970541fed92a archived-at: Wed, 23 Nov 2016 21:48:53 -0000 --001a11441222fe3c970541fed92a Content-Type: text/plain; charset=UTF-8 Look up the elastic racetrack for more explanation. I don't know how many issues were solved by just using callLater :/ but I'm surprised the animation isn't finished. I can look at the sequence code and see if there is something different when they are ruin in a transition. If you can't wait a frame you can call validateNow() on your list or on the document (that contains the transitions) and sometimes that works. There is an event that exists in the base effects classes that isn't dispatched by the sub effects classes. I'll try and dig it up. Also, there may be a case to add events to the transition class. There are plenty of events for state changes. I'll post them when I'm not on mobile. On Nov 23, 2016 3:10 PM, "Josh Tynjala" wrote: > I have a mobile app in which I need to wait until a transition is 100% > complete before I call on itemrenderers to populate a list. I have looked > and looked, and I actually don't believe that there is an event for this. > I > found this JIRA from way back in 2007 and there seems to still be no > solution: > > https://issues.apache.org/jira/browse/FLEX-10947 > > Here is the layout of the States and Transition in my app: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > The closest that I have come to a workaround is to listen for the > "effectEnd" event on either the Sequence tag or the Move Effect. > Unforunately, the transition is not completely finished when this happens > so > my component transitions about 90% into place before it starts to load my > itemrenderers which pauses the transition. It finally snaps into place > after almost 3 seconds. I need a better alternative. I also tried > listening to when a state was entered, but that happens way before > transition is complete. The google machine even failed me HaHa!! Does > anybody have any ideas for a good workaround to this problem? Again, I > need > to know when a transition is 100% complete and my component is in place. > > Thanks. > > > > -- > View this message in context: http://apache-flex-users. > 2333346.n4.nabble.com/Event-Fired-When-A-Transition-is- > Complete-tp14202.html > Sent from the Apache Flex Users mailing list archive at Nabble.com. > --001a11441222fe3c970541fed92a--