Re: [Kicad-developers] GAL canvas strategy - testers needed!

A couple of more commits are up (including backing out the polyline change). > On 19 Sep 2018, at 19:27, jp charras wrote: > > Le 19/09/2018 à 13:01, Rene Pöschl a écrit : >> On 19/09/2018 11:54, jp charras wrote: >>> Le 19/09/2018 à 11:40, Rene Pöschl a écrit : Ok i looked at the pot

[Kicad-developers] Jenkins build is back to normal : linux-kicad-full-gcc-head #3981

See ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe :

[Kicad-developers] Pcbnew find dialog question

Does anyone know why we always disable the warp mouse pointer option in the find dialog when called from the SELECTION_TOOL? I am in the progress of fixing another bug and I noticed that the pointer warp option does not respect the user setting in the dialog unless the legacy canvas is enabled.

Re: [Kicad-developers] GAL canvas strategy - testers needed!

The 74LS00 in my (admittedly dated) library aren’t filled. Are they in more recent libraries? (If so, we’ll need to back out my change as it will indeed affect them.) ___ Mailing list: https://launchpad.net/~kicad-developers Post to :

Re: [Kicad-developers] Pcbnew find dialog question

Hi Wayne, It’s certainly less necessary with the modern canvas (which has selection highlighting), but I’m only speculating. Cheers, Jeff. > On 19 Sep 2018, at 16:32, Wayne Stambaugh wrote: > > Does anyone know why we always disable the warp mouse pointer option in > the find dialog when

Re: [Kicad-developers] Pcbnew find dialog question

Hey Jeff, I tested the warping in the gal canvases and it works as expected so I was surprised to see that the warping was being forced off. I just want to be sure there isn't a specific reason for this before I change it. Cheers, Wayne On 9/19/2018 11:41 AM, Jeff Young wrote: > Hi Wayne, >

Re: [Kicad-developers] GAL canvas strategy - testers needed!

Yes, a good chuckle On 9/19/18 10:36 AM, Jeff Young wrote: The 74LS00 in my (admittedly dated) library ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe :

Re: [Kicad-developers] GAL canvas strategy - testers needed!

Le 19/09/2018 à 17:36, Jeff Young a écrit : > The 74LS00 in my (admittedly dated) library aren’t filled. Are they in more > recent libraries? > > (If so, we’ll need to back out my change as it will indeed affect them.) > Hi Jeff, your commit e6734def0 create issues with filled bodies: The

Re: [Kicad-developers] GAL canvas strategy - testers needed!

Hi JP, Do you think it’s worth checking the colours of the stroke and fill, or just remove the change and require that the libraries get fixed? (Why doesn’t the original issue show up with legacy? Maybe it is checking for stroke == fill and then closing the polygons?) Cheers, Jeff.

Re: [Kicad-developers] GAL canvas strategy - testers needed!

Le 19/09/2018 à 18:20, Jeff Young a écrit : > Hi JP, > > Do you think it’s worth checking the colours of the stroke and fill, or just > remove the change and require that the libraries get fixed? just remove the change and require that the libraries get fixed is enough for me. If an used want

[Kicad-developers] [PATCH] Print stacktrace when SIGSEGV or SIGABRT appears

Hi, I wrote some basic crash-handler based on signal handler code published on the mailinglist some time ago: * https://lists.launchpad.net/kicad-developers/msg27148.html For now, it uses the glibc backtrace function to print a basic stack-trace onto the console, and if possible a crash dump

[Kicad-developers] Layer manager issue.

I've noticed recently (around v5 release) that the layer manager (at least on windows 10) looks like it's getting a bunch of paint events (I'm guessing) which causes horrible flickering of the panel and seems to responsible for longer than expected board loading and closing Pcbnew. Has any one

Re: [Kicad-developers] Layer manager issue.

OSX is double-buffered, so I wouldn’t notice the flicker even if it were happening. FWIW, I haven’t noticed it in profiling. > On 19 Sep 2018, at 18:33, Wayne Stambaugh wrote: > > I've noticed recently (around v5 release) that the layer manager (at > least on windows 10) looks like it's

Re: [Kicad-developers] [PATCH] Print stacktrace when SIGSEGV or SIGABRT appears

Thomas, Is there some reason you did not use wxDebugReport[1]? This would hide the platform dependent issues and make for much cleaner code. Cheers, Wayne [1]: https://docs.wxwidgets.org/3.0/classwx_debug_report.html On 9/19/2018 12:38 PM, Thomas Pointhuber wrote: > Hi, > > I wrote some

Re: [Kicad-developers] [PATCH] Print stacktrace when SIGSEGV or SIGABRT appears

Hi, On 19.09.2018 18:38, Thomas Pointhuber wrote: > For now, it uses the glibc backtrace function to print a basic > stack-trace onto the console, and if possible a crash dump file in the > current working directory. Then it needs to at least be made glibc specific. I'm not fond of these

Re: [Kicad-developers] Layer manager issue.

Le 19/09/2018 à 19:33, Wayne Stambaugh a écrit : > I've noticed recently (around v5 release) that the layer manager (at > least on windows 10) looks like it's getting a bunch of paint events > (I'm guessing) which causes horrible flickering of the panel and seems > to responsible for longer than

Re: [Kicad-developers] Layer manager issue.

Am Mi., 19. Sep. 2018 um 10:34 Uhr schrieb Wayne Stambaugh < stambau...@gmail.com>: > I've noticed recently (around v5 release) that the layer manager (at > least on windows 10) looks like it's getting a bunch of paint events > (I'm guessing) which causes horrible flickering of the panel and

Re: [Kicad-developers] [PATCH] Print stacktrace when SIGSEGV or SIGABRT appears

Hi, I rewrote it to use wxDebugReport and wxHandleFatalExceptions. What I noticed (at least for my build setup), the stack-trace is unusable in this version for me because it lacks all kicad internals: ``` ``` compared

Re: [Kicad-developers] [PATCH] Print stacktrace when SIGSEGV or SIGABRT appears

Am Mi., 19. Sep. 2018 um 11:14 Uhr schrieb Thomas Pointhuber < thomas.pointhu...@gmx.at>: > Hi, > > I rewrote it to use wxDebugReport and wxHandleFatalExceptions. What I > noticed (at least for my build setup), the stack-trace is unusable in > this version for me because it lacks all kicad

Re: [Kicad-developers] GAL canvas strategy - testers needed!

Le 19/09/2018 à 13:01, Rene Pöschl a écrit : > On 19/09/2018 11:54, jp charras wrote: >> Le 19/09/2018 à 11:40, Rene Pöschl a écrit : >>> Ok i looked at the pot symbols. They are indeed strange. (ignore my last >>> message) >>> >>> However, how does the new fill algorithm work with things like the

Re: [Kicad-developers] [PATCH] Print stacktrace when SIGSEGV or SIGABRT appears

On 19/09/18 20:13, Thomas Pointhuber wrote: > > I rewrote it to use wxDebugReport and wxHandleFatalExceptions. What I > noticed (at least for my build setup), the stack-trace is unusable in > this version for me because it lacks all kicad internals: Hi Thomas, I like a lot your idea of having a

Re: [Kicad-developers] Layer manager issue.

On 9/19/2018 2:07 PM, Seth Hillbrand wrote: > > > Am Mi., 19. Sep. 2018 um 10:34 Uhr schrieb Wayne Stambaugh > mailto:stambau...@gmail.com>>: > > I've noticed recently (around v5 release) that the layer manager (at > least on windows 10) looks like it's getting a bunch of paint events >

Re: [Kicad-developers] Layer manager issue.

On 9/19/2018 1:50 PM, jp charras wrote: > Le 19/09/2018 à 19:33, Wayne Stambaugh a écrit : >> I've noticed recently (around v5 release) that the layer manager (at >> least on windows 10) looks like it's getting a bunch of paint events >> (I'm guessing) which causes horrible flickering of the panel

Re: [Kicad-developers] GAL canvas strategy - testers needed!

Could you go into detail in how the library item is at fault? Or at least how it should be fixed? On 19/09/2018 00:04, Jeff Young wrote: I pushed John’s 3 patches along with one of my own which fixes the POT rendering. (It is actually an error in the library item, but it’s not alone -- at

Re: [Kicad-developers] GAL canvas strategy - testers needed!

Ok i looked at the pot symbols. They are indeed strange. (ignore my last message) However, how does the new fill algorithm work with things like the logic gates. (Example the symbol for 74LS00) It has an open polygon on purpose as it consists of that polygon plus an arc. We still want the

Re: [Kicad-developers] GAL canvas strategy - testers needed!

Le 19/09/2018 à 11:40, Rene Pöschl a écrit : > Ok i looked at the pot symbols. They are indeed strange. (ignore my last > message) > > However, how does the new fill algorithm work with things like the logic > gates. (Example the symbol for 74LS00) It has an open polygon on purpose > as it

Re: [Kicad-developers] GAL canvas strategy - testers needed!

On 19/09/2018 11:54, jp charras wrote: Le 19/09/2018 à 11:40, Rene Pöschl a écrit : Ok i looked at the pot symbols. They are indeed strange. (ignore my last message) However, how does the new fill algorithm work with things like the logic gates. (Example the symbol for 74LS00) It has an open