Submitted by Anonymous on Mon, 03/12/2001 - 11:29. Developers
Does anybody know how to trap the error
object "" doesn`t have windowed ancestor
Thanx.
Mon, 07/02/2012 - 12:53
#1
Windowed ancestor error
I`m guessing that this error isn`t in your own code but is produced by Xt as a result of actions by Xm instigated by your code. You may find it useful to use http//www.motifzone.com/resources/man/XtWindowOfObject.html in the offending code. More likely, though, you`re falling into a hole in drag/drop code dealing with selections, which assume widgets. We`d need to see more of your code to isolate the problem -- and this isn`t an error that you want to trap and ignore, but one that you want to deal with by fixing the offending code.
I`d like to fix it but this is a very big application involving many windows and so I can`t show you the code. Nevertheless is it possible to trap the error by using XtAppSetErrorHandler and then try to find in the application context where is the problem ???
Thanx.
Sure. I`d be more tempted, though, to save a couple of levels in the trace and simply link with a debugged version of Xt -- or just Intrinsic.o -- and set a breakpoint in the error-issuing portion of _XtWindowedAncestor. You should also run the application synchronously so that you get a direct trace to the offending statement, without the confusion that timer-derived functions can introduce.