On Tuesday 10 June 2003 09:16, Peter Murray-Rust wrote: > Unless I have missed a window or dialog, when Jmol fails to Open a file > successfully there is no obvious report of problems and no indication that > the Open has failed (the existing molecule or contents remain). It could be > useful to have a dialog which announces the failure - and where possible > diagnostics. > > I encountered the problem when reading CML files without an XML declaration > (<?xml version="1.0" ... ?>). It seems that Jmol requires this. (It's not > required by the XML spec). It is a useful way of announcing that a file is > XML but I suspect that many CML files don't have it and users don't > understand why Jmol fails. If possible I would recommend that it was not > mandatory and that the file type was specified by the file selector and/or > suffix.
The CML reader does not require the <?xml> line... i.e. I never told it that it should do that... Also, Jmol is programmed to report the errors it found while parsing the file... The fact that Jmol does not show any content, might indicate that the file *is* parsed but that the content is not recognized... You can try turning on debugging and see if anything strange is happening in the Jmol console (by doing java -Dcdk.debugging=true jar jmol)... Otherwise, can you send me the CML file you are trying? Maybe I can find the problems quickly... Egon ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ Jmol-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jmol-developers
