Which version of Motif are you using. There was a problem I found in
OpenMotif's tool tip code that I got them to fix, but I think in
order for it to be fixed you need 2.2.2.
That is not the problem I see.
As you note, I did have to execute to make it appear. I guess I
always load, execute, quit, to do tests--force of habit.
On MacOS X, I can't build with -O2 because of some problems with
their optimizing routines that cause other problems--none the less,
have you discovered a fix for what I see--or are you saying that it
isn't an error?
David
On Mon, 2003-06-23 at 17:55, David Thompson wrote:
Start up, load /usr/local/dx/samples/programs/AutoColor.net, quit.
That's enough to see it happen. For me.
David
...still looking.
I see the XtError message at exit that you mentioned but only
if I execute AutoColor.net. Loading and quiting doesn't do it
for me.
As I mentioned before, I recall seeing this error message but
that it went away (somehow). Now I observe that my build
with source unchanged but with a few files built with
-g (instead of -g -O2), doesn't exhibit the behavior.
I have noticed that my malloc checker always complains
about a memory problem in libXt when dxui exits that
involves a call to XtPopdown from Motif's tool tip code.
Martin
--
.............................................................................
David L. Thompson Visualization and Imagery Solutions, Inc.
mailto:[EMAIL PROTECTED] 5515 Skyway Drive, Missoula, MT 59804
Phone : (406)756-7472
