Even the symbol current library repo with it's 90+ symbol libraries?
The default project file only includes about 20 or so of those libraries
so you would have to modify your default project file for this to happen.
On 12/28/2017 5:49 PM, Jan Mrázek wrote:
> Even in KiCAD 4 I always added all the
Even in KiCAD 4 I always added all the libraries in the project. It
always slowed down only the first opening of the component chooser
dialog in schematic editor, but every other usage in the session was
without a lag.
In nightly, I would say the first opening is maybe a little faster,
howeve
You cannot fairly compare opening 20 or so symbol libraries compared to
90+ symbol libraries. Try cutting your global symbol library table down
to 20-25 symbol libraries see if that improves the performance issues.
You could also create a project file (.pro) that has all of the symbol
libraries in
I am sorry for a mistype; automatically -> immediately.
Dne 28.12.2017 v 23:36 Jan Mrázek napsal(a):
Chris and Wayne,
I have the latest nightly build and I can confirm a slow-down when I
try to add a component in a schematic. The first usage after KiCAD
startup takes roughly 3-5 seconds to l
Chris and Wayne,
I have the latest nightly build and I can confirm a slow-down when I try
to add a component in a schematic. The first usage after KiCAD startup
takes roughly 3-5 seconds to load. Every other usage takes approx. 0.5
seconds and it is quite annoying and productivity killing.
I
Chris,
I stand corrected. I just messed around a bit with this on Debian and
it works as I previously described. The first load is slow because of
the caching of both the symbol libraries and the footprint libraries.
On the second launch of the chooser, the symbol library progress dialog
is dism
You could try taking a look at the symbol library enumerate call in
CMP_TREE_MODEL_ADAPTER::AddLibrary(). Run the chooser once and then set
a breakpoint at the EnumerateSymbolLib() call and see if the plugin
cache (SCH_LEGACY_PLUGIN::cacheLib()) is being deleted and reloaded. If
it is, then somet
Thank you, Wayne. Let me know if there's anything you want me to look
into or do - I've missed a lot of the new code and don't really have
time to work out from scratch what went wrong, but I'll gladly help out
with a point in the right direction. And let me know if you do you want
me to put it beh
I don't think it's the footprint preview that is the issue. I think
something happened when the symbol library table progress dialog was
added or afterwards. When I added the symbol library table code, it was
slow the first time you opened the chooser because the symbol library
table uses lazy lo
Something definitely happened. It was fast for me, but now takes several
seconds.
On the other hand, not having it would be worse.
Cheers,
Jeff.
> On 28 Dec 2017, at 20:58, Chris Pavlina wrote:
>
> Hi,
>
> How many have noticed a drop in performance in the component chooser,
> particularly
Hi,
How many have noticed a drop in performance in the component chooser,
particularly surrounding footprint preview? I've noticed a rise in
complaints about it, including one now who's saying it takes around two
seconds to open every time. I'm not sure if something changed since I
wrote it or if
11 matches
Mail list logo
