On 2018-03-20 08:41, Ted Roche wrote:
On Mon, Mar 19, 2018 at 4:21 PM,
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
On Mon, Mar 19, 2018 at 4:21 PM,
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.
@leafe.com>
Subject: AW: _VFP vs _SCREEN
Think of _VFP as "the engine" and _SCREEN as the "visual representation".
Don't fiddle with the engine!
wOOdy
-Ursprüngliche Nachricht-
Von: ProFox <profox-boun...@leafe.com> Im Auftrag von
mbsoftwaresoluti...@mbsoft
On 2018-03-19 17:37, Jürgen Wondzinski wrote:
Think of _VFP as "the engine" and _SCREEN as the "visual
representation".
Don't fiddle with the engine!
wOOdy
Ah, good way to look at it. Stay away from the _VFP object! lol
___
Post Messages to:
März 2018 21:21
An: ProFox <profox@leafe.com>
Betreff: _VFP vs _SCREEN
(I checked the ProFox archive but searching for _VFP _SCREEN (with
underscore, with underscored escaped, and without underscore) did not
turn up any matches or at least the ones applicable). I know we've
discussed this
(I checked the ProFox archive but searching for _VFP _SCREEN (with
underscore, with underscored escaped, and without underscore) did not
turn up any matches or at least the ones applicable). I know we've
discussed this somewhere in the past but could not find the reference.)
I was adding
6 matches
Mail list logo