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@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@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@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Reply via email to