Can a stack know which standalone engine it's running on?

[Devin Asay]

But doesn’t the processor just report on the host operating system? I wan’t to know which LiveCode engine is running.

Here’s the scenario:

I have a LiveCode splash screen-type application for which I’ve compiled both Windows-32 and Windows-64-bit versions. The standalone opens a stack that contains the actual business logic. In my About dialog, I’d like to be able to report which LiveCode engine the stack is running under. Do we have a way to get that information?

Devin


> On Apr 27, 2020, at 3:56 PM, Mark Waddingham via use-livecode <use-livecode at lists.runrev.com> wrote:
> 
> The version almost uniquely identifies every public engine build - the buildNumber always does.
> 
> The platform together with the processor uniquely identify the target it was built for.
> 
> Warmest Regards,
> 
> Mark.
> 
> Sent from my iPhone
> 
>> On 27 Apr 2020, at 22:43, Devin Asay via use-livecode <use-livecode at lists.runrev.com> wrote:
>> 
>> The subject line says it. Is there a way for my stack to know which Windows standalone engine it is running on? For diagnostic purposes I would like to be able to report the current LiveCode standalone engine. I’m probably missing something obvious.
>> 
>> Devin
>> 
>> Devin Asay
>> Director
>> Office of Digital Humanities
>> Brigham Young University
>> 
>> _______________________________________________
>> 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

Devin Asay
Director
Office of Digital Humanities
Brigham Young University