Re: [Kicad-developers] Loading symbol libraries

Jeff, Your patch bypasses the issue but the underlying problem still exists anywhere the library cache file name is checked repetitively. Looking at your analysis, the guilty call is the wxFileName == operator. This comparison should be a simple string comparison since that is what matters

Re: [Kicad-developers] Loading symbol libraries

It’d probably be better if I actually attached the patch…. 0005-Load-each-symbol-library-atomically-for-better-perfo.patch Description: Binary data On 24 Jan 2018, at 23:34, Jeff Young wrote:The attached patch speeds loading the symbol libraries from the cache to

Re: [Kicad-developers] Future plans on the KiCad library releases?

On 1/24/2018 11:57 AM, Carsten Schoenert wrote: > Hi, > > Am 15.01.18 um 12:09 schrieb Rene Pöschl: >> On 15/01/18 11:16, Carsten Schoenert wrote: >>> Hi, >>> >>> as the packaging for Debian will change as well for the next KiCad >>> release I've some questions pointed to the contributors and

Re: [Kicad-developers] Future plans on the KiCad library releases?

Hi, Am 15.01.18 um 12:09 schrieb Rene Pöschl: > On 15/01/18 11:16, Carsten Schoenert wrote: >> Hi, >> >> as the packaging for Debian will change as well for the next KiCad >> release I've some questions pointed to the contributors and admins of >> the libraries to be able to prepare the needed

Re: [Kicad-developers] [RFC] Pin edition coupling description

Le 24/01/2018 à 16:33, Wayne Stambaugh a écrit : > Orson, > > Looks fine to me. I'm not sure how clear the icon will be to users but > it makes more sense to me than the current icon. The wording definitely > makes more sense. Thanks for fixing this. > > Cheers, > > Wayne> > On 1/24/2018

Re: [Kicad-developers] Loading symbol libraries

I believe there is only one code path leading to this function. Would you post the full stacktrace? On 01/24/2018 04:59 PM, Jeff Young wrote: > 75% (!) of the time building the component tree is spent here: > > bool SCH_LEGACY_PLUGIN_CACHE::IsFile( const wxString& aFullPathAndFileName ) > const

Re: [Kicad-developers] Loading symbol libraries

75% (!) of the time building the component tree is spent here: bool SCH_LEGACY_PLUGIN_CACHE::IsFile( const wxString& aFullPathAndFileName ) const { return m_libFileName == aFullPathAndFileName; } > On 24 Jan 2018, at 15:31, Jeff Young wrote: > > I’ve been trying to

Re: [Kicad-developers] Loading symbol libraries

I’ve been trying to profile it to see exactly where the time is spent, but I’m having trouble getting valgrind to work. I might put this on the back burner while I fix the issues you identified in the Update Footprints stuff. > On 24 Jan 2018, at 15:27, Wayne Stambaugh

Re: [Kicad-developers] Loading symbol libraries

Jeff, I still think there is something wrong with populating the component tree model. It was working fine (even with the footprint viewer loading) until Orson made changes to it support the new symbol library editor. He reverted those changes but maybe he missed something subtle that is

Re: [Kicad-developers] [RFC] Pin edition coupling description

On 01/23/2018 05:43 PM, Rene Pöschl wrote: [snip] > I am not so sure the default state should be enabled. If i understand it > correctly the enabled state would result in pins being modified without > the user directly noticing it. (If they are on the same position but in > a different unit, they

Re: [Kicad-developers] [RFC] Pin edition coupling description

I attach a patch that hopefully describes the mode a bit clearer. There is also a new icon to reflect the new logic behind the patch (see the attached imaged for comparison: left is the old icon, right is the proposed icon). Regards, Orson On 01/23/2018 05:09 PM, jp charras wrote: > Le

[Kicad-developers] Loading symbol libraries

I have my symbol libraries pared down to some 3900 symbols. Loading the first time takes roughly 3-1/2 seconds. The second time it will say “Loading symbols”, but what it’s actually doing is building the component tree. This takes about 1-1/2 seconds. I tried making the component tree static

[Kicad-developers] No scaled bitmaps in class_DisplayFootprintsFrame.cpp

I just happened to notice that all the other toolbars use scaled bitmaps except this one. Intentional? ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe :

Re: [Kicad-developers] Update PCB from Schematic dialog issues

I remember someone telling me, don't kick a dead horse, well Jeff, don't drag a dead horse. :D On Wed, Jan 24, 2018 at 1:16 AM, Jeff Young wrote: > Hi Andrey, > > Given a blank slate, I’d probably agree with you. > > But you’ve gotta give some love to the horse you’re on…. > >

Re: [Kicad-developers] Update PCB from Schematic dialog issues

Hi Andrey, Given a blank slate, I’d probably agree with you. But you’ve gotta give some love to the horse you’re on…. Cheers, Jeff. > On 24 Jan 2018, at 08:52, Andrey Kuznetsov wrote: > > Wayne, that's what you get for using PoS like wxWidgets. > It's been like that

Re: [Kicad-developers] Update PCB from Schematic dialog issues

Wayne, that's what you get for using PoS like wxWidgets. It's been like that since I looked at it 8 years ago, and it's still shit. That's why I used Qt in my project, it was polished from the get go, had easy to understand framework and had plenty of functions to accomplish anything in anyway.