I believe 32bit run mode was the default for earlier versions of LiveCode but 9.x is 64bit by default. I bring that up out of curiosity because I had a problem with a browser plug-in (64/32bit) running inside a LiveCode Browser widget in the past. The plugin would crash running in 64bit, sometimes taking LiveCode Engine with it, but if it worked perfectly in LC in 32bit mode or earlier versions of LiveCode. Of course the plugin worked fine in Safari and on both 32bit and 64bit kernel machines. I've since replaced that plug-in with my own LCB Library that does most of what I need that fo (and also got rid of my 32bit laptop) so I didn't investigate further.
> On Jan 20, 2020, at 07:41 , Mark Waddingham via use-livecode < > use-livecode@lists.runrev.com> wrote: > > > > On 2020-01-20 15:20, Matthias Rebbe via use-livecode wrote: > >> Just want to let you know that Livecode Dev Team confirmed that this is > a bug > >> https://quality.livecode.com/show_bug.cgi?id=22534 > > > > Well, we confirmed it crashed ;) Whether it is a bug in LC or Adobe DC > or not > > is another matter. > > > > There was a similar issue a very long time ago with Adobe's PDF plugin - > it would > > cause the browser external to crash if used (we used the system webview > back then > > as we do now)... The Adobe plugin was doing things it shouldn't (I can't > recall > > if we managed to come up with a hack in the browser external to stop it > or not; or > > whether Adobe eventually cleaned up their plugin!) > > > > Warmest Regards, > > > > Mark. > > > > -- > > Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/ > > LiveCode: Everyone can create apps > > _______________________________________________ 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
