RE: ProFox Messages are not showing up

I get this message every once in a while, with the last one on 5/1 at 8:49 am. Fletcher Fletcher Johnson fletchersjohn...@yahoo.com LinkedIn.com/in/FletcherJohnson twitter.com/fletcherJ strava.com/athletes/fletcherjohnson 408-946-0960 - work 408-781-2345 - cell -Original Message- From:

Re: Old Andy Kramek trick from WhilFest years ago...I can't recall exactly how he said it

At 19:25 2019-05-07, "MB Software Solutions, LLC" wrote: On 5/7/2019 8:13 PM, Gene Wirchenko wrote: >     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

Re: Old Andy Kramek trick from WhilFest years ago...I can't recall exactly how he said it

On 5/7/2019 8:13 PM, Gene Wirchenko wrote: 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. When

RE: Old Andy Kramek trick from WhilFest years ago...I can't recall exactly how he said it

Hi Gene, yepp, either be very serious about the counterparts, or just issue a thisform.lockscreen = 0 and don't give a shit about that counterparts; just flip it to OFF in any situation. wOOdy -Ursprüngliche Nachricht- Von: MB Software Solutions, LLC Gesendet: Mittwoch, 8. Mai

RE: Old Andy Kramek trick from WhilFest years ago...I can't recall exactly how he said it

At 13:20 2019-05-07, "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. I set .lockscreen to .t. at the beginning of instantiating a form and back to .f. after

AW: Old Andy Kramek trick from WhilFest years ago...I can't recall exactly how he said it

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

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

RE: Old Andy Kramek trick from WhilFest years ago...I can't recall exactly how he said it

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

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