---------------
- When using the Excel plugin, errors were seen by users like
"TypeError: This object does not support enumeration". We now
make the user deal with these.
- When using the Excel plugin, errors were intermittently raised to the
user in the form "Fatal error: <unknown>.Path" and the user could
subsequently not save the document back to Zope because the
external editor process had quit.
- Changes to documents intermittently may not have been saved back to Zope
when using any plugin that involved COM (Word, Excel, Powerpoint, etc).
- If Word was exited before a user actively saved, if there were
outstanding changes in the document being edited, those changes
would not be saved to the server despite the user answering
"yes" to the "do you want to save before you exit" dialog
presented by Word.
- The "title" attribute of the object being externally edited is
now available within the set of headers returned by EE to the
zopeedit client.
- Detecting whether the client has External Editor installed from
within IE using JavaScript or VBScript is now possible, assuming
that the client software is installed via the InnoSetup
installer. See "win32/ocx.txt" for more info.
- External Editor now compatible with objects that return a
"filestream iterator" in Zope 2.7.1+. (if upgrading: this fix
does not require an update to EE client, just the EE Zope
product).
- Properly escape hyphens in man page. Thanks to Federico Sevilla III.
- Check if the editor was launched before locking the file in Zope. This
prevents errors if the editor is closed before the lock request
completes.
- Do not ask the user what editor to use on Posix platforms. Instead just
tell the user to edit the config file. The askstring()
function does not work with a hidden root Tk window in Python 2.3.4.
Thanks to Christopher Mann.