April 06, 2020
What are the release notes for ChemDraw v19?
- ChemDraw allows users to enable and disable add-ins. The enable/disabled state of add-ins is persisted between launches of ChemDraw, but not between versions. These add-ins can be disabled, and this state will be persisted by ChemDraw.
- When ChemOffice Suite is installed in a 64-bit system, it installs a 64-bit version of the ChemDraw executable also in addition to the usual x86 version. This 64-bit executable was qualified only to the extent of its full functioning for ChemDraw for Excel features. Hence, it is recommended to use only the default x86 (32-bit) version of ChemDraw for all other functionalities until a full support is declared for the 64-bit version.
- There is no 64-bit version of the Python Extension available to install along with the 64-bit ChemScript / Python. Hence, to continue using the Python Extension feature in ChemFinder even after installing ChemScript 64-bit, re-run the installer package and select to install the 32-bit version of ChemScript, Python and Python Extension. Both the 32-bit & 64-bit versions of ChemScript can co-exist in the same 64-bit system.
- ChemDraw Cloud feature will work only if your Windows system contains Internet Explorer 11 installed. Any system containing a prior version of Internet Explorer needs to be upgraded to version 11 for the use of ChemDraw Cloud feature.
- Exporting files that contain images with a shadow or opaque effect to EPS with color option set to RGB and CYMK works fine. However, for the images whose color option is set to Grayscale or monochrome, the image quality of the exported image will be bad.
- IUPAC atom numbering scheme after Structure to Name conversion will be displayed only in the expanded regions of the molecule.
- The Paste as HELM feature does not support parsing of the following information in HELM strings:
- Monomer ambiguity
- Hydrogen parings for DNA
- List of polymer groups
- Extended annotations
- The Enhanced Retrosynthesis feature may not provide all desired reaction results if:
- Query product contains stereochemistry undefined stereo-center atoms.
Workaround: For optimum results, present such queries with all stereo-center atoms defined using relevant stereo-bond connectivity.
- Query product contains erroneous atom definition (e.g., valence errors, wrong atom types etc.).
Workaround: Make sure to rectify atom errors in the query product before doing enhanced retrosynthesis.
- Enhanced Retrosynthesis results will show only the queried product as the end product of each reaction even if more side products are expected for any reaction.
- Cannot import pre-18 version of ChemScript module in default Python after installing ChemScript 19.1 64-bit. The ChemOffice Suite 2019 ships with 32 and 64-bit versions of ChemScript and Python, which in turn requires that a version of ChemScript is used with bitness matching the "default" Python version. The ChemScript Python library will not load if it's bitness does not match that of the default Python from which it was launched. This issue can be seen if 32-bit ChemScript is used when the last installed version of Python is 64-bit and vice versa.
Workaround: Run the bit-correct version of Python IDLE and invoke the ChemScript Python script through it. This can be done by creating a 32-bit Python IDLE shortcut for running 32-bit Python. Windows 10 steps are given below:
- Go to the Python installation path "C:\Python32\Lib\idlelib" and locate the file "idle.py".
- Right-click on "idle.py" and choose "Send to > Desktop (create shortcut)".
- Specify a name for the shortcut (For example, "IDLE (Python GUI) 32-bit").
- Right-click on new shortcut in desktop and choose “Properties”.
- Set "Target" in Shortcut tab as: C:\Python32\python.exe C:\Python32\Lib\idlelib\idle.py.
- Set "Start in:" in as: C:\Python32\.
- Click "Apply" and "OK".
or... Alternately: Double clicking on the shortcut will launch the 32-bit version of Python IDLE and now if you open any other script through the ‘File>Open’ menu, it will be run as a 32-bit version. You can even move this file to "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Python 3.2" so that it will appear in "All Programs->Python 3.2".
- It was observed that ChemDraw OLE editing in MS Office 2010/2013/2016/2019 applications failed to work after installing Windows 10 Anniversary update (1607).
This was later fixed by Microsoft update: Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4013429) (OS Build 14393.953)
- The ChemDraw & Chem3D Plugins are no longer part of any ChemOffice/ChemDraw 19.1 Windows packages (ChemOffice, ChemDraw Professional & Prime). However, users can continue to use any older version of the ChemDraw & Chem3D Plugin along with ChemDraw 19.1 applications. The ChemDraw & Chem3D ActiveX controls are still included and can be used with IE.
- When trying to add/edit a structure in a ChemOffice sheet that was created in a system with opposite bit architecture (32 or 64) compared to the current system bit architecture (64 or 32) via ‘Edit in Excel’ option from Office 365 Online portal, a (1) ‘Cannot run Macro …’ error or (2) ‘Link update’ failure may appear by blocking that operation. Workarounds:
- Keep your local MS Excel running before selecting the ‘Edit in Excel’ option from Office 365 online portal.
- Choose Edit Links option and remove the existing *.xla link by clicking the Break Link button. Now you will be able to edit the contents in that file and save the changes. This step may need to be repeated in the other system if you want to edit the same document there.
- When a ChemDraw structure is copied from Keynote/Pages/Numbers document and pasted to ChemDraw Document, it loses the structure information.
- The contents in a document uploaded to ChemDraw Cloud with a Japanese file name may lose when modify contents in it and save. This issue will not appear if the file name is in English.
- ChemScript19 may not work properly after installing ChemOffice on a Windows 8.1, 64-bit machine.
Workaround: Reboot your machine after installing ChemOffice on a Windows 8.1, 64-bit system. ChemScript should operate normally.
- With systems running Windows 8.1 (64-bit) and Visual Studio C# 2010 Express, the demo (Demo.csproj) might crash due to a possible error in VS 2010 Express conversion process.
Workaround: Manually remove the "Demo.exe.config" file from the "C:\ProgramData\PerkinElmerInformatics\ChemOffice2019\ChemScript\Examples\Demo”. This will prevent this issue from recurring on systems with Visual C# 2010 Express.