- From: McCrackin, Dan <dan.mccrackin@thermo.com>
- Date: Thu, 7 Apr 2005 10:02:16 +0200
- To: Amaya <www-amaya@w3.org>
Hello, I've been using your (rather excellent) Amaya as an html editor for some time now, and have recently run into an interesting bug in version 9.1. In Brief: Version: Amaya 9.1, Feb 23, 2005 under Windows XP. Description: Accidently opening a read only file prevents Amaya from ever sucessfully editing that file, unless you hunt down the cached copy and delete it. Elaboration: When a file is opened for editing, it appears that at some point you copy the file into Amaya's cache (Documents and Settings/username/amaya/....) When a save is done, this cached copy gets copied back to the actual file being edited. *BUT* if the original file was (mistakenly) write protected when first opened, then the *cached* copy is also write protected. Shutting down Amaya, un-writeprotecting the file and reopening Amaya results in Amaya trying to copy the file into its cache again, in the same spot, which fails. It then proceeds to display the old, write protected version. The only fix seems to be hunting down the write protected cached copy, and deleting it. After doing this, everything seems to be OK again. To Reproduce: To see this most dramatically, write protect an html file, then open it and try to edit it. Exit Amaya. Now replace your local write protected file with another file of the same name that is _not_ write protected. Try to edit it. You should see the _original_ write protected file instead of your local file. Just thought you should know. Thank you! Dan McCrackin Dan McCrackin, Ph.D., P.Eng. Senior Research Engineer Laboratory Automation and Integration Thermo Electron Corporation mailto:dan.mccrackin@thermo.com (905)332-2000 ext. 290 - (905)332-1114 fax (800)365-7587 toll free
Received on Thursday, 7 April 2005 07:02:26 UTC