Re: [Kicad-developers] [RFC] gerbview fixing branch

I just tried to build this, and I have noticed that the combobox showing the layer on the top toolbar has an issue. When you click it you get a very small scroll list, in old gerbview it fills the entire height of the screen. 2015-09-15 21:02 GMT+02:00 Mark Roszko : > Not

Re: [Kicad-developers] [RFC] gerbview fixing branch

For the forseeable future because bzr has literally made me rage beyond belief, the gerbview branch is now on github. https://github.com/marekr/kicad-devel/tree/gerbview On Tue, Sep 15, 2015 at 3:08 PM, Adam Wolf wrote: > (When Clion was announced, I filed bugs on

Re: [Kicad-developers] Eeschema ERC should detect unmatched local labels

whooops sorry for the flood, looks like the email that was unable to be send was sent... Le 15/09/2015 08:22, yann jautard a écrit : Just my two cents here : I perfectly see that detecting unmached names on ERC will give lots of false errors, but what about taking the problem from the other

Re: [Kicad-developers] Can I move values in footprints library back to silkscreen?

On Tue, Sep 15, 2015 at 08:28:35AM +0200, yann jautard wrote: > Exactly. So why change something everyone is used to ? Didn't make the library policies :P I suggested the ones I use (tested & reliable) then some other set was decided. I think the dev list is not the place to discuss this and I

Re: [Kicad-developers] Can I move values in footprints library back to silkscreen?

Go talk to the library people, see https://launchpad.net/~kicad-lib-committers 2015-09-15 8:38 GMT+02:00 Lorenzo Marcantonio : > On Tue, Sep 15, 2015 at 08:28:35AM +0200, yann jautard wrote: > >> Exactly. So why change something everyone is used to ? > > Didn't make

Re: [Kicad-developers] Eeschema ERC should detect unmatched local labels

Just my two cents here : I perfectly see that detecting unmached names on ERC will give lots of false errors, but what about taking the problem from the other end, and when adding label to a wire having a little list with all the already used labels that appears and let you chose the one you

Re: [Kicad-developers] Can I move values in footprints library back to silkscreen?

On Mon, Sep 14, 2015 at 08:12:23PM +0200, nnn wrote: > Ok but my question is if I can move values from fab to silks (hidden) as > they were before in all pretty repos (and change convention) and use Fab > layers as assembly layers (as in IPC7351) to provide users ready to use > assembly layer with

Re: [Kicad-developers] Can I move values in footprints library backto silkscreen?

Why not keeping them on assembly (hidden)? Silk is way too busy and with too small resolution... in fact it usually can't hold the refdes, either :D Good idea - so values could stay on Fab but I'd hide them and add %R on the Fab. If somebody prefers values it's easy to change (find and replace

Re: [Kicad-developers] Eeschema ERC should detect unmatched local labels

Just my two cents here : I perfectly see that detecting unmached names on ERC will give lots of false errors, but what about taking the problem from the other end, and when adding label to a wire having a little list with all the already used labels that appears and let you chose the one you

Re: [Kicad-developers] Eeschema ERC should detect unmatched local labels

Just my two cents here : I perfectly see that detecting unmached names on ERC will give lots of false errors, but what about taking the problem from the other end, and when adding label to a wire having a little list with all the already used labels that appears and let you chose the one you

Re: [Kicad-developers] Can I move values in footprints library back to silkscreen?

Le 15/09/2015 08:24, Lorenzo Marcantonio a écrit : Whatever choice we make for the 'official' library *can't* satisfy everyone, there are just too many use cases/workflows... Exactly. So why change something everyone is used to ? ___ Mailing

Re: [Kicad-developers] [RFC] gerbview fixing branch

(When Clion was announced, I filed bugs on every blocker that stopped me from using it for KiCad. I revisited it periodically, but it looks like most of them have been fixed. Good to hear.) On Tue, Sep 15, 2015 at 2:02 PM, Mark Roszko wrote: > Not pushing this for

[Kicad-developers] [RFC] gerbview fixing branch

Not pushing this for stable, for the future. Just my work in progress. https://code.launchpad.net/~mark-roszko/kicad/gerbview This is mainly a UX improvement of gerbview rather than introducing features right now. 1. Cleaning, removed dead code, removed unused includes, removed some stupid. 2.

Re: [Kicad-developers] cmakeified wxFormBuilder fork

Woops, forgot to add, only builds fine on Linux right now. On Tue, Sep 15, 2015 at 3:07 PM, Mark Roszko wrote: > https://github.com/marekr/wxFormBuilder > > Is there any interest in a cmakeified version/fork of wxFormBuilder? > Because I know accessability of the wxfb is a

[Kicad-developers] 3D Model default paths

Hi, By default in RC1 the paths are set to:C:\mingw6w\[something]\kicad\modules\packages3d You have to change them to where kicad was installed to get the 3d viewer to work. Is this a bug? I have just managed to clone the code so it might be an issue I could look at. Thanks Dan

Re: [Kicad-developers] 3D Model default paths

For now you should set an environment variable named KISYS3DMOD to point to the top directory of your 3D model files; previously this was [installation path]\lib\packages3d - after that the software should behave as it used to. The 3D model path resolution is fundamentally broken and is

Re: [Kicad-developers] Problem of kicad-source and kicad-doc Packaging Help Documents

Actually the help documentation is broken on Windows too in the RC. The help is at C:\Program Files\KiCad\share\doc\kicad\help\en\kicad.pdf The searched paths are like this: Path C:\msys64\mingw64 C:\Program Files\KiCad\share\kicad\template\doc\help\en_GB C:\Program Files\KiCad\kicad.html

Re: [Kicad-developers] Problem of kicad-source and kicad-doc Packaging Help Documents

I filed a bug report for the Windows version so people using RC1 may trip over the bug report. https://bugs.launchpad.net/kicad/+bug/1496049 Best Regards, Brian. On 15 September 2015 at 17:04, Brian Sidebotham wrote: > As a PS - I think RC2 looks like it's just

Re: [Kicad-developers] KiCad RC1 crash! (PCB Calculator) Windows x64

Dan, you may run http://www.dependencywalker.com/ to see if there's anything funny going on with your system in particular. Perhaps some runtime component is being picked up outside of the KiCad install that's causing a bit of instability. Post the results if you're not used to the output so we

[Kicad-developers] Bad Error in footprint (Not picked up by DRC)

Is this the right place to report problems with footprints. In "Capacitors_Elko_ThroughHole:Elko_vert_20x10mm_RM5" There is a + symbol that is in the silkscreen, and also in the copper layer. When we saw our Gerber file it was shorting 2 nets together and the DRC had not picked this up. 1) What

Re: [Kicad-developers] Problem of kicad-source and kicad-doc Packaging Help Documents

As a PS - I think RC2 looks like it's just round the corner because not being able to look the help documents is pretty poor. There's no links to the documentation in the start menu either so we'd have to point people to the install directory\share\doc\kicad... etc. Best Regards, Brian. On 15

Re: [Kicad-developers] KiCad RC1 crash! (PCB Calculator) Windows x64

Works fine on my Win8.1 64-bit and Win 10 64. On Tue, Sep 15, 2015 at 7:23 AM, Nick Østergaard wrote: > I can not reproduce this on windows 8.0 64-bit. > > 2015-09-15 11:17 GMT+02:00 Dan Walmsley : >> In RC1 on Windowx x64, simply launch PCB Calculator from

Re: [Kicad-developers] KiCad RC1 crash! (PCB Calculator) Windows x64

I can not reproduce this on windows 8.0 64-bit. 2015-09-15 11:17 GMT+02:00 Dan Walmsley : > In RC1 on Windowx x64, simply launch PCB Calculator from KiCad and then > close it. > > The whole of Kicad will crash. > > Dan > > ___ >

Re: [Kicad-developers] Bad Error in footprint (Not picked up by DRC)

On Tue, Sep 15, 2015 at 04:19:16PM +, Dan Walmsley wrote: > Is this the right place to report problems with footprints. > In "Capacitors_Elko_ThroughHole:Elko_vert_20x10mm_RM5" > There is a + symbol that is in the silkscreen, and also in the copper layer. How should silk short a copper trace?

Re: [Kicad-developers] [PATCH] Fix assertion failure on attempt to orient a selected label

Since we are asking users to run debug builds (something I'm not 100% comfortable with but it is what it is), I went ahead and committed your patch. Thanks. On 9/14/2015 1:46 PM, Chris Pavlina wrote: > Well, personally, I don't like it - as developers looking for things to > refactor aren't the

Re: [Kicad-developers] Problem of kicad-source and kicad-doc Packaging Help Documents

On 9/14/2015 1:08 AM, Joseph Chen wrote: > On 09/13/2015 01:36 PM, Wayne Stambaugh wrote: >> The docs in lp:~kicad-developers/kicad/doc are obsolete. The latest >> docs are on github and are rebuilt whenever changes are made to the git >> repo and should be downloaded from there. >> >> It looks

Re: [Kicad-developers] KiCad RC1 crash! (PCB Calculator) Windows x64

There have been no changes from RC1(r6188) to r6197 that would affect the pcb calculator or starting/closing it. On Tue, Sep 15, 2015 at 7:43 AM, Dan Walmsley wrote: > Hi tried with the latest build 6197, and the bug has been fixed, but it > definitely comes back on the RC1

Re: [Kicad-developers] KiCad RC1 crash! (PCB Calculator) Windows x64

I'm not having any issues on w7 pro 64 bit either. @Dan, did you install this using and installer or build and install from source? On 9/15/2015 8:38 AM, Mark Roszko wrote: > There have been no changes from RC1(r6188) to r6197 that would affect > the pcb calculator or starting/closing it. > >

Re: [Kicad-developers] Problem of kicad-source and kicad-doc Packaging Help Documents

On 15 September 2015 at 15:03, Wayne Stambaugh wrote: > > > On 9/14/2015 1:08 AM, Joseph Chen wrote: >> On 09/13/2015 01:36 PM, Wayne Stambaugh wrote: >> The failure above is inevitable, because the running pcbnew is looking >> for file name "pcbnew.pdf", while the actual