difficulty opening .mrv file

Hello,





Myself and colleagues are having trouble opening the attached file (.mrv) which was created from MarvinSketch.





If we attempt to open with MarvinSketch, nothing apparently happens.


If we attempt to open with MarvinView we get the following error message:





java.lang.NullPointerException


at chemaxon.marvin.modules.CmlImport.initUsingAtomArrayAttributes(Unknown Source)


at chemaxon.marvin.modules.CmlImport.readMol00(Unknown Source)


at chemaxon.marvin.modules.CmlImport.readMol0(Unknown Source)


at chemaxon.marvin.modules.MrvImport.readChemicalStruct(Unknown Source)


at chemaxon.marvin.modules.MrvImport.readDocument0(Unknown Source)


at chemaxon.marvin.modules.MrvImport.readDocument(Unknown Source)


at chemaxon.formats.MolImporter.readDoc(Unknown Source)


at chemaxon.marvin.View.readStream(Unknown Source)


at chemaxon.marvin.View.main(Unknown Source)


at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)


at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)


at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)


at java.lang.reflect.Method.invoke(Method.java:324)


at com.zerog.lax.LAX.launch(Unknown Source)


at com.zerog.lax.LAX.main(Unknown Source)








I have tried two versions of the sketch/view, that is 3.4.3 and 3.5.5 and it appears the same behaviour occurs. Can you please indicate where the problem lies - in the file or the application(s)?





Cheers,


Inhibox.

Thanks for the bug report. We will check it.

We have checked the issue. It's not a bug. The problem is in your mrv file.


There were some extra line breaks in the mrv source.


Each attribute of the <atomarray> tag should be in one line (without line break).


I have found extra line breaks in x3, y3 and z3 attributes.


I have corrected your mrv (see the attached file).


I don't know how you created this file. My theory is that you must have copied the mrv source into an editor that gave extra linebreaks into the code.

Thank you once again for your excellent support. I should know what to look out for next time around!





Cheers,


Daniel.