That was my experience too… until LC added native support for other Android
processors. Now I find the Android emulator to be very usable!
—
Scott Morrow
Elementary Software
(Now with 20% less chalk dust!)
web https://elementarysoftware.com/
email sc...@elementarysoftware.com
booth
that automatically instantiate mobile
scrollers by examining controls on preOpenCard and setting up the
scrollers as needed.
I do not know why this is impossible for the engine to do, but it's easy
enough to work around in a script.
--
Richard Gaskin
Fourth World Systems
Mobile Wondering
On 4/6/20 10:12 AM, Alex Tweedly via use-livecode wrote:
But, afaik, it's not just scrolling fields; aren't there also issues with keyboard input
requiring you to scroll / move the field to remain visible,
That was fixed recently with mobileSetKeyboardDisplay.
Also, besides mouse events
I had been wondering when the third-class status of mobile platforms in the LC
world, particularly in relation to scrolling fields and groups, would crop up
here.
Some time ago I looked at converting an iOS project to LC, and was appalled at
the crude 1984-style appearance of scroll bars. I
Alex Tweedly wrote:
> On 06/04/2020 03:55, scott--- via use-livecode wrote:
>>> 1. xTalk features just don't work, or work totally inadequately
>>> (e.g. scrolling fields).
>> I feel this is overly harsh. Livecode fields (and the creation of
>> native UIText fields) do work on mobile. I think
On 06/04/2020 03:55, scott--- via use-livecode wrote:
1. xTalk features just don't work, or work totally inadequately (e.g. scrolling
fields).
I feel this is overly harsh. Livecode fields (and the creation of native UIText
fields) do work on mobile. I think the issue is that the use of some
> 1. xTalk features just don't work, or work totally inadequately (e.g.
> scrolling fields).
I feel this is overly harsh. Livecode fields (and the creation of native UIText
fields) do work on mobile. I think the issue is that the use of some objects
(like fields) on mobile is not as drag ’n'
