Lib in subfolder: "Library xyz.lbr was not found on the current library path(s)"

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Hello,
Not sure if this is a bug, but I noticed that when right-clicking a component in the schematic and selecting "open component", this generates an error message "Library xyz.lbr was not found on the current library path(s)" for libraries, that are in sub-folders of my custom library paths. It works if I add every sub-folder into the library path.
This is a bit strange because they are found when using the add command, but not by right-clicking them and opening them (which saves a lot of time compared to finding them in the Control window!).
(Not sure if this possible already, but it's nice if this also works when there are spaces in the file and the path.)
I use EAGLE 9.3.0 on Windows 7 Enterprise SP1 64 bit.
Here are some screenshots (sorry, I read that there is no simple way to change the UI language, so they're not in English):
1. my path settings:
2. control window - library "example_lib.lbr" in sub-folder is loaded (project-based libraries to make sharing them with others possible - in a version as they are in the current project):
3. right-clicking a device which is in the example_lib.lbr and selecting "open device":
4. error message "Library example_lib.lbr was not found on the current library path(s)"
Best regards,
Matthias
Related topics, but not the same:
Library Not Found Error (06-25-2017)
(problem was, that the libraries are managed libraries. I disagree with jorge.garcia in message 6 that it's not useful to use the "open device" command for managed libraries because they are read-only. In fact, many times I want to open a library that I didn't create on my own to double-check all the dimensions in the footprint or the pin/pad relationships or copy parts of it to my own library. Drag'n'dropping them out of the control window became much easier with Autodesk's Eagle - thank you a lot! - however, it is really handy to have this command in the context menu right where the part is used.)
Problème Update Library on MacOS X still exist....(Eagle 9.1.2) (08-05-2018)
(problem was that the author renamed the component)
Eagle 9.1 My own library opens in read-only mode (07-05-2018)
(problem was that the user placed his own libraries within the default library path which I didn't)
P.S.: the session timeout for this forum is way to short - I was logged out while writing this and my post was deleted because why not - fortunately I copied everything before clicking post