mobileStandaloneSaved |
Type | message |
Dictionary | LCS |
Library | LiveCode Script |
Syntax | mobileStandaloneSaved <pTargetType>, <pAppBundle>
|
Associations | stack |
Summary | Sent to the mainstack after it has been saved as a mobile standalone
application or the simulation was started.
|
Introduced | 5.5.3 |
OS | ios, android |
Platforms | desktop, server |
Parameters | Name | Type | Description |
---|
pTargetType | | "simulator":
"device":
|
pAppBundle | | A string variable containing the folder that the mobile standalone
application was saved in. This is empty if the build failed.
|
|
Example | on mobileStandaloneSaved pTarget, pFolder
get shell("hdiutil create -fs HFS+ -volname MyApp"&\
" -size 100m ~/Desktop/MyApp.dmg")
get shell("hdiutil mount ~/Desktop/MyApp.dmg")
get shell("ditto -rsrc -V "&pFolder&" /Volumes/MyApp"&\
" >> /Volumes/Backup/MyApp.log")
get shell("hdiutil unmount /Volumes/MyApp")
get shell("hdiutil burn ~/Desktop/MyApp.dmg"& \
" -noverifyburn -noeject")
end mobileStandaloneSaved
|
Related | Message: savingStandalone, standaloneSaved, savingMobileStandalone
|
Description | After a mobile stack has been saved as a standalone application it is
reopened. This message is then sent to the mainstack to allow custom
build time automation.
|