You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flex.apache.org by "Maurice Amsellem (JIRA)" <ji...@apache.org> on 2014/03/20 11:01:47 UTC
[jira] [Commented] (FLEX-34176) TextInput problem in a scaled group
[ https://issues.apache.org/jira/browse/FLEX-34176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13941573#comment-13941573 ]
Maurice Amsellem commented on FLEX-34176:
-----------------------------------------
thanks for reporting
> TextInput problem in a scaled group
> -----------------------------------
>
> Key: FLEX-34176
> URL: https://issues.apache.org/jira/browse/FLEX-34176
> Project: Apache Flex
> Issue Type: Bug
> Components: Spark: TextInput
> Affects Versions: Apache Flex 4.12.0
> Environment: Mobile
> Reporter: Ori Segal
> Assignee: Maurice Amsellem
> Priority: Critical
>
> While using version 4.12 mobile we encountered two issues related to TextInput component when it is included in a scaled Group -
>
> 1. The text is not scaled and appears cut in side the TextInput.
> <s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
> xmlns:s="library://ns.adobe.com/flex/spark" applicationDPI="160">
>
> <s:Group width="100%" height="50%" scaleX="0.5" scaleY="0.5">
> <s:TextInput layoutDirection="rtl" />
>
> <s:TextInput layoutDirection="ltr" top="100" />
> </s:Group>
>
> </s:Application>
> Here is a video that shows the issue:
> http://screencast.com/t/gyAnB6iDl0Gg
>
> 2. When the scaled Group is set with layoutDirection "rtl" the internal components disappear.
>
> <?xml version="1.0" encoding="utf-8"?>
> <s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
> xmlns:s="library://ns.adobe.com/flex/spark" applicationDPI="160">
>
> <s:Group width="100%" height="50%" scaleX="0.5" scaleY="0.5" layoutDirection="rtl">
> <s:TextInput layoutDirection="rtl" />
>
> <s:TextInput layoutDirection="ltr" top="100" />
> </s:Group>
>
> </s:Application>
> it happens also when scaling the entire application without using applicationDPI.
> The use case is mainly for low-resolution Android devices where we need to scale only an area that includes a form (otherwise the keyboard covers it) and not the rest of the application.
--
This message was sent by Atlassian JIRA
(v6.2#6252)