Mailing-List: contact issues-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flex.apache.org
Date: Sun, 22 Sep 2013 23:15:02 +0000 (UTC)
From: =?utf-8?Q?B=C3=A9renger_=28JIRA=29?= <jira@apache.org>
To: issues@flex.apache.org
Message-ID: <JIRA.12669939.1379891270644.260.1379891702785@arcas>
In-Reply-To: <JIRA.12669939.1379891270644@arcas>
References: <JIRA.12669939.1379891270644@arcas>
Subject: [jira] [Updated] (FLEX-33750) Callout' "middle" position problem
 with layoutDirection set to rtl
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/FLEX-33750?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

B=C3=A9renger updated FLEX-33750:
----------------------------

    Attachment: Callout Test.fxp

Sample project
               =20
> Callout' "middle" position problem with layoutDirection set to rtl
> ------------------------------------------------------------------
>
>                 Key: FLEX-33750
>                 URL: https://issues.apache.org/jira/browse/FLEX-33750
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: Spark: CalloutButton, Spark: Layout
>    Affects Versions: Apache Flex 4.10.0
>         Environment: Windows - Firefox - Flash Player 11.8
>            Reporter: B=C3=A9renger
>            Priority: Minor
>         Attachments: Callout problem 2.png, Callout Test.fxp
>
>
> When an component (i.e. Button) is in a layout where the layoutDirection =
is right-to-left and when this component calls a CallOut with the positions=
 set to "middle", this CallOut is not well positionned.
> Step to reproduce:
> 1/ define a Callout with horizontalPosition=3D"middle" and verticalPositi=
on=3D"middle"
> 2/ define a HGroup with layoutDirection=3D"rtf"
> 3/ inside, define a Spacer to highlight the problem
> 4/ following, define a Button with call the Callout

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira