launch document problem

Peter Haworth pete at
Thu Jan 28 12:06:41 EST 2016

Thanks Mark. I filed  report (16776) and it's been classified as a bug with
the workaround documented by Kay.

The only issue I have now is avoiding hard coding the browser to use.  Does
anyone know of a way to find the default browser setting in OSX (this
program will only be running on Macs).

lcSQL Software <>
Home of lcStackBrowser <> and
SQLiteAdmin <>

On Wed, Jan 27, 2016 at 11:46 PM, Mark Waddingham <mark at> wrote:

> Hi Pete,
> On 2016-01-28 01:26, Peter Haworth wrote:
>> Prowling around the web, I found that the url I'm seeing is a "file
>> reference url", not sure whether this is an Apple thing or cross platform.
>> Since it works in Safari and not in Chrome, I suspect it may be an Apple
>> thing.
> I believe 'launch document' uses the Launch Services API - it might be
> that needs a bit of patching to ensure it is using the latest and greatest
> way of communicating file references. The Apple APIs have made a move
> towards using URIs for most things these days so it could be that the
> engine is using a 'legacy' API these days.
> However the engine processes a launch document command is converting the
>> normal filepath to this file reference url which apparently Chrome doesn't
>> like.  I think I will file a QCC report about it.  Not sure it's really a
>> bug since the file reference url is valid in Safari but would be nice to
>> have a way to have the filepth not be converted to a file reference url.
> Given that Kay observed that 'launch document with' works, but 'launch
> document' does not I suspect it should be easy to figure out. Please do
> file a report :)
> Warmest Regards,
> Mark.
> --
> Mark Waddingham ~ mark at ~
> LiveCode: Everyone can create apps
> _______________________________________________
> use-livecode mailing list
> use-livecode at
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:

More information about the Use-livecode mailing list