"setters" and "getters"
Hmm. I actually use that on a different module
actually, after talking with Andre.. .
what I am trying to do is create "caches" where a process does not need to run,
say, every time you hit a card.
so he says "don't use config" …
sCacheA. # is a better name
Once you se
On 9/1/19 7:48 AM, Sannyasin Brahmanathaswami via use-livecode wrote:
There are two ways to go with this:
1) keep adding "keys" to the BIG global sConfigA
OR
2) we could keep the custom properties of Stack Engine (which is always open)
Does anyone have experience and has come to "best practice
Given a modular stack framework for mobile, where
1) a "engine" stack to always open, but hidden on boot → call it "Stack Engine"
2) then you have multiple "modular" stacks -- call them views--which are opened
and closed on "demand/navigation" → call them
a. stack "story"
