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: <D170CE1D.2C5B4%aharui@adobe.com>
References: 
 <CAMLfUsYDnuNYoOfOV+DXW_ip38znSDJH1hLJCh2O-1AyoCvN0A@mail.gmail.com>
 <554B2B27.20109@extravision.com>
 <CAMLfUsZYiu9vvBgc=b47JAW42pOhbXhTeGYTRr+OdiThVt=mnQ@mail.gmail.com>
 <CAMLfUsZJrXwirzA7zpdFcBvwE0krL2N-UaDgO+0dRHKr-KBHdQ@mail.gmail.com>
 <CAMLfUsYWdbCP+1WdjFRPiYwKTiWp8GZHa9+CVhpy86GNKmfsfg@mail.gmail.com>
 <CAMLfUsZ0BisjksxNBh4_MYwyOng=GpeTt-inHLCFqAKj2gGL3Q@mail.gmail.com>
 <CAMLfUsYTi4Lp3ooZhcD0GH6P03c92q5MT3Dx7Aj5LkN3G4iEvQ@mail.gmail.com>
 <D170CE1D.2C5B4%aharui@adobe.com>
From: =?UTF-8?B?SMOpY3RvciBB?= <neverbirth@gmail.com>
Date: Thu, 7 May 2015 18:52:57 +0200
Message-ID: 
 <CAMLfUsZLhQvb7zxKvP0+p5mweeyLaFiT64NpchtyVBYkjA8CZg@mail.gmail.com>
Subject: Re: Layout problem
To: "users@flex.apache.org" <users@flex.apache.org>
Content-Type: multipart/alternative; boundary=047d7b4145d4cc36b6051580c01b

--047d7b4145d4cc36b6051580c01b
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Using the MXML in the original mail:

http://imgbox.com/5JcXcQju

However for some reason, after the width exceeds some value, width=3D50%
seems to stop working, or maybe some maxHeight is reached? and I get this:

http://imgbox.com/Sb6fkDW4

Using a BitmapImage the result is the desired (also, note, that in this
case scaleX and scaleY doesn't make any difference, as width is constrained
by the 50%, and the height seems to be dependent of the height).

http://imgbox.com/TsfJgT57
http://imgbox.com/mobddmWR


On Thu, May 7, 2015 at 5:09 PM, Alex Harui <aharui@adobe.com> wrote:

> Can you post a link to a screenshot of what you are seeing?
>
> -Alex
>
> On 5/7/15, 7:21 AM, "H=C3=A9ctor A" <neverbirth@gmail.com> wrote:
>
> >I've been making some tests on my own. On some of them the number of
> >Images
> >inside each HGroup seemed to affect how the layout was performed, strang=
e.
> >Anyway, I've seen that using BitmapImage instead of Image (with
> >scaleMode=3D"letterbox", of course) gave the desired result, and since t=
his
> >case doesn't require any special loading control nor skin the designer c=
an
> >follow this route, and since BitmapImage performs better, +1 to it, but =
it
> >would be nice to see this behaviour in an Image control.
> >
> >On Thu, May 7, 2015 at 12:35 PM, H=C3=A9ctor A <neverbirth@gmail.com> wr=
ote:
> >
> >> Maybe a -1 could be passed to height or width to simulate "auto".
> >>
> >> On Thu, May 7, 2015 at 12:32 PM, H=C3=A9ctor A <neverbirth@gmail.com> =
wrote:
> >>
> >>> I guess it's this same issue:
> >>>
> >>>
> >>>
> >>>
> http://stackoverflow.com/questions/21132203/flash-spark-image-width-100-
> >>>height-auto
> >>>
> >>> So still no workaround in pure MXML? Seems a bit of a letdown, would =
be
> >>> nice to have and may even be common sense. I'd say we all needed it a=
t
> >>> least once, but I've always resorted to use code.
> >>>
> >>> On Thu, May 7, 2015 at 11:25 AM, H=C3=A9ctor A <neverbirth@gmail.com>
> wrote:
> >>>
> >>>> Sorry, 320/160DPI. Anyway, that's not the issue, and it's seemingly
> >>>> working as expected.
> >>>>
> >>>> On Thu, May 7, 2015 at 11:18 AM, H=C3=A9ctor A <neverbirth@gmail.com=
>
> >>>>wrote:
> >>>>
> >>>>> It also seemed strange to me. It's because of DPIs, the images were
> >>>>> done for 360DPI, targetting 180DPI.
> >>>>>
> >>>>> On Thu, May 7, 2015 at 11:06 AM, Tom Chiverton <tc@extravision.com>
> >>>>> wrote:
> >>>>>
> >>>>>>
> >>>>>> On 07/05/15 10:01, H=C3=A9ctor A wrote:
> >>>>>>
> >>>>>>> scaleX=3D"0.5" scaleY=3D"0.5" smooth=3D"true" width=3D"50%"
> >>>>>>>
> >>>>>>
> >>>>>> What's the reasoning behind giving a scale factor for both axis as
> >>>>>> well as a width and expecting the height to adjust ?
> >>>>>>
> >>>>>> Tom
> >>>>>>
> >>>>>
> >>>>>
> >>>>
> >>>
> >>
>
>

--047d7b4145d4cc36b6051580c01b--