I would like to know if there is some way of knowing precisely what events and the timing within a given program.  Like a hierarchy chart.  When I click on a button, I understand that a onclick event will fire.  But I am talking about understanding all the events that happen kind of under the covers.  LIke when a form is displayed with a grid and the ondraw event happens, or when a tab is clicked and all the under the under-the-covers events that are fired when going from tab to tab.  There must be a mapp
ing of all this stuff.  There must be someway of knowing in the context of a running program, what is going to happen next.  

It seems to me that unless I understand the timing of all these events, then I am just touching the surface of the capabilities of my programming in Delphi.  How can I understand this, anybody have any tips?

On Tue, 14 Oct 2014 19:41:27 -0700, Owen H wrote:
> Unfortunately, there are many things that happen under the covers that are
> not necessary tied to specific events for objects.  There use to be a
> tool called WinSight and through this tool one could watch the messages
> etc., happening.  My understanding is it did not ship with 2009 and
> beyond.   Microsoft has a tool called Spy++ but it comes with visual
> studio.  I hope the Embarcadero folks chime in on this.  You would think
> that if the Embarcadero folks wanted their product to gain market share,
> they would include some tools to aid in debugging.  Maybe they do, but I
> don't know what they are.

IMO, your only resources are MSDN documentations and Spy++. MSDN will give
you explanation of how each standard control works, most of the parts. Spy++
will show you the leftovers and undocumented ones.

As for WinSight, you are correct. It's no longer shipped since Delphi 2009.
I don't think there's other similar tool made by Embarcadero.

Owen H wrote:

> > {quote:title=Graeme Geldenhuys wrote:}{quote}
> > On 2014-10-14 22:23, Owen Huffaker wrote:
> > > How can I understand this, anybody have any tips?
> > 
> > Implement each and every event handler and log the output to a file or
> > console window. A file is probably better. Then review the log.
> > 
> > 
> > Regards,
> >   - Graeme -
> 
> 
> Unfortunately, there are many things that happen under the covers that are not necessary tied to specific events for objects.  There use to be a tool called WinSight and through this tool one could watch the messages etc., happening.  My understanding is it did not ship with 2009 and beyond.   Microsoft has a tool called Spy++ but it comes with visual studio.  I hope the Embarcadero folks chime in on this.  You would think that if the Embarcadero folks wanted their product to gain market share, they wou
ld
>  include some tools to aid in debugging.  Maybe they do, but I don't know what they are.

I know it's boring and time-consuming, but don't Enable Debug DCUs and F7 get the job done, with time to digest the importance (or lack of) of every step?

-- 
Tredmill

> {quote:title=Graeme Geldenhuys wrote:}{quote}
> On 2014-10-14 22:23, Owen Huffaker wrote:
> > How can I understand this, anybody have any tips?
> 
> Implement each and every event handler and log the output to a file or
> console window. A file is probably better. Then review the log.
> 
> 
> Regards,
>   - Graeme -


Unfortunately, there are many things that happen under the covers that are not necessary tied to specific events for objects.  There use to be a tool called WinSight and through this tool one could watch the messages etc., happening.  My understanding is it did not ship with 2009 and beyond.   Microsoft has a tool called Spy++ but it comes with visual studio.  I hope the Embarcadero folks chime in on this.  You would think that if the Embarcadero folks wanted their product to gain market share, they would
 include some tools to aid in debugging.  Maybe they do, but I don't know what they are.

On 2014-10-14 22:23, Owen Huffaker wrote:
> How can I understand this, anybody have any tips?

Implement each and every event handler and log the output to a file or
console window. A file is probably better. Then review the log.


Regards,
  - Graeme -