[Kicad-developers] OCE and KiCad

I have had an out-of-tree IGES/STEP 3D plugin based on OCE for a few months now. I'd like to get this plugin into the main branch but there are some OCE issues that need to be resolved and which I'd need some help with: 1. Do we use only OCE or a choice of OCE or OpenCascade? 2. What is the

Re: [Kicad-developers] Stable release bug fixes.

Hello Wayne, Am 05.07.2016 um 17:14 schrieb Wayne Stambaugh: While I'm on the subject @Michael, would you please back port your boost context 1.61 patch? I'm sure at some point in the not too distant future, someone will try to build stable version 4 against boost 1.61. After having spent the

Re: [Kicad-developers] Trouble with bitmapped font

Hi Lorenzo, I was about to comment, I have no single experience with shaders, but from what I understood from KiCad shaders, they are "automatic generated" (converted from text file to CPP file?) during build? cmake? time.. So what you describe looks to be that it was using the old shader (as

Re: [Kicad-developers] Trouble with bitmapped font

On Tue, Jul 05, 2016 at 09:21:05PM +0200, Lorenzo Marcantonio wrote: > I fear that's yet another intel gpu issue :(( False alarm... *this time* was not because of my GPU suckitude :D For some reason a full recompile fixed the thing. AND the ugly text inconsitencies are gone! Woot! Good work,

[Kicad-developers] [PATCH proposal v2] Fix bitset access outside boundaries in LSET::FmtHex()

Same as before, but I missed "int" in a nested loop. I'm sorry for polluting the list, I should have checked better. Learning it the embarrassing way :( >From 1d3167c53618b01d77d6d3fa9aea46d0da3e1ce0 Mon Sep 17 00:00:00 2001 From: decimad Date: Tue, 5 Jul 2016 19:16:55

[Kicad-developers] Trouble with bitmapped font

I fear that's yet another intel gpu issue :(( After updating to a pcbnew with the new opengl bitmap font code it doesn't work anymore. It says: Unhandled exception class: St13runtime_error what: Could not find shader uniform: fontTexture stracing the thing (I tought it was some file missing...)

[Kicad-developers] [PATCH proposal] Fix bitset access outside boundaries in LSET::FmtHex()

The current implementation of LSET::FmtHex would access bits outside the range of of the bitset. I combined the fix with a code refactorization that clears up things in my opinion, which of course is the one that does not count ;) A save/reload cycle in debug builds that would crash does not

[Kicad-developers] [PATCH] Add size_t to "common.h" and remove KIROUND in favor of constexpr.

Add size_t to common.h for everyone to use. While touching that file also remove KIROUND macro and make the function constexpr replacing the compile-time functionality of the macro. >From 18cc52ed083a4c76ed3a845a77f0167d76bd5534 Mon Sep 17 00:00:00 2001 From: decimad Date:

Re: [Kicad-developers] git stable mirror

I'm OK with this. I just was on github and I didn't see any way to pull from a different repo in the add new repo section of github. Would the person (I think it was Miguel) who set this up for the product branch please create a mirror on github for the stable 4 branch? Thanks, Wayne On

[Kicad-developers] git stable mirror

Hey, would it be possible to add the stable branch to the git mirror as well? That would make my work much easier. Take this as a wishlist-item ;) Michael ___ Mailing list: https://launchpad.net/~kicad-developers Post to :

Re: [Kicad-developers] Stable release bug fixes.

Patching against stable and then merging forward sounds like a much better development strategy to me, I second this idea very much. :) On Jul 5, 2016 11:16, "Wayne Stambaugh" wrote: > As the development branch diverges from the stable release branch, it is > becoming

Re: [Kicad-developers] [PATCH] Fix for stable (4.02) version: PCBNEW crashes on loading a file exported from Gerbview

Thanks JP. I already merged the change when I saw the commit to the product branch and it without any issues. On 7/5/2016 11:23 AM, jp charras wrote: > Hi Wayne, > > Attached a patch to fix lp:1598809 issue. > It is for stable branch, and built against rev 6290. > > I committed this fix also

[Kicad-developers] [PATCH] Fix for stable (4.02) version: PCBNEW crashes on loading a file exported from Gerbview

Hi Wayne, Attached a patch to fix lp:1598809 issue. It is for stable branch, and built against rev 6290. I committed this fix also in product branch. Thanks. -- Jean-Pierre CHARRAS === modified file 'pcbnew/files.cpp' --- pcbnew/files.cpp2016-05-27 18:36:53 + +++ pcbnew/files.cpp

[Kicad-developers] Stable release bug fixes.

As the development branch diverges from the stable release branch, it is becoming difficult to merge patch commits from the development branch to the stable branch. I don't have that kind of time to clean up, build, and test the merge conflicts. The problem has gotten much worse since we've

Re: [Kicad-developers] Stable release 5 road map.

Maybe a better idea would be mention StepUp in the Pcbnew documentation and just provide a link to your documentation. This way you don't need to maintain your documentation in two places. perfect ... I'm going to create a pull request Thanks Maurice On 7/5/2016 2:17 PM, Wayne Stambaugh

Re: [Kicad-developers] Stable release 5 road map.

On 7/5/2016 7:22 AM, easyw wrote: >> I'm fine with this. Please create pull request against the current >> documentation. > I will Maybe a better idea would be mention StepUp in the Pcbnew documentation and just provide a link to your documentation. This way you don't need to maintain your

Re: [Kicad-developers] Stable release 5 road map.

Hi, On 05.07.2016 09:55, Wayne Stambaugh wrote: > If you are > working on new features that are not in the version 5 road map, please > inform me of what you working on and whether or not it will be ready to > release by FOSDEM 2017. My current branches: 1. writeable pin table This could

Re: [Kicad-developers] Stable release 5 road map.

I'm fine with this. Please create pull request against the current documentation. I will I'm sure our doc devs would be happy to help you. I'm not sure which section of the documentation this should go into. There is a scripting section in the Pcbnew so that may work. I don't know if that

Re: [Kicad-developers] Stable release 5 road map.

On 7/5/2016 5:23 AM, easyw wrote: > Hi Wayne, > > I think it would be nice to have also a note on KiCad user manual about > the external kicad StepUp exporter. I'm fine with this. Please create pull request against the current documentation. I'm sure our doc devs would be happy to help you.

Re: [Kicad-developers] Stable release 5 road map.

Hi Wayne, I think it would be nice to have also a note on KiCad user manual about the external kicad StepUp exporter. Please consider that to use this exporter, the users would need just a stable version of FreCAD (>=0.15) and a single python file ... Everything is based on an assembler

Re: [Kicad-developers] Stable release 5 road map.

Funny you should ask Cirilo since your name came up about the 3D model plugins. The current road map version 5 is published as part of the developer documentation which is available on the KiCad website. In the road map there is mention of support for exporting to STEP and/or IGES. Any chance

Re: [Kicad-developers] Stable release 5 road map.

Is there a pre-commit version somewhere where we can see what's on the roadmap? I want to work on a PCB API so that pcbnew importers/exporters can be turned into plugins and I can add an MCAD exporter, but given my free time and the size of the job I wouldn't expect it to be ready for FOSDEM

[Kicad-developers] Stable release 5 road map.

I spent much of yesterday discussing and finalizing the stable version 5 road map with everyone here at CERN. I will be committing the revised road map soon. Before I do, I want to make sure no one is working on anything outside the road map that I do not know about. If you are working on new

Re: [Kicad-developers] Regarding [PATCH] refactor_profile.patch

Hi, On 05.07.2016 01:45, Michael Steinberg wrote: > I was made aware that MinGW's implementation of std::chrono might be > lacking, but my testbed is not including that yet, so I cannot > double-check the implementation. I've started a build on Jenkins, but it will take a while until the system

[Kicad-developers] vacation

Just a heads-up. I will be away for vacation from 10/7 to 25/7 (or a little more, I am not sure about it, sorry). As usually I go on vacation almost without devices, apart from mobile and kindle. Probably I will leave my laptop at home also this time. Also not sure about it. KiCad docs are under