Andy Davies wrote: > Whil said: >> I want to see >> >> customer.init() >> customer.SetCreditLimit() >> customer.ProcessNewOrder() >> customer.DisplayOrders(). >> >> in debugo > > don't you get this in the call stack?
Backchannel comments said I should be more verbose. <s> Suppose I've got a form with 30 methods in it. Well, I've 'inherited' a form, that is. So some of the 30 are local, some are inherited from a form class. Now when I run the form, 'something' happens. It's possible that the LISA methods all fire, and those are easy to trace. Although it'd be nice to see a list of which methods are local and which are running parent class code. But after that... what else happens. Hit the "Post Customer" button, and it can be arduous to trace each method, when it's being called, how many times, with what parms in different scenarios... The stack won't do this. It'll tell you the hierarchy of a single method, but not one method after another Setting a flag in each method will tell you which fire, in what order, and with what parms, if you so construct the flag that way. THAT'S what I'm after, in this tiny situation. I gotta say I'm underwhelmed by the response to this thread. Evidently I'm just about the only one working on someone's else app. <g> Whil _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** 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.
