I also saw this quirky window behavior when I displayed the output of a stable net on a remote linux-based machine. For me it also had something to do with bit depth, although I still don't understand all the issues there (dx supported bit depth/linux or machine display supported bit depth). Anyway, with SA's help the bit depth compatibility thing got worked out (or otherwise went away), but I had to manually delete the Imagetool icon in the net and replace with a fresh one in order for the behavior to really disappear. Wierd, but it worked. I've had experience with the Imagetool not recovering completely from an unknown, messed up state even when all the settings are appropriate (and the same, apparently, between fresh and stale imagetool). I'd give this a try even before messing with the bit depth (and after, if bit depth change doesn't work).
Sharon On Jul 27, 1:58pm, David L. Thompson wrote: > Subject: Re: [opendx-users] I have a problem using the image module > I saw this when X was running in an unsupported bit depth. For > example, before dx supported 32 bit, it would do what you describe. I > would check your X setup and see what bit depth it is running in. > > David > > >Hello, > > I have encountered a problem using OpenDx under linux. I have somehow > >modified my environment or the program or something so that the image tool > >is misbehaving. > > > > When logged onto the console of the machine, no matter what > >network I run, either on the local machine or from a remote machine, the image > >module will produce a window labeled "Image" with the graphics in it, but > >without the menu bar at the top "File Execute ...". If I click on the > >image module, another "Image" window appears with the menu bar, but without > >a picture of the data. > > > > If I run DX on another display, but with the same network, > >I do not have this problem. > > > > The account on the machine with the problem is different from the > >account on the other machines, so environment variables and files are a > >definite possibility, but I can't find anything that obviously causes this. > > > > I would appreciate if if anyone has any suggestions on how I can > >fix this. > > > >Thanks > >Dan > > -- > ............................................................................. > David L. Thompson The University of Montana > mailto:[EMAIL PROTECTED] Computer Science Department > http://www.cs.umt.edu/u/dthompsn Missoula, MT 59812 > Work Phone : (406)257-8530 >-- End of excerpt from David L. Thompson
