Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Saving & Retrieving VFP Form positions
Message
From
15/05/2002 00:41:23
Dragan Nedeljkovich (Online)
Now officially retired
Zrenjanin, Serbia
 
General information
Forum:
Visual FoxPro
Category:
Windows API functions
Miscellaneous
Thread ID:
00655670
Message ID:
00656710
Views:
16
>>And just my personal preference here: instead of setting the four properties one by one, I rather call thisform.move(nTop, nLeft, nHeight, nWidth). The resize event happens only once, so if there's some code there, it gets executed only once.
>
>I agree you should do this if you want the resize event to fire at all. Simply setting the properties in the Init, doesn't fire the Resize event. If you set it in the Activate event (or after), Resize fires.
>
>I also didn't find a problem with the Resize event firing only once. Because of the single threaded nature of VFP, I believe the method that set the properties would finish before the Resize event was allowed to fire. Do your tests show something different?

I've seen it fire twice in the debugger, but didn't run any particular tests to see if it was the influence of the "objective observer" or really happening twice. I've recoded those things to use the move() just to make sure. IAC, I figure that one method call (even with four parameters) would be more lightweight than setting four properties, at least one of which may trigger some events and/or code.

back to same old

the first online autobiography, unfinished by design
What, me reckless? I'm full of recks!
Balkans, eh? Count them.
Previous
Reply
Map
View

Click here to load this message in the networking platform