On 4/16/2018 9:25 AM, Maciej Sumiński wrote:
> Hi Wayne,
>
> I see, but I wonder if there is any benefit in making the colon
> exception just for rescue/cache libraries? I suppose it makes them
> special in the sense they cannot be used as regular libraries due to
> illegal character in symbol nam
Hi Wayne,
I see, but I wonder if there is any benefit in making the colon
exception just for rescue/cache libraries? I suppose it makes them
special in the sense they cannot be used as regular libraries due to
illegal character in symbol names.
As I said, I am not familiar with caching/rescue cod
Hey Orson,
The colons are required to prevent symbol name clashes in the cache
library. I had to prefix the library nickname to the symbol name to
prevent symbols from being overwritten when they exist in more than on
library. In other words, cache library symbol names look just like
LIB_IDs usi
Hi Jean-Pierre,
I understand the patch and thank you for the fix, but apparently I do
not have enough knowledge about caching in eeschema to comment on the
approach. Frankly, I was a bit surprised to find out that colons are
permitted in symbol names stored in a cache library.
Regards,
Orson
On
Hi Wayne and Orson,
Could you have a look into the fix I committed in rev 2974a2c10.
Before this fix, the library cache was broken (all symbol names incorrectly
saved).
This is specific to the cache, but really annoying...
Please, see comments in commit 2974a2c10.
But I am not sure this is the
5 matches
Mail list logo
