Where to write a shared file to?

Peter Haworth pete at lcsql.com
Fri Mar 1 15:29:51 EST 2013


Tom,
I don;t remember the details but I believe using the special folder path
"support" gave different results on OSX in a couple of LC versions.  Sorry
I don;t remember the details but I think it's in the release notes
somewhere.
Pete
lcSQL Software <http://www.lcsql.com>


On Sat, Mar 2, 2013 at 8:50 AM, Thomas McGrath III <mcgrath3 at mac.com> wrote:

> Thanks Graham, but we decided to go ahead with the support folder for now
> and see haw it works out.
>
> thanks again
>
> tom
>
> -- Tom McGrath III
> http://lazyriver.on-rev.com
> mcgrath3 at mac.com
>
> On Mar 1, 2013, at 11:44 AM, Graham Samuel <livfoss at mac.com> wrote:
>
> > I'm using Parallels as well, but I do have Windows 7 as well as XP if
> you want me to look into it.
> >
> > Graham
> >
> > On 28 Feb 2013, at 19:21, Thomas McGrath III wrote:
> >
> >> Thanks Graham, I am testing this but I don't have a Windows box (yet)
> so I can only test on Parallels in Windows XP but the results do look
> promising. Problem is I need to know for sure.
> >>
> >> Thanks again
> >>
> >> Tom
> >>
> >> -- Tom McGrath III
> >> http://lazyriver.on-rev.com
> >> mcgrath3 at mac.com
> >>
> >> On Feb 28, 2013, at 1:13 PM, Graham Samuel <livfoss at mac.com> wrote:
> >>
> >>> I think it's OK if you haven't got a sandbox situation to deal with,
> but I'm not 100% sure - but a quick experiment would prove it. I can do
> this, but not right now, so maybe it's better to experiment yourself.
> >>>
> >>> Cheers
> >>>
> >>> Graham
> >>>
> >>> On 28 Feb 2013, at 18:57, Thomas McGrath III wrote:
> >>>
> >>>> Graham,
> >>>>
> >>>> Thanks for the reply.I was looking at the preferences or documents
> folder due to permission issues but I am just not sure if I use my apps
> Support folder if another application can write to it? Or is the support
> folder able to be accessed from both apps? Do you know?
> >>>>
> >>>> Thanks
> >>>>
> >>>> Tom
> >>>>
> >>>> -- Tom McGrath III
> >>>> http://lazyriver.on-rev.com
> >>>> mcgrath3 at mac.com
> >>>>
> >>>> On Feb 28, 2013, at 12:45 PM, Graham Samuel <livfoss at mac.com> wrote:
> >>>>
> >>>>> Tom, unless I've misunderstood what you need, why not use the
> specialFolderPath("support") path? These are paths that can be written to
> by an application on both platforms. It's easy to see what the path
> actually is, so you can tell the low level application. I'm using this
> approach for somewhere to put a data stack (a stack that can be saved at
> runtime) on a two-platform app and it works for me.
> >>>>>
> >>>>> HTH
> >>>>>
> >>>>> Graham
> >>>>> On 28 Feb 2013, at 18:32, Thomas McGrath III wrote:
> >>>>>
> >>>>>> I am working on a cross-platform (Mac/Windows) app and I had to
> hire out for a low level application to be written that will trap 'all' key
> events on both platforms. Pretty straight forward. It timestamps and writes
> the key or keys that were hit out to a file that I in turn look for changes
> to from within LC. The key trapper will have it's own installer and I need
> to tell it where to write to before it is built.
> >>>>>>
> >>>>>> My question is where is the best place to write this file to on a
> Mac? on a PC?
> >>>>>>
> >>>>>> I am not going through the Mac App store but I don't want to run
> into problems with permissions etc. once deployed.
> >>>>>>
> >>>>>>
> >>>>>> I am searching online now but there is a lot of gobble goop that is
> not pertinent.
> >>>>>>
> >>>>>> Any help or ideas are appreciated.
> >>>>>>
> >>>>>> Tom
> >>>>>>
> >>>>>> -- Tom McGrath III
> >>>>>> http://lazyriver.on-rev.com
> >>>>>> mcgrath3 at mac.com
> >>>>>>
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> use-livecode mailing list
> >>>>>> use-livecode at lists.runrev.com
> >>>>>> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> >>>>>> http://lists.runrev.com/mailman/listinfo/use-livecode
> >>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>> use-livecode mailing list
> >>>>> use-livecode at lists.runrev.com
> >>>>> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> >>>>> http://lists.runrev.com/mailman/listinfo/use-livecode
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> use-livecode mailing list
> >>>> use-livecode at lists.runrev.com
> >>>> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> >>>> http://lists.runrev.com/mailman/listinfo/use-livecode
> >>>
> >>>
> >>> _______________________________________________
> >>> use-livecode mailing list
> >>> use-livecode at lists.runrev.com
> >>> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> >>> http://lists.runrev.com/mailman/listinfo/use-livecode
> >>
> >>
> >> _______________________________________________
> >> use-livecode mailing list
> >> use-livecode at lists.runrev.com
> >> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> >> http://lists.runrev.com/mailman/listinfo/use-livecode
> >
> >
> > _______________________________________________
> > use-livecode mailing list
> > use-livecode at lists.runrev.com
> > Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> > http://lists.runrev.com/mailman/listinfo/use-livecode
>
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>



More information about the Use-livecode mailing list