Procedure files write-protect automatically after X amount of time. Can I turn this off?

Share icon

I'm pretty sure this is an OSX problem, because I get similar messages when editing pdfs I've not opened for a while. Now onto the details:

Often when I try to edit an existing procedure file, I get a dialog window saying it's write-protected, which means I have to click the pencil icon then I'm ok to proceed. Is there a way to turn off this irritating behaviour? I would like procedures I have told to be write-protected to remain so, and those I haven't set as write protected to also remain so. I'm sure this doesn't happen on Windows.

Any tips?
This happens on windows, at least between instances of IGOR if not during the same instance.. No idea how to turn it off, I just click the pencil icon first thing when I open a procedure I am going to be editing.

August 29, 2012 at 10:40 am - Permalink

There is no automatic write-protect after X amount of time.

Global procedure files (in "Igor Procedures") and #included procedure files are always opened write-protected so that casual users don't modify them. There is no way to change this.

August 29, 2012 at 10:41 am - Permalink

Thanks Howard! Some if not all of the affected procedures I've #included.

Could this be added to the wish list as an option? Something like

#include/WP "casual_users_do_not_edit" // current Igor behaviour: open write-protected
#include "go_to_town_this_is_my_procedure_Im_still_working_on" // open un-write-protected

August 30, 2012 at 01:53 am - Permalink

notwhatucallanatural wrote:
Thanks Howard! Some if not all of the affected procedures I've #included.

Could this be added to the wish list as an option? Something like

#include/WP "casual_users_do_not_edit" // current Igor behaviour: open write-protected
#include "go_to_town_this_is_my_procedure_Im_still_working_on" // open un-write-protected


I would suggest instead ...

#include // current include
#include/NP // non-protected mode, anyone can edit
#include/PP="xxxx" // password protected against edit, with field encrypted (somehow)


I actually do not like the non-protected or even the password protected modes even though I suggest them as an option. Smart users do know how to open Igor Pro files with external editors as needed, and changing certain procedure files "on the fly" should be strictly verboten as needed to avoid even otherwise seasoned users from shooting themselves in the foot (so to speak).

--
J. J. Weimer
Chemistry / Chemical & Materials Engineering, UAHuntsville

August 30, 2012 at 08:47 am - Permalink

Quote:
Could this be added to the wish list as an option?


I'll keep it in mind for the next time I am working on that area of the program.

August 30, 2012 at 09:10 am - Permalink