Return-Path: X-Original-To: apmail-cordova-dev-archive@www.apache.org Delivered-To: apmail-cordova-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 33BCE105B4 for ; Thu, 5 Dec 2013 15:42:59 +0000 (UTC) Received: (qmail 13207 invoked by uid 500); 5 Dec 2013 15:42:58 -0000 Delivered-To: apmail-cordova-dev-archive@cordova.apache.org Received: (qmail 13113 invoked by uid 500); 5 Dec 2013 15:42:55 -0000 Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cordova.apache.org Delivered-To: mailing list dev@cordova.apache.org Received: (qmail 12667 invoked by uid 99); 5 Dec 2013 15:42:53 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Dec 2013 15:42:53 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jwargo23@gmail.com designates 209.85.213.53 as permitted sender) Received: from [209.85.213.53] (HELO mail-yh0-f53.google.com) (209.85.213.53) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Dec 2013 15:42:49 +0000 Received: by mail-yh0-f53.google.com with SMTP id b20so12737323yha.12 for ; Thu, 05 Dec 2013 07:42:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; bh=/uwOZM2hBKYvCnkvsd6xRUPiUlI2rSeyv0X25NiIkOY=; b=WXwEfT+MwcyJBlSEReRT62YxlOc+ELUACsudgyueLH1tLmudDgBwtKeofbllrmKnin LyWkyxcCsiOsKxXgAymj1aPG4bqV8vg/nXVOD/dasbMukDGfWcSJBd6blIP0/ktG5VSm dd+jUnpUZuEqoEWUcGtrp8nt5CsxIRTvZMdmSbTULSBpbCSdRk6j5ehU6PLCwMQ0TJEk mhsVWIwlOH7fXb478KN9BxotQ4QaAiC0Zj6RdEH5Qg7FbcZKFskp5donZDXsk+TOd6Fa 5zuBrTjwsRjZ++skUcxn+9USJH85EvQHOZU7eG6WHtTMq5U8aXxUKiwK58gmGkpEvsK2 n/ng== X-Received: by 10.236.0.193 with SMTP id 41mr321498yhb.82.1386258148759; Thu, 05 Dec 2013 07:42:28 -0800 (PST) Received: from [127.0.0.1] (h139.141.188.173.dynamic.ip.windstream.net. [173.188.141.139]) by mx.google.com with ESMTPSA id c44sm58477353yho.20.2013.12.05.07.42.26 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 05 Dec 2013 07:42:27 -0800 (PST) Message-ID: <52A09ED4.9050907@gmail.com> Date: Thu, 05 Dec 2013 10:42:12 -0500 From: "John M. Wargo" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: dev@cordova.apache.org Subject: Re: Camera API: correctOrientation References: <20131205012550.24461460.45883.6711@blackberry.com> <529FDE0D.7000508@gmail.com> <52A08974.4070608@gmail.com> In-Reply-To: Content-Type: multipart/alternative; boundary="------------090303020008010700030803" X-Virus-Checked: Checked by ClamAV on apache.org --------------090303020008010700030803 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit That makes sense. As I only have this iOS 7 device, can someone do a quick test on an older version of the OS? On 12/5/2013 9:51 AM, Andrew Grieve wrote: > One explanation is that the iOS camera now always rotates the image for you? > > > On Thu, Dec 5, 2013 at 9:11 AM, John M. Wargo wrote: > >> Jesse, >> >> I've been thinking about what you said and I'm not getting it. I created >> an app that has three buttons, one takes a picture without >> correctOrientation even defined, another sets correctOrientation to true >> while the last one sets correctOrientation to false. >> >> When I look at the photos on my Mac or in Windows Explorer, all three >> photos have the same orientation. >> >> When I look at the EXIF properties in an EXIF editor, all three photos >> have orientation set the same value. The editor says its 0, but the field >> seems to be a two byte value which contains 00 01. >> >> Since I'm comparing three photos at the same time, one of them should be >> turned on its side (the one where correctOrientation is true) while the >> other two are displayed in portrait orientation. That's expected behavior >> based on what you say below, but that's not what's happening for me. >> >> I'm still leaning toward this particular option being broken. >> >> >> On 12/4/2013 9:04 PM, Jesse wrote: >> >>> It definitely does something, you just may not notice it. >>> If you try to display an image you took in your app on iOS in any image >>> viewer that does not correctly interpret exif, then the picture will still >>> display correctly. >>> If you remove the code, it will not. >>> >>> @purplecabbage >>> risingj.com >>> >>> >>> On Wed, Dec 4, 2013 at 5:59 PM, John M. Wargo wrote: >>> >>> I can't get it to do anything on iOS, so I think it's broken. >>>> Any chance someone can do a quick test to confirm my suspicion? Probably >>>> need to remove it from the docs if it doesn't do anything. >>>> >>>> >>>> On 12/4/2013 8:41 PM, Jesse wrote: >>>> >>>> It appears to do nothing, except on iOS. >>>>> It is listed as supported on iOS and Android, and back in 1.7, it was >>>>> iOS >>>>> only, >>>>> >>>>> Android does this: >>>>> this.correctOrientation = args.getBoolean(8); >>>>> >>>>> iOS uses it after the image is captured, and calls >>>>> imageCorrectedForCaptureOrientation >>>>> [1] which rotates it according to the orientation of the camera when the >>>>> picture was taken. >>>>> >>>>> >>>>> [1] >>>>> https://github.com/apache/cordova-plugin-camera/blob/ >>>>> master/src/ios/CDVCamera.m#L455 >>>>> >>>>> >>>>> @purplecabbage >>>>> risingj.com >>>>> >>>>> >>>>> On Wed, Dec 4, 2013 at 5:25 PM, Josh Soref >>>>> wrote: >>>>> >>>>> John wrote: >>>>> >>>>>> Can someone explain to me what correctOrientation is supposed to do? >>>>>>> http://docs.phonegap.com/en/1.7.0/cordova_camera_camera.md.html >>>>>> Lists a bunch of platforms that don't implement it. >>>>>> >>>>>> My guess is that some older platforms wouldn't automatically switch >>>>>> between portrait and landscape orientations for photos. >>>>>> --------------------------------------------------------------------- >>>>>> This transmission (including any attachments) may contain confidential >>>>>> information, privileged material (including material protected by the >>>>>> solicitor-client or other applicable privileges), or constitute >>>>>> non-public >>>>>> information. Any use of this information by anyone other than the >>>>>> intended >>>>>> recipient is prohibited. If you have received this transmission in >>>>>> error, >>>>>> please immediately reply to the sender and delete this information from >>>>>> your system. Use, dissemination, distribution, or reproduction of this >>>>>> transmission by unintended recipients is not authorized and may be >>>>>> unlawful. >>>>>> >>>>>> >>>>>> >>>>>> --------------090303020008010700030803--