Re: [Kicad-developers] PPA: library packages modifications

Hi Package naming will change in ppa to follow exactly the same schema as debian's packages. I will process those change as soon as possible. Regards. Le 16 févr. 2018 23:46, "Nick Østergaard" a écrit : 2018-01-15 11:55 GMT+01:00 Carsten Schoenert

Re: [Kicad-developers] PPA: library packages modifications

Hello Nick, Am 16.02.2018 um 23:45 schrieb Nick Østergaard: ... > So what did the final naming become? > > According to the PPA it looks like: > https://code.launchpad.net/~js-reynaud/+archive/ubuntu/ppa-kicad/+packages?field.name_filter=_filter=published_filter=artful > > kicad-library (not

Re: [Kicad-developers] [PATCH] Pcbnew menu bar

Hi all, Probably not too relevant, but can we have a workaround of https://bugs.launchpad.net/kicad/+bug/1575097 (hidden icons) by adding View -> High Contrast (Checkable like the "Flip board view") View -> Tracks -> Outline (Radio button like the canvas selector) -> Fill View ->

Re: [Kicad-developers] Reverse parsing for spaces

It probably doesn't make much sense at this point given that the file format is going to be replaced in v6 so it will be a moot issue. I plan on quoting all strings in the new file format so spaces will pose no problem. On 02/16/2018 06:57 PM, hauptmech wrote: > Just adding another opinion to

Re: [Kicad-developers] Version string changes.

Thank you. I see you also added the 5.0-dev tag for this. 2018-02-13 15:04 GMT+01:00 Wayne Stambaugh : > Just a quick notice to all of the package devs that may impact kicad > version strings used for packaging. I have changed the way the version > strings are generated in

Re: [Kicad-developers] Reverse parsing for spaces

Just adding another opinion to the mix here. %20 does not make the current file format any more difficult to read than it already is. The current format can be parsed by a human and edited with a text editor. That's good, and that's all you need. \x20 (which is what you would use if you were

Re: [Kicad-developers] Improving Eagle Import netlist matching

Hi all, Sorry I didn't get to it sooner. Been busy at a new job. I was going to say that globals will work fine except for the visual aspect. Though I think just replacing the global net on the pcb with the net from the schematic with the matching end label ( ignoring any sheet path) should

Re: [Kicad-developers] Improving Eagle Import netlist matching

Alright, I switched the importer to use global net labels. Perhaps schematics are not always the prettiest ones, but at least they are equivalent to the original project. Cheers, Orson On 02/16/2018 02:59 PM, Wayne Stambaugh wrote: > If using global nets resolves the issue and doesn't cause any

Re: [Kicad-developers] PPA: library packages modifications

2018-01-15 11:55 GMT+01:00 Carsten Schoenert : > Hi, > > adding some notes here for the planned Debian packaging. > Jean-Samuel emailed my some days ago already about his planes and we > have tried to stay in contact about a consistent packaging schema > between Ubuntu

Re: [Kicad-developers] Reverse parsing for spaces

> My beef with % encoding is that it is not human readable. I won’t argue with that. It’s a struggle at best. > On 16 Feb 2018, at 21:17, Wayne Stambaugh wrote: > > My beef with % encoding is that it is not human readable. Human > readability is an important goal when

Re: [Kicad-developers] Reverse parsing for spaces

My beef with % encoding is that it is not human readable. Human readability is an important goal when designing KiCad file formats. On 2/16/2018 4:04 PM, Jeff Young wrote: > Yeah, that’s why I was suggesting %-encoding. Substituting %20 for spaces > wouldn’t be a file format change. And it’s

Re: [Kicad-developers] Reverse parsing for spaces

Yeah, that’s why I was suggesting %-encoding. Substituting %20 for spaces wouldn’t be a file format change. And it’s a common enough escape sequence that anyone writing 3rd-party tools could easily deal with it. I think %-encoding is probably better than ‘\’-prefixing, mostly because it can

Re: [Kicad-developers] Reverse parsing for spaces

The space issue is tricky because it's not a quoted string. Quoting the string would be a file format change although you could make the argument so is the space. I believe all of the other strings in question are quoted in the file format so it should just be a matter of quoting any special

Re: [Kicad-developers] Reverse parsing for spaces

Hi Jeff- I was working on that but just got slammed at work, so there's been less time for testing/fixing all of the places where it touches. But there's a three-day weekend coming up here in the states, so I'm hopeful (eternally so) that there will be sufficient time to complete it. That said,

[Kicad-developers] Reverse parsing for spaces

There was an issue a while back where we were considering reverse parsing something or another so that spaces didn’t trip us up. What’s the status of that? The reason I ask is that I’m looking at another bug where a user wants to put ‘/‘ characters in their global labels (which we of course

Re: [Kicad-developers] [PATCH] Pcbnew menu bar

> Is 0003-Fix-up-file-menu-and-hotkeys.patch suitable for merging straight away? Yes, I believe it is. Cheers, Jeff. > On 16 Feb 2018, at 19:31, Michael Kavanagh wrote: > > Footprint library table is has a global part yes, but its still to do > with the PCB being

Re: [Kicad-developers] [PATCH] Pcbnew menu bar

Footprint library table is has a global part yes, but its still to do with the PCB being designed and not the application, so IMO belongs in the setup menu. Regardless, I'll work on the revised plans this weekend, and move "Grid Settings..." to the view menu. Is

Re: [Kicad-developers] Getting kicad to work with wxPython Phoenix

Hello Wayne, as Nick has written about a different part in this thread ... Am 24.11.17 um 14:00 schrieb Wayne Stambaugh: > I'm surprised there is no RFP for phoenix yet given that it will (has) > become the replacement for wxpython. wxpython is a dead code base as > far as I know. I certainly

Re: [Kicad-developers] Getting kicad to work with wxPython Phoenix

Hello Miles, Since it seems that Phoenix has now been released I just tried to test against it with your patch. But I get a build error related to sip. [ 75%] Building CXX object pcbnew/CMakeFiles/pcbnew_kiface.dir/pcbnew.cpp.o In file included from

Re: [Kicad-developers] Build broken against glm 0.9.8.4

Confirmed. I just built against Fedora 27, and the compiler error has been resolved. Fedora released glm 0.9.8.4-5.fc27 on Feb 7, which contains the note: "Fix compatibility with GCC 7.3.1 (#1542941)" Steve On 02/16/2018 11:07 AM, Nick Østergaard wrote: > It looks like the fedora

[Kicad-developers] Update needed for AUTHORS.txt file

Greetings. Some time ago one of the messages to this mailing list made me look at the AUTHORS.txt file. It says "See also CHANGELOG.txt for contributors." but there is no such file. The most recent changelog file is the CHANGELOG-2012.txt file. The comment about where to look for the names

Re: [Kicad-developers] [PATCH] Pcbnew menu bar

Hey Jeff, I agree with these changes so as soon as Michael posts the revised patches, we can get them reviewed and I can merge them. Thanks for helping out with the patch review. I appreciate the help. Cheers, Wayne On 2/16/2018 10:47 AM, Jeff Young wrote: > Hi Wayne, > > With these

Re: [Kicad-developers] Build broken against glm 0.9.8.4

It looks like the fedora builds are working again. I guess the issue I noticed was in fedora then. Thanks. 2018-02-07 16:09 GMT+01:00 Maciej Sumiński : > I was told the problem is gcc 7.3 and glm 0.9.8.x combination. There is > a patch on our bug tracker [1] that is

Re: [Kicad-developers] [PATCH] Pcbnew menu bar

Hi Wayne, With these changes: “Footprint Library Wizard” and “Footprint Library Table” are environmental settings so they belong under Preferences, not Setup. That (and moving “User Defined Grid…”) should make it short enough not to need the nested menu for Dimensions. I still feel strongly

Re: [Kicad-developers] [PATCH] Pcbnew menu bar

Gentlemen, Where do we stand on this? I would like to get this into rc1 if possible just to reduce long term maintenance issues. Once I branch version 5, all patches have to be merged from the development branch to the version 5 branch so it makes more work for me. Thanks, Wayne On 2/15/2018

Re: [Kicad-developers] Kicad-from-scratch: Segfault after unarchiving active project.

Hi Jeff, Many thanks for quick reaction. I have just pushed your patch. Cheers, Orson On 02/16/2018 03:22 PM, Jeff Young wrote: > Hi Clemens, > > If you build your own Kicad, you can try the patch attached to the below bug > report. > > Cheers, > Jeff. > >> On 16 Feb 2018, at 13:00, Jeff

Re: [Kicad-developers] Non translatable string

I don't think we can fix this. The "Apply" string is referenced by the wxID_APPLY constant in wxWidgets and is not actually defined in the KiCad source. It should be handled internally by wxWidgets. Obviously that is not happening. It is possible that this string is not translated in

[Kicad-developers] Zone vs polygon outline

Hello, there is an inconsistency between the way zones and polygons handle their outline. In zones outline is drawn on the inside, so the size of the zone is exactly the same as drawn by the user. In polygons, half of the width of the outline is added to the size of the polygon. Illustration

Re: [Kicad-developers] Kicad-from-scratch: Segfault after unarchiving active project.

Thank you! The patch https://launchpadlibrarian.net/357282373/0003-Rebuild-project-tree-when-unarchiving-into-project-d.patch fixes the crash! -> Good. But there seems to be a minor issue left: After Unarchive Project, the project tree also contains the .pro file as a branch. The .pro file

Re: [Kicad-developers] Kicad-from-scratch: Segfault after unarchiving active project.

Hi Clemens, If you build your own Kicad, you can try the patch attached to the below bug report. Cheers, Jeff. > On 16 Feb 2018, at 13:00, Jeff Young wrote: > > Thanks, Clemens. I can reproduce this easily. > > Logged as: https://bugs.launchpad.net/kicad/+bug/1749955 >

Re: [Kicad-developers] Improving Eagle Import netlist matching

If using global nets resolves the issue and doesn't cause any other issues, it has my vote as well. On 02/16/2018 08:36 AM, Maciej Sumiński wrote: > I vote for switching to global nets. I may handle this, just want to be > sure Russell has not started already working on it, so there is no work >

Re: [Kicad-developers] Improving Eagle Import netlist matching

I vote for switching to global nets. I may handle this, just want to be sure Russell has not started already working on it, so there is no work duplication. Regards, Orson On 02/16/2018 02:17 PM, Wayne Stambaugh wrote: > Gentlemen, > > What is the status of this bug fix? I know there was some

Re: [Kicad-developers] Improving Eagle Import netlist matching

Gentlemen, What is the status of this bug fix? I know there was some discussion about this patch. Do we have path forward on this yet? I would like to get this into rc1 if possible. Thanks, Wayne On 02/14/2018 08:17 AM, Russell Oliver wrote: > Please find the attached patch for this issue. 

Re: [Kicad-developers] Kicad-from-scratch: Segfault after unarchiving active project.

Thanks, Clemens. I can reproduce this easily. Logged as: https://bugs.launchpad.net/kicad/+bug/1749955 Cheers, Jeff. > On 16 Feb 2018, at 12:14, Clemens Koller wrote: > > Attaching debug information of GDB session: > >

Re: [Kicad-developers] Git tags for 5.x.x-rc1 yet?

I haven't created the 5.0 branch which will become rc1. There are two critical (segfault) bugs in the bug tracker that need to be fixed before that can happen. I was prepared to create the branch over the weekend but the two bugs in question were just reported yesterday so it depends how quickly

Re: [Kicad-developers] Kicad-from-scratch: Segfault after unarchiving active project.

Attaching debug information of GDB session: -8<- [...] [New Thread 0x7fffe6711700 (LWP 24139)] [Thread 0x7fffe6711700 (LWP 24139) exited] SetProjectFullName: old:'' new:'/home/admin/share/project/kicad/project/test9/test9.pro' 13:10:42: Debug: FileWatcherReset: watched paths: 13:10:42:

[Kicad-developers] Kicad-from-scratch: Segfault after unarchiving active project.

Some more KiCad-from-scratch testing on Arch Linux: Setup: KiCad Version: (2018-02-16 revision 3c9a5b096)-master, release build There is an previously archived project in some working directory .../test9/test9.zip next to the project files test9.pro (as well as an empty schematics and layout,

[Kicad-developers] KiCad-from-scratch: View->Refresh with empty project functional?

Hi! Whenever KiCad is started from scratch [1], in the menu View->Refresh [Ctrl-R] is not greyed out (same with toolbar icon). Is there anything which can be refreshed at that point? Regards, Clemens [1] KiCad-from-scratch: rm -r ~/.config/kicad rm -r ~/.cache/kicad

Re: [Kicad-developers] Git tags for 5.x.x-rc1 yet?

Thanks! Will wait. :-) On 2018-02-16 12:07, Maciej Sumiński wrote: > Hi Clemens, > > RC1 is not released/tagged yet, Wayne plans to do it this weekend [1]. > > Regards, > Orson > > 1. https://lists.launchpad.net/kicad-developers/msg33890.html > > On 02/16/2018 12:04 PM, Clemens Koller wrote:

Re: [Kicad-developers] Git tags for 5.x.x-rc1 yet?

Hi Clemens, RC1 is not released/tagged yet, Wayne plans to do it this weekend [1]. Regards, Orson 1. https://lists.launchpad.net/kicad-developers/msg33890.html On 02/16/2018 12:04 PM, Clemens Koller wrote: > Hi, There! > > I am wondering if I am following the right git repository on

[Kicad-developers] Git tags for 5.x.x-rc1 yet?

Hi, There! I am wondering if I am following the right git repository on github/launchpad to do testing for V5 as there is no 5.0.0-rc1 or -testing tag. Do you, Wayne(?) keep the V5 stuff in your private repo or are they just not out there, yet? $ git remote show origin * remote origin Fetch