On Thursday, December 5, 2002, at 10:15 AM, Marcus Mendenhall wrote:
Warning: the file below may have either Macintosh (cr) or Unix (lf)
line endings. I didn't check which before I attached it. You will
need to feed it to an editor to get your favorite line endings.
Thank you for the file. It was most helpful. (The Open scene graph
pointer was very helpful too!)
Since you mention the Macintosh, this brings to mind a curious problem
I am having under OSX (10.2.2) and was wondering if anyone can help. I
tried to construct a control panel with two vector interactors. Adding
the first vector interactor to a clean VPE window works fine. Opening
the control panel works fine. Adding a second vector interactors,
however, causes a problem. One can add the second vector interactor
just fine. But once the second vector item is added, opening a control
panel window at this point causes dxui to lock up. The control panel
window is opened, but it is blank and dxui no longer will respond to
inputs. The only way out is to kill dxui. This is easily repeatable on
both my Mac OSX machines, BTW (running opendx/lesstif).
I ran dxui under gdb to see if anything could be discovered and noted
that opening a control panel produces a string of error messages along
the lines of.
Major opcode of failed request: 70 (X_PolyFillRectangle)
Minor opcode of failed request: 0
Resource id in failed request: 0x0
Serial number of failed request: 5980
X Error of failed request: BadDrawable (invalid Pixmap or Window
parameter)
It does not seem to matter which sort of control panel is being
accessed. All the ones I have tried produce the same sort of error
messages in gdb. Scalar will do this too, for example. However,
multiple Scalars do not lock up dxui, whereas multiple Vectors do. I
will add that if I run dxui under gdb, then dxui does not lock up with
multiple Vector interactors.
From the error message it is clear that that would seem to be some sort
of a lesstif/Xwindows problem with opendx here and that Vector is the
lucky one to make things really bad. Has anyone seen this, and if so,
is there a fix to it? (That is to say, other than running everything
under gdb, which would be an expedient, but unsatisfactory solution
:-)) It is most annoying!
----------------------------------------------------------------------
Michael W. Martin Phone: (281) 333-2177
Draper Laboratory FAX: (281) 333-5276
2200 Space Park Dr. EMail: [EMAIL PROTECTED]
Houston, TX 77058 WWW: http://www.jsc.draper.com/
USA Mail Code: EG/Draper
----------------------------------------------------------------------
