Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (nike.apache.org: domain of maxw@google.com designates
 209.85.128.52 as permitted sender)
MIME-Version: 1.0
Sender: maxw@google.com
In-Reply-To: <6B57DE16-4DF4-4AF3-947E-20E6AD86AD4B@gmail.com>
References: <521DDBC6.2060509@johnwargo.com>
 <6B57DE16-4DF4-4AF3-947E-20E6AD86AD4B@gmail.com>
From: Max Woghiren <maxw@chromium.org>
Date: Wed, 28 Aug 2013 10:14:18 -0400
Message-ID: 
 <CAAzFgyiqiDg23oN7LMb=s99Bv0vHXT3GDqVhv2ng3+QdpvDAqg@mail.gmail.com>
Subject: Re: Camera API
To: dev <dev@cordova.apache.org>
Content-Type: multipart/alternative; boundary=001a11332adabb20a904e5029c7c

--001a11332adabb20a904e5029c7c
Content-Type: text/plain; charset=ISO-8859-1

I would expect, if anything, that specifying only one of the two dimensions
would be desired.  I'm guessing one overrides the other if both are
specified but don't conform to the aspect ratio; that should probably be in
the docs.


On Wed, Aug 28, 2013 at 10:04 AM, James Jong <wjamesjong@gmail.com> wrote:

> You're right that it could be calculated based on one or the other.  The
> code expects both today.  I think the point is to be clear that the aspect
> ratio is maintained, so that the user does not expect to be able to
> arbitrarily set both.
>
> -James Jong
>
> On Aug 28, 2013, at 7:15 AM, John Wargo <john@johnwargo.com> wrote:
>
> > I've got another silly question. In looking at the Camera API, I see the
> following:
> >
> > targetWidth: Width in pixels to scale image. Must be used with
> targetHeight. Aspect ratio remains constant. (Number)
> >
> > targetHeight: Height in pixels to scale image. Must be used with
> targetWidth. Aspect ratio remains constant. (Number)
> >
> > I'm not getting why targetWidth MUST be used with targetHeight (and visa
> versa) when aspect ratio remains constant. If aspect ratio remains
> constant, then setting one automatically forces the other - that's the
> whole point of maintaining aspect ratio, right? If the API is maintaining
> aspect ratio while sizing the image, then forcing the developer to specify
> both parameters is simply wasted work.
> >
> > What am I missing here?
>
>

--001a11332adabb20a904e5029c7c--