Years ago (2003?) at WhilFest (Great Lakes Great Databases Workshop), speaker and Fox great Andy Kramek showed us some cool alternate refresh/repaint routine, and I think it was where he said LockScreen = .T. and then set the _screen.visible = .F., but can't recall.
Does anybody remember that? This is one of those things that has always bugged me and I wanted to get resolution on it.
tia, --Mike
--- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
Both ThisForm and _Screen have the LockScreen property. If you are updating a lot of things, you can flip it to .T. then flip it back to .F. when done.
Remember, if you _Screen.LockScreen, then the user moves the form, it leaves bits of the form outline behind.
I've never changed the visibility of _Screen after I made it visible.
Oh, if there is an ActiveX object on the form, LockScreen does nothing to help it. Some of them may expose the right hWnd value to allow you to use the API for it.
HTH, Tracy
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of MB Software Solutions, LLC Sent: Tuesday, May 07, 2019 4:04 PM To: profoxtech@leafe.com Subject: Old Andy Kramek trick from WhilFest years ago...I can't recall exactly how he said it
Years ago (2003?) at WhilFest (Great Lakes Great Databases Workshop), speaker and Fox great Andy Kramek showed us some cool alternate refresh/repaint routine, and I think it was where he said LockScreen = .T. and then set the _screen.visible = .F., but can't recall.
Does anybody remember that? This is one of those things that has always bugged me and I wanted to get resolution on it.
tia, --Mike
--- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
[excessive quoting removed by server]
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
On 5/7/2019 4:20 PM, Tracy Pearson wrote:
Both ThisForm and _Screen have the LockScreen property. If you are updating a lot of things, you can flip it to .T. then flip it back to .F. when done.
Remember, if you _Screen.LockScreen, then the user moves the form, it leaves bits of the form outline behind.
I've never changed the visibility of _Screen after I made it visible.
Oh, if there is an ActiveX object on the form, LockScreen does nothing to help it. Some of them may expose the right hWnd value to allow you to use the API for it.
HTH, Tracy
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of MB Software Solutions, LLC Sent: Tuesday, May 07, 2019 4:04 PM To: profoxtech@leafe.com Subject: Old Andy Kramek trick from WhilFest years ago...I can't recall exactly how he said it
Years ago (2003?) at WhilFest (Great Lakes Great Databases Workshop), speaker and Fox great Andy Kramek showed us some cool alternate refresh/repaint routine, and I think it was where he said LockScreen = .T. and then set the _screen.visible = .F., but can't recall.
Does anybody remember that? This is one of those things that has always bugged me and I wanted to get resolution on it.
tia, --Mike
This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
[excessive quoting removed by server]
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
At 13:20 2019-05-07, "Tracy Pearson" tracy@powerchurch.com wrote:
Both ThisForm and _Screen have the LockScreen property. If you are updating a lot of things, you can flip it to .T. then flip it back to .F. when done.
I set .lockscreen to .t. at the beginning of instantiating a form and back to .f. after the setup. I have not looked at the speed-up recently, but in my testing years ago, it made about a 20% difference.
I do not use it otherwise.
[snip]
Sincerely,
Gene Wirchenko
-
Gene Wirchenko -
juergen＠wondzinski.de -
MB Software Solutions, LLC -
Tracy Pearson