Why not? It's purpose is to help you track down the slow parts of your application.
On 6 September 2017 11:58:29 GMT-04:00, Dave Crozier <[email protected]> wrote: >Unfortunately, the coverage profiler doesn't help Frank. > >Koen's suggestion of GoFish4 has given me more than enough information >to get going on tracking down the poor performance. > >Dave > >-----Original Message----- >From: ProFox [mailto:[email protected]] On Behalf Of Frank >Cazabon >Sent: 06 September 2017 16:30 >To: [email protected] >Subject: Re: Event logging > >You could use the coverage profiler. > >Frank. > >Frank Cazabon > >On 06/09/2017 11:16 AM, Dave Crozier wrote: >> Fellow Foxers, >> Just a little aside to late Wednesday afternoon: >> >> I have a heavyweight data entry program in VFP written which supports >one monster form with pageframes stacked inside each other each page >containing various visual classes down to up to 10 levels. >> >> This form is now showing its age as it has been added to over some 20 >years and never been streamlined or optimised in any way. The main >problem is that the switching from the main form pageframe onto each of >the 10 tabs in the pageframe is somewhat slow running on the network >and I am sure that it is all the Draw(), Paint() and refresh repeat >calls that are affecting it. >> >> So, I have decided to rip it apart and find out just where the >majority of the repeat "refresh" coding is being done. >> >> I thought I could initially use the event Logger but it doesn't log >calls to any refresh methods so then I turned my mind to the coverage >logger which doesn't really help me at all. >> >> Anyone any ideas as to how I can easily accumulate the calls to the >various controls refresh methods and get some simple statistics to have >a look at where all the processing effort is going? >> >> All I can think of is to programmatically bind a "logging procedure" >event to each control's refresh event and then log the results into >something like a csv table for further analysis or at worst, log events >by collecting information from the refresh events in the base classes >for each control but that would be very long winded. >> >> Any other ideas other than those mentioned? >> >> Dave >> >> [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
