Re: [Kicad-developers] KiCad Snapshot version with enabled GTK+3 and wxPython4.0 scripting in Debian experimental

Hi Wayne, Am 15.01.19 um 00:28 schrieb Wayne Stambaugh: >> I'm a bit supersized that there is no plan to configure the current >> KiCad development version at least with GTK+3 backend as default given >> the original plan to eventually have a RC ready before or around Fosdem >> and 5.1 should supp

Re: [Kicad-developers] SIGTRAP crash with ngspice

Hi Steven, Your code is slow because you are using O(n^2) algorithm (look up big O notation if you don't know what that means, tldr is that for 1mb string it will take on the order of 10^12 operations to process in the worst case where there are lots of '\b' characters). Instead of iteratively del

Re: [Kicad-developers] SIGTRAP crash with ngspice

Thanks, Wayne. I'll read through that. As an experiment, I tried the code below, but it turns out to be far too slow to be usable. What I've discovered is that all the "percent complete" status comes in as a single one+ megabyte string, so removing backspaces and the preceding characters one

Re: [Kicad-developers] Bug 1754130

Please table this conversation until we start talking about the new constraint management system as part of v6 development. I don't really have time right now an I would rather not loose any valuable input. I will open up the discussion once we have an initial draft in place. Cheers, Wayne On

Re: [Kicad-developers] KiCad Snapshot version with enabled GTK+3 and wxPython4.0 scripting in Debian experimental (was Re: 5.1 stable release)

h with GTK+3 and wxPython4.0 enabled scripting support for Debian > experimental. > > As Debian has started his freeze for Debian 10 (Buster) right on the > last weekend I won't do any uploads of KiCad snapshot versions to Debian > unstable currently and will use experimental inste

Re: [Kicad-developers] SIGTRAP crash with ngspice

On 1/14/19 1:06 PM, Steven A. Falco wrote: > The issue was discussed here: > > https://forum.kicad.info/t/trying-to-get-ngspice-working-on-fedora/14628 > > If you tell me what my "coding policy errors" are, or point me to something I > should read, then I can do better next time. http://docs.ki

Re: [Kicad-developers] SIGTRAP crash with ngspice

I could try something like: wxString t = aEvent.GetString(); size_t position; while( (position = t.find("\b")) != wxString::npos ) { if( position >= 1 ) { t = t.Remove(position - 1, 2); } } m_simConsole->AppendText( t + "\n" ); m_simConsole->Set

Re: [Kicad-developers] Bug 1754130

Hallo Wayne, Sorry for the repeat message, but I never managed to subscribe to the mailing list using my usual e-mail account. I would be glad to elaborate on that. But the main point is that for power electronics a net clearance is not all that usefull. The simplest example is when you have a DC

Re: [Kicad-developers] SIGTRAP crash with ngspice

I have a minor concern with this patch. Namely, we can't guarantee that we only get one update per event. If multiple are issued, we potentially throw away valid returns. I would prefer either iterative removing of the \b and its preceding char or a wxString::Printf() into a new string to ev

[Kicad-developers] KiCad Snapshot version with enabled GTK+3 and wxPython4.0 scripting in Debian experimental (was Re: 5.1 stable release)

ian packaging of KiCad snapshots from the master branch with GTK+3 and wxPython4.0 enabled scripting support for Debian experimental. As Debian has started his freeze for Debian 10 (Buster) right on the last weekend I won't do any uploads of KiCad snapshot versions to Debian unstable curr

Re: [Kicad-developers] SIGTRAP crash with ngspice

On 14/01/2019 19:06, Steven A. Falco wrote: > Tom or Orson, > > Any objections to this patch. I didn't test it but on the surface it > appears to resolve the issue. I have no formal objections, go ahead and merge the patch but honestly I feel like we (the Kicad dev team) are sometimes overburden

Re: [Kicad-developers] SIGTRAP crash with ngspice

The issue was discussed here: https://forum.kicad.info/t/trying-to-get-ngspice-working-on-fedora/14628 If you tell me what my "coding policy errors" are, or point me to something I should read, then I can do better next time. I've attached a new copy of the patch - the code change is identical,

Re: [Kicad-developers] SIGTRAP crash with ngspice

Steve, Please include the bug report link so I can link the patch to the bug report. I'll fix the coding policy errors since I'm assuming this is as one a done patch for you. Tom or Orson, Any objections to this patch. I didn't test it but on the surface it appears to resolve the issue. Cheer

Re: [Kicad-developers] SIGTRAP crash with ngspice

If needed be that it won't be merged in kicad, we could patch it in with the build scripts for fedora until the libngspice package is updated and this should allow us to enable ngspice on the fedora copr builds. On Mon, 14 Jan 2019 at 16:30, Steven A. Falco wrote: > I wanted to close the loop on

Re: [Kicad-developers] Bug 1754130

While this is tangential to the thurst of this conversation, a comprehensive constraint system is incredibly important for many projects and I'm very happy to share and contribute on this topic if it can be of value. So, here we go... Netclass to netclass clearance would be a distance that all net

Re: [Kicad-developers] Bug 1754130

Hey Mark, Will do. This will give us a chance to better understand how to even map this over to KiCad. I'm still no sure I even understand what is meant by netclass to netclass clearance. Cheers, Wayne On 1/14/2019 11:42 AM, mdoes...@xs4all.nl wrote: > Hello Wayne, > > Please consider it on

Re: [Kicad-developers] Bug 1754130

Hello Wayne, Please consider it on hold for now. Once kicad supports netclass to netclass clearances I will have another look. The dimensions are not copied yet, since I stopped working on it once I found out that all the unnamed nets lost their netclass after the first update from the schematic.

Re: [Kicad-developers] Bug 1754130

Hey Mark, On 1/11/2019 5:11 AM, mdoes...@xs4all.nl wrote: > Here's a patch to import the netclasses from eagle. There are a few minor coding policy issues. We now have clang formatting available when you perform a git commit if you would prefer not to have to remember KiCad's formatting. You ju

Re: [Kicad-developers] SIGTRAP crash with ngspice

I wanted to close the loop on the SIGTRAP crash that I reported a few days ago. The issue is probably unique to Fedora, and stems from a huge quantity of "percent complete" messages that the ngspice library passes back to KiCad. I'm not kidding when I say huge - it amounts to over 1 megabyte of

Re: [Kicad-developers] $comp file format question

I see. Think they should be documented and cleaned, even if it is during a load. Thanks Brian -Original Message- From: Kicad-developers On Behalf Of jp charras Sent: January 14, 2019 9:25 AM To: kicad-developers@lists.launchpad.net Subject: Re: [Kicad-developers] $comp file format que

Re: [Kicad-developers] $comp file format question

Le 14/01/2019 à 14:56, Brian Piccioni a écrit : > JP > Thanks for the explanation. > > Is the AR field documented anywhere? Are there any other undocumented .sch > fields? Not I am aware of. > > It would seem to me that the extraneous/obsolete AR fields should be deleted > when the file is sav

Re: [Kicad-developers] $comp file format question

JP Thanks for the explanation. Is the AR field documented anywhere? Are there any other undocumented .sch fields? It would seem to me that the extraneous/obsolete AR fields should be deleted when the file is saved since they are no longer need for undo commands. Regards Brian -Original Me

[Kicad-developers] Build failed in Jenkins: linux-kicad-full-gcc-head #4520

See Changes: [jean-pierre charras] Fix a minor I18n issue [jean-pierre charras] DIALOG_BOM: fix a few issues. Mainly an annoying issue when a plugin -- [...trunca

[Kicad-developers] BOARD_CONNECTED_ITEM::GetClearance

I am removing all BOARD_CONNECTED_ITEM::GetClearance with aItem==NULL for the purpose of checking net<->net clearances only. Does it make sense to send this patch, or should I just wait until v6 development is started? regards, Mark ___ Mailing list: h