At 07:17 PM 5/6/01 -0700, Ben Wing wrote:
Andy Piper wrote:
>
> At 12:06 PM 5/1/01 +0200, Andreas Jaeger wrote:
> >Andy Piper <andyp(a)bea.com> writes:
> >
> > > I've seen this at frame deletion and never been able to track it
> > > down. I believe its widget related becuase it came and went while I
> > > was hacking on them.
> >
> >Do you have any idea how to track it down? I can easily reproduce it
> >but don't know anything about the widget stuff.
>
> Absolutely no idea - it seems to be in the guts of the X code. I read all
> the manuals and put breakpoints everywhere, but I just don't know what the
> error is indicating.
what you need to do is recompile the Xt sources with debug info, and find the
place in the sources where this error is being issued, and set a breakpoint
there. this shouldn't be hard, although perhaps a bit time-consuming if
the Xt
sources don't recompile easily.
the message indicates that XtRemoveGrab was called on a widget without an
associated earlier XtAddGrab call. those calls are used to create menus and
modal dialog boxes -- anything that temporarily locks out input to all other
widgets.
andy, what state is the focus-handling in your code in?
It depends what you mean :) Its handled after a fashion for widgets (you
can focus in and out) but I suspect there is more esoteric X trickery needed.
andy