You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@flex.apache.org by Steve Lewis <sl...@yahoo.com> on 2013/04/19 17:16:42 UTC
TextInput Control
Hi,
We just deployed a Flex (4.9.1) AIR (3.4) mobile app nationwide and the
response has been very positive. Really appreciate everyone's hard work to
keep the Flex platform moving forward. The biggest issue we are dealing
with from users is not being able to fire the numeric keyboard directly.
They have to switch to it from the default keyboard. We are using
spark.skins.mobile.TextInputSkin. I realize you lose keyboard control when
this skin is used, however, when I remove it the scrolling issue surfaces -
(numeric keyboard shows when skin is removed). I have been following this
issue for a while and was wondering if any solutions are available or plans
to fix in future?
Thanks
Steve
RE: TextInput Control
Posted by Steve Lewis <sl...@yahoo.com>.
Thanks for the responses. Doesn't sound real promising. Is the numeric
keyboard that much different than the default - other than having less
chars? I think a custom component might be the best route. Just want to
display numbers 1 thru 9. Pretty sure there is a way to intercept the call
to the default keyboard and call something else...hopefully. Anyway, thanks
for the help.
-----Original Message-----
From: Alex Harui [mailto:aharui@adobe.com]
Sent: Friday, April 19, 2013 3:00 PM
To: users@flex.apache.org
Subject: Re: TextInput Control
Scrolling of StageText is mostly a runtime issue. There are no clipping
APIs so if your user stops the scroll at certain points in a screen that
isn't full screen, it won't look good. Also, the StageText lags behind when
scrolling.
If you willing to live with those 'artifacts', we could add code to the SDK
to try to move the StageTexts as you scroll.
However, I have to add that if you use the new FlexJS framework to build an
mobile app published via Cordova/PhoneGap, I think you won't have these
issues.
On 4/19/13 11:38 AM, "jude" <fl...@gmail.com> wrote:
> I ran into the scroller issue as well. It needs to get fixed in the
> SDK but the mobile skins are much more complex than the Spark. I
> couldn't find a way to fix it in the skin in the time I had. I do have
> a workaround to fix the scroller issue in the control,
> http://goo.gl/X9MuS. YMMV. Then you can set the soft keyboard type,
softKeyboardType="number".
>
> On Fri, Apr 19, 2013 at 10:16 AM, Steve Lewis
<sl...@yahoo.com>wrote:
>
>> Hi,
>>
>>
>>
>> We just deployed a Flex (4.9.1) AIR (3.4) mobile app nationwide and
>> the response has been very positive. Really appreciate everyone's
>> hard work to keep the Flex platform moving forward. The biggest
>> issue we are dealing with from users is not being able to fire the
numeric keyboard directly.
>> They have to switch to it from the default keyboard. We are using
>> spark.skins.mobile.TextInputSkin. I realize you lose keyboard
>> control when this skin is used, however, when I remove it the
>> scrolling issue surfaces - (numeric keyboard shows when skin is
>> removed). I have been following this issue for a while and was
>> wondering if any solutions are available or plans to fix in future?
>>
>>
>>
>> Thanks
>>
>>
>>
>> Steve
>>
>>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: TextInput Control
Posted by Alex Harui <ah...@adobe.com>.
Scrolling of StageText is mostly a runtime issue. There are no clipping
APIs so if your user stops the scroll at certain points in a screen that
isn't full screen, it won't look good. Also, the StageText lags behind when
scrolling.
If you willing to live with those 'artifacts', we could add code to the SDK
to try to move the StageTexts as you scroll.
However, I have to add that if you use the new FlexJS framework to build an
mobile app published via Cordova/PhoneGap, I think you won't have these
issues.
On 4/19/13 11:38 AM, "jude" <fl...@gmail.com> wrote:
> I ran into the scroller issue as well. It needs to get fixed in the SDK but
> the mobile skins are much more complex than the Spark. I couldn't find a
> way to fix it in the skin in the time I had. I do have a workaround to fix
> the scroller issue in the control, http://goo.gl/X9MuS. YMMV. Then you can
> set the soft keyboard type, softKeyboardType="number".
>
> On Fri, Apr 19, 2013 at 10:16 AM, Steve Lewis <sl...@yahoo.com>wrote:
>
>> Hi,
>>
>>
>>
>> We just deployed a Flex (4.9.1) AIR (3.4) mobile app nationwide and the
>> response has been very positive. Really appreciate everyone's hard work to
>> keep the Flex platform moving forward. The biggest issue we are dealing
>> with from users is not being able to fire the numeric keyboard directly.
>> They have to switch to it from the default keyboard. We are using
>> spark.skins.mobile.TextInputSkin. I realize you lose keyboard control when
>> this skin is used, however, when I remove it the scrolling issue surfaces -
>> (numeric keyboard shows when skin is removed). I have been following this
>> issue for a while and was wondering if any solutions are available or plans
>> to fix in future?
>>
>>
>>
>> Thanks
>>
>>
>>
>> Steve
>>
>>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: TextInput Control
Posted by jude <fl...@gmail.com>.
I ran into the scroller issue as well. It needs to get fixed in the SDK but
the mobile skins are much more complex than the Spark. I couldn't find a
way to fix it in the skin in the time I had. I do have a workaround to fix
the scroller issue in the control, http://goo.gl/X9MuS. YMMV. Then you can
set the soft keyboard type, softKeyboardType="number".
On Fri, Apr 19, 2013 at 10:16 AM, Steve Lewis <sl...@yahoo.com>wrote:
> Hi,
>
>
>
> We just deployed a Flex (4.9.1) AIR (3.4) mobile app nationwide and the
> response has been very positive. Really appreciate everyone's hard work to
> keep the Flex platform moving forward. The biggest issue we are dealing
> with from users is not being able to fire the numeric keyboard directly.
> They have to switch to it from the default keyboard. We are using
> spark.skins.mobile.TextInputSkin. I realize you lose keyboard control when
> this skin is used, however, when I remove it the scrolling issue surfaces -
> (numeric keyboard shows when skin is removed). I have been following this
> issue for a while and was wondering if any solutions are available or plans
> to fix in future?
>
>
>
> Thanks
>
>
>
> Steve
>
>
Re: TextInput Control
Posted by "Lionel A. Pierre" <li...@medez.com>.
Just my 2 cents on this one...
This is a very visible issue. Flex could gain a lot by having it addressed.
I've had to sacrifice the numeric keyboard functionality in a large mobile
app also because of it.
Users do notice that.
*Lionel A. Pierre*