Short Version / File Version

[ckelly5430]

Is there an easy way to get the MAC short version and the Windows File Version of my app into a splashscreen?

[Klaus]

HI ckelly5430,

yes there is

Livecode stores the standalone builder settings in a custom property set named "cRevStandaloneSettings"
and you can retrieve this info in a standalone, since this CP set is obviously not deleted when building the standalone.

These are the keys:
scriptLibraries
Linux x64
MacOSX
OSX,name
UNIX,fileSelector
Windows
Windows,LegalCopyright
UNIX,pageSetup
Solaris SPARC
OSX,documentType
Linux
ios
inclusions
Windows,documenticonFile
answerDialog
OSX,documentExtension
Windows,FileDescription
OSX,longVersion
UNIX,printerChooser
OSX,copyright
android
OSX,identifier
name
Solaris Intel
OSX,shortVersion
Windows,fileversion1
Windows,fileversion2
Windows,productversion1
Windows,fileversion3
Windows,productversion2
Windows,fileversion4
Windows,productversion3
cursors
Windows,productversion4
OSX,info
MacOSX PowerPC-32
Windows,UUID
askDialog
Windows,iconFile
OSX,signature
defaultBuildFolder
Windows,ProductName
UNIX,colorChooser
MacOSX x86-32
ios,ipad intial orientations
Windows,companyname

So you can do something like this:

Code: Select all

...
put the cRevStandaloneSettings["OSX,shortVersion"] of stack "name of standalone mainstack here" \
           into fld "versionnumber" of cd 1 of stack "splash"
...

You get the picture


Best

Klaus

[FourthWorld]

I believe the cRevStandaloneSettings property set is removed during build time, so that info won't be available in a standalone.

For this reason, I continue to use my own custom properties for things like version number and app name, and use a setProp handler in a custom tool to update the corresponding cRevStandaloneSettings values as needed.

FWIW, the properties I use are defined in the ECMI spec, available on the Rev Interoperability Project page where we also have tools for conveniently setting those properties:
http://livecodejournal.com/revinterop/index.html

One of the benefits of using a common set of property name conventions is that it allows tool makers and other developers to have a common place we can rely on for such general info.

[Klaus]

Hi Richard,

I believe the cRevStandaloneSettings property set is removed during build time, so that info won't be available in a standalone.

do you kno when this has changed? It used to work in earlier versions,
but now it is not even listed in the IDE und "custom properties", I had
to use MetaCard to see the cp set


Best

Klaus

[FourthWorld]

Hi Richard,

I believe the cRevStandaloneSettings property set is removed during build time, so that info won't be available in a standalone.

do you know when this has changed?

I don't; I'd thought it always worked that way.

It used to work in earlier versions, but now it is not even listed in the IDE und "custom properties", I had
to use MetaCard to see the cp set

If you turn on the Preferences checkbox labeled "LiveCode UI elements appear in lists of stacks" that also allow IDE-specific custom property sets to become visible in the Inspector.

[Klaus]

Ah, thanks, never thought this would also affect cps.

[FourthWorld]

Ah, thanks, never thought this would also affect cps.

Me neither until I discovered it by accident one day. Believe me, I took my time switching from MC to LC.