Eagle 9.1 My own library opens in read-only mode

[rg944]

Hello Eagle Team,

I configured in Eagle 9.1 a path to a directory with libraries created by myself.
The folder with the libraries shows up in the Control Panel. Opening one of the libraries shows in the lib Editor the message "Resources and example files are opened in read-only mode. Choose File->Save As... to save changes to this document". The same behaviour as in this video. But my own lib is not an example file. The lib Editor shows also the file path to a local temporary directory.

Opening the device of that library from a layout shows the error message, that the containing library can not be found. This is not the usual behaviour of Eagle.

Opening the same lib from Windows Explorer opens the lib Editor and the lib can be modified and saved. No read-only message.

How can I deactivate the read-only feature of Eagle?

Thank you for any help.

Best regards

Richard

[rachaelATWH4]

Hi Richard,

I just tested this with a part from one of my custom libraries and it seems to be working ok for me. Can you give more details of your setup?

Which OS are you running? 

Can you give a screenshot showing your directory configuration?

Screenshots of the error dialogs?

Maybe you could record a screencast showing the issue occurring in case that gives any further clues?

On thing I wondered, are there any non-standard characters in the path to the directory where the the libraries are stored? Or maybe spaces?

Best Regards,

Rachael

[andrii.anpilogov]

Hi @rg944

Indeed it looks weird.

Could you share your directories setup and path to the library file you have problem with?

Thanks

[rg944]

Hello Rachael,

thank you for the answer.

OS: Win7

Eagle Version 9.1.0 Premium License

My directory configuration, Only a library folder is added

Libraries show up in Control Panel

Open library from Control Panel shows the library editor. Here you can see the Temporary Directory and the Read-Only Message.

This happens to each library in that directory.

Best regards

Richard

[andrii.anpilogov]

Hi @rg944

Thanks for sharing this.

You placed your own libraries in EAGLE installation folder.

You should put it into your own folder. Any file located in EAGLE installation directory is read-only.

Regards

[rachaelATWH4 · Accepted solution]

You appear to be opening libraries from the SETS/lbr/SETS folder which is within the EAGLE install directory. This area is read only. You need to put your personal libraries in $HOME/EAGLE/libraries and then they should open correctly.

Best Regards,

Rachael

[rg944]

Hello Rachael and Andrii,

Your Solution works for me.

I was used to put that folder in the Eagle directory, as I did it for years in previous Eagle Versions.
Lesson is learned. No more customization in the Eagle directory.

Thank you for the quick response.

Greetings

Richard

[rachaelATWH4]

---

@rg944 wrote:

I was used to put that folder in the Eagle directory, as I did it for years in previous Eagle Versions.
Lesson is learned. No more customization in the Eagle directory.

This is a change in 9.1 which is intended to stop people creating setups where they then have to copy lots of stuff over every time they update EAGLE and also to ensure the integrity of the core installation as previously the files installed with EAGLE were often modified by users which makes life for the support team a nightmare sometimes.

This is a very positive change which should have been done long ago (decades!) and one which most experienced users gravitated towards in their own setups anyway, but this now enforces good practice for all users from the outset.

Best Regards,

Rachael

[rg944]

Hello Rachael,

You should also document somewhere that the directory for customization should not contain the string "EAGLE 9.1.0"!

For example:

libs in "c:\EAGLE 9.1.0_Custom" are loaded in read-only mode.

libs in "c:\EAGLE_Custom_9.1.0" can be modified

I hope you have better string compare methods implemented on more sensitive areas (like user authentication). If not, the nightmares will not stop ... 

Best regards

Richard

[andrii.anpilogov]

Hi @rg944

This is a bug. Thanks for highlighting this!

[rachaelATWH4]

---

@rg944 wrote:

Hello Rachael,

You should also document somewhere that the directory for customization should not contain the string "EAGLE 9.1.0"!

---

Nope, not me, I am not an Autodesk employee, I am an EAGLE user like yourself 

I'm sure that'll get fixed by Autodesk now they are aware. But really you should be putting your custom files in a non version specific folder otherwise you are effectively undoing the positive change in segregating versions specific installed resources from user defined resources which should persist independently of any particular EAGLE version changes.

[rg944]

Hello Rachael,
I am sorry. I thought I saw the Autodesk Logo in your Profile, but it was Andrii.
I changed my configuration and will see, I think it will work for me in the future.