When the engine resizes the stack, I’m assuming that it takes into account any system furniture? That isn’t a consideration for iOS (at least yet). I’m excluding keyboard for the moment.
I’m not sure why there should be a difference between any platform though. Line 14 put the group’s center 25px above the bottom of the stack which should have put it right on the bottom edge of the screen. The group is 50px tall and the icons are 32px square. I can see them being off left/right side of narrower devices, but if off the bottom that does not seem right. Maybe we should replace the group with a single grc as a test. Also, the top of the group rect should match the bottom of the browser rect. Everything is done by logical px on iOS... is it different on Android? In the end, I guess I need to get an Android device so I can start testing. Thanks, Brian On Aug 19, 2018, 11:05 PM -0500, J. Landman Gay via use-livecode <use-livecode@lists.runrev.com>, wrote: > On 8/19/18 10:21 PM, Brian Milby via use-livecode wrote: > > I'm not sure what the fleet of widths would > > need to be supported on the Android side though. > > They vary all over the place. Basically you need to calculate a ratio > and set all the control sizes accordingly. > > > I can't speak directly to Android, but once you start doing resize > > handlers, I can't see using fullscreenmode. If you are going to position > > anything, may as well position it based on actual device metrics. > > That's kind of what I meant. You either use fullscreenMode or you don't, > but I can see a case for turning it off for a card or two when you want > to use screen metrics only. > > > On iOS, all of the controls within the footer group moved without having to > > touch them individually. > > I think it may be resolution-dependent. Unlike iOS, Android is all over > the map, so when the group moved up (without auto-scaling) on the > Samsung I was using, only the tops of the icons showed. The group's top > margin was disproportionately large and the bottom half of the icons > were still below the stack. On other Android devices you'd get different > results, so you'd need to do all the calculations not just for size but > also for resolution. At least, I think so. I'm not positive any more > because I gave up all that work the moment the engine started doing it > for me. > > -- > Jacqueline Landman Gay | jac...@hyperactivesw.com > HyperActive Software | http://www.hyperactivesw.com > > _______________________________________________ > 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
