Post
by jacque » Sun May 07, 2017 9:22 pm
I'm not sure what happened the first time, but I was able to run your stack today. It's behaving as I'd expect.
The measurement in the "button loc" field isn't really reporting the location, it is reporting the left and right edges of the test button, so what you say is the "top" is actually the left. The right edge is at 106 after repositioning. The actual location of the button (its center, which the stack doesn't measure anywhere) after moving it is 60,55. The topleft of the button after moving is 14,14. All these measurements match in either environment.
When using fullscreeMode "showAll", any areas outside the card rect are visible. Because of the off-card visual areas, what appears to be very far from the top of the screen in portrait mode is still actually 14 pixels in from the top edge of the card rectangle. It is possible to set the position to a negative number which will put the button outside the card area, but there are some disadvantages to this: LC will not always redraw areas outside the card, so if you navigate to another card, remnants of the previous card will remain onscreen, even if the button doesn't really exist on the new card. There are ways to script around this, but it's usually better to rethink the stack design so that natural scaling looks okay in any orientation on any device. I frequently just set the backcolor of the stack to a compatible, and sometimes contrasting, color so that a natural border appears around the actual card rectangle. If you do that in your test stack, you'll see how the measurements are accurate relative to the card.
Edit: You can also see what's going on more clearly if you set the fullscreenMode to "letterbox".
Jacqueline Landman Gay | jacque at hyperactivesw dot com
HyperActive Software | http://www.hyperactivesw.com