Not sure how it occurred or how to correct, but I've lost the ability to modify an IPF file of mine due to a read-only status. Igor says I've opened the file as a read only file and it is therefore locked from modification. How do I correct this problem?
In the lower left corner of the locked procedure window there will be an icon that is a pencil with a diagonal line across it. Click on the icon to make it writable. The error message should have included this fix.
The ipf file property attributes are not read-only and I also made sure and applied that attribute to the Wavemetrics file folder as well. However, when I open the file in Igor I still do not have the ability to edit the file.
As for the symbol in the bottom left corner of the file, it is a black lock. Clicking on it, gives me no option to change.
If the same procedure is opened in two simultaneous Igor sessions, the procedure in the last session to be opened with have the lock.
We now know that the original problem was caused by the file permissions on his disk.
In fact, you are correct- when Igor opens a procedure file or a plain-text notebook file, it keeps it open. That prevents other applications (or another instance of Igor) from opening the file for writing. This is changing in Igor 7: Igor will open plain-text files, including procedure files, read the text into memory, then close the file. That will allow you to open these files in your favorite text editor or another instance of Igor.
Do you have write permission for the file?
Do you have write permission for the folder containing the file?
John Weeks
WaveMetrics, Inc.
support@wavemetrics.com
March 5, 2014 at 10:19 am - Permalink
March 5, 2014 at 10:21 am - Permalink
As for the symbol in the bottom left corner of the file, it is a black lock. Clicking on it, gives me no option to change.
Clayton
March 5, 2014 at 11:42 am - Permalink
Thanks,
Clayton
March 5, 2014 at 11:47 am - Permalink
If the same procedure is opened in two simultaneous Igor sessions, the procedure in the last session to be opened with have the lock.
March 5, 2014 at 11:51 am - Permalink
We now know that the original problem was caused by the file permissions on his disk.
In fact, you are correct- when Igor opens a procedure file or a plain-text notebook file, it keeps it open. That prevents other applications (or another instance of Igor) from opening the file for writing. This is changing in Igor 7: Igor will open plain-text files, including procedure files, read the text into memory, then close the file. That will allow you to open these files in your favorite text editor or another instance of Igor.
John Weeks
WaveMetrics, Inc.
support@wavemetrics.com
March 6, 2014 at 09:53 am - Permalink