Don’t know, you should test it. According to the help it returns the screenrect after removing things like the keyboard overlay. But that may still be in virtual pixels, based on the card rect.
> On Jan 4, 2016, at 8:55 PM, Sannyasin Brahmanathaswami <bra...@hindu.org> > wrote: > > Seems better to let Livecode do the job… which means working in iPad size > even though your main target is phones. Odd, but that would work for controls > that are meant to stay top and bottom. > > OTHO I don’t understand how it is that “tricky”… doesn’t the screen rect > solve this for any device? > > on preOpenCard > put the effective screenrect into tRect > set the bottom of group “tabBar” to item 4 of tRect > end preOpenCard > > > > > > > > On January 4, 2016 at 3:12:46 PM, Colin Holgate > (colinholg...@gmail.com<mailto:colinholg...@gmail.com>) wrote: > > Which you choose is often dependent on whether you have tools that stick to > the top and bottom, or the sides. If you do use code to make them snap into > place, it can be tricky. You need to find the real width and height of the > device itself, divide one into the other, and use that as a multiplier > against your card size to know how far from the center the controls should be > placed. If you’re only doing current iOS devices you could make assumptions > about it being 16:9 or 4:3, but that might not always be the case, and it > wouldn’t be correct for most Android devices. > _______________________________________________ > 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
