Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 8 of 8 total
Thread TEdit + Mobile (Android) + Chrome + VirtualKB
Thu, Jul 30 2015 1:53 PMPermanent Link

Malcolm Taylor

Having recreated in EWB2 a trivial EWB1 project, I noticed a different
behaviour with the VKbd.

With my EWB1 version, when I tap on a TEdit lower down the viewport,
the VKbd pops up and the form scrolls up enough for the TEdit to remain
in view.

Not so with my EWB2 version.  At first I though there was no scroll at
all so I searched the Help to see if I had made a bad choice of
Form.Layout or something but found nothing.  I then tried again with
different settings - and discovered that it does scroll, but only after
the first character is tapped on the VKbd.

So it does 'work', but it is a little disconcerting when the user
cannot see the active TEdit until after starting data entry.

Does anyone else see this, or is it just me?  I see it (with my little
app) in Chrome on both a 4.9-inch mobile and a 7-inch tablet.
Fri, Jul 31 2015 6:37 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Malcolm,

<< Not so with my EWB2 version.  At first I though there was no scroll at all so I searched the Help to see if I had made a bad choice of Form.Layout or something but found nothing.  I then tried again with different settings - and discovered that it does scroll, but only after the first character is tapped on the VKbd. >>

I'm having a hard time picturing what you're describing.  How are you tapping on a TEdit if it's beyond the visible client area and requires scrolling to get to it ?

Tim Young
Elevate Software
www.elevatesoft.com
Fri, Jul 31 2015 6:38 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Malcolm,

Never mind, got it now - you're saying that the keyboard causes the scrolling.  Got it.  I'll have to test this and see what the issue is.

Tim Young
Elevate Software
www.elevatesoft.com
Fri, Jul 31 2015 7:11 AMPermanent Link

Malcolm Taylor

Tim Young [Elevate Software] wrote:

> Never mind, got it now - you're saying that the keyboard causes the
> scrolling.  Got it.  I'll have to test this and see what the issue is.

Yes, user sees TEdit, taps on it, then the VKb pops up and obscures it
... until the user begins input.
EWB1 did not show that .. the form was scrolled up enough to keep the
TEdit visible as the VKb popped up so the user could still see it prior
to beginning input.
Fri, Jul 31 2015 7:22 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Malcolm,

<< Yes, user sees TEdit, taps on it, then the VKb pops up and obscures it.. until the user begins input.
EWB1 did not show that .. the form was scrolled up enough to keep the TEdit visible as the VKb popped up so the user could still see it prior to beginning input. >>

EWB1 always "auto-focused" controls, which isn't ideal for touch environments with virtual keyboards that automatically pop up.  EWB2's TApplication class has an AutoFocus property that is set to False, by default, in Android and iOS environments.  You can set it to True to re-enable the auto-focusing.  However, as I said, I wouldn't recommend it.

Tim Young
Elevate Software
www.elevatesoft.com
Fri, Jul 31 2015 7:38 AMPermanent Link

Malcolm Taylor

Tim Young [Elevate Software] wrote:

>
> EWB1 always "auto-focused" controls, which isn't ideal for touch
> environments with virtual keyboards that automatically pop up.
> EWB2's TApplication class has an AutoFocus property that is set to
> False, by default, in Android and iOS environments.  You can set it
> to True to re-enable the auto-focusing.  However, as I said, I
> wouldn't recommend it.
>

OK, thanks for the explanation.  I will have a little play to see how
it behaves, if I can work out how to detect the environment, .. but you
are usually right.  ;o)

Malcolm
Fri, Jul 31 2015 8:05 AMPermanent Link

Chris Holland

SEC Solutions Ltd.

Avatar

Team Elevate Team Elevate

There are a couple of variables in TApplication called IsIOS and
IsAndroid which you can use to detect the environment.

Chris Holland
[Team Elevate]

On 31/07/2015 12:38, Malcolm wrote:
> Tim Young [Elevate Software] wrote:
>
>>
>> EWB1 always "auto-focused" controls, which isn't ideal for touch
>> environments with virtual keyboards that automatically pop up.
>> EWB2's TApplication class has an AutoFocus property that is set to
>> False, by default, in Android and iOS environments.  You can set it
>> to True to re-enable the auto-focusing.  However, as I said, I
>> wouldn't recommend it.
>>
>
> OK, thanks for the explanation.  I will have a little play to see how
> it behaves, if I can work out how to detect the environment, .. but you
> are usually right.  ;o)
>
> Malcolm
>
Fri, Jul 31 2015 9:16 AMPermanent Link

Malcolm Taylor

Chris Holland wrote:

> There are a couple of variables in TApplication called IsIOS and
> IsAndroid which you can use to detect the environment.
>
Thanks Chris.  Surprised
Image