Return-Path: X-Original-To: apmail-incubator-callback-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-callback-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F0E4DDC52 for ; Wed, 15 Aug 2012 12:53:38 +0000 (UTC) Received: (qmail 73674 invoked by uid 500); 15 Aug 2012 12:53:38 -0000 Delivered-To: apmail-incubator-callback-dev-archive@incubator.apache.org Received: (qmail 73581 invoked by uid 500); 15 Aug 2012 12:53:38 -0000 Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: callback-dev@incubator.apache.org Delivered-To: mailing list callback-dev@incubator.apache.org Received: (qmail 73498 invoked by uid 99); 15 Aug 2012 12:53:38 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Aug 2012 12:53:38 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 1385A2C5BE5 for ; Wed, 15 Aug 2012 12:53:38 +0000 (UTC) Date: Wed, 15 Aug 2012 23:53:38 +1100 (NCT) From: "Tekken Tux (JIRA)" To: callback-dev@incubator.apache.org Message-ID: <130629051.12927.1345035218080.JavaMail.jiratomcat@arcas> In-Reply-To: <892847112.12854.1345034977973.JavaMail.jiratomcat@arcas> Subject: [jira] [Updated] (CB-1245) CompassError object is not passed to compassError callback function MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CB-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tekken Tux updated CB-1245: --------------------------- Description: I'm quite sure the Pre+ actually has no compass, but instead of calling the compassError callback function with an CompassError of type CompassError.COMPASS_NOT_SUPPORTED, it just calls the callback function without any parameter. The following example outputs "undefined": {code:title=compass.js|borderStyle=solid} var watchID = navigator.compass.watchHeading(compassSuccess, compassError, options); ... function compassError(e) { console.log(e); } {code} I think this is because in compass.js in function getCurrentHeading it just says: {quote} errorCallback(); {quote} with no params was: I'm quite sure the Pre+ actually has no compass, but instead of calling the compassError callback function with an CompassError of type CompassError.COMPASS_NOT_SUPPORTED, it just calls the callback function without any parameter: {code:title=compass.js|borderStyle=solid} var watchID = navigator.compass.watchHeading(compassSuccess, compassError, options); ... function compassError(e) { console.log(e); } {code} outputs "undefined". I think this is because in compass.js in function getCurrentHeading it just says: {quote} errorCallback(); {quote} with no params > CompassError object is not passed to compassError callback function > ------------------------------------------------------------------- > > Key: CB-1245 > URL: https://issues.apache.org/jira/browse/CB-1245 > Project: Apache Cordova > Issue Type: Bug > Components: webOS > Affects Versions: 2.0.0 > Environment: Palm Pre+, windows, cygwin > Reporter: Tekken Tux > Assignee: Herm Wong > Original Estimate: 2h > Remaining Estimate: 2h > > I'm quite sure the Pre+ actually has no compass, but instead of calling the compassError callback function with an CompassError of type CompassError.COMPASS_NOT_SUPPORTED, it just calls the callback function without any parameter. > The following example outputs "undefined": > {code:title=compass.js|borderStyle=solid} > var watchID = navigator.compass.watchHeading(compassSuccess, compassError, options); > ... > function compassError(e) { > console.log(e); > } > {code} > I think this is because in compass.js in function getCurrentHeading it just says: > {quote} > errorCallback(); > {quote} > with no params -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira