Backward compatibility
Revision as of 11:09, 9 October 2008 by AngelHerraez (talk | contribs) (new section, Backward compatibility)
Jmol intentionally keeps a strong backward-compatibility, that is, new versions try to maintain operative all things that could be done in older versions, with the same command syntax, and to also keep defaults.
However, on a few occasions there are stronger reasons to decide upon a change in the default behaviour; this can break existing scripts if you update the Jmol version.
This is a place to try and collect such discrepancies, for the benefit of the community of users and webpage/script programmers.
Please, add here any issues you have found when updating Jmol versions:
- Script commands that get broken when moved to a new version of Jmol.
- Changes in default behavior.
Make sure to specify the old and new version numbers across which the behaviour was changed.