Re: Developer SDK Version Number

2013-02-09 Thread François Chaplais
The links to the externals resources in the PDF manual are are broken §12.3.1, p.361 François ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lis

Re: Developer SDK Version Number

2013-02-07 Thread Monte Goulding
On 08/02/2013, at 8:24 AM, Thomas McGrath III wrote: > No luck on the shift keys for mac but I am making headway on 'all' the rest > of my needs for this project. 4.5 week deadline and many hurdles to over > come. For such a simple project concept this one is turning out to be a > challenge.

Re: Developer SDK Version Number

2013-02-07 Thread Thomas McGrath III
Monte, No luck on the shift keys for mac but I am making headway on 'all' the rest of my needs for this project. 4.5 week deadline and many hurdles to over come. For such a simple project concept this one is turning out to be a challenge. But, It's work and I'm glad for it. Thanks for asking.

Re: Developer SDK Version Number

2013-02-07 Thread Monte Goulding
On 08/02/2013, at 3:44 AM, Thomas McGrath III wrote: > Does anyone have the latest version number for the Developer SDK "Externals > Environment" for LiveCode? I have version 3. Yes although Trevor sent me one once that has some slight differences for Obj-C. Did you find a way forward with th

Re: Developer SDK Version Number

2013-02-07 Thread Thomas McGrath III
Thanks Mark, -- Tom McGrath III http://lazyriver.on-rev.com mcgra...@mac.com On Feb 7, 2013, at 1:02 PM, Mark Wieder wrote: > Thomas McGrath III writes: > >> >> Does anyone have the latest version number for the Developer SDK "Externals >> Environment" for LiveCode? I have version 3. > > Th

Re: Developer SDK Version Number

2013-02-07 Thread Mark Wieder
Thomas McGrath III writes: > > Does anyone have the latest version number for the Developer SDK "Externals > Environment" for LiveCode? I have version 3. That's the latest I've seen. Still waiting for the fabled new api, but I'm not holding my breath. Note that there's still a bug in the header