Re: [Kicad-developers] Build Docs Page Not Working

The browser cache gets cleared on every session at my side... It still works, somehow. But loading the left menu seems to stall (until some timeout?) every once in a while on refresh for several seconds. Regards, Clemens On 07/04/2019 17.38, Mark Roszko wrote: > It's not fixed. The build job is

[Kicad-developers] Common settings changing in 3D viewer

Hi, I'm trying to get the 3d viewer hooked up to the common settings, so I can change the DPI scaling. The 3d viewer frame is a KIWAY_PLAYER, but doesn't seem to participate in the Kiway ecosystem, as it's never created by a call to Player(). This means it's never included in common settings upda

Re: [Kicad-developers] Common settings changing in 3D viewer

While not directly related, see https://bugs.launchpad.net/kicad/+bug/1562672 for some more background. > On 8 Apr 2019, at 09:56, John Beard wrote: > > Hi, > > I'm trying to get the 3d viewer hooked up to the common settings, so I > can change the DPI scaling. > > The 3d viewer frame is a K

[Kicad-developers] Cut/copy/paste symbol

I just fixed cut/copy/paste symbol (in the Symbol Editor’s library tree) to use the system clipboard. Does anyone know of any other areas where we “cheat” and use global variables for cut/copy/paste instead of the system clipboard? Cheers, Jeff. ___ M

Re: [Kicad-developers] Merge schedule

On 05/04/2019 12:09, Jeff Young wrote: > I’ve got a changelist which cleans up the various SCH_ and LIB_ Draw() > routines to remove the interactivity features (since they’re now print-only). > Hi all, Since we're discussing merging again, may I push my Crash Reporter patch (touches mostly kifa

Re: [Kicad-developers] Merge schedule

Hi Tomasz I was wondering about this yesterday. Has it even been merged on master? I think I would prefer not to merge it on stable if it has not even been tested on master, but if you think it is low risk I guess it is ok. As I have not tested it I don't know what it looks like, but if you thin

Re: [Kicad-developers] Merge schedule

Tom, On 4/8/2019 7:34 AM, Tomasz Wlostowski wrote: > On 05/04/2019 12:09, Jeff Young wrote: >> I’ve got a changelist which cleans up the various SCH_ and LIB_ Draw() >> routines to remove the interactivity features (since they’re now print-only). >> > > Hi all, > > Since we're discussing mergin

Re: [Kicad-developers] 5.1.1

Hi, On Sat, Apr 06, 2019 at 11:31:27PM -0400, Seth Hillbrand wrote: > I'd like to suggest spinning out 5.1.1 soon and pushing the existing > 5.1.1 bugs to 5.1.2. > > Thoughts? I'd like to use this opportunity and add ten random package GUIDs to the "uninstall before" list in the Windows install

Re: [Kicad-developers] 5.1.1

I am noy sure what this means. Does it depend on changes in kicad or the installer only? man. 8. apr. 2019 14.46 skrev Simon Richter : > Hi, > > On Sat, Apr 06, 2019 at 11:31:27PM -0400, Seth Hillbrand wrote: > > > I'd like to suggest spinning out 5.1.1 soon and pushing the existing > > 5.1.1 bug

Re: [Kicad-developers] Common settings changing in 3D viewer

Hi Jeff, Thanks, makes sense. I have kept this behaviour, but I have pushed a little bit of logic inside EDA_3D_VIEWER to avoid duplicating logic between classes. Now, the 3D viewer does handle its own updates for the CommonSettingsChanged, but they are sent "manually" by the PCB frame. This allo

Re: [Kicad-developers] Keep text upright

On 2019-04-06 7:06 p.m., Jeff Young wrote: The keep text upright feature works poorly with left- or right-justified text (it flips around the anchor point). [snip]> if you rotate some text with keep-upright on, and then turn it off, the text won’t “un-flip”. But maybe that’s not so bad

Re: [Kicad-developers] Merge schedule

On 08/04/2019 13:58, Nick Østergaard wrote: > Hi Tomasz > > I was wondering about this yesterday. Has it even been merged on master? > > I think I would prefer not to merge it on stable Hi Nick, I don't plan to merge it to any stable release anytime soon. I meant the nightlies... Cheers, Tom

[Kicad-developers] Windows build error.

According to `git bisect`, commit 77f15eeeaf89a5d2179ee800f6faa11faf718d0e broke windows builds (32 and 64 bits) with the following error: C:/msys64/home/wstambaugh/src/kicad-trunk/kicad/import_project.cpp:144:46: error: conversion from 'wxString' to non-scalar type 'std::__cxx11::string {aka std:

Re: [Kicad-developers] Windows build error.

Fails on linux as well man. 8. apr. 2019 17.12 skrev Wayne Stambaugh : > According to `git bisect`, commit > 77f15eeeaf89a5d2179ee800f6faa11faf718d0e broke windows builds (32 and 64 > bits) with the following error: > > C:/msys64/home/wstambaugh/src/kicad-trunk/kicad/import_project.cpp:144:46: >

[Kicad-developers] A couple of featurettes that could use a spin....

I’ve just committed a couple of featurettes that could use a test spin if anyone has the opportunity. 1) Dry run reporting for Clean Up Tracks and Vias 2) Test Footprints in DRC 3) Support for full character set in labels, netnames, etc. Cheers, Jeff.

Re: [Kicad-developers] Windows build error.

Le 08/04/2019 à 17:10, Wayne Stambaugh a écrit : > According to `git bisect`, commit > 77f15eeeaf89a5d2179ee800f6faa11faf718d0e broke windows builds (32 and 64 > bits) with the following error: > > C:/msys64/home/wstambaugh/src/kicad-trunk/kicad/import_project.cpp:144:46: > error: conversion from

Re: [Kicad-developers] Merge schedule

Ok, cool. I guess we all agree to merge it on master :) man. 8. apr. 2019 16.45 skrev Tomasz Wlostowski : > On 08/04/2019 13:58, Nick Østergaard wrote: > > Hi Tomasz > > > > I was wondering about this yesterday. Has it even been merged on master? > > > > I think I would prefer not to merge it on

Re: [Kicad-developers] Windows build error.

On 4/8/2019 11:24 AM, jp charras wrote: > Le 08/04/2019 à 17:10, Wayne Stambaugh a écrit : >> According to `git bisect`, commit >> 77f15eeeaf89a5d2179ee800f6faa11faf718d0e broke windows builds (32 and 64 >> bits) with the following error: >> >> C:/msys64/home/wstambaugh/src/kicad-trunk/kicad/import

Re: [Kicad-developers] 5.1.1

On 07/04/19 18:59, Wayne Stambaugh wrote: Do we need any more than three weeks to get the translations updated, the libraries tag, and packages built? Please let me know if this is an issue. I hope i will be able to take a look at the library this weekend (The last few weeks where a bit busy

Re: [Kicad-developers] A couple of featurettes that could use a spin....

Le 08/04/2019 à 17:43, Jeff Young a écrit : > I’ve just committed a couple of featurettes that could use a test spin if > anyone has the opportunity. > > 1) Dry run reporting for Clean Up Tracks and Vias > 2) Test Footprints in DRC > 3) Support for full character set in labels, netnames, etc. >

[Kicad-developers] recent macos build failures

Hi folks! Anyone having issues like this recently? *08:58:06* default: /vagrant/build/kicad/src/kicad/qa/eeschema/eeschema_test_utils.cpp:28:23: error: no member named 'getenv' in namespace 'std'; did you mean simply 'getenv'?*08:58:06* default: const char* env = std::getenv( "KICAD_T

[Kicad-developers] m_graph is null when exporting netlist

Hi Jon, When we try to build a netlist for Update PCB from Schematic we get an assert in NETLIST_EXPORTER_GENERIC::makeListOfNets() because m_graph is null. Is this because real-time updating is turned off? Is there a call to build it that we should be making in the meantime? Cheers, Jeff. _

Re: [Kicad-developers] m_graph is null when exporting netlist

The graph should be updated before netlisting even if real-time is turned off. What is the call stack where you get the assert? I'm not a build machine now so I will be of limited use, but it sounds like somehow the exporter is being constructed without setting the pointer to the global connectio

Re: [Kicad-developers] m_graph is null when exporting netlist

It’s in the cross-probing code. The init looks like this: NETLIST_OBJECT_LIST* net_atoms = BuildNetListBase(); NETLIST_EXPORTER_KICAD exporter( this, net_atoms ); STRING_FORMATTER formatter; exporter.Format( &formatter, GNL_ALL ); payload = formatter.GetString(); > On 8 Apr 2019, at 20:12, Jo

Re: [Kicad-developers] m_graph is null when exporting netlist

I see there are other places where it’s constructed with the global g_ConnectionGraph. Do I just need to add that? > On 8 Apr 2019, at 20:18, Jeff Young wrote: > > It’s in the cross-probing code. The init looks like this: > > NETLIST_OBJECT_LIST* net_atoms = BuildNetListBase(); > NETLIST_EXP

Re: [Kicad-developers] m_graph is null when exporting netlist

Yes, try that. We can probably pull it out of the ctor and just use the global until/unless it is refactored away. On Mon, Apr 8, 2019 at 3:19 PM Jeff Young wrote: > I see there are other places where it’s constructed with the > global g_ConnectionGraph. Do I just need to add that? > > On 8 Ap

Re: [Kicad-developers] recent macos build failures

Am 2019-04-08 14:57, schrieb Adam Wolf: Hi folks! Anyone having issues like this recently? 08:58:06 default: /vagrant/build/kicad/src/kicad/qa/eeschema/eeschema_test_utils.cpp:28:23: error: no member named 'getenv' in namespace 'std'; did you mean simply 'getenv'? 08:58:06 default:

Re: [Kicad-developers] m_graph is null when exporting netlist

Yep, seems to have worked. Thanks! > On 8 Apr 2019, at 20:20, Jon Evans wrote: > > Yes, try that. We can probably pull it out of the ctor and just use the > global until/unless it is refactored away. > > On Mon, Apr 8, 2019 at 3:19 PM Jeff Young > wrote: > I see there

Re: [Kicad-developers] A couple of featurettes that could use a spin....

Thanks for testing, JP. The Update PCB from Schematic issue should be fixed now. Cheers, Jeff. > On 8 Apr 2019, at 19:12, jp charras wrote: > > Le 08/04/2019 à 17:43, Jeff Young a écrit : >> I’ve just committed a couple of featurettes that could use a test spin if >> anyone has the opportun

Re: [Kicad-developers] Keep text upright

Hi Kevin, It would be reasonably straight-forward to fix that. Log a wishlist bug for Board setup setting to indicate which edges of board are “up” for “keep upright”. Cheers, Jeff. > On 8 Apr 2019, at 15:32, Kevin Cozens wrote: > > On 2019-04-06 7:06 p.m., Jeff Young wrote: >> The keep tex

Re: [Kicad-developers] 5.1.1

On 4/7/19 12:59 PM, Wayne Stambaugh wrote: > On 4/7/19 10:14 AM, Seth Hillbrand wrote: >> Am 2019-04-07 09:00, schrieb Wayne Stambaugh: >>> Seth, >>> >>> I was actually considering this but I was holding off for one last high >>> priority bug[1] to be fixed.  I'm fine with pushing the low and mediu

Re: [Kicad-developers] recent macos build failures

Thanks! Amazing response time! On Mon, Apr 8, 2019 at 2:34 PM Seth Hillbrand wrote: > Am 2019-04-08 14:57, schrieb Adam Wolf: > > Hi folks! > > > > Anyone having issues like this recently? > > > > 08:58:06 default: > > /vagrant/build/kicad/src/kicad/qa/eeschema/eeschema_test_utils.cpp:28:23