Re: [Kicad-developers] swig 4.0.0 patch

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

Re: [Kicad-developers] Developer doc web page down

Hi Nick, Any chance you can get pictures in python docs fixed too? Like inheritance graph here http://docs.kicad-pcb.org/doxygen-python/classpcbnew_1_1BOARD__ITEM.html This has been broken for a while. On Fri, May 10, 2019 at 7:59 AM Nick Østergaard wrote: > Disclamier: I disabled the auto

Re: [Kicad-developers] IMPORTANT build change for OSX users

:) > On 10 May 2019, at 20:32, Adam Wolf wrote: > > I actually got a friendly build error last night! > > 03:24:32 default: In file included from ./src/regex/regcustom.h:40: > 03:24:32 default: ./include/wx/chartype.h:192: > 03:24:32 default: 10: error: "wxUSE_UNICODE_UTF8 is not >

Re: [Kicad-developers] Problems with Boost library building Kicad from git sources on Slackware64-current Linux

On Fri, 10 May 2019, mdoes...@xs4all.nl wrote: You need to use: cmake -DBoost_NO_BOOST_CMAKE=ON Many thanks for that. Adding it and applying your SWIG patch (posted in another thread) let me build OK. Afterwards I also tried, $:/tmp/SBo/kicad-git/build$ make test Running

[Kicad-developers] Proposal: Shared Plugin Development Repository

https://forum.kicad.info/t/proposal-shared-plugin-development-repository/16943 *If you are a plugin developer*, please vote here: https://github.com/kicad-extra/arkon/issues/1 1 -- This is a proposal to create

Re: [Kicad-developers] swig 4.0.0 patch

Mark, I merged your patch into the master and 5.1 branches. Thank you for your contribution to KiCad. Cheers, Wayne On 5/9/19 3:58 AM, mdoes...@xs4all.nl wrote: > Sorry about that, here's the patch > > > > > ___ > Mailing list:

[Kicad-developers] KiCad janitor down?

Is the KiCad janitor sleeping on the job again? I push a fix[1] for lp:1828214 a couple of hours ago and it still has not updated the bug tracker status. Generally it doesn't take this long. Cheers, Wayne [1] https://git.launchpad.net/kicad/commit/?id=ae54f34392407cfd9d4628cf3087f07f239cebb2

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

The non-zero width edges might be creating even larger problems. If we have a round edge and we generate 32 segments for it, and those segments are non-zero width, then don’t we generate another 32 lines at the end of each segment to make it round? Or do we use some kind of shader there? >

Re: [Kicad-developers] swig 4.0.0 patch

Hi Steve, Make test will run the tests. You need to run that after building. The qa_all_tests can be used to build only tests, but it is redundant if you already built everything. Cheers, John On 10 May 2019 18:32:21 BST, "Steven A. Falco" wrote: >I used the footprint wizard to create some

Re: [Kicad-developers] swig 4.0.0 patch

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

Re: [Kicad-developers] 6.0 task proposal

I apologize if this is diverging from the subject too much, but it, at least, has the potential to be pertinent to an architecture underlying this topic. I'm finding more programs emplying the powerful concept of command pallets[1] and find the idea to be very appealing for a program like KiCad.

Re: [Kicad-developers] 6.0 task proposal

I also think command palettes are great, and one of the things I want to explore in the future in comparison to chained hotkeys as a way of getting past the restrictive nature of our current hotkey system. I think this is mostly irrelevant to the change Jeff proposes -- in the new proposed

Re: [Kicad-developers] swig 4.0.0 patch

`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

[Kicad-developers] eemodern - segfault on eeschema when aborting a paste operation with "esc" key on commit 5f4a6e33a0054489434b7f388e8dc559707140f6 (also in previous)

This mail just to "close" the issue. This morning I just Tested commit 589a37bfe8c773d621b6dae9a0f3347babaf1ba1 and now it works correclty for me (no more segfaults). Cheers, Dino. ___ Mailing list: https://launchpad.net/~kicad-developers Post to

[Kicad-developers] 6.0 task proposal

Once we remove PCBNew’s legacy canvas I’d like to propose that we simplify the hotkey architecture: Get rid of the HotKey data-structures; have Actions specify a hotkey key-combination. Advantages: 1) Actions are already grouped into common, schematic, pcb, etc. so this will get rid of the

Re: [Kicad-developers] Problems with Boost library building Kicad from git sources on Slackware64-current Linux

You need to use: cmake -DBoost_NO_BOOST_CMAKE=ON ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help :

Re: [Kicad-developers] 6.0 task proposal

> On 10 May 2019, at 11:46, John Beard wrote: > > On 10/05/2019 11:08, Jeff Young wrote: >> Once we remove PCBNew’s legacy canvas I’d like to propose that we simplify >> the hotkey architecture: >> Get rid of the HotKey data-structures; have Actions specify a hotkey >> key-combination. > >

Re: [Kicad-developers] 6.0 task proposal

It’s worth pointing out that either scheme also has the huge advantage that a hotkey can be assigned to any Action (and going forward, that will be pretty much everything we do). > On 10 May 2019, at 12:15, John Beard wrote: > > On 10/05/2019 11:53, Jeff Young wrote: >> My concern with this

Re: [Kicad-developers] 6.0 task proposal

On 10/05/2019 11:53, Jeff Young wrote: My concern with this is that the more spread out you store the info, the more maps you need, and the more room for error you have (when maps are missing keys, etc.). I have a single big default list in mind, rather than many disparate lists. This is

Re: [Kicad-developers] 6.0 task proposal

Jeff, You proposal doesn't seem to meet the objectives we discussed about allowing the user to chose the hotkey behavior for actions that can perform an action at the current cursor position but maybe I'm missing something. Also, don't forget about Jon's proposal for chained key combinations. I

Re: [Kicad-developers] 6.0 task proposal

On 10/05/2019 11:08, Jeff Young wrote: Once we remove PCBNew’s legacy canvas I’d like to propose that we simplify the hotkey architecture: Get rid of the HotKey data-structures; have Actions specify a hotkey key-combination. +0 (strongly support stripping legacy hotkey infrastructure,

Re: [Kicad-developers] 6.0 task proposal

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.

Re: [Kicad-developers] IMPORTANT build change for OSX users

Awesome! I’ll still give it a week or so before removing the mutex’s so that everyone can catch up. That being said, if some of you forget and then start experiencing seemingly-random crashes, you’ll know why. ;) Cheers, Jeff > On 10 May 2019, at 14:42, Adam Wolf wrote: > > I have made

Re: [Kicad-developers] 6.0 task proposal

Wayne is referring to chained (sequential) hotkeys that I discussed with the group at KiCon (this has also been requested on the tracker[1]) I think that the architecture you proposed could support this too. We haven't yet gotten in to any thinking about exactly how the architecture for chained

Re: [Kicad-developers] Developer doc web page down

Thanks, Nick! On Thu, May 9, 2019 at 4:38 PM Nick Østergaard wrote: > It should work now, and it may also be a bit more responsive. > > On Thu, 9 May 2019 at 16:16, Nick Østergaard wrote: > > > > I know. I will report back when it works. > > > > tor. 9. maj 2019 16.15 skrev Jon Evans : > >> >

Re: [Kicad-developers] 6.0 task proposal

Hi Wayne, That’s right; this proposal was just supposed to be about architecture, not features. However, it does need to support new features. I don’t think there’s an issue with immediate vs. select-tool. As for chaining, you’re really chaining actions, not hotkeys, right? So either

Re: [Kicad-developers] Developer doc web page down

Disclamier: I disabled the auto update for now as the change is not merged pending review. I will fix it after the weekend. fre. 10. maj 2019 16.54 skrev Jon Evans : > Thanks, Nick! > > On Thu, May 9, 2019 at 4:38 PM Nick Østergaard wrote: > >> It should work now, and it may also be a bit more

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

Hi, I've been recently playing with Victor's huge 32-layer PCB design and trying to improve the performance of pcbnew for larger designs. This board causes even pretty decent PCs to crash/render glitches due to pcbnew's enormous VBO (Vertex Buffer) memory consumption. It turns out it's caused by

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

Does anyone have a good sense of which hardware / software platforms would be impacted by a switch to OpenGL 3.0 as baseline requirement? As far as I am aware, all commercial tools in the space have more advanced / modern system requirements than KiCad, with the possible exception of Eagle. We

Re: [Kicad-developers] swig 4.0.0 patch

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

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

I don't think any desktop computer released after 2010 would have issues with GL3 unless the hardware/OS is defective in some way. On Fri, May 10, 2019 at 11:43 AM Jon Evans wrote: > Does anyone have a good sense of which hardware / software platforms would > be impacted by a switch to OpenGL

Re: [Kicad-developers] swig 4.0.0 patch

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

Re: [Kicad-developers] swig 4.0.0 patch

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.

Re: [Kicad-developers] swig 4.0.0 patch

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

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

Am 2019-05-10 12:33, schrieb Tomasz Wlostowski: Hi, I've been recently playing with Victor's huge 32-layer PCB design and trying to improve the performance of pcbnew for larger designs. This board causes even pretty decent PCs to crash/render glitches due to pcbnew's enormous VBO (Vertex

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

Hi Tomasz, This is an interesting challenge! Did you consider other approaches apart from the ones you listed? I have no full knowledge how GAL is rendering so maybe some of my suggestions may not make sense. I believe GAL is already doing some cache of the layers using textures. It may not

Re: [Kicad-developers] swig 4.0.0 patch

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