flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jed Hatamosa (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLEX-34061) Textinput panning issue
Date Thu, 06 Mar 2014 01:41:47 GMT

    [ https://issues.apache.org/jira/browse/FLEX-34061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13921858#comment-13921858

Jed Hatamosa commented on FLEX-34061:

Hi Maurice,

Sorry for the late reply. Thanks for your time on trying to fix the issue. Im still hoping
that someone can still fix this. 

> Textinput panning issue
> -----------------------
>                 Key: FLEX-34061
>                 URL: https://issues.apache.org/jira/browse/FLEX-34061
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: .Unspecified - Mobile, Spark: TextInput
>    Affects Versions: Apache Flex 4.11.0
>            Reporter: Jed Hatamosa
>            Priority: Minor
>         Attachments: Flickering_Background.MOV, PanWithHeader.png, PanWithoutHeader.png
> I have 2 issues in textinput panning:
> First issue is when the softKeyboardBehavior property in config file is set to "pan".
Using the current sdk 4.11 and using the default skin for textinput pans the whole application
including the header ( Please see image attachment titled PanWithoutHeader.png ). If I'm actually
going to use the old skin which is the "spark.skins.mobile.TextInputSkin" the panning is working
fine (Please see image attachment titled PanWithHeader.png ) but the problem with the old
skin is I couldn't use the softKeyboardType property. Is there any solution on this? 
> Second issue is actually wen I use a third-party keyboard with transparency option, and
the transparency option was set to 50% ( Meaning I can see the behind elements in the keyboard
), there is actually a grayish background that keeps on flickering and it's very annoying
to look at. Please see Flickering_background.mov for the details.
> I really need to have a solution on these issues or other work around solutions since
my client is very anxious to get this fixed. Hope you guys can help me.

This message was sent by Atlassian JIRA

View raw message