Re: [Kicad-developers] Track locking

If they are "locked", then yes, I think they should not be moved, neither by the user nor by PNS. On Mon, May 09, 2016 at 05:43:24PM +0200, Maciej Sumiński wrote: > I have noticed there is an option to mark tracks & vias as 'locked' in > the legacy canvas (right click on a track->Set

Re: [Kicad-developers] pcbnew preferences - cleanup before rework - collab

Thanks to the people who gave input on this before. I'm just going to point this out one more time and see if I can get another wave of input, before summarizing it and trying to get some changes made :) https://misc.c4757p.com/pad/p/pcbnew-prefs On Wed, May 04, 2016 at 04:37:53PM -0400, Chris

Re: [Kicad-developers] PATCH: OS X Beep Fix

Thank you! I pushed your patch in revision 6775 with coding style fixes. On Thu, May 05, 2016 at 01:44:54AM -0600, Collin Anderson wrote: > Hi, I have attached a patch that fixes an annoyance that is present in the > footprint editor and pcbnew, but only under OS X. In either of these >

Re: [Kicad-developers] [PATCH 0/4] Backport libcurl code from development branch

I do hope you didn't intent to credit Dick for 6640, that one's mine! ;) On Thu, May 05, 2016 at 10:57:34AM -0400, Wayne Stambaugh wrote: > On 5/5/2016 10:47 AM, Chris Pavlina wrote: > > On Thu, May 05, 2016 at 10:15:02AM -0400, Wayne Stambaugh wrote: > >> [snip] > >> &

Re: [Kicad-developers] [PATCH 0/4] Backport libcurl code from development branch

On Thu, May 05, 2016 at 10:15:02AM -0400, Wayne Stambaugh wrote: > [snip] > > I didn't see any credit to Dick for the work he did on libcurl > transition so that will need to be added to commit message. Hm, did he write any of the code in these patches? > > On 5/5/2016 4:39 AM, Simon Richter

Re: [Kicad-developers] PATCH: OS X Beep Fix

Yes, please don't go interleaving preprocessor statements with fragments of code like that, it's ugly and very prone to causing mistakes and misunderstandings. #ifdef __APPLE__ if( type != wxEVT_CHAR ) aEvent.Skip(); #else aEvent.Skip(); #endif ^ That is much clearer to me, it actually

Re: [Kicad-developers] Preferences rework - pcbnew

t; > On Wed, May 4, 2016 at 9:19 AM, Chris Pavlina <pavlina.ch...@gmail.com> > wrote: > > > While I understand your point, and I think I agree with it (though I'm > > almost > > on the fence), I wonder if I should explain - I think the argument for > > removi

Re: [Kicad-developers] Round Rectangle corner radius control suggestion

An alternative interface could be to optionally accept % as a unit in fields for values with a clear relationship to another value, as the fields already do accept units like in and mm. I kind of like the idea, but I wonder how intuitive that would be - it works fine if you know it's there, but

Re: [Kicad-developers] Preferences rework - pcbnew

by now and it might > > reduce development workload for new features. > > > > On Tue, May 3, 2016 at 7:52 AM, Wayne Stambaugh <stambau...@gmail.com> > > wrote: > >> On 5/2/2016 4:54 PM, Chris Pavlina wrote: > >>> I'd like to start having a l

Re: [Kicad-developers] Bitmap fonts (+ dotted grid)

I like that the distinction between bright and dark lines was kept into the dots. The extra coarser grid on top of the fine grid is very useful :) On Tue, May 03, 2016 at 11:01:35PM +0200, Nick Østergaard wrote: > 2016-05-03 21:10 GMT+02:00 Bernhard Stegmaier : > > You

Re: [Kicad-developers] Preferences rework - pcbnew

ive? > > 2016-05-03 14:52 GMT+02:00 Wayne Stambaugh <stambau...@gmail.com>: > > On 5/2/2016 4:54 PM, Chris Pavlina wrote: > >> I'd like to start having a look at how I can organize the preferences for > >> pcbnew, having mostly finished in eeschema. (

Re: [Kicad-developers] PATCH: 3D resolver

ne who > complained to pound sand. Unfortunately my role as product leader makes > things a bit more complicated. I'm with you on the c++11 side of > things. We'll get there eventually just not as quickly as I would like. > > On 5/3/2016 10:05 AM, Chris Pavlina wrote: > >

Re: [Kicad-developers] Bitmap fonts (+ dotted grid)

Remember, I'm about to rearrange all the options anyway, so it's probably not much of a concern where it goes for now. Feel free to begin the preferences organization bikeshedding on the thread I already started for that, though :D On Tue, May 03, 2016 at 03:58:21PM +0200, Maciej Sumiński wrote:

Re: [Kicad-developers] PATCH: 3D resolver

5/2/2016 8:23 PM, Chris Pavlina wrote: > > On Mon, May 02, 2016 at 11:40:25AM -0400, Wayne Stambaugh wrote: > >> I'm not 100% sure we should pull the plug on mingw32/msys1 just yet. > >> There will most likely be a bunch ubuntu and fedora users who are using > >> older s

Re: [Kicad-developers] PATCH: 3D resolver

On Mon, May 02, 2016 at 11:40:25AM -0400, Wayne Stambaugh wrote: > I'm not 100% sure we should pull the plug on mingw32/msys1 just yet. > There will most likely be a bunch ubuntu and fedora users who are using > older stable versions that this will effect as well. Personally I'm > fine with

[Kicad-developers] Preferences rework - pcbnew

I'd like to start having a look at how I can organize the preferences for pcbnew, having mostly finished in eeschema. (A few things remain to be tweaked and will probably be done at the same time as pcbnew, to keep things in sync). The problem of legacy preferences vs GAL preferences needs to be

Re: [Kicad-developers] Debian and Ubuntu packaging.

To be entirely honest and somewhat opinionated, I have no problem telling Debian users that they chose a distribution that tampers with packages and so they get to live with it. KiCad's easy to build anyway, should they decide they don't like that choice. Perhaps we could provide our own Debian

Re: [Kicad-developers] New pcbnew features and versioning

> Thanks, > > Wayne > > On 5/2/2016 12:34 PM, Chris Pavlina wrote: > > Wayne, > > > > The patch includes a minor refactoring of a function that ended up not being > > necessary in the end - originally my code made changes to it that were hard > > witho

Re: [Kicad-developers] Eeschema refactor update.

I'll send you a big bag to collect all that yak hair. On Mon, May 02, 2016 at 02:14:58PM -0400, Wayne Stambaugh wrote: > After several more false starts trying to design a unified SCHEMATIC > object, I've finally figured out the thorn in my side. There is a > circular dependency between

Re: [Kicad-developers] Missing features in GAL

On Mon, May 02, 2016 at 05:29:06PM +0200, Maciej Sumiński wrote: > Now we plan to fill the remaining gaps between the legacy and GAL > canvases. I think it is a good opportunity to either improve or remove > certain tools, therefore I am asking for your input. > > What do you think about porting

Re: [Kicad-developers] New pcbnew features and versioning

patch. I will apply it to all of my > systems and test it to make sure it doesn't break anything. > > Thanks, > > Wayne > > On 5/1/2016 6:59 PM, Chris Pavlina wrote: > > Followed up on this question in a separate mail. > > > > Patch is attached. Please have a g

Re: [Kicad-developers] New pcbnew features and versioning

Followed up on this question in a separate mail. Patch is attached. Please have a good look over it, if it's going to stable I don't want to be the only one who's had a look :) On Sat, Apr 30, 2016 at 07:57:36PM -0400, Chris Pavlina wrote: > I'm very close to finished - I'll take some t

[Kicad-developers] pcbnew format versioning and broken libraries

Hi, Recently I pointed out that if a library contains broken, or in this case too recent, footprints, modedit silently fails to load the library. I asked about preferred ways to handle this, and was going to modify things such that an actual message is displayed. Turns out I filed a bug report

Re: [Kicad-developers] FOOTPRINT_LIBRARY_HEADER_CNT

changes in actual behavior, and I will be testing this section very thoroughly tomorrow.) On Sun, May 01, 2016 at 08:06:41AM +0200, jp charras wrote: > Le 01/05/2016 à 05:39, Chris Pavlina a écrit : > > I have a pretty specific question about some relatively old code that > > intersect

[Kicad-developers] FOOTPRINT_LIBRARY_HEADER_CNT

I have a pretty specific question about some relatively old code that intersects with what I'm working on now. Dick was the original author, not sure if he'd remember... - pcbnew/legacy_plugin.h: 33 #define FOOTPRINT_LIBRARY_HEADER "PCBNEW-LibModule-V1" 34 #define

Re: [Kicad-developers] New pcbnew features and versioning

k and got sick on top of that so my motivation to > spend what little free time I had working on KiCad was low. > > Cheers, > > Wayne > > On 4/28/2016 2:38 PM, Chris Pavlina wrote: > > Just a quick ping to reassure y'all I'm still working on this - been caught > >

Re: [Kicad-developers] Copyright header

On Fri, Apr 29, 2016 at 10:16:04AM -0400, Wayne Stambaugh wrote: > On 4/29/2016 9:59 AM, Chris Pavlina wrote: > > > > I don't think it's allowed to use "YEAR" in copyright notices, I was just > > using > > that as a placeholder :P > > I would hope

Re: [Kicad-developers] Copyright header

ri, Apr 29, 2016 at 09:48:59AM -0400, Wayne Stambaugh wrote: > On 4/29/2016 8:31 AM, Chris Pavlina wrote: > > Hi, > > > > The following appears in our copyright header: > > > > * Copyright (C) 2015 > > * Copyright (C) 2015 KiCad Developers, see CHANGELOG.TX

[Kicad-developers] Copyright header

Hi, The following appears in our copyright header: * Copyright (C) 2015 * Copyright (C) 2015 KiCad Developers, see CHANGELOG.TXT for contributors. CHANGELOG.TXT hasn't been updated since 2012. Perhaps we should modify this somehow? Would it be possible to shorten it to just "Copyright (C) YEAR

Re: [Kicad-developers] New pcbnew features and versioning

ard file format > was implemented over fours years ago there have been a handful of > changes. I think we're going to be OK with just the date code. > > On 4/12/2016 12:06 PM, Chris Pavlina wrote: > > Let's just not do more than one format change in a single day... I thin

Re: [Kicad-developers] Optimization

run the right code... I still notice *no* difference in KiCad. On Tue, Apr 26, 2016 at 11:07:52AM -0400, Chris Pavlina wrote: > Hi, > > I hope I don't sound ranty - but really, I think we need to put in place some > policy about well-meaning but ineffective optimizations.

[Kicad-developers] Optimization

Hi, I hope I don't sound ranty - but really, I think we need to put in place some policy about well-meaning but ineffective optimizations. They're one of the quickest ways to screw up maintainability and introduce the possibility of errors. I strongly suspect 6711 "Optimize VECTOR2::Rotation for

Re: [Kicad-developers] Net Ties

ing about is real life PCBs. > > My $0.02, > Jean-Paul > N1JPL > > > > On Apr 22, 2016, at 5:08 PM, Chris Pavlina <pavlina.ch...@gmail.com> wrote: > > > > "I can think of a hackish way to do it so you shouldn't implement a good, > > proper wa

Re: [Kicad-developers] Net Ties

one would need some means of allowing overlapping of these nets > > connected with a net tie and also raising a DRC error if the nets are not > > connected. Maybe a special "net connector" is required that is member of > > both nets? > > > > Just

Re: [Kicad-developers] Margin (and others) layers question

Yup. I often use it to specify regions where I don't want components placed, like to set a 5mm border around the edge to keep things from being too close. That's about what I understood its purpose to be. On Fri, Apr 22, 2016 at 03:56:52PM +0200, jp charras wrote: > Le 22/04/2016 15:06,

Re: [Kicad-developers] Net Ties

You've never seen an EDA package support net ties? Or seen them used to separate logical power planes? Quite common, really... I'd _love_ to see proper net tie support in KiCad. :) On Fri, Apr 22, 2016 at 09:04:10AM -0400, Wayne Stambaugh wrote: > On 4/20/2016 4:00 PM, Simon Richter wrote: > >

Re: [Kicad-developers] hotkeys config menu coherence

ent > changes in a polite way. Please be patient, I did not mean be offensive or > supercilious. > > On Thu, Apr 21, 2016 at 10:12:39AM -0400, Chris Pavlina wrote: > > It's still partially in progress, I've just been massively tied up lately. > > > > I don't unde

Re: [Kicad-developers] DIALOG_ORIENT_FOOTPRINTS

It's gone :) On Wed, Apr 13, 2016 at 08:25:48AM -0400, Wayne Stambaugh wrote: > Since we have enough alternative methods for rotating a block of > footprints, I don't think removing this is going to be much of a burden > on anyone. > > On 4/13/2016 5:35 AM, Chris Pavlina wrote:

Re: [Kicad-developers] dyn_cast

sue with renaming it to > make the intent clear but thorough real world testing should be done > before changing over to dynamic_cast<>. > > On 4/13/2016 12:42 PM, Tomasz Wlostowski wrote: > > On 13.04.2016 18:38, Chris Pavlina wrote: > >> I would argue - quite strong

Re: [Kicad-developers] dyn_cast

28PM +0200, Tomasz Wlostowski wrote: > On 13.04.2016 18:19, Simon Richter wrote: > > Hi, > > > > On 13.04.2016 18:13, Chris Pavlina wrote: > > > >> What is the purpose of dyn_cast<> in include/core/typeinfo.h? Why don't we > >> just > >> us

Re: [Kicad-developers] DIALOG_ORIENT_FOOTPRINTS

rden > on anyone. > > On 4/13/2016 5:35 AM, Chris Pavlina wrote: > > Just rotate them first, then place. We don't need specific tools for > > every conceivable permutation of movements. Unless even more people come > > in saying they need this, or Wayne overrides me...

[Kicad-developers] dyn_cast

What is the purpose of dyn_cast<> in include/core/typeinfo.h? Why don't we just use dynamic_cast<>? And can we either replace the former with the latter, or add a comment to the former explaining its purpose? Looks like an optimization for speed, but has anyone actually profiled and found

Re: [Kicad-developers] RES: [PATCH] Logic reformulation in Plot_Edges_Modules

I agree. I'm against committing this simply because I think it doesn't add anything, though I do see the intent behind it. On Wed, Apr 13, 2016 at 11:03:45AM -0500, José Ignacio wrote: > Looking at the change in context, it might be a slight improvement in > readability, using a positive vs a

Re: [Kicad-developers] DIALOG_ORIENT_FOOTPRINTS

Yup, this is the way to do it. A generic tool for doing all of these sort of batch edit ops, not a specific "orient all footprints" tool. On Apr 13, 2016 05:42, "Tomasz Wlostowski" <tomasz.wlostow...@cern.ch> wrote: > On 13.04.2016 11:35, Chris Pavlina wrot

Re: [Kicad-developers] DIALOG_ORIENT_FOOTPRINTS

using the align and > distribute tools > > I Agree half-implemented features are bad, better to update them and > properly implement. > > Regards > David G > > On 13/04/16 08:53, Chris Pavlina wrote: > > GAL already has this. Block or multi select, Ctrl-M for &

Re: [Kicad-developers] DIALOG_ORIENT_FOOTPRINTS

able to alter it as an absolute angle, or as a relative to > current (prefix the new angle with + or - to get relative movement) > would be beneficial. > > Regards > David G > > On 13/04/16 06:40, Chris Pavlina wrote: > > I wonder how many of you are even aware of DIALOG_

Re: [Kicad-developers] DIALOG_ORIENT_FOOTPRINTS

t; of times just to see what they would do (really to see if it was worth it > to port over to GAL) and yikes. It is way, way too simplistic to do > anything useful and from the small amount I tested it has a handful of > issues with it. > > Jon > > On Tue, Apr 12, 2016

Re: [Kicad-developers] Silk on pads

court by this. > There is one scenario where it may be use full, though SMT pads would more > likely be used. > This is for touch panels where the solder mask and Silk screen are over the > pad area with no exposed metal. > > Regards Peter > > On 13/04/16 08:57, Wayne Stambaugh wrote:

Re: [Kicad-developers] DIALOG_ORIENT_FOOTPRINTS

12/2016 6:54 PM, Chris Pavlina wrote: > > It's not even undoable - so not only is it kinda useless, it's _broken_. > > > > Please? It's so much nicer not to have to maintain this stuff. :D > > > > On Tue, Apr 12, 2016 at 06:40:07PM -0400, Chris Pavlina wrote:

Re: [Kicad-developers] DIALOG_ORIENT_FOOTPRINTS

It's not even undoable - so not only is it kinda useless, it's _broken_. Please? It's so much nicer not to have to maintain this stuff. :D On Tue, Apr 12, 2016 at 06:40:07PM -0400, Chris Pavlina wrote: > I wonder how many of you are even aware of DIALOG_ORIENT_FOOTPRINTS. It's >

[Kicad-developers] DIALOG_ORIENT_FOOTPRINTS

I wonder how many of you are even aware of DIALOG_ORIENT_FOOTPRINTS. It's hidden in the Secret Menu in pcbnew (the spread-and-place) one, menu item Orient All Footprints. The code hasn't been touched since 2010 except a few cleanups, and it seems really simplistic and useless to me. I was going to

[Kicad-developers] Silk on pads

Quick question... does anybody know why we are putting silkscreen over PTH pads by default? And can we change this? Obviously they shouldn't be manufactured this way, so we're depending on either the user to remember to choose "Subtract soldermask from silkscreen" or on the fab to do it, both of

Re: [Kicad-developers] [PATCH] Logic reformulation in Plot_Edges_Modules

Indeed. a b !(!a || !b) a && b 0 0 0 0 0 1 0 0 1 0 0 0 1 1 1 1 Please be careful. I'm guessing that this patch was untested. On Tue, Apr 12, 2016 at 04:23:18PM -0500, José Ignacio wrote: > I don't believe that's correct !(!a || !b) is

Re: [Kicad-developers] New pcbnew features and versioning

g letters if more than one format change is done? > > 20160412A, 20160412B, 20160412C... > > On April 12, 2016 2:30:23 PM CEST, Chris Pavlina <pavlina.ch...@gmail.com> > wrote: > >Honestly I don't see the advantage to using Semantic Versioning for an > >internal f

Re: [Kicad-developers] New pcbnew features and versioning

out files, etc. > > (How many independent version numbers could option (b) require?) > > On Thu, Apr 7, 2016 at 1:04 PM, Chris Pavlina <pavlina.ch...@gmail.com> > wrote: > > What about using the date the change was made as a "version number"? Can > >

Re: [Kicad-developers] 0.1 degrees

new validator. If it's > fixed upstream, you could always copy it. It sucks that this will most > likely be temporary code until we bump the wxWidgets version. > > On 4/11/2016 9:12 AM, Chris Pavlina wrote: > > Making a derivative entry box is silly. If wxFloatingPointValidat

Re: [Kicad-developers] 0.1 degrees

+0200, jp charras wrote: > Le 11/04/2016 14:10, Chris Pavlina a écrit : > > ...why would I make some special entry box for this? What's wrong with what > > I've already done? > > Nothing really wrong, but: > > * At least on Windows, wxFloatingPointValidator does not w

Re: [Kicad-developers] [PATCH] DIALOG_SHIM default event handler fixes.

I thought you declared that policy a while ago :) On Apr 8, 2016 4:39 PM, "Wayne Stambaugh" wrote: > I've known for a while that the quasi-modal mode provided by DIALOG_SHIM > was broken. The only reason it hasn't reared it's head is because of > the design of most of

Re: [Kicad-developers] 0.1 degrees

...why would I make some special entry box for this? What's wrong with what I've already done? On Apr 11, 2016 2:18 AM, "Lorenzo Marcantonio" <l.marcanto...@cz-dynamic.it> wrote: > On Sat, Apr 09, 2016 at 10:37:43AM -0400, Chris Pavlina wrote: > > Anyone mind if I go th

Re: [Kicad-developers] PATCH: fix race condition related to 3D cache and resolver

Patch committed in rev 6685. Thank you. On Sun, Apr 10, 2016 at 10:39:26AM +1000, Cirilo Bernardo wrote: > The attached patch fixes a segfault due to a race condition. > If a user starts eeschema with an empty sheet and clicks > the 'cvpcb' button, memory is corrupted and the program > segfaults.

Re: [Kicad-developers] 0.1 degrees

I just fixed three of them. If there are others, I didn't see them, so please point them out to me. On Sat, Apr 09, 2016 at 07:47:28PM -0400, Wayne Stambaugh wrote: > Great! Thanks for fixing this. It's been a long time coming. > > On 4/9/2016 4:20 PM, Chris Pavl

Re: [Kicad-developers] New pcbnew features and versioning

I like the idea. It'll take some work to implement properly, though. I can start working on it, but it will likely be at least a week before I have anything. On Sun, Apr 10, 2016 at 04:05:42PM +0200, jp charras wrote: > Le 10/04/2016 15:31, Chris Pavlina a écrit : > > So - would you

Re: [Kicad-developers] New pcbnew features and versioning

there was a problem on new layers added to the > new release), to help users smoothing the change You seem to be confusing backward and forward compatibility... > > I'm just saying that if a board doesn't contain any new feature, can be > saved as old (as few days now) release version...

Re: [Kicad-developers] New pcbnew features and versioning

;than fail if there is anything that the parser can't handle. If there > >are no new features in the file, then it should open as expected. > > Maurice > > On 10/04/2016 14.56, Chris Pavlina wrote: > >The upgrade from 4022 to 4.0 wasn't as smooth as it could have been, no

Re: [Kicad-developers] New pcbnew features and versioning

bout what user's > need in a real production world" > > If you don't care about what happened with the 4022 vs new stable for users, > then it is fine for me ;) > > > On 10/04/2016 13.59, Chris Pavlina wrote: > >This gets filed under "things said by people who haven'

Re: [Kicad-developers] New pcbnew features and versioning

at could be lost if the file contains some > new features... > that is a standard feature in most sw, to allow a better collaborative > environment > Maurice > > > On 10/04/2016 02.49, Chris Pavlina wrote: > >Possible to implement, of course, but that could get rather messy as t

Re: [Kicad-developers] New pcbnew features and versioning

; Wayne > > On 4/9/2016 11:42 AM, Chris Pavlina wrote: > > Here's a patch that checks the PCB file format version against the currently > > supported one, and displays a message explaining the situation if the PCB > > file > > is too recent. I assumed MMDD format f

Re: [Kicad-developers] 0.1 degrees

at 03:06:08PM -0400, Chris Pavlina wrote: > Awesome, I'm starting on that now. > > On Sat, Apr 09, 2016 at 02:36:49PM -0400, Wayne Stambaugh wrote: > > We've being talking about this for a long time so I would like to see > > this implemented. Entering 900 for 90.0 degree

Re: [Kicad-developers] 0.1 degrees

> someone would need to write it so that it verified values were entered > > correctly etc > > > > On Sun, Apr 10, 2016 at 2:37 AM, Chris Pavlina <pavlina.ch...@gmail.com> > > wrote: > >> Anyone mind if I go through and fix the "in 0.1 degrees" uni

Re: [Kicad-developers] 0.1 degrees

0, 2016 at 3:27 AM, Chris Pavlina <pavlina.ch...@gmail.com> > wrote: > > Values already have to be validated. The only issue I can think of is > > related > > to the decimal point / comma issue, but we're *already* accepting decimal > > points in values in oth

Re: [Kicad-developers] New pcbnew features and versioning

- we'll have to add versioning to those, as it's not there at all right now as JP said. 2. Use a more friendly error dialog without the "IO_ERROR" and source code location, at least in non-debug builds. That will frighten people. :) On Thu, Apr 07, 2016 at 09:47:41AM -0400, Chr

Re: [Kicad-developers] 0.1 degrees

in the same way. On Sun, Apr 10, 2016 at 03:16:53AM +1200, Simon Wells wrote: > This was seen in a previous thread iirc and wayne mentioned that > someone would need to write it so that it verified values were entered > correctly etc > > On Sun, Apr 10, 2016 at 2:37 AM, Chris Pavl

[Kicad-developers] 0.1 degrees

Anyone mind if I go through and fix the "in 0.1 degrees" units that are all over pcbnew? I don't see any reason why we can't let the user enter unit degrees with a decimal point. -- Chris ___ Mailing list: https://launchpad.net/~kicad-developers Post

Re: [Kicad-developers] RES: RES: RES: [PATCH] new feature, value and reference with angle in PCB

> Enviado: quinta-feira, 7 de abril de 2016 18:28 > Para: Chris Pavlina > Cc: kicad-developers@lists.launchpad.net > Assunto: [Kicad-developers] RES: RES: [PATCH] new feature, value and > reference with angle in PCB > > tys Chris ! > I'll try

Re: [Kicad-developers] Custom shaped pads work. Second test.

>From a UX perspective, I am strongly in favor of merging rounded and non-rounded rectangles into radius>0 and radius=0. On Sat, Apr 09, 2016 at 06:59:54AM +1200, Simon Wells wrote: > It is most likely osx specific based on a screenshot that nickoe sent > me, But i am not sure the text should

Re: [Kicad-developers] PATCH: 3D coverity issue + minor fixes

Committed in rev 6673. Thank you. On Fri, Apr 08, 2016 at 08:31:50AM +1000, Cirilo Bernardo wrote: > The attached patch fixes a problem reported by coverity (thanks to Mario > for the fix): > > * CID 143740: Null pointer dereferences (NULL_RETURNS) > /plugins/3d/vrml/x3d/x3d_appearance.cpp:

Re: [Kicad-developers] New pcbnew features and versioning

ave never made more than one file format change on a > single day, I think we are safe. :) > > On 4/7/2016 2:04 PM, Chris Pavlina wrote: > > What about using the date the change was made as a "version number"? Can > > integerize it like 20160407 for exa

Re: [Kicad-developers] New pcbnew features and versioning

hu, Apr 07, 2016 at 07:47:10PM +0200, jp charras wrote: > Le 07/04/2016 18:42, Chris Pavlina a écrit : > > On Thu, Apr 07, 2016 at 06:36:40PM +0200, jp charras wrote: > >> Le 07/04/2016 17:52, Wayne Stambaugh a écrit : > >>> On 4/7/2016 9:47 AM, Chris Pavlina wrote: &g

Re: [Kicad-developers] New pcbnew features and versioning

On Thu, Apr 07, 2016 at 06:36:40PM +0200, jp charras wrote: > Le 07/04/2016 17:52, Wayne Stambaugh a écrit : > > On 4/7/2016 9:47 AM, Chris Pavlina wrote: > >> Hi all, > >> > >> I'm targeting this email primarily at Wayne as versioning and release > >>

Re: [Kicad-developers] New pcbnew features and versioning

, 2016 at 11:52:08AM -0400, Wayne Stambaugh wrote: > On 4/7/2016 9:47 AM, Chris Pavlina wrote: > > Hi all, > > > > I'm targeting this email primarily at Wayne as versioning and release > > policy is > > involved. > > > > We've got a bit of a probl

Re: [Kicad-developers] New pcbnew features and versioning

to the format), people still on the previous release will get a proper error message when opening files the new major release has generated. On Thu, Apr 07, 2016 at 05:20:41PM +0200, Marco Ciampa wrote: > On Thu, Apr 07, 2016 at 11:01:26AM -0400, Chris Pavlina wrote: > > I'm not sure what

Re: [Kicad-developers] New pcbnew features and versioning

I'm not sure what you mean by that. On Thu, Apr 07, 2016 at 04:52:52PM +0200, Marco Ciampa wrote: > On Thu, Apr 07, 2016 at 09:47:41AM -0400, Chris Pavlina wrote: > [...] > > Thoughts? > > I am not a dev. I KNOW. > > But... such a change (file and footprint format

Re: [Kicad-developers] New pcbnew features and versioning

Good point about the footprint files. I'll prepare a patch within a couple days. On Thu, Apr 07, 2016 at 04:35:05PM +0200, jp charras wrote: > Le 07/04/2016 15:47, Chris Pavlina a écrit : > > Hi all, > > > > I'm targeting this email primarily at Wayne as versioning an

Re: [Kicad-developers] [PATCH] Enable C++11

Patch committed in rev 6635. Thank you. ;) On Wed, Apr 06, 2016 at 05:31:37AM +0200, Simon Richter wrote: > Hi, > > On 06.04.2016 05:19, Simon Richter wrote: > > > This enables C++11 support, if either CMake is sufficiently new to have > > this feature built in, or the compiler is supported

Re: [Kicad-developers] [PATCH] Drop dependency on

Patch committed in rev 6670. Thank you. On Wed, Apr 06, 2016 at 05:19:44AM +0200, Simon Richter wrote: > > This appears to be unused. > --- > include/plugins/3dapi/xv3d_types.h | 1 - > 1 file changed, 1 deletion(-) > ___ Mailing list:

Re: [Kicad-developers] [PATCH 0/2] Two small portability patches

Patches 1 and 2 pushed in revisions 6668 and 6669. Thank you. On Wed, Apr 06, 2016 at 08:08:09AM +0200, Simon Richter wrote: > Hi, > > these should be fairly obvious: > > - all Windows platforms use declspec(dllexport) > - MSVC does not set a symbol called "MSVC" > - use wxFileName to access

Re: [Kicad-developers] problems in old 3DViewer with new bbox code

Patch committed in rev 6667. Thank you. On Wed, Apr 06, 2016 at 10:35:22PM +, Mário Luzeiro wrote: > Hi all, > > Attached is a patch that fixes an assert while displaying the 3D shapes > bounding boxes (because of the new merged code) > It also fixes a compile error in my machine because of

Re: [Kicad-developers] PATCH: fix to various 3D issues reported by coverity

Patch committed in rev . Thank you. On Thu, Apr 07, 2016 at 11:39:07AM +1000, Cirilo Bernardo wrote: > This patch fixes a number of issues reported by the latest coverity scan; > however it does not include a fix for one issue (I have asked Mario to help > fix this remaining one): > > ** CID

Re: [Kicad-developers] RES: [PATCH] new feature, value and reference with angle in PCB

be there by default. I'll have a look at that myself later, though if you know what the issue is I'd happily accept a fix :) On Tue, Apr 05, 2016 at 10:26:08PM +, Pereira, Patrick wrote: > Hello, > > Some corrections to this path. > > Best regards. > __

Re: [Kicad-developers] PATCH: fix segfault in python scripting caused by new 3D code

Committed in rev 6665. Thank you. On Wed, Apr 06, 2016 at 09:10:23AM +1000, Cirilo Bernardo wrote: > The attached patch ensures the S3D_MASTER class does not cause > a segfault in pcbnew when used from Python scripting. > > The issue is due to an "extern KIWAY* TheKiway" which was exposed > to

Re: [Kicad-developers] Linux new line bug fix.

xt edit controls where this same behavior can be an issue. If you > happen to find any, please let me know and I will fix them. > > On 4/2/2016 9:41 AM, Chris Pavlina wrote: > > Tested with a few hellish combinations of characters and everything I could > > think of managed n

Re: [Kicad-developers] Linux new line bug fix.

Tested with a few hellish combinations of characters and everything I could think of managed not to break it. Also, three thumbs up from me about not liking programs silently changing what you've typed. On Sat, Apr 02, 2016 at 08:37:51AM -0400, Wayne Stambaugh wrote: > I just committed the fix

Re: [Kicad-developers] Make Cairo optional

On Tue, Mar 29, 2016 at 09:46:25AM +0200, jp charras wrote: > [[snip]] > But the main reason is the fact on Opengl I am easily out of memory with > large boards, with 4Go of > RAM (W7 32 bits). > I am thinking this is due to memory fragmentation. > > I am afraid we have more easily this issue if

Re: [Kicad-developers] [PATCH 3/3] Action for "Defaults" button in "Hotkey Editor" dialog (lp:1395442)

Personally I prefer the patches as separate commits like this - I find it easier to review in small chunks, and easier to give useful feedback if something is wrong. It's trivial to commit them together anyway (just apply all of them in sequence with 'patch', or if you use git and git-am just

Re: [Kicad-developers] [PATCH 0/3] Updates for MIME types, resources and desktop files

I'm fine with patch 1 - I'm going to commit it later today if nobody complains, as it does actually fix a few things. I don't personally have a problem with patch 2, but I don't want to commit it without explicit permission as it does do a good bit of rearranging. Thoughts? Patch 3 didn't come

Re: [Kicad-developers] Array tool patches

Personally, I'd rather patch 1 actually _hid_ the pad numbering options rather than just greying them out - I found it a bit confusing at first, I instinctively started trying to figure out how to un-grey them before I realized they were pad-specific options... :P On Tue, Mar 22, 2016 at

Re: [Kicad-developers] PATCH: IDF tools

Committed in r6637. Thank you. On Mon, Mar 21, 2016 at 09:35:42PM +1100, Cirilo Bernardo wrote: > The attached patch makes the following changes to the IDF > tool 'dxf2idf': > > 1. DXF units are now correctly scaled to mm > 2. Polylines are now supported > 3. LWPolylines are now supported > > -

Re: [Kicad-developers] [PATCH] Enable C++11

16.04 LTS will be released in April. Personally I think we should be free to stop supporting 14.04 Geriatric Giraffe already in the development branch - why should a devel branch of kicad support non-devel branches of Ubuntu? KiCad stable runs on Ubuntu "stable" (LTS). But I seem to be in the

Re: [Kicad-developers] [PATCH] Enable C++11

Are we sure this isn't the issue where cmake forgets to rebuild pcbnewPYTHON_wrap.cxx? I've been having that issue about once every couple weeks for a while, just delete it and rebuild :P On Mon, Mar 21, 2016 at 08:13:48PM +0100, Nick Østergaard wrote: > 2016-03-21 20:10 GMT+01:00 jp charras

Re: [Kicad-developers] [PATCH] Enable C++11

Someone should probably ask - apologies if someone already did: Do you have a policy in mind for using C++11 features in new patches? It may be prudent to let the patch settle for a few days just to make sure nobody else has build trouble before we start making it harder to back out. On Mon, Mar

<    2   3   4   5   6   7   8   9   10   11   >