It occurs to me: since we can now use text-only stacks, the launcher app
could simply download the latest version on launch and start using it. That
way you wouldn't even need to build a new app when changes are needed.
Our project was set up before that option was available, but I'm tempted to
On 7/3/2016 10:29 PM, Sannyasin Brahmanathaswami wrote:
GOAL: have a object/group (think navigation bar at the bottom of the
screen or some other elements you may want to be common across all
the stacks….) that can be displayed in all the stacks.
This is exactly the setup I needed for the big
Sannyasin Brahmanathaswami wrote:
> So, it's back to a behavior script that is external to the binary
> stacks a subject we discussed in depth earlier. *unless* one can
> refer to a behavior in another stack that is not part of the same
> stack file… I'm not sure how that will work… to be tested.
yep, that request has been on the books since 2005 and I upvoted in March of
this year…
So, it's back to a behavior script that is external to the binary stacks a
subject we discussed in depth earlier. *unless* one can refer to a behavior in
another stack that is not part of the same stack file
Sannyasin Brahmanathaswami wrote:
> GOAL: have a object/group (think navigation bar at the bottom of the
> screen or some other elements you may want to be common across all
> the stacks….) that can be displayed in all the stacks.
...
> So…is there a way to similarly instantiate the presence of
Architecture Challenge (for me a least)
Framework set up,
where these are independent binary stacks…
not substacks of a mainstack.
/source-package
Loader.livecode
# sets up back script with common functions
# reads json files for configurations settings
# then opens "home.livec
