On 24/05/2024 11:37, ericsson.sunshine via groups.io wrote:
Thank you for the
opinions replied.
I found another method, to record all recursive paths into single
line for every recursion path in old LTspice V.17.
It's using the 'dos command window' app, then go to the lib
directory maybe 'C:\Users\account\Documents\LTspiceXVII\lib',?
type 'dir /A:D /B /S > all_dir_path.txt', all recursion paths
will be saved in the file 'all_dir_path.txt', in an ideal world ,
it should be solved once.
But it seems new problem happened, it's
1. The content that can be saved in the text box of 'Tools ->
settings -> Search Paths -> Symbol Search Path/Libray Search
Path' seems having word length bytes limits.
2. If the symbols or libs have the same name in different
recursion paths , it can tell which is the original path of the
.asc file saved in LTspice V.17 when run it in new LTspice V.24. I
guess it's because the ranking order lists in the search paths in
LTspice V.24. But I don't quite know the searching rule of this
recursive feature in LTspice V.17. -> Such that , have no idea
how to rank those path lists.
Thank you for the sharing.
Personally, I don't find the Sym path feature useful at all, because
it is non-recursive. Arguably, there is no reason why the Lib path
needs to be recursive. The standard lib\sub folder has all the
models in it, so the user's lib folder can have every model the user
has added, with the only drawback that the user needs to manually
maintain it. So, I use the Lib path feature.
I've mentioned it before, but my solution to selection of user's
symbols is:
- Keep the user's symbol folder structure similar to the default
one
- Make a symbolic link from the top level user's folder into the
top level default folder
Then the user's symbol library appears in the symbol chooser (F2)
under whatever name you give to the symbolic link - I call it
"Supplementary". Unlike the standard component libraries, the V24
Component Update process doesn't remove the added symbolic link each
time each time it's run. But just in case that changes in the
future, it would only delete the symbolic link, not the actual
user's symbol folder, and can easily be restored.
The problem still remains that when you use your own symbols from
your own library, you must remember to manually search them out and
add them to any zip of a shared schematic. I guess I probably manage
to do that about 90% of the time. An "archive" feature would be a
solution to this issue, but one doesn't exist yet.
--
Regards,
Tony
Tony Casey