iOS cameraControl microphone permission bug
Does anyone know if there is an iOS workaround for an app that uses a cameraControl but does not need or use audio? The bug is that iOS asks for microphone permission even though I'm setting the audioDevice to empty. Here is the bug report: https://quality.livecode.com/show_bug.cgi?id=21438 I can't get an app accepted that uses cameraControl for stills because iOS asks for microphone permission when its not actually needed. Thanks to anyone that can help! ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
RE: Naive question number 3374
because cursor is a property and move wants to move an object seems to me that possibly the compiler should catch this, or not.but in any circumstance, cursor is defined as a property and move expects to move an object ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: on-rev urgent ticket system down?
Thanks for that suggestion PeterI'll do that now! ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
on-rev urgent ticket system down?
Would anyone know if on-rev support 'urgent' system might be down? I've sent 4 emails with the subject 'urgent' and have yet to hear from them. I have indeed generally heard from them in an hour in the past, but no go for over 18 hours now. Is there some other way to get them a message if their 'urgent' system is not functioning and they are not aware of that fact? (and yes, I am sending the 'urgent' email from my on-rev registered email address) To those that may be on-rev customers and read this.no, the servers are not down, its just that my particular account has an issue that needs their immediate attention.I add this just so I don't freak out current on-rev customers ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
how can exportImageToAlbum be broken on android for so long...
I've never, ever gotten it to work. There are two outstanding bug reports that are nearly a year old. Such a fundamental feature that has, as far as I can tell, never worked on android. It certainly does not work from 6.x.x and on My image is a png and I'm doing the following: put the long ID of image myimage into tlongid mobileExportImageToAlbum tlongid This returns export failed every time. I've tried to use a filename: mobileExportImageToAlbum tlongid, testfilename 'export failed' I've tried: put the text of image myimage into ttext mobileExportImageToAlbum ttext fails with either export failed or could not find image Why has a fundamental android feature that has been broken for so long been ignored? ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
GPS timestamp
I posted this in the android forums but have not gotten a response yet, so thought I'd ask here. Here's my post from the forum: Didn't know whether to post this in Talking Livecode or here, because although I'm asking the following with android in mind, I'm really looking for answers that apply to both android AND iOS. My baseline question is: when I query for a detailed=true location reading, one of the items returned is timestamp. In the documentation, there really is nothing describing what or where this timestamp is coming from. Is it from actual GPS packets? ...or from the cellular network if the reading came from AGPS (tower triangulation)? In reading about GPS timestamps in google's api's (IOS as well), there seems to be different timestamps one can get depending upon which Location object is queried.and thus those timestamps can be and mean different things. I'm simply trying to ascertain what the heck timestamp am I getting from LC I don't know if its a LC thing, or if GPS timestamps from mobile devices in general are unreliable, but when simply logging detailed location data in a test app, I see all sorts of (seeming) anomalies with the timestamp, and it would be ultra-helpful to have some information/documentation on the origin of what LC is returning as timestamp... (BTW, I *only* do a detailed=true location mobileSensorReading when I receive a locationChanged message) For example, sometimes I'll get timestamps that are several minutes to over an hour IN THE FUTURE..sometimes I'll see a timestamp that is indeed old, but cannot be *reliably* deemed as old since one can receive readings WITH THE SAME OLD TIMESTAMP where the GPS coordinates are changing and the accuracies are changing/improving. If a GPS reading has changed (along with its calculated accuracy), then why would I get many GPS readings with the EXACT same timestamp? The above makes it difficult (impossible?) to discern actual stale readings vs usable readings. Can anyone shed any light on what LC's timestamp actually is and/or why I'm seeing some of the timestamp anomalies that I detailed above? ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: mobilePickPhoto camera - unstable on android
Hello Neil, Thank you so much for responding. I have done so, here is the link: http://quality.runrev.com/show_bug.cgi?id=8 Thanks again Neil! Paul K On Thu, Aug 22, 2013 at 3:44 AM, Neil Roger n...@runrev.com wrote: Hi Paul, If possible, could you submit a bug report on this issue with RunRev Quality Control and we will be happy to investigate it further. You will be able to submit a report here- http://quality.runrev.com Kind Regards, Neil Roger -- RunRev Support Team ~ http://www.runrev.com -- On 22/08/2013 04:41, Paul Kocsis wrote: At present time, testing with community 6.1.1rc2. I'm finding that on android, mobilePickPhoto camera is NOT stable. On a 4.1.3 galaxy s2, about 1 out of 30-ish (sometimes more) calls to mobilePickPhoto camera will not return (I.E. mobilePickPhoto camera' is called, camera comes up, photo is taken, 'save' is tapped, then app crashes and immediately restarts). I know that when a crash occurs, it is inside mobilePickPhoto camera as the next statement after mobilePickPhoto does not get called. It is MUCH worse on a Motorola Atrix 2.3.5. I can fairly easily get this crash to occur (maybe 1 out of 5 or 10 attempts). (grasping at straws, but...) It almost seems like the older the phone/android, the more often it happens...but although not the latest, a galaxy s2 running 4.1.3 experiences the problem too (just not as often)...I have tried to put a wait for 100 milli with messages before and after the mobilePickPhoto camera command but it has not affected the crashes (can't *really* put a wait for 100... immediately after since if I do I lose the result from mobilePickPhoto, so I do a 'put the result into tresult' and then do my waitbut no matter.doesn't make things better or worse). Is there anyone out there that has had more than a cursory use of mobilePickPhoto camera on android than can either deny or confirm what I am seeing? Thanks! Paul K. __**_ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/**mailman/listinfo/use-livecodehttp://lists.runrev.com/mailman/listinfo/use-livecode __**_ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/**mailman/listinfo/use-livecodehttp://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
mobilePickPhoto camera - unstable on android
At present time, testing with community 6.1.1rc2. I'm finding that on android, mobilePickPhoto camera is NOT stable. On a 4.1.3 galaxy s2, about 1 out of 30-ish (sometimes more) calls to mobilePickPhoto camera will not return (I.E. mobilePickPhoto camera' is called, camera comes up, photo is taken, 'save' is tapped, then app crashes and immediately restarts). I know that when a crash occurs, it is inside mobilePickPhoto camera as the next statement after mobilePickPhoto does not get called. It is MUCH worse on a Motorola Atrix 2.3.5. I can fairly easily get this crash to occur (maybe 1 out of 5 or 10 attempts). (grasping at straws, but...) It almost seems like the older the phone/android, the more often it happens...but although not the latest, a galaxy s2 running 4.1.3 experiences the problem too (just not as often)...I have tried to put a wait for 100 milli with messages before and after the mobilePickPhoto camera command but it has not affected the crashes (can't *really* put a wait for 100... immediately after since if I do I lose the result from mobilePickPhoto, so I do a 'put the result into tresult' and then do my waitbut no matter.doesn't make things better or worse). Is there anyone out there that has had more than a cursory use of mobilePickPhoto camera on android than can either deny or confirm what I am seeing? Thanks! Paul K. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
