Maybe it was, that Lockscreen also accepts a numeric 0 instead of .F. Every lockscreen = .t. increments an internal counter, and every lockscreen = .F. decrements it. Thus you really need to watch out to always have a balanced on/off couple count. You can override that with just setting that counter to 0, and don't care about "have I thought about every exit path in that module?" That undocumented(?) feature is helpful if you're doing a lot of subroutines but don't know if everyone is behaving correctly 😊
wOOdy
-----Ursprüngliche Nachricht----- Von: ProFox profox-bounces@leafe.com Im Auftrag von MB Software Solutions, LLC Gesendet: Dienstag, 7. Mai 2019 23:33 An: profox@leafe.com Betreff: Re: Old Andy Kramek trick from WhilFest years ago...I can't recall exactly how he said it
Hi Tracy,
No, that's not it. I use thisform.lockscreen now. It was something more "nifty" or "crafty" with his approach.
I don't have any issues really; was just trying to remember what was "cool" about his trick/tip that was better than Thisform.refresh. Just curiosity.
Thanks, --Mike