[Kicad-developers] Removing segment hard-coding

[Seth Hillbrand]

Hi All-

I pushed a branch that removes the remaining hard-coded segment counts 
to my kicad fork[1].  It touches many things, so I'd love to get some 
testing before merging.


It has the side effect of needing to decouple the remaining tool_manager 
interfaces from pcbnew.  I noticed a couple of hacks that used some of 
these calls to fix focus bugs on Windows.  I think I preserved this but 
it would be nice to verify.  The comments noted that these occurred when 
the main window was minimized.  @JP, I think that this was your comment 
(tool_dispatcher.cpp:320)


Thanks-
Seth

[1] https://code.launchpad.net/~sethh/kicad/+git/kicad/+ref/segments

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

Re: [Kicad-developers] Kicad's way of drawing filled zones

[Wayne Stambaugh]

Hey Tom,

On 5/14/19 4:34 AM, Tomasz Wlostowski wrote:
> On 13/05/2019 17:46, Wayne Stambaugh wrote:
>> I guess I should weigh in on this issue.  I would prefer we exhaust all
>> other options before bumping opengl to some later version.
> 
> Hi Wayne,
> 
> I think JP's solution is the way to go, it fixes the original issue
> instead of working it around. What's your opinion?

I'm fine with JP's solution.  I seem to remember some concern about
possibly breaking some of the exporting and/or plotting so we need to be
careful in that regard.

Cheers,

Wayne

> 
> Cheers,
> Tom
> 
> 

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

Re: [Kicad-developers] PATCH: Raytracing - a more pleasing way sequencing blocks to render ?

[Wayne Stambaugh]

Hey Henner,

I merged your patch into the master and 5.1 branches.

Thanks,

Wayne

On 5/14/19 12:36 AM, Henner Zeller wrote:
> On Thu, 9 May 2019 at 13:06, Wayne Stambaugh  wrote:
>>
>> Hi Henner,
>>
>> On 5/1/19 9:44 AM, Henner Zeller wrote:
>>> On Wed, 1 May 2019 at 06:14, John Beard  wrote:

 On 01/05/2019 13:57, Mário Luzeiro wrote:
> Hi John,
>
> yeah the Morton code is to improve cache hits.
>
> Regarding the speed test, since OS are multi-tasking there could be some 
> interference on the results so 1s difference is not a very measurable 
> difference ( 4% ).
> A possibility would be to run the same scene multiple times and make an 
> average of the times.

 Sure, it was just a fun observation. It does change a bit from run to
 run, but I was at least expecting a small penalty. Next up, wipes[1] and
 then perhaps Snake :-D

 A more robust benchmarking harness would probably be the way to go if we
 really were serious about putting the pedal to the metal here.

 But I think the centre-first approach is certainly better usability, but
 I'm unsure about the checkerboard.
>>>
>>> I agree, without checkerboard it makes it quicker to see what is going
>>> on in the center. Attached the (even simpler) just spiraling out from
>>> the center patch.
>>
>> I tested this patch and it works as advertised.  Would you please fix a
>> few minor coding policy issues (missing spaces after opening and before
>> closing parentheses) and resubmit it?  There is now a clang-format
>> (>=3.9) commit hook[1] that allows you to check your code formatting
>> before you commit.
> 
> Sorry for the formatting mess-up, attached you find the patch properly
> clang-tidied.
> I really like the new clang tidy script, much more seamless than the
> uncrustify stuff from the past.
> 
> Thanks,
>   Henner.
> 
>>
>> Thanks,
>>
>> Wayne
>>
>> [1]:
>> http://docs.kicad-pcb.org/doxygen/md_Documentation_development_coding-style-policy.html#tools
>>
>>>

 Cheers,

 John

 [1]: https://www.youtube.com/watch?v=cGqAu9gj_F0

 ___
 Mailing list: https://launchpad.net/~kicad-developers
 Post to : kicad-developers@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~kicad-developers
 More help   : https://help.launchpad.net/ListHelp
>>
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp

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

Re: [Kicad-developers] swig 4.0.0 patch

[Steven A. Falco]

The nightlies don't even appear to get started.  All 4 chroots are not even 
"clickable".  So it looks like the builds are not even launching.

Steve

On 5/14/19 9:18 AM, Nick Østergaard wrote:
> Awesome, thanks! I didn't notice. The fedora nightlies are clearly
> failing because of other reasons not related to kicad as such it
> seems.
> 
> On Tue, 14 May 2019 at 13:29, Wayne Stambaugh  wrote:
>>
>> Nick,
>>
>> It already has been merged in the master and 5.1 branches.  The commit
>> in master is 5685174808f5ca973e916a10f9f93660ee4dc4f2.
>>
>> Wayne
>>
>> On 5/14/19 3:47 AM, Nick Østergaard wrote:
>>> @Wayne Stambaugh  any impediments to getting this merged?
>>>
>>> On Fri, 10 May 2019 at 21:37, Steven A. Falco  wrote:

 Here is the result.  Everything passed.  The tests run surprisingly 
 quickly.

  sh-5.0# make test
 Running tests...
 /usr/bin/ctest --force-new-ctest-process
 Test project /builddir/build/BUILD/kicad-5.1.2
 Start 1: qa_python
 1/6 Test #1: qa_python    Passed1.49 sec
 Start 2: common_gerbview
 2/6 Test #2: common_gerbview ..   Passed0.12 sec
 Start 3: common_pcbnew
 3/6 Test #3: common_pcbnew    Passed0.07 sec
 Start 4: common_eeschema
 4/6 Test #4: common_eeschema ..   Passed0.08 sec
 Start 5: pcbnew
 5/6 Test #5: pcbnew ...   Passed0.16 sec
 Start 6: eeschema
 6/6 Test #6: eeschema .   Passed0.23 sec

 100% tests passed, 0 tests failed out of 6

 Steve


 On 5/10/19 1:44 PM, Steven A. Falco wrote:
> I'll run that.  Please give me a half hour or so, because I have to 
> regenerate my rawhide build area - the "mock" tool ordinarily deletes 
> everything as soon as a build completes.
>
>   Steve
>
> On 5/10/19 1:37 PM, Wayne Stambaugh wrote:
>> `make test` will run all of the qa tests.  The python qa test is the
>> first one run.  It's not comprehensive but it will let you know if
>> you've completely broken python support.
>>
>> On 5/10/19 1:32 PM, Steven A. Falco wrote:
>>> I used the footprint wizard to create some footprints.  I'll be happy 
>>> to run qa tests - is there a "make" target for them?  I've never run 
>>> them before...
>>>
>>> Steve
>>>
>>> On 5/10/19 1:21 PM, Wayne Stambaugh wrote:
 Hi Steve,

 Did you actually test and confirm that the python scripting is working?
  I ran a few of the default scripts just as quick and dirty test along
 with the qa tests.  If the qa tests work for you, I will go ahead and
 merge the patch.

 Wayne

 On 5/10/19 1:09 PM, Steve Falco wrote:
> Should have mentioned that rawhide is using swig 4.0.0.
>
> On Fri, May 10, 2019, 1:06 PM Steve Falco  > wrote:
>
> I am now able to build on rawhide with this patch. It works for 
> me.
>
> Steve
>
> On Fri, May 10, 2019, 1:04 PM Wayne Stambaugh 
>  > wrote:
>
> Has anyone with swig 4 tested this patch yet.  I tested it 
> and it
> appears not to break anything with swig < 4.  If it works for
> swig 4, we
> should get this merged so platforms using swig 4 wont have to
> downgrade
> to build KiCad.
>
> Wayne
>
> On 5/9/19 3:58 AM, mdoes...@xs4all.nl
>  wrote:
> > Sorry about that, here's the patch
> >
> >
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> 
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> 
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>

>>>
>>
>
>


 ___
 Mailing list: 

Re: [Kicad-developers] swig 4.0.0 patch

[Nick Østergaard]

Awesome, thanks! I didn't notice. The fedora nightlies are clearly
failing because of other reasons not related to kicad as such it
seems.

On Tue, 14 May 2019 at 13:29, Wayne Stambaugh  wrote:
>
> Nick,
>
> It already has been merged in the master and 5.1 branches.  The commit
> in master is 5685174808f5ca973e916a10f9f93660ee4dc4f2.
>
> Wayne
>
> On 5/14/19 3:47 AM, Nick Østergaard wrote:
> > @Wayne Stambaugh  any impediments to getting this merged?
> >
> > On Fri, 10 May 2019 at 21:37, Steven A. Falco  wrote:
> >>
> >> Here is the result.  Everything passed.  The tests run surprisingly 
> >> quickly.
> >>
> >>  sh-5.0# make test
> >> Running tests...
> >> /usr/bin/ctest --force-new-ctest-process
> >> Test project /builddir/build/BUILD/kicad-5.1.2
> >> Start 1: qa_python
> >> 1/6 Test #1: qa_python    Passed1.49 sec
> >> Start 2: common_gerbview
> >> 2/6 Test #2: common_gerbview ..   Passed0.12 sec
> >> Start 3: common_pcbnew
> >> 3/6 Test #3: common_pcbnew    Passed0.07 sec
> >> Start 4: common_eeschema
> >> 4/6 Test #4: common_eeschema ..   Passed0.08 sec
> >> Start 5: pcbnew
> >> 5/6 Test #5: pcbnew ...   Passed0.16 sec
> >> Start 6: eeschema
> >> 6/6 Test #6: eeschema .   Passed0.23 sec
> >>
> >> 100% tests passed, 0 tests failed out of 6
> >>
> >> Steve
> >>
> >>
> >> On 5/10/19 1:44 PM, Steven A. Falco wrote:
> >>> I'll run that.  Please give me a half hour or so, because I have to 
> >>> regenerate my rawhide build area - the "mock" tool ordinarily deletes 
> >>> everything as soon as a build completes.
> >>>
> >>>   Steve
> >>>
> >>> On 5/10/19 1:37 PM, Wayne Stambaugh wrote:
>  `make test` will run all of the qa tests.  The python qa test is the
>  first one run.  It's not comprehensive but it will let you know if
>  you've completely broken python support.
> 
>  On 5/10/19 1:32 PM, Steven A. Falco wrote:
> > I used the footprint wizard to create some footprints.  I'll be happy 
> > to run qa tests - is there a "make" target for them?  I've never run 
> > them before...
> >
> > Steve
> >
> > On 5/10/19 1:21 PM, Wayne Stambaugh wrote:
> >> Hi Steve,
> >>
> >> Did you actually test and confirm that the python scripting is working?
> >>  I ran a few of the default scripts just as quick and dirty test along
> >> with the qa tests.  If the qa tests work for you, I will go ahead and
> >> merge the patch.
> >>
> >> Wayne
> >>
> >> On 5/10/19 1:09 PM, Steve Falco wrote:
> >>> Should have mentioned that rawhide is using swig 4.0.0.
> >>>
> >>> On Fri, May 10, 2019, 1:06 PM Steve Falco  >>> > wrote:
> >>>
> >>> I am now able to build on rawhide with this patch. It works for 
> >>> me.
> >>>
> >>> Steve
> >>>
> >>> On Fri, May 10, 2019, 1:04 PM Wayne Stambaugh 
> >>>  >>> > wrote:
> >>>
> >>> Has anyone with swig 4 tested this patch yet.  I tested it 
> >>> and it
> >>> appears not to break anything with swig < 4.  If it works for
> >>> swig 4, we
> >>> should get this merged so platforms using swig 4 wont have to
> >>> downgrade
> >>> to build KiCad.
> >>>
> >>> Wayne
> >>>
> >>> On 5/9/19 3:58 AM, mdoes...@xs4all.nl
> >>>  wrote:
> >>> > Sorry about that, here's the patch
> >>> >
> >>> >
> >>> >
> >>> >
> >>> > ___
> >>> > Mailing list: https://launchpad.net/~kicad-developers
> >>> > Post to : kicad-developers@lists.launchpad.net
> >>> 
> >>> > Unsubscribe : https://launchpad.net/~kicad-developers
> >>> > More help   : https://help.launchpad.net/ListHelp
> >>> >
> >>>
> >>> ___
> >>> Mailing list: https://launchpad.net/~kicad-developers
> >>> Post to : kicad-developers@lists.launchpad.net
> >>> 
> >>> Unsubscribe : https://launchpad.net/~kicad-developers
> >>> More help   : https://help.launchpad.net/ListHelp
> >>>
> >>
> >
> 
> >>>
> >>>
> >>
> >>
> >> ___
> >> Mailing list: https://launchpad.net/~kicad-developers
> >> Post to : kicad-developers@lists.launchpad.net
> >> Unsubscribe : https://launchpad.net/~kicad-developers
> >> More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] swig 4.0.0 patch

[Wayne Stambaugh]

Nick,

It already has been merged in the master and 5.1 branches.  The commit
in master is 5685174808f5ca973e916a10f9f93660ee4dc4f2.

Wayne

On 5/14/19 3:47 AM, Nick Østergaard wrote:
> @Wayne Stambaugh  any impediments to getting this merged?
> 
> On Fri, 10 May 2019 at 21:37, Steven A. Falco  wrote:
>>
>> Here is the result.  Everything passed.  The tests run surprisingly quickly.
>>
>>  sh-5.0# make test
>> Running tests...
>> /usr/bin/ctest --force-new-ctest-process
>> Test project /builddir/build/BUILD/kicad-5.1.2
>> Start 1: qa_python
>> 1/6 Test #1: qa_python    Passed1.49 sec
>> Start 2: common_gerbview
>> 2/6 Test #2: common_gerbview ..   Passed0.12 sec
>> Start 3: common_pcbnew
>> 3/6 Test #3: common_pcbnew    Passed0.07 sec
>> Start 4: common_eeschema
>> 4/6 Test #4: common_eeschema ..   Passed0.08 sec
>> Start 5: pcbnew
>> 5/6 Test #5: pcbnew ...   Passed0.16 sec
>> Start 6: eeschema
>> 6/6 Test #6: eeschema .   Passed0.23 sec
>>
>> 100% tests passed, 0 tests failed out of 6
>>
>> Steve
>>
>>
>> On 5/10/19 1:44 PM, Steven A. Falco wrote:
>>> I'll run that.  Please give me a half hour or so, because I have to 
>>> regenerate my rawhide build area - the "mock" tool ordinarily deletes 
>>> everything as soon as a build completes.
>>>
>>>   Steve
>>>
>>> On 5/10/19 1:37 PM, Wayne Stambaugh wrote:
 `make test` will run all of the qa tests.  The python qa test is the
 first one run.  It's not comprehensive but it will let you know if
 you've completely broken python support.

 On 5/10/19 1:32 PM, Steven A. Falco wrote:
> I used the footprint wizard to create some footprints.  I'll be happy to 
> run qa tests - is there a "make" target for them?  I've never run them 
> before...
>
> Steve
>
> On 5/10/19 1:21 PM, Wayne Stambaugh wrote:
>> Hi Steve,
>>
>> Did you actually test and confirm that the python scripting is working?
>>  I ran a few of the default scripts just as quick and dirty test along
>> with the qa tests.  If the qa tests work for you, I will go ahead and
>> merge the patch.
>>
>> Wayne
>>
>> On 5/10/19 1:09 PM, Steve Falco wrote:
>>> Should have mentioned that rawhide is using swig 4.0.0.
>>>
>>> On Fri, May 10, 2019, 1:06 PM Steve Falco >> > wrote:
>>>
>>> I am now able to build on rawhide with this patch. It works for me.
>>>
>>> Steve
>>>
>>> On Fri, May 10, 2019, 1:04 PM Wayne Stambaugh >> > wrote:
>>>
>>> Has anyone with swig 4 tested this patch yet.  I tested it and 
>>> it
>>> appears not to break anything with swig < 4.  If it works for
>>> swig 4, we
>>> should get this merged so platforms using swig 4 wont have to
>>> downgrade
>>> to build KiCad.
>>>
>>> Wayne
>>>
>>> On 5/9/19 3:58 AM, mdoes...@xs4all.nl
>>>  wrote:
>>> > Sorry about that, here's the patch
>>> >
>>> >
>>> >
>>> >
>>> > ___
>>> > Mailing list: https://launchpad.net/~kicad-developers
>>> > Post to : kicad-developers@lists.launchpad.net
>>> 
>>> > Unsubscribe : https://launchpad.net/~kicad-developers
>>> > More help   : https://help.launchpad.net/ListHelp
>>> >
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to : kicad-developers@lists.launchpad.net
>>> 
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>
>

>>>
>>>
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp

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

Re: [Kicad-developers] 6.0 action-based hotkeys proposal

[Jeff Young]

Just an update here:

The compromise didn’t turn out to be one after all.  I had always assumed 
TOOL_ACTION::LegacyHotKey( HK_RESET_LOCAL_COORD ) looked up the hotkey’s ID and 
stored it in the action, but it doesn’t: it looks up and stores the 
key-combination.  So the proposal: "The default hotkey key-combinations are 
defined in the TOOL_ACTION constructors." is already how it works.

That means I can put the mapping stuff on the long finger.  I’ll still be able 
to get rid of the wxIDs and all their associated mappings.

With one caveat: the toolbars are still using the wxIDs.  So we also need an 
ACTION_TOOLBAR.  (Which will also remove yet another copy of duplicated UI 
strings when instantiating toolbar buttons.)

I thought about a CONDITIONAL_TOOLBAR as well which would use the conditions to 
set the tool highlighting, but I think that’s probably overkill.  We already 
have SyncMenusAndToolbars() which updates their highlighting.

Cheers,
Jeff.


> On 12 May 2019, at 20:42, Jeff Young  wrote:
> 
> OK, how about a compromise:
> 
> The default hotkey key-combinations are defined in the TOOL_ACTION 
> constructors.
> 
> A config file is then read which contain maps from action-name to 
> key-combinations.  Each map entry is applied to its action, overwriting the 
> default.
> 
> This also allows us to skip yet-ever-more-config-options: if the user wants 
> immediate actions then they can import the immediate-action-mappings config 
> file.  The default will be the (somewhat more learner-friendly) 
> select-tool-mappings.
> 
> Similarly, as Tom suggests they could import the Altium-mappings config file.
> 
> For Tom’s last paragraph, I plan to rename CONTEXT_MENU to ACTION_MENU.  
> CONDITIONAL_MENUs constructor then takes a isContextMenu flag; if it’s not 
> set then conditions which evaluate to false produce disabled menu items 
> (rather than non-existant menu items).
> 
> We can then plug these menus into the main menu bar and get rid of the 
> wx-based IDs altogether (and all the corresponding EVT_MENU and EVT_UPDATE_UI 
> calls).  Actions will get dispatched automatically by TOOL_DISPATCHER, and 
> the enabling/disabling will get handled automatically by the CONDITIONs.
> 
> Comments?
> 
> Cheers,
> Jeff
> 
> 
>> On 10 May 2019, at 16:01, Tomasz Wlostowski  
>> wrote:
>> 
>> On 10/05/2019 11:46, John Beard wrote:
>>> Do the tool actions actually even need to know their hotkey? I think
>>> perhaps they shouldn't really care *what* the hotkey is or even if one
>>> is set, it's not their problem. It's the tool framework that should be
>>> maintaining this mapping.
>> 
>> Hi,
>> 
>> +1 here. The hotkeys (standard, sequential and
>> whatever-else-we-come-up-with) can be kept separate from the ACTION
>> objets in the code and stored in a configuration file. This would let
>> people coming from other EDA packages to have their own config files
>> with custom hotkey mappings.
>> 
>> IMO the same approach later can be used for toolbar/menu layouts.
>> 
>> Cheers,
>> Tom
>> 
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
> 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

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

Re: [Kicad-developers] Kicad's way of drawing filled zones

[Tomasz Wlostowski]

On 13/05/2019 17:46, Wayne Stambaugh wrote:
> I guess I should weigh in on this issue.  I would prefer we exhaust all
> other options before bumping opengl to some later version.

Hi Wayne,

I think JP's solution is the way to go, it fixes the original issue
instead of working it around. What's your opinion?

Cheers,
Tom



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

Re: [Kicad-developers] swig 4.0.0 patch

[Nick Østergaard]

@Wayne Stambaugh  any impediments to getting this merged?

On Fri, 10 May 2019 at 21:37, Steven A. Falco  wrote:
>
> Here is the result.  Everything passed.  The tests run surprisingly quickly.
>
>  sh-5.0# make test
> Running tests...
> /usr/bin/ctest --force-new-ctest-process
> Test project /builddir/build/BUILD/kicad-5.1.2
> Start 1: qa_python
> 1/6 Test #1: qa_python    Passed1.49 sec
> Start 2: common_gerbview
> 2/6 Test #2: common_gerbview ..   Passed0.12 sec
> Start 3: common_pcbnew
> 3/6 Test #3: common_pcbnew    Passed0.07 sec
> Start 4: common_eeschema
> 4/6 Test #4: common_eeschema ..   Passed0.08 sec
> Start 5: pcbnew
> 5/6 Test #5: pcbnew ...   Passed0.16 sec
> Start 6: eeschema
> 6/6 Test #6: eeschema .   Passed0.23 sec
>
> 100% tests passed, 0 tests failed out of 6
>
> Steve
>
>
> On 5/10/19 1:44 PM, Steven A. Falco wrote:
> > I'll run that.  Please give me a half hour or so, because I have to 
> > regenerate my rawhide build area - the "mock" tool ordinarily deletes 
> > everything as soon as a build completes.
> >
> >   Steve
> >
> > On 5/10/19 1:37 PM, Wayne Stambaugh wrote:
> >> `make test` will run all of the qa tests.  The python qa test is the
> >> first one run.  It's not comprehensive but it will let you know if
> >> you've completely broken python support.
> >>
> >> On 5/10/19 1:32 PM, Steven A. Falco wrote:
> >>> I used the footprint wizard to create some footprints.  I'll be happy to 
> >>> run qa tests - is there a "make" target for them?  I've never run them 
> >>> before...
> >>>
> >>> Steve
> >>>
> >>> On 5/10/19 1:21 PM, Wayne Stambaugh wrote:
>  Hi Steve,
> 
>  Did you actually test and confirm that the python scripting is working?
>   I ran a few of the default scripts just as quick and dirty test along
>  with the qa tests.  If the qa tests work for you, I will go ahead and
>  merge the patch.
> 
>  Wayne
> 
>  On 5/10/19 1:09 PM, Steve Falco wrote:
> > Should have mentioned that rawhide is using swig 4.0.0.
> >
> > On Fri, May 10, 2019, 1:06 PM Steve Falco  > > wrote:
> >
> > I am now able to build on rawhide with this patch. It works for me.
> >
> > Steve
> >
> > On Fri, May 10, 2019, 1:04 PM Wayne Stambaugh  > > wrote:
> >
> > Has anyone with swig 4 tested this patch yet.  I tested it and 
> > it
> > appears not to break anything with swig < 4.  If it works for
> > swig 4, we
> > should get this merged so platforms using swig 4 wont have to
> > downgrade
> > to build KiCad.
> >
> > Wayne
> >
> > On 5/9/19 3:58 AM, mdoes...@xs4all.nl
> >  wrote:
> > > Sorry about that, here's the patch
> > >
> > >
> > >
> > >
> > > ___
> > > Mailing list: https://launchpad.net/~kicad-developers
> > > Post to : kicad-developers@lists.launchpad.net
> > 
> > > Unsubscribe : https://launchpad.net/~kicad-developers
> > > More help   : https://help.launchpad.net/ListHelp
> > >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > 
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
> 
> >>>
> >>
> >
> >
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

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