Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Object destruction
Message
From
01/02/2014 09:30:39
 
 
General information
Forum:
Visual FoxPro
Category:
Forms & Form designer
Environment versions
Visual FoxPro:
VFP 9 SP1
OS:
Windows 8
Network:
Windows 2008 Server
Database:
Visual FoxPro
Application:
Web
Miscellaneous
Thread ID:
01592795
Message ID:
01592830
Views:
62
>>>>>
thisform.lockscreen = .t.	    && this one does not (noticeably) save time, but the view is better
>>>>>
>>>>>lnN = 0
>>>>>
>>>>>with thisform.oCntPZChart
>>>>>	for each loO in .objects
>>>>>		wait window m.lcC + padl( m.lnN, 4, '0' ) nowait
>>>>>		lnN = m.lnN + 1
>>>>>		.removeobject( m.loO.name )
>>>>>	next
>>>>>endwith
>>>>>with thisform.oCntPage1
>>>>>	for each loO in .objects
>>>>>		wait window m.lcC + padl( m.lnN, 4, '0' ) nowait
>>>>>		lnN = m.lnN + 1
>>>>>		.removeobject( m.loO.name )
>>>>>	next
>>>>>endwith
>>>>
>>>>And without wait window? Should be even faster.
>>>
>>>Has been tested. The performance was totally similar. Do this test:
>>>
for n = 1 to 10000
>>>   wait window str(n) nowait
>>>next
>>>On my machine it is ready within one ... second.
>>
>>Does making the window invisible before closing help?
>
>Also tried. There was no effect at all.
>Also tried: lockscreen True. The visual effect is better, but no measurable performance gains, to my surprise.

In WinDev I am making extensive use out of the performance profiler which details the code and functions that are consuming time in any process. I have not used that in VFP but maybe the VFP profiler can help identify specific lines/functions?
In the End, we will remember not the words of our enemies, but the silence of our friends - Martin Luther King, Jr.
Previous
Reply
Map
View

Click here to load this message in the networking platform