On 1/15/2015 1:57 PM, Richard Gaskin wrote:
J. Landman Gay wrote:
> On 1/15/2015 10:05 AM, Richard Gaskin wrote:
>> While the absence of reports related to general file access in the
>> bundle would seem to suggest this change was implemented well in the
>> engine, René's report shows this workaround for Apple's new security
>> policy needs to be added to the SQLite external as well.
>
> It's more general than that, see my bug report comment. The problem
> occurs not only in Yosemite but also in Mavericks, and applies to any
> file that is moved to the new location, not just databases.
Thanks for adding your note to the report. With the original submission
focused on SQLite and subsequent notes involving writing to the app
bundle, your note will help clarify what's going on.
Why do you suppose this has survived so long with no one discovering it
until now?
I don't know. In my case I didn't need to build a new standalone until
yesterday, coupled with the fact that my main project is still done in
LC 6.5.x for other reasons. I've only recently started using 6.7, and
only for a few newer projects.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
_______________________________________________
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
