From: Bob H. <ha...@st...> - 2007-10-25 05:55:22
|
Nico, Jmol 11.3.38 is ready to go. It addresses all of Rolf's findings. There are now three antialias settings: antialiasDisplay TRUE/FALSE [default TRUE] antialiasImages TRUE/FALSE [default FALSE] antialiasTranslucent TRUE/FALSE [default FALSE] The third applies to either images or the display. It cleans up translucent objects. It has no effect unless antialiasDisplay or antialiasImages is also set TRUE. Memory requirements are significant, in multiples of (width) * (height) 32-bit integers: antialias OFF ON-translucent ON+translucent no translucent 2 8 8 objects with translucent 4 10 16 objects Note that no antialising at all is required for POV-Ray output. POV-Ray will do antialiasing on its own. Rolf -- really great testing there. The complex combination of text, draw objects, translucency, POV-Ray, and image writing was just what I needed. Please check again and see if it isn't all corrected. It's still possible that the dialog won't work for you, but it does under Windows. So you might want to do a little debugging yourself in PovraySaver.java to see what is going wrong there if this persists. I note that in Windows I get a warning that POV-Ray security doesn't like the loading of files from any random directory. But it's a simple OK/CANCEL prompt. Bob Rolf Huehne wrote: >Bob Hanson wrote: > > >>I believe Rolf's problems were due to bugs in the combinations >> >> antialiasDisplay + translucent >> antialiasDisplay + POV-Ray >> antialiasDisplay + image writing >> >>and possibly my improperly closing a buffered file writer (but I don't >>know about that). >> >>Rolf, if you could take a look at what I've just checked in for Jmol >>11.3.37, that would be great. >> >> >> >I checked out revision 8510 from SVN and tested it: > >1) Povray export with draw objects (translucent or opaque) showed the >same problem as before. But since I have found the Jmol Java Console >(unexpectedly) in the Help menu of the application (starting with a size >of 10x28 pixel!?) I can provide now the error message: > > > font was not properly assigned >2) Povray export without draw objects worked well. I got the ".pov" and >".ini" file and after starting povray with ".ini" file as parameter I >got a PNG file of the expected size. > > > check >3) Povray export using the dialog didn't start povray any more (option >is checked). There was written a ".pov" file but no ".ini" file. > > > please check; certainly working under Windows. >4) Antialiasing worked now in the application, although I didn't notice >any quality difference with the (translucent) draw objects. But the >(translucent) draw objects are all drawn in front of the other objects >with antialiasing. You can see an example at >"http://www.fli-leibniz.de/~rhuehne/1DEH-no_antialiasing.jpg" and >"http://www.fli-leibniz.de/~rhuehne/1DEH-antialiasing.jpg". > > > I had not considered translucent objects. Turns out this was a VERY tricky fix. Originally we thought translucent objects wouldn't need antialiasing, but my experimentation today suggests that they do. But that requires substantially more memory allocation. So it's an option. >5) Image export with the applet still ignores the "antialiasImages" setting. > > > This was a nasty complex interaction of settings. Should be fixed. But if not.... Bob -- Robert M. Hanson Professor of Chemistry St. Olaf College Northfield, MN http://www.stolaf.edu/people/hansonr If nature does not answer first what we want, it is better to take what answer we get. -- Josiah Willard Gibbs, Lecture XXX, Monday, February 5, 1900 |