Hello Robert
Thanks for reporting this.
I knew that the model's internal name was being used for the exported
filename, but none of us thought that would be a problem, as you have
now found. The error due to special characters will certainly have to
be taken care of; I'll see what I can do, or else it will have to be
a task of Bob's ;-)
(All this was, I think, carried over from duplicating the first
exporter, maybe Povray or the first Vrml. Actually, the Povray
exporter has a dialog; that's a line I can follow; more news on this
later on the day)
What we would actually need is a proper export dialog. That has being
mentioned once in the dev-list. But that needs someone willing to
code it (I most certainly cannot do that).
Maybe doing the export using the command line ("write" command) would
avoid your problems, since then you choose the filename as part of
the command.
As for the target folder, what you describe is just an effect of Java
standards; it uses the folder where Jmol.jar was run from, in the
case of the app. I'm not sure what the signed applet would do, but
likely the same, use the default Jmol directory.
Sorry for your trouble; it will lead Jmol in the best direction of
improvement,
though.
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Jmol-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jmol-developers
