Re: [Kicad-developers] [PATCH 00/14] RFC: Events in Dialogs

Simon, What version of wxFB are you using to generate the changes? Thanks, Wayne On 10/12/2016 1:49 PM, Simon Richter wrote: > Hi, > > I've stumbled over a few events that are not actually used anymore, so I've > looked for a way to find these. The easiest way seems to be to make event >

[Kicad-developers] [PATCH 08/14] CHECK: use HTML_MESSAGE_BOX instead of base

--- pcbnew/dialogs/dialog_freeroute_exchange.cpp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pcbnew/dialogs/dialog_freeroute_exchange.cpp b/pcbnew/dialogs/dialog_freeroute_exchange.cpp index f84bd7e..6af87e2 100644 --- a/pcbnew/dialogs/dialog_freeroute_exchange.cpp +++

Re: [Kicad-developers] [PATCH 00/14] RFC: Events in Dialogs

Hi Wayne, On 12.10.2016 20:22, Wayne Stambaugh wrote: > What version of wxFB are you using to generate the changes? That is the current version from github, basically -- Debian packages for that version live at http://www.simonrichter.eu/debian/ . The build dates I remove with an extra sed

Re: [Kicad-developers] KiCad hackathon invitation

12/10/16, 19:25, Maciej Sumiński kirjoitti: >> of October. If you have another idea for a hackathon subject, do not >> hesitate to propose it! https://bugs.launchpad.net/kicad/+bug/1443330 Round length matching meanders working with non-default values would be nice too. I'm jumping for the SVG

Re: [Kicad-developers] KiCad hackathon invitation

On 12.10.2016 21:47, Vesa Solonen wrote: > https://bugs.launchpad.net/kicad/+bug/1443330 > That's for the flight to Sao Paulo (+ a bunch of other minor bugs) > Round length matching meanders working with non-default values would be > nice too. What do you mean by non-default? Tom

Re: [Kicad-developers] KiCad hackathon invitation

12/10/16, 23:14, Tomasz Wlostowski kirjoitti: > On 12.10.2016 21:47, Vesa Solonen wrote: >> https://bugs.launchpad.net/kicad/+bug/1443330 >> > That's for the flight to Sao Paulo (+ a bunch of other minor bugs) Excellent, thanks already :)) >> Round length matching meanders working with

Re: [Kicad-developers] Boost 1.62.

It builds fine here as well (Linux x86_64). Perhaps it is only an issue on msys2, but still it needs to be solved. What are the error messages? Regards, Orson On 10/12/2016 11:14 AM, Simon Wells wrote: > can you elaborate the issue you have on osx? i just did a fresh build > (aka nuked my build

Re: [Kicad-developers] Boost 1.62.

can you elaborate the issue you have on osx? i just did a fresh build (aka nuked my build dir) and the only issue i had on osx was this stupidly annoying cmake issue that was to do with bundling of the libs that eventually went away last time and i have no damn idea why it magically went away On

Re: [Kicad-developers] Boost 1.62.

hi, i found problem, in my environment cmake does not correctly find boost 1.62 installation. 1.62 is not included in KNOWN_VERSIONS, 1.61 is the newest known in FindBoost.cmake. I got cmake warnings: Imported targets not available for Boost version 106200 Compiles ok, but can not copy files,

Re: [Kicad-developers] Exclude components from PCB

On 10/12/2016 10:07 AM, Jonatan Liljedahl wrote: > Hi Wayne, > > Thanks, good to know! For this issue, it's important to have separate > flags for inclusion in PCB netlist and Spice netlist, but maybe that's > already the plan? It is. > > > On Wed, Oct 12, 2016 at 4:00 PM, Wayne Stambaugh

Re: [Kicad-developers] Updated FindPython cmake modules

Simon, I've been going through my patch backlog and ran into this one. Is this patch still relevant? Thanks, Wayne On 5/20/2016 6:50 PM, Simon Wells wrote: > heres the patch > > On Sat, May 21, 2016 at 10:49 AM, Simon Wells wrote: >> Please find attached updated patch

Re: [Kicad-developers] Possible hang in SHAPE_POLY_SET ::Fracture() (from Bug 1632648:] Filled zone crashes KiCad in Stable 4.0.4)

Le 12/10/2016 à 15:08, jp charras a écrit : > Le 12/10/2016 à 14:53, Tomasz Wlostowski a écrit : >> On 12.10.2016 14:49, jp charras wrote: >>> Hi Orson and Tomasz, >>> >>> A few days ago I had a look at this issue, previously reported to the Kicad >>> forum. >>> Although it happens on 4.04 and

Re: [Kicad-developers] Boost 1.62.

That is simply because CMake 3.6 does not yet know boost 1.62, this is no problem because none of our boost dependencies introduce indirect dependencies. Michael Am 12.10.2016 um 15:51 schrieb Wayne Stambaugh: It appears that you have to do a clean build. However, I missed some cmake

[Kicad-developers] Exclude components from PCB

Hi list, I'm new here and quite new to Kicad. I'm actually a software developer but doing hobby DIY electronics as well. That's my little presentation, now on to the topic: See https://forum.kicad.info/t/simulator-vs-pcb/4219/8 What do you think? Perhaps it would make sense to add a

Re: [Kicad-developers] Possible hang in SHAPE_POLY_SET ::Fracture() (from Bug 1632648:] Filled zone crashes KiCad in Stable 4.0.4)

On 12.10.2016 14:49, jp charras wrote: > Hi Orson and Tomasz, > > A few days ago I had a look at this issue, previously reported to the Kicad > forum. > Although it happens on 4.04 and not in the current version, I am thinking it > is not fixed (it does > not happen just because there are a few

Re: [Kicad-developers] Possible hang in SHAPE_POLY_SET ::Fracture() (from Bug 1632648:] Filled zone crashes KiCad in Stable 4.0.4)

Le 12/10/2016 à 14:53, Tomasz Wlostowski a écrit : > On 12.10.2016 14:49, jp charras wrote: >> Hi Orson and Tomasz, >> >> A few days ago I had a look at this issue, previously reported to the Kicad >> forum. >> Although it happens on 4.04 and not in the current version, I am thinking it >> is

Re: [Kicad-developers] Exclude components from PCB

Jonaton, Since you are new to the list, you have missed the discussion about the new schematic file format. New flags are going to bet added for taggind schematic symbols as not in netlist and/or not in BOM. Adding this as a field will get lost in the new file format. The new file format is

[Kicad-developers] Possible hang in SHAPE_POLY_SET ::Fracture() (from Bug 1632648:] Filled zone crashes KiCad in Stable 4.0.4)

Hi Orson and Tomasz, A few days ago I had a look at this issue, previously reported to the Kicad forum. Although it happens on 4.04 and not in the current version, I am thinking it is not fixed (it does not happen just because there are a few changes which generate a slightly different zone

Re: [Kicad-developers] Exclude components from PCB

Hi Wayne, Thanks, good to know! For this issue, it's important to have separate flags for inclusion in PCB netlist and Spice netlist, but maybe that's already the plan? On Wed, Oct 12, 2016 at 4:00 PM, Wayne Stambaugh wrote: > Jonaton, > > Since you are new to the list,

Re: [Kicad-developers] Boost 1.62.

This is a possibility. I will try a clean build when I get a chance. The last few boost upgrades on msys2 did not require a clean build. On 10/12/2016 1:24 AM, Nick Østergaard wrote: > Maybe a clean build is needed when upgrading boost version? > > 2016-10-12 2:58 GMT+02:00 Michael Steinberg

Re: [Kicad-developers] Boost 1.62.

Anyway, I see a tendency to deboostify KiCad, so maybe we could simply include Tom's libcontext [1]? It is a stripped down version of boost::context, and I believe Tom may guarantee the API will stay stable. Regards, Orson 1. https://github.com/twlostow/libcontext On 10/12/2016 02:13 PM, Wayne

Re: [Kicad-developers] Boost 1.62.

It appears that you have to do a clean build. However, I missed some cmake warnings about missing dependencies: CMake Warning at C:/msys64/mingw32/share/cmake-3.6/Modules/FindBoost.cmake:743 (message): Imported targets not available for Boost version 106200 Call Stack (most recent call first):

Re: [Kicad-developers] Updated FindPython cmake modules

Hi Wayne, I will need to relook at this and see where i got up to and whether i was able to finish it off.. The whole idea behind it though is not to remove the ability to provide own paths but to be more sane with the defaults. It shouldn't be treating the "oldest supported" as the

[Kicad-developers] KiCad hackathon invitation

Hi there, At the end of this month there will be another KiCad hackathon, hosted by e-HAL [1] and supported by Garoa hackerspace [2]. We have prepared a few blueprints [3] for the features that we would like to develop during the event. If you find any of them interesting and feel like helping

[Kicad-developers] [PATCH] Gerbv: fix Moire macro

As reported in the Gerber standard, section 4.13.4.7, Moire parameters 4 and 5 represent the ring thickness and gap width. Since we are working with diameters, at each step the outer ring diameter should be decreased by two times their sum. --- gerbview/class_aperture_macro.cpp | 2 +- 1 file

Re: [Kicad-developers] KiCad hackathon invitation

On 10/12/2016 06:16 PM, Maciej Sumiński wrote: > Hi there, > > At the end of this month there will be another KiCad hackathon, hosted > by e-HAL [1] and supported by Garoa hackerspace [2]. We have prepared a > few blueprints [3] for the features that we would like to develop during > the event. >

Re: [Kicad-developers] KiCad hackathon invitation

>. We have prepared a few blueprints [3] for the features that we would like to >develop during the event. Hope you can work on the SVG importer! I miss that feature. I tried to use Inkscape ->Export DXF->Import with KiCad but it doesn't work properly :/ Mario Luzeiro

Re: [Kicad-developers] Default paper size and locale

On Tue, Oct 11, 2016 at 02:36:09PM -0400, Wayne Stambaugh wrote: > I'm OK with changing this to the current locale. It has to default to > something when the object is created. A PAGE_INFO object ctor could be > created to do this. There is a couple of problems with that. Mostly that paper

[Kicad-developers] [PATCH 03/14] Remove version number from wxFB output

Bumping the version number makes patches more difficult to read, so don't write a version number into the file. --- 3d-viewer/3d_cache/dialogs/dlg_3d_pathconfig_base.cpp | 2 +- 3d-viewer/3d_cache/dialogs/dlg_3d_pathconfig_base.h | 2 +-

[Kicad-developers] [PATCH 02/14] wxFormBuilder: update older schema files

This brings the remaining stragglers to the current wxFB version. No semantic changes. --- common/dialogs/dialog_image_editor.fbp | 104 +++-- common/dialogs/dialog_image_editor_base.cpp| 5 + common/dialogs/dialog_image_editor_base.h | 2 +-

[Kicad-developers] [PATCH 12/14] CHECK: Fully handle event in derived class.

--- eeschema/dialogs/dialog_rescue_each.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/eeschema/dialogs/dialog_rescue_each.cpp b/eeschema/dialogs/dialog_rescue_each.cpp index c2065fd..5566240 100644 --- a/eeschema/dialogs/dialog_rescue_each.cpp +++

[Kicad-developers] [PATCH 11/14] CHECK: Does any variant need to handle Close events?

--- eeschema/dialogs/dialog_lib_edit_text.h | 1 + 1 file changed, 1 insertion(+) diff --git a/eeschema/dialogs/dialog_lib_edit_text.h b/eeschema/dialogs/dialog_lib_edit_text.h index b58a165..547f3fd 100644 --- a/eeschema/dialogs/dialog_lib_edit_text.h +++

[Kicad-developers] [PATCH 06/14] CHECK: use HTML_MESSAGE_BOX instead of base

--- common/class_marker_base.cpp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/common/class_marker_base.cpp b/common/class_marker_base.cpp index 91e05a2..da1808e 100644 --- a/common/class_marker_base.cpp +++ b/common/class_marker_base.cpp @@ -39,7 +39,7 @@ #include

Re: [Kicad-developers] Updated FindPython cmake modules

Hey Simon, Thanks for the update. I agree that we should not default to oldest supported. Let me know when you have an answer. Cheers, Wayne On 10/12/2016 12:51 PM, Simon Wells wrote: > Hi Wayne, > > I will need to relook at this and see where i got up to and whether i > was able to finish

[Kicad-developers] [PATCH 00/14] RFC: Events in Dialogs

Hi, I've stumbled over a few events that are not actually used anymore, so I've looked for a way to find these. The easiest way seems to be to make event handlers pure virtual functions and see which derived dialogs actually override the functions. For most dialogs, that is straightforward, as

[Kicad-developers] [PATCH 07/14] CHECK: use HTML_MESSAGE_BOX instead of base

--- eeschema/pinedit.cpp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/eeschema/pinedit.cpp b/eeschema/pinedit.cpp index 30b4d99..4b328c7 100644 --- a/eeschema/pinedit.cpp +++ b/eeschema/pinedit.cpp @@ -42,7 +42,7 @@ #include #include -#include

[Kicad-developers] [PATCH 09/14] CHECK: fix typo

--- pcbnew/sel_layer.cpp | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/pcbnew/sel_layer.cpp b/pcbnew/sel_layer.cpp index 44fad09..e968632 100644 --- a/pcbnew/sel_layer.cpp +++ b/pcbnew/sel_layer.cpp @@ -97,6 +97,8 @@ private: void OnLeftGridCellClick( wxGridEvent&

[Kicad-developers] [PATCH 13/14] CHECK: does any dialog in the family need this?

--- pcbnew/dialogs/dialog_graphic_item_properties_for_Modedit.cpp | 1 + 1 file changed, 1 insertion(+) diff --git a/pcbnew/dialogs/dialog_graphic_item_properties_for_Modedit.cpp b/pcbnew/dialogs/dialog_graphic_item_properties_for_Modedit.cpp index da5a89d..062046d 100644 ---

[Kicad-developers] [PATCH 10/14] CHECK: Explicitly handle events for hidden button

--- eeschema/dialogs/dialog_lib_edit_text.cpp | 7 +++ eeschema/dialogs/dialog_lib_edit_text.h | 1 + 2 files changed, 8 insertions(+) diff --git a/eeschema/dialogs/dialog_lib_edit_text.cpp b/eeschema/dialogs/dialog_lib_edit_text.cpp index a1c7cee..b9cec6b 100644 ---

[Kicad-developers] [PATCH 05/14] wxFormBuilder: Remove unused events

--- 3d-viewer/3d_viewer/dialogs/dialog_3D_view_option_base.cpp | 2 -- 3d-viewer/3d_viewer/dialogs/dialog_3D_view_option_base.fbp | 2 +- 3d-viewer/3d_viewer/dialogs/dialog_3D_view_option_base.h | 1 - bitmap2component/bitmap2cmp_gui_base.cpp | 4