Hi Till:
should it possible to include in the "Debug Windows", as soon as 
possible, one "Event Spy" window that shows apart the event 
informations, if it was generated by a method (ie.: :show()), it's name, 
ProcName() and ProcLine()? It is desirable that they can be browsed.
It is very hard tracking the events during the debug process.

TIA


Beling

"Carlos Beling" <beling@uai.com.br> wrote in message
news:1QAnY#qAEHA.2808@S15147418...
> Hi Till:
> should it possible to include in the "Debug Windows", as soon as
> possible, one "Event Spy" window that shows apart the event
> informations, if it was generated by a method (ie.: :show()), it's name,
> ProcName() and ProcLine()? It is desirable that they can be browsed.
> It is very hard tracking the events during the debug process.

Carlos,

Good idea, I'll think about it. However, getting this type of
information isn't trivial. Most of the events generated occur
at the operating system-level so these aren't hard-wired
into the Xbase++ kernel. What it probably comes down to
is having to peek into the event queue after each debugger
operation. Nevertheless, I've put it down on our list of
requested features. I don't think anything can be done about
it for the next snapshot or even the final release.

Regards,
  Till

--
---------------------------------------------------
ARD - Alaska Research & Development

Web:       http://www.alaska-research.com
Investors: http://www.alaska-research.com/tifund
E-Mail:    mailto:till.warweg@alaska-research.com
Contact:   mailto:info@alaska-research.com
---------------------------------------------------

Hi:
many thanks. The greatest time we spend in debugging is tracking the 
event. I tink that in first time the events we need tracking are those 
defined in Appevent.ch (more or less as "EventSpy" does).

Beling
Best regards

Technical Support wrote:
> "Carlos Beling" <beling@uai.com.br> wrote in message
> news:1QAnY#qAEHA.2808@S15147418...
> 
>>Hi Till:
>>should it possible to include in the "Debug Windows", as soon as
>>possible, one "Event Spy" window that shows apart the event
>>informations, if it was generated by a method (ie.: :show()), it's name,
>>ProcName() and ProcLine()? It is desirable that they can be browsed.
>>It is very hard tracking the events during the debug process.
> 
> 
> Carlos,
> 
> Good idea, I'll think about it. However, getting this type of
> information isn't trivial. Most of the events generated occur
> at the operating system-level so these aren't hard-wired
> into the Xbase++ kernel. What it probably comes down to
> is having to peek into the event queue after each debugger
> operation. Nevertheless, I've put it down on our list of
> requested features. I don't think anything can be done about
> it for the next snapshot or even the final release.
> 
> Regards,
>   Till
> 
> --
> ---------------------------------------------------
> ARD - Alaska Research & Development
> 
> Web:       http://www.alaska-research.com
> Investors: http://www.alaska-research.com/tifund
> E-Mail:    mailto:till.warweg@alaska-research.com
> Contact:   mailto:info@alaska-research.com
> ---------------------------------------------------
> 
> 
>