Re: iPhone X or "Apple is just the most annoying company of all time"

On 11/2/17 7:17 PM, Colin Holgate via use-livecode wrote: Apple do document what they mean by a safe area, and the amount it eats into the screen isn’t very much: https://developer.apple.com/ios/human-interface-guidelines/overview/iphone-x/ Android developers have been dealing with a gazillio

Device implementation problems

A few days ago I raised the question on how the device behaviour differs from how it is in the IDE environment. The question posed was if there is a command go card "xyz" and the script continues to run immediately, would there be interference in terms of "getting the go done". Interp

RE: results of SPLIT when keys not unique

I wyyy over thought this. This is tested: SELECT animals.animalnumber, animals.animalname FROM animals GROUP BY animals.animalname; Ralph DiMola IT Director Evergreen Information Services rdim...@evergreeninfo.net -Original Message- From: Dr. Hawkins [mailto:doch...@gmail.com] Sen

Re: iPhone X or "Apple is just the most annoying company of all time"

Apple do document what they mean by a safe area, and the amount it eats into the screen isn’t very much: https://developer.apple.com/ios/human-interface-guidelines/overview/iphone-x/ ___ use-livecode mailing list use-livecode@lists.runrev.com Please vis

Re: results of SPLIT when keys not unique

On Thu, Nov 2, 2017 at 3:45 PM, Ralph DiMola wrote: > Whoops, not tested and I saw an error. > > Select mytable.animalname,mytable.animalnumber from (select distinct > mytable.animalname from mytable as mytable2) left join mytable on > mytable.animalname = mytable2animalname You're a bit over my

Re: results of SPLIT when keys not unique

The last one of course. Bob S > On Nov 2, 2017, at 15:39 , Monte Goulding via use-livecode > wrote: > > A quick test and it looks like split will clobber any new elements with the > same key as those previously parsed. The docs state that only one element > will be created but are unclear

Re: results of SPLIT when keys not unique

On Thu, Nov 2, 2017 at 3:39 PM, Monte Goulding via use-livecode wrote: > It would probably be nice to have some explicit syntax to govern this > behavior so that you could explicitly declare > you want clobbering behavior or first come best dressed. explicit is (almost) always nice (says the gu

Re: results of SPLIT when keys not unique

On Thu, Nov 2, 2017 at 3:45 PM, Ralph DiMola wrote: > Whoops, not tested and I saw an error. > > Select mytable.animalname,mytable.animalnumber from (select distinct > mytable.animalname from mytable as mytable2) left join mytable on > mytable.animalname = mytable2animalname > You just shot *way*

Re: results of SPLIT when keys not unique

> On 3 Nov 2017, at 9:39 am, Monte Goulding wrote: > > It would probably be nice to have some explicit syntax to govern this > behavior so that you could explicitly declare you want clobbering behavior or > first come best dressed. Oh… one might also feasibly want output like this I guess: v

RE: results of SPLIT when keys not unique

Whoops, not tested and I saw an error. Select mytable.animalname,mytable.animalnumber from (select distinct mytable.animalname from mytable as mytable2) left join mytable on mytable.animalname = mytable2animalname Ralph DiMola IT Director Evergreen Information Services rdim...@evergreeninfo.net

RE: results of SPLIT when keys not unique

Would something like this work? Select mytable.animalname,mytable.animalnumber from (select distinct mytable.animal from mytable as mytable2) left join mytable on mytable.animalname = mytable2animalname Ralph DiMola IT Director Evergreen Information Services rdim...@evergreeninfo.net -Orig

Re: results of SPLIT when keys not unique

A quick test and it looks like split will clobber any new elements with the same key as those previously parsed. The docs state that only one element will be created but are unclear about which element value will be retained. It would probably be nice to have some explicit syntax to govern this

results of SPLIT when keys not unique

If I use split such that keys are not unique, will that have the effect of filtering out duplicates? For example, if I have dog 3 dog 5 cat 8 and SPLIT it, will I end up with 5 in entry dog? More specifically, is this a defined behavior, or "just how it currently works" I'm trying to find

Re: Link to iOS device settings

Based on that SO discussion you should be able to use launch url. It looks like the url scheme changed from `prefs:` to `App-Prefs:` in iOS 10. So you might want to try one then the other. So: launch url “App-Prefs:root=NOTIFICATIONS_ID&path=” if the result is “no association" then launch u

Link to iOS device settings

Is it possible from a LiveCode app to link to the iOS device Settings? I would like to help users enable Push Notifications if they didn't the first time the app was launched, and rather than just describe where it is I'd like to jump to the Settings app. Seems to be doable in native progra

Re: JSON import error

On 11/2/17 2:45 PM, Mark Wieder via use-livecode wrote: On 11/02/2017 11:57 AM, J. Landman Gay via use-livecode wrote: On 11/2/17 6:52 AM, Dave Kilroy via use-livecode wrote: https://en.wikipedia.org/wiki/Rubber_duck_debugging Yeah. Story

Re: iPhone X or "Apple is just the most annoying company of all time"

If it's like the 5c and doesn't sell, this won't be a problem. On Thu, Nov 2, 2017 at 1:35 PM, Brian Milby via use-livecode < use-livecode@lists.runrev.com> wrote: > With the X Apple is suggesting that the status bar not be turned off in > most cases. That would eliminate the issue of the top sid

Re: JSON import error

On 11/02/2017 11:57 AM, J. Landman Gay via use-livecode wrote: On 11/2/17 6:52 AM, Dave Kilroy via use-livecode wrote: https://en.wikipedia.org/wiki/Rubber_duck_debugging Yeah. Story of my life. I've since hit another error in the JSON impo

Re: JSON import error

On 11/2/17 6:52 AM, Dave Kilroy via use-livecode wrote: https://en.wikipedia.org/wiki/Rubber_duck_debugging Yeah. Story of my life. I've since hit another error in the JSON import but now I'm afraid to post about it. :) -- Jacqueline Lan

Re: iPhone X or "Apple is just the most annoying company of all time"

With the X Apple is suggesting that the status bar not be turned off in most cases. That would eliminate the issue of the top side cut out. You should be able to use the screenrect to determine device (I guess) and not hide. On Thu, Nov 2, 2017 at 12:07 PM Bob Sneidar via use-livecode < use-livecod

Re: iPhone X or "Apple is just the most annoying company of all time"

I bet they are working on it right now! Bob S > On Nov 2, 2017, at 09:56 , Ralph DiMola via use-livecode > wrote: > > 1. iPhone X has rounded corners and an annoying "tab" at the top and the > fact that there is no home button. Users will swipe up from the bottom to > get back to the home pa

iPhone X or "Apple is just the most annoying company of all time"

1. iPhone X has rounded corners and an annoying "tab" at the top and the fact that there is no home button. Users will swipe up from the bottom to get back to the home page. This may cause an issue for apps with buttons towards the bottom of the screen. 2. Apps that have an edge-to-edge design will

RE: Announcing our first Livecode app in the iOS App Store

Congrats! I remember the exhilaration I had after I made it through the Apple gauntlet. Ralph DiMola IT Director Evergreen Information Services rdim...@evergreeninfo.net -Original Message- From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of hlowe via use-livecod

Re: JSON import error

https://en.wikipedia.org/wiki/Rubber_duck_debugging ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferen

RE: Announcing our first Livecode app in the iOS App Store

Congratulations on the health informatics app! Occasionally I need to do mappings to ICD-10 so I’ll definitely check out your app... Kind regards Dave ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, uns

Re: JSON import error

file: will recognise the BOM and decode the text correctly. > On 2 Nov 2017, at 5:36 pm, J. Landman Gay via use-livecode > wrote: > > I sent my message too soon. If I import as "file:" instead of "binfile:" it > mostly works. > > You always figure it out as soon as you post. It's a rule. _