On 2018-03-20 08:41, Ted Roche wrote:
On Mon, Mar 19, 2018 at 4:21 PM, mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
I was adding another "global" application attribute for a signal flag for later code to reference, and I realized I've always used the _SCREEN object. Would seem more logical to reference the _VFP object. Your thoughts on this design decision?
If you have more than one GLOBAL application attributes, why not keep them in a GLOBAL object? All sorts of functions can be built in: push, pop, load from an INI file, persist to a database, store universal application settings, manage user settings, etc...
I do actually have a custom global object (oUtils)...and honestly I'm rethinking now why I didn't attach them to that instead of _screen. My first guess is that this was due to INI values being read in at startup BEFORE the oUtils global object was created.