Hmmm - this message has been sitting in my outbound mail queue for 2 or
3 days - sorry for the late reply.
Thanks Neil (and everyone else who replied). This has been a great help.
Monte's right - this would be a great example for a community effort (if
his efforts on the engine forum don't lead to a better solution).
-- Alex.
On 03/05/2013 10:36, n...@runrev.com wrote:
Hi Alex,
I believe the issue you are experiencing is due to the way the kindle fire
handles it orientations.
To rectify this, you will need to create a config file that informs your
application of the correct orientations. More information on this can be
found on page 28 of the Android Release notes under "Device Specific
Orientations"
Kind Regards,
Neil Roger
--
RunRev Support Team ~ http://www.runrev.com
--
I'm just starting to play with Mobile builds - so this could be the
first of a series of dumb questions :-)
I build a stack (one button, one field, no script at all), and build for
Android (following the instructions from Colin's book).
The "Initial orientation" is set to "portrait".
I can't get any Virtual Devices to run - but I can download and test on
my Kindle Fire.
- builds, loads and runs (i.e. does nothing :-) OK
Rotating the device does nothing (i.e. the button/field) remain fixed
relative to the device, and hence they also become sideways /
upside-down / sideways again / OK again.
If I then add
on preopencard
mobileSetAllowedOrientations "portrait,portrait upside
down,landscape left,landscape right"
end preopencard
to the card script, then rotating the device causes the button/field to
re-orient themselves relative to the device, i.e. so that they are in
constant "proper" orientation. BUT - in landscape mode, the button/field
are upside down ! They're OK (i.e. right way up) in portrait and
"portrait upside down" states, but in landscape the controls (and the
status bar which shows the Kindle name + time + wifi/battery status) are
upside down.
What should I do ?
Could someone donate a working, multi-orientation stack so I can test it
(just in case it's something about Kindle Fire, or even some specific
fault with my particular Kindle Fire device) ?
Thanks for any suggestions ...
-- Alex.
_______________________________________________
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
_______________________________________________
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
