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 54173200BAF for ; Mon, 17 Oct 2016 06:51:28 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 52BBC160AF8; Mon, 17 Oct 2016 04:51:28 +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 98F87160AD0 for ; Mon, 17 Oct 2016 06:51:27 +0200 (CEST) Received: (qmail 47143 invoked by uid 500); 17 Oct 2016 04:51:26 -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 47128 invoked by uid 99); 17 Oct 2016 04:51:26 -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; Mon, 17 Oct 2016 04:51:26 +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 C48341A01F8 for ; Mon, 17 Oct 2016 04:51:25 +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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NEUTRAL=0.652, 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 ReDq7i-F32Ep for ; Mon, 17 Oct 2016 04:51:24 +0000 (UTC) Received: from mwork.nabble.com (mwork.nabble.com [162.253.133.43]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 51A2B5FB39 for ; Mon, 17 Oct 2016 04:51:23 +0000 (UTC) Received: from mjoe.nabble.com (unknown [162.253.133.57]) by mwork.nabble.com (Postfix) with ESMTP id AD6085BD6278B for ; Sun, 16 Oct 2016 21:51:16 -0700 (MST) Date: Sun, 16 Oct 2016 21:43:38 -0700 (PDT) From: bilbosax To: users@flex.apache.org Message-ID: <1476679418973-13813.post@n4.nabble.com> Subject: Mobile Width and Height MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Mon, 17 Oct 2016 04:51:28 -0000 I have written my first mobile AIR app. On my iPad, the layout is a dismal failure. It looks perfect in the simulator. I have the application set up to run in portrait mode with no auto-orientation. It starts at 160 DPI and scales up. When the application is complete, I get the width and height of the stage, and then use these numbers to calculate the layout of all of my buttons and column widths for my datagrid. On the iPad, all of the buttons are spread way too far apart, several running off the screen. The datagrid is all supposed to fit on the screen but four of the colums ran off the screen. It is almost as if it calculated the width of the screen in landscape mode instead of in portrait mode. So I have two questions: 1) If you layout the application in portrait orientation, is the width of the stage the width in portrait orientation or landscape orientation? 2) I am confused on how to lay everything out on mobile devices with varying screen densities. Is it better to get the app width and height and then set up distances and spacing in pixels, or to use percentages? Thanks for any insight. This was disappointing. -- View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Mobile-Width-and-Height-tp13813.html Sent from the Apache Flex Users mailing list archive at Nabble.com.