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 A5065200D29 for ; Thu, 26 Oct 2017 20:03:21 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id A3A051609E8; Thu, 26 Oct 2017 18:03:21 +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 E9C251609E5 for ; Thu, 26 Oct 2017 20:03:20 +0200 (CEST) Received: (qmail 48165 invoked by uid 500); 26 Oct 2017 18:03:20 -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 48153 invoked by uid 99); 26 Oct 2017 18:03:19 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Oct 2017 18:03:19 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 0F54C1A1796 for ; Thu, 26 Oct 2017 18:03:19 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.215 X-Spam-Level: ** X-Spam-Status: No, score=2.215 tagged_above=-999 required=6.31 tests=[FREEMAIL_ENVFROM_END_DIGIT=0.25, SPF_HELO_PASS=-0.001, SPF_NEUTRAL=0.652, URIBL_BLOCKED=0.001, URI_HEX=1.313] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id qS9Y0cbNrRlB for ; Thu, 26 Oct 2017 18:03:17 +0000 (UTC) Received: from n4.nabble.com (n4.nabble.com [162.253.133.72]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 89A265FCDA for ; Thu, 26 Oct 2017 18:03:17 +0000 (UTC) Received: from mben.nabble.com (localhost [127.0.0.1]) by n4.nabble.com (Postfix) with ESMTP id 2E6CC15538387 for ; Thu, 26 Oct 2017 11:03:15 -0700 (MST) Date: Thu, 26 Oct 2017 11:03:15 -0700 (MST) From: bilbosax To: users@flex.apache.org Message-ID: <1509040995187-0.post@n4.nabble.com> In-Reply-To: References: <1508869190961-0.post@n4.nabble.com> <1508955134178-0.post@n4.nabble.com> <1508969592576-0.post@n4.nabble.com> Subject: Re: Splash Screen Resizing MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable archived-at: Thu, 26 Oct 2017 18:03:21 -0000 In hindsight, yes, it does look obvious, but at the time I didn=E2=80=99t f= ind it intuitive at all. When I googled =E2=80=9CFlex mobile splash screen=E2=80= =9D and things like that, all I found were references to default.png sizes for iOS and how to put the images in your project, or how to include them in ADT commands. Not once did I stumble across any references to the Application level to handle splash screens. Now if I take out the space between splash and screen in th= e google search, bingo, you get your answer, but of course I would have had t= o know the name of the functions to have a clue to do that. It seems obvious in hindsight, but it wasn=E2=80=99t while I was searching. I never just pop= in here and ask a question without spending a large amount of time on the google machine. I wish I were a much better coder than I am, but just kind of picked it up along the way, so it just feels like an exercise in controlled stumbling to me LOL -- Sent from: http://apache-flex-users.2333346.n4.nabble.com/