Mailing-List: contact users-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@flex.apache.org
MIME-Version: 1.0
In-Reply-To: <CAL2pvOc1XwrYq_QWuSSTQ_nWB+gTYKPH5FBmFQd1-5sBcuSfMQ@mail.gmail.com>
References: <CAL2pvOc1XwrYq_QWuSSTQ_nWB+gTYKPH5FBmFQd1-5sBcuSfMQ@mail.gmail.com>
From: Josh Tynjala <joshtynjala@gmail.com>
Date: Wed, 29 Mar 2017 11:49:22 -0600
Message-ID: <CADZSWG73rKYHyHFbtyv9b2bPsVdRkC7UWXDqdQ=385LHB1rO4A@mail.gmail.com>
Subject: Re: More Issues With TextInput on Flex 4.16 AIR 25
To: users@flex.apache.org
Content-Type: multipart/alternative; boundary=001a11445708b67ddd054be234ba
archived-at: Wed, 29 Mar 2017 17:50:09 -0000

--001a11445708b67ddd054be234ba
Content-Type: text/plain; charset=UTF-8

It's been my experience that flash.text.StageText has multiple issues with
AIR 25.0.0.134. I believe that the Flex TextInput uses StageText on mobile,
so you may be running into these bugs.

It looks like there's a new AIR 25 beta on Adobe Labs today, so I think
they're planning to release an update to AIR 25 soon. I see in the release
notes that some StageText issues have been fixed. You might try using that
build instead of the released version.

Since a stable build of AIR 25 has been released, you may not see a beta
build in the Flex SDK Installer anymore. You can overlay the beta AIR SDK
over the Flex SDK manually using these instructions:

https://helpx.adobe.com/x-productkb/multi/how-overlay-air-sdk-flex-sdk.html

- Josh

On Wed, Mar 29, 2017 at 11:04 AM, Paul Moreau <paul.moreau@zutec.com> wrote:

> Hi folks,
>
> I'd normally go to StackOverflow but I usually find that Flex issues
> posted are normally met with tumbleweed...
>
> I have included an mxml view file if anybody wants to replicate. I tried
> to include the entire project but the zipped file was too large.
>
> *Issue :* Text not visible on TextInput until user focuses on another
> component.
>
> *Steps to replicate :*
> *( using Flex 4.16 AIR 25  running on an iOS device  , not an emulator )*
>
> Create a TextInput  ( use the default skin )
> Navigate to another view
> Pop back to original view
> Click on TextInput
> Type value ( no text appears , caret also not visible )
> Click off TextInput ( text appears )
>
> I am using 'DestructionPolicy = never' as I need the user to be able to go
> to a new form on the fly and then pop back to the main form without losing
> the data or the scroll position.
>
> I've noticed on iOS 10.0+ , an undo/redo popup appears after pressing
> back...
>
> Any ideas?
>
> Thanks,
>
> --
>
>
>
>
>
>
> *DISCLAIMER: This electronic message together with any attachments is
> confidential. If you are not the intended recipient, do not copy, disclose
> or use the contents in any way. Please also advise us by return e-mail that
> you have received the message and then please destroy. Zutec  Ltd is not
> responsible for any changes made to this message and / or any attachments
> after sending by Zutec. We use virus scanning software but exclude all
> liability for viruses or anything similar in this email or any attachment.*
>

--001a11445708b67ddd054be234ba--