On 2018-03-20 08:41, Ted Roche wrote:
On Mon, Mar 19, 2018 at 4:21 PM,
<[email protected]> 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.
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
