On 31/07/2012, at 05:39 PM, Monte Goulding wrote: > I tend to agree. I can't help wondering if the first card could be scaled and > then kick off some non blocking process to do other cards.
If your 'main' stack was an external stack that was loaded at runtime, the first time the app ran you could do a blanket resize (if necessary) of objects and controls so that they at least matched the required pixel density and device form factor (e.g. std phone, HD tablet) and then save the stack. The next time the app was opened all? you'd have to worry about was handling the orientation changes. Terry... > > -- > M E R Goulding > Software development services > > mergExt - There's an external for that! > > On 31/07/2012, at 5:30 PM, Chipp Walters <ch...@chipp.com> wrote: > >> I vote for scale on launch. Just too much work building multiple interfaces >> for each screensize. The tool should allow for "setting" the control size >> and position based on density and/or pixel resolution. >> >> >> >> -- >> Chipp Walters >> CEO, Altuit, Inc. >> _______________________________________________ >> use-livecode mailing list >> use-livecode@lists.runrev.com >> Please visit this url to subscribe, unsubscribe and manage your subscription >> preferences: >> http://lists.runrev.com/mailman/listinfo/use-livecode > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > Dr Terry Judd Senior Lecturer in Medical Education Medical Eduction Unit Faculty of Medicine, Dentistry & Health Sciences The University of Melbourne _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
