Return-Path: X-Original-To: apmail-flex-users-archive@www.apache.org Delivered-To: apmail-flex-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 763F910A91 for ; Wed, 4 Mar 2015 21:32:48 +0000 (UTC) Received: (qmail 5160 invoked by uid 500); 4 Mar 2015 21:32:48 -0000 Delivered-To: apmail-flex-users-archive@flex.apache.org Received: (qmail 5130 invoked by uid 500); 4 Mar 2015 21:32:48 -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 5118 invoked by uid 99); 4 Mar 2015 21:32:47 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Mar 2015 21:32:47 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of markline@gmail.com designates 209.85.215.45 as permitted sender) Received: from [209.85.215.45] (HELO mail-la0-f45.google.com) (209.85.215.45) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Mar 2015 21:32:42 +0000 Received: by labgf13 with SMTP id gf13so22900821lab.5 for ; Wed, 04 Mar 2015 13:30:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=lOhzpkVORQO/0wCgrOmdfDJO9dryW9FP1dfzPGYHNbw=; b=xtDvxXovJTfNVeSlz+9Iq0DL5vvFm8bfGCXngloZaCpi/Vy4TlNllwzgTAqYVfpDCS YIFxPYrYi+GocyPuS8/9xFAbEbvUGtYRjD6VwvawojTI9fvkbiAWWHXLp5hSwaEw6lge zpPyRecvvuKtKIkCWt3mmpLlvmBGJ1qQsovahQgdqs7LIn0U8wxLXzgQEDhz0igyvUEW edPAnmLvuGBNnSQBGob0Pt0YzVSeIgJu0uAoH6hgtUJri81jDSqLXQJkGMijV2htqc3k gqyXd8LsmrRdKdMd502YCPhLgbsFYdtoFK/537X9VRqPTM/p62CvBlxl5orWRJyPAVjA afzw== MIME-Version: 1.0 X-Received: by 10.112.185.66 with SMTP id fa2mr5001639lbc.117.1425504651403; Wed, 04 Mar 2015 13:30:51 -0800 (PST) Received: by 10.112.77.167 with HTTP; Wed, 4 Mar 2015 13:30:51 -0800 (PST) Date: Wed, 4 Mar 2015 21:30:51 +0000 Message-ID: Subject: Event order processing From: Mark Line To: users@flex.apache.org Content-Type: multipart/alternative; boundary=001a11c314645f670b05107d2a58 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c314645f670b05107d2a58 Content-Type: text/plain; charset=UTF-8 Hi, I was wondering if someone could confirm something for me about event processing. I know if you two events are dispatched one after another, the second event will be dispatched only after all handlers of the first event are executed and the dispatchEvent method is returned. However does anyone know what would happen if during the event processing of the first event it dispatched another event. Would the new event be processed before any of the other event listeners (think event life cycle if it was bubbling). A very basic example: Eg would Flex make sure the event handlers registered for my this.addEventListener(FlexEvent.CHANGE_START, eventTwoHandler) before return flow to the button1_clickHandler. --001a11c314645f670b05107d2a58--