debugging focus problem

[degs]

Hi,

Can anyone suggest what debug channels would be useful for locating the cause 
of focus or mouse input routing problems?

thanks
-- degs

[Mike McCormack]

You'll get most of the information you want from:

--debugmsg +x11drv,+win,+message

The problem is you'll get too much. Sometimes you can pipe the output 
through egrep...

Mike

degs wrote:
> Hi,
>
> Can anyone suggest what debug channels would be useful for locating the cause 
> of focus or mouse input routing problems?
>
> thanks
> -- degs

[degs]

On Monday 29 April 2002 22:50, Mike McCormack wrote:
> You'll get most of the information you want from:
>
> --debugmsg +x11drv,+win,+message

Thanks - that looks like it its going to be useful.
> The problem is you'll get too much. Sometimes you can pipe the output
> through egrep...

Its getting stuck pretty early on so there's not *that* much to wade 
through...
> Mike
>
> degs wrote:
> > Hi,
> >
> > Can anyone suggest what debug channels would be useful for locating the
> > cause of focus or mouse input routing problems?
> >
> > thanks
> > -- degs

[Andreas Mohr]

On Mon, Apr 29, 2002 at 10:33:04PM +0100, degs wrote:
> Hi,
>
> Can anyone suggest what debug channels would be useful for locating the cause 
> of focus or mouse input routing problems?

--debugmsg +relay,+win,+msg,+sendmsg,+message,+event,+x11,+x11drv,+cursor
Mainly relay, event, msg, x11drv, I think.

Then have a look at search.microsoft.com to locate some docu about one or
another thing, and that's it.

[degs]

On Monday 29 April 2002 23:06, Andreas Mohr wrote:
> On Mon, Apr 29, 2002 at 10:33:04PM +0100, degs wrote:
> > Hi,
> >
> > Can anyone suggest what debug channels would be useful for locating the
> > cause of focus or mouse input routing problems?
>
> --debugmsg +relay,+win,+msg,+sendmsg,+message,+event,+x11,+x11drv,+cursor
> Mainly relay, event, msg, x11drv, I think.
>
> Then have a look at search.microsoft.com to locate some docu about one or
> another thing, and that's it.

Thanks. It looks like mouse messages are going to the window's parent rather 
than the window itself. I'm not very familiar with win32 so I don't know if 
this is usual or not but it seems a bit odd. Anyway - at least I have an idea 
what's going on now.

-- degs