don't
> know when in the v6 cycle any of this will happen but I'm guessing it
> will happen fairly early. Tom or Orson, do either of you have any idea
> when this will happen?
>
> Wayne
>
> On 03/04/2018 02:40 PM, Jon Evans wrote:
> > FWIW, I don't find t
Maybe I don't really understand what you mean, but I can't see any
jumpiness on Linux when panning around (with middle-mouse drag).
What do you mean by "it automatically fits to window, so there's not really
any place to go"? It does not do any kind of auto-fitting except for the
zoom-extents on f
lways a small
> shift of the whole view down and then up again.
> Sometimes, but not always if you just pan left/right it will make this
> small jump downwards every time you cross center, just as if it would
> “snap" to middle position.
>
>
> On 4. Mar 2018, at 21:25, Jon
I can certainly help check it. I think Wayne would have to make a call as
to whether or not it's too big a change to introduce now.
-Jon
On Mon, Mar 5, 2018 at 7:59 AM, hauptmech wrote:
> While testing version 5 I realized that clearances are still not settable
> (like track width or via size)
ve some things that I definitely want
> implemented as part of this object most of which you have probably
> already run into with your connectivity work.
>
> Cheers,
>
> Wayne
>
>
> On 3/4/2018 3:07 PM, Jon Evans wrote:
> > We should probably make some kind of road map if
Actually the second point in that post is a gem (rerouting of tracks when
you move a component) It is a feature of some super-high end packages
(Xpedition, Allegro I think) but missing from lots of paid tools (Altium,
Zuken, etc).
It's on my list of things I want to add to KiCad at some point (if
than auto-routing. If we ever get to the point we are sitting around
> twiddling our thumbs, then we should work on an auto-router.
>
> On 3/5/2018 12:16 PM, Jon Evans wrote:
> > Actually the second point in that post is a gem (rerouting of tracks
> > when you move a component) I
Hi all,
Since my day job involves a lot of engineering planning/timelines/etc, I've
had this rolling around in my head...
I started brainstorming some proposed changes to the roadmaps.
I am using Google drive because that's what is easiest for me to play with;
I'm happy to send patches against th
t 1:11 PM, Andy Peters wrote:
>
>
> On Mar 5, 2018, at 10:57 AM, Jon Evans wrote:
>
> Hi all,
>
> Since my day job involves a lot of engineering planning/timelines/etc,
> I've had this rolling around in my head...
> I started brainstorming some proposed chang
In many commercial tools you can use some or another feature to mark up the
design at the schematic level with what components "go together".
Then that information is used during PCB placement, the first-pass arrange
of components when you start designing a board can place those components
together
opularity contest.
> We have to make sensible decisions based upon project requirements and
> manpower limitations so all final decisions are made by the lead
> development team.
>
> On 3/5/2018 12:57 PM, Jon Evans wrote:
> > Hi all,
> >
> > Since my day job involves a lot
y who makes/reuse/share a lot of schematics.
>
> Am I the only one suffering from the inability to reuse schematics?
>
> my 2c
> Fabrizio
>
>
> On Tue, Mar 6, 2018 at 9:03 PM, Jon Evans wrote:
>
>> I will be sure to send a proposed update to the official doc after the
Hi all,
As part of preparing a new 6.0 roadmap, I want to make sure we have all
functionality that only exists in Legacy mode captured on Launchpad so we
don't forget about it. José just reminded me that Legacy mode in PcbNew
has some selection filtering features that don't exist in GAL, so selec
ct miracles, but basic P&S footprint dragging should be in
> early V6.
>
> Tom
> >
> >> On 7 Mar 2018, at 22:20, Jon Evans wrote:
> >>
> >> Hi all,
> >>
> >> As part of preparing a new 6.0 roadmap, I want to make sure we have all
;
>
> Cheers,
> Andrzej
>
> W dniu 2018-03-03 o 23:39, Jon Evans pisze:
>
> Hey Andy, Andrzej,
>
> Updated patch attached, let me know if this behavior makes more sense
>
> Best,
> Jon
>
> On Fri, Mar 2, 2018 at 3:29 PM, Andy Peters wrote:
>
>&g
Netlist export is a key feature of every schematic editor. So is
multi-sheet support. These aren't random extra features, they are a normal
part of any modern schematic editor.
On Thu, Mar 8, 2018, 12:45 Ouabache Designworks wrote:
>
>
> On Thu, Mar 8, 2018 at 9:21 AM, Tomasz Wlostowski <
> toma
I think option A is a good feature to add across schematic and layout. A
macro substitution system for text is very handy especially as we introduce
a better object properties system.
For example, it would be nice if we could assign arbitrary properties to
the project as a whole, as well as each s
Relating to https://bugs.launchpad.net/kicad/+bug/1680638
I figured Wayne and perhaps some others would like to check this out before
merging to make sure it properly addresses the problem.
-Jon
From 210eae84bd55854323939f179abe2c8927fe020c Mon Sep 17 00:00:00 2001
From: Jon Evans
Date: Thu, 8
Works for me, although your comments have tabs instead of spaces in front.
I fixed this and committed your patch. Thanks!
On Thu, Mar 8, 2018 at 8:49 PM, hauptmech wrote:
> https://bugs.launchpad.net/kicad/+bug/1753330
>
> ___
> Mailing list: https://
I'm going to try this just to see where I get, but I'm not an expert.
One other thing that might be worth trying is to use Qt Creator to
build/debug. It can be used as a frontend for GCC/GDB and might get around
your Ctrl-C issue.
On Fri, Mar 9, 2018 at 9:48 AM, Tomasz Wlostowski wrote:
> Dear
I have never worked on Blender but just poked around the source a bit.
They write custom modules in CPython rather than using a wrapper like SWIG.
To expose internal data, they have a Python wrapper over a C data access
API.
The C API seems to have portions that are auto-generated by the build, an
Display net name of pad automatically: You can use this to auto-label test
points with the net name they are connected to, for example
Other places where text substitution is useful to me:
- Set project-level properties, like schematic title, part number,
revision, etc. Have it automatically sh
> Any thoughts on how you envisage this working? Text substitution through
> using escaped macros or a direct reference that can be picked via say a
> dropdown box in the dialog?
>
>
>
> On Mon, Mar 12, 2018 at 5:34 AM Jon Evans wrote:
>
>> Display net name of pad autom
Yes, the version string was bumped to 5.0.0-rc2-dev
Maybe it would be less confusing to have it be "5.0.0-pre-rc2-dev" ?
On Mon, Mar 12, 2018 at 10:02 AM, Rene Pöschl wrote:
> Hello
>
> It seems at least some packages of current nightlies report themselves as
> version 5.0.0-rc2. (The arch packa
I have seen multiple users who run nightlies think they have RC2 because
they read "5.0.0-rc2" and stop reading after that :-)
Maybe we should switch the tag back to "5.0-dev" between RC releases?
I think all of us developers are going to look up the git hash anyway to
know exactly when a given ver
The free version is actually very complete for many use cases:
https://www.visualstudio.com/vs/compare/
On Mon, Mar 12, 2018 at 12:36 PM, Wayne Stambaugh
wrote:
> No doubt I'm out of touch. :) It's been at least 10 years since I used
> msvs. It's great that they have decided to support open so
That's a good point, I think we should all try to be better about assigning
ourselves to things on launchpad so that people don't accidentally work on
the same thing!
Jon
On Mon, Mar 12, 2018, 19:48 hauptmech wrote:
> Thanks, at first glance it looked like the work there was fast and furious
>
+Michael
This looks like "clever" code so I can't tell if this is a bug or not
without running through a bunch of test cases which I'm not going to do
right now.
Do you see any issues with the operation of the code, Mark, or just the
warning?
-Jon
On Mon, Mar 12, 2018 at 9:28 PM, Mark Roszko wr
Nice work! It may just be experimental, but it seems pretty close to a
feature for 6.0 to me :-)
I gave it a try on various boards I have worked on recently and it seems to
work as advertised and is not noticeably slower than a solid fill on my
computer.
Assuming we work out any issues related to
:48 GMT+01:00 Wayne Stambaugh :
>
>> On 3/12/2018 10:40 AM, Steven A. Falco wrote:
>> > On 03/12/2018 10:23 AM, Jon Evans wrote:
>> >> I have seen multiple users who run nightlies think they have RC2
>> because they read "5.0.0-rc2" and stop reading
t; happens again when
> > highlighting.
> >
> > Best-
> > Seth
>
> Trying to guess if the calculation time is long is really not easy.
>
>
> >
> > 2018-03-13 8:48 GMT-07:00 jp charras jp.char...@wanadoo.fr>>:
> >
> > Le 13/0
8 à 20:38, Jon Evans a écrit :
> > For the last point, you could use the approach I put in GerbView of
> start measuring the time, and
> > then throw up a progress window if the time exceeds N seconds (with a
> button to cancel the operation)
> > That way you don't eve
OK, Makes sense.
On Tue, Mar 13, 2018 at 4:25 PM, jp charras wrote:
> Le 13/03/2018 à 20:47, Jon Evans a écrit :
> > I wonder if it might be a faster algorithm to calculate the perimeter
> (and holes) of zones, offset
> > it in by the zone thickness as a polygon, and then d
Hi all,
I recently (2f86b497) changed the behavior of the wxGrid in the footprint
wizard dialog to fix some issues with boolean (checkbox) parameters.
The default behavior from wxWidgets (at least in 3.0) is buggy in that the
update events don't get sent out when you'd expect from the
wxGridCellB
ou can see my implementation here: https://git.launchpad.net/~
> jeyjey/kicad/commit/?h=6.0&id=7dda85fdae21f162bd7413fdceb16e49698f31bf.
>
> Cheers,
> Jeff.
>
>
> On 14 Mar 2018, at 13:50, Jon Evans wrote:
>
> Hi all,
>
> I recently (2f86b497) changed the behavior
s on other platforms.
>
> I do think we should add (2). I'm happy for you to tackle it, Jon.
>
> (I’m also happy to merge my version to 5.0 first if others think it’s
> worth the risk.)
>
> Cheers,
> Jeff
>
>
> On 14 Mar 2018, at 14:03, Jon Evans <mailto:
ting turned off?)
>
> On 15 Mar 2018, at 01:16, Jon Evans wrote:
>
> I gave it a try and there is some strange behavior on Linux :-(
> Clicks on the checkboxes seem to sometimes get handled twice so the box
> quickly toggles between states.
> So, I don't think it sho
Committed, thanks!
On Sun, Mar 18, 2018 at 5:42 AM, Carsten Schoenert
wrote:
> Am 17.03.2018 um 20:21 schrieb Carsten Schoenert:
> > Is this somehow intended that these needed macros are removed in the
> > file common/dialog_about/AboutDialog_main.cpp?
> > Are there any more files to look at?
>
I tested these patches and they work fine for me. I also think it's great
to add the via filtering checkbox, because I was just in need of that
feature on a layout a few days ago...
But I will defer to Wayne on whether or not this should go in for rc2.
-Jon
On Sat, Mar 17, 2018 at 12:32 PM, Andr
Hi Simon,
Thanks for sharing your work! This sounds like a neat feature and I'd like
to test it and give feedback.
Unfortunately your patch does not apply against current master, and it
looks like it is based on an old enough point that I couldn't fix the merge
issues manually.
Could you please re
I don't have a strong opinion on the functionality of this patch (I tested
it and it works as advertised) but there is one more style issue; blank
lines are needed before each if statement
https://kicad-source-mirror.readthedocs.io/en/stable/Documentation/development/coding-style-policy/#42-blank-l
Simon Santesteban
wrote:
> I think I have it updated correctly now. There was a conflict in
> pcbnew/menubar_footprint_editor.cpp
>
> See patch attached.
>
> Simon
>
> El 19/03/2018 a las 15:28, Jon Evans escribió:
>
> Hi Simon,
>
> Thanks for sharing your work! This sou
uld
help a lot, but I think they would touch too much to be a part of 5.0.
Fortunately there is progress reporting on this step, so at least users
will have feedback.
-Jon
From af6e43b9f0ca47b1d52adfd3b1ae227e5b0a9a37 Mon Sep 17 00:00:00 2001
From: Jon Evans
Date: Mon, 19 Mar 2018 22:54:16 -04
I haven't started on it yet, feel free to do so if you want and have time.
On Tue, Mar 20, 2018, 09:48 Jeff Young wrote:
> Hi Jon,
>
> Do you want me to take this up, or are you working on it?
>
> Cheers,
> Jeff.
>
>
> On 15 Mar 2018, at 12:20, Jon Evans w
? I suspect not
> but I could be overlooking something.
>
> All that said, this is a useful addition and definitely speeds up error
> resolution on problematic boards.
>
> -S
>
> 2018-03-19 19:58 GMT-07:00 Jon Evans :
>
>> I'd like some eyes on this before I
Hi JP,
I gave it a brief try and saw an assert problem:
Assertion failed: (aOutline.IsClosed()), function AddOutline, file
./src/kicad/common/geometry/shape_poly_set.cpp, line 429.
frame #4: 0x00010c818631
_pcbnew.kiface`SHAPE_POLY_SET::AddOutline(this=0x71d28060,
aOutline=0x7000
Why don't you like the idea of saving the schematic when you hit the save
button? That seems like a reasonable expected behavior to me at least.
(I dislike nag dialogs especially when they seem to have no purpose)
-Jon
On Tue, Mar 20, 2018 at 1:26 PM, Jeff Young wrote:
> CvPcb has a Save comma
utton and save schematic with it.
>>
>>
>> Regards,
>> Bernhard
>>
>> On 20. Mar 2018, at 18:28, Jon Evans wrote:
>>
>> Why don't you like the idea of saving the schematic when you hit the save
>> button? That seems like a reasonable expecte
Thanks JP, it works for me now! Nice work!
On Tue, Mar 20, 2018 at 1:29 PM, jp charras wrote:
> Le 20/03/2018 à 15:12, Jon Evans a écrit :
> > Hi JP,
> >
> > I gave it a brief try and saw an assert problem:
> >
>
> Attached, the modified patch with fixes for w
Stacking up the BOARD_COMMITs was most of the problem. Thanks for the tip,
Seth!
On Tue, Mar 20, 2018 at 9:52 AM, Jon Evans wrote:
> I will try Seth's performance idea to see if I can make a
> minimally-intrusive improvement there.
> I was proposing it as an option because (a)
idea even if there is a performance hit.
>
> Cheers,
>
> Wayne
>
> On 3/19/2018 10:58 PM, Jon Evans wrote:
> > I'd like some eyes on this before I push it, since it's a rather
> > significant change.
> >
> > I have added a (disabled by default) option
uld be active for the
> library tables, but not the footprint wizard.)
>
> Thanks,
> Jeff.
>
> <0003-Don-t-make-users-click-twice-to-toggle-a-wxGrid-chec.patch>
>
>
> On 20 Mar 2018, at 13:49, Jon Evans <mailto:j...@craftyjon.com >> wrote:
>
> I haven
I went ahead and merged these. Thanks!
On Sun, Mar 18, 2018 at 12:10 PM, Jeff Young wrote:
> I’ve always considered a jagged feature envelope a design bug. I’d
> support adding the via checkbox.
>
> Cheers,
> Jeff.
>
>
> On 18 Mar 2018, at 15:31, Jon Evans wrote:
&g
gt;>>
>>>> Oops, scratch that last one (it doesn’t even compile).
>>>>
>>>> Let’s try again:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On 21 Mar 2018, at 10:59, Jeff Young >>>> j.
I actually thing that's a reasonable thing to think about supporting.
On Wed, Mar 21, 2018, 19:38 Russell Oliver wrote:
> Yes, I guess so, unless there is a plan with the new schematic format to
> allow "unique/independent" symbols that include modifications from the
> library symbol, that are o
h wrote:
> >>
> >> Does the footprint wizard use GRID_TRICKS? In either case, we should
> roll these changes into GRID_TRICKS so it can be used everywhere we us
> boolean checkboxes in wxGrid.
> >>
> >> On 03/21/2018 05:38 PM, Jon Evans wrote:
> >>>
Is there any good reason to allow "deleting" layers that are part of
footprints?
I could see deleting routing layers (inner copper, etc) but I think we
should just get rid of the idea that you can "delete" the silkscreen etc.,
just make it "disable" so that it can be re-enabled without any fuss.
O
Yes, it looks like the code that actually updates the parameter wizard
model was removed in a0364a113
On Fri, Mar 23, 2018 at 11:36 AM, jp charras wrote:
> On W7/32 bits I confirm the UI works fine, but the footprint wizard table
> does not update the
> footprint when clicking on a boolean.
> Th
Committed, thanks
On Sat, Mar 24, 2018 at 4:58 AM, Marco Ciampa wrote:
> Other small typo
>
> here is the patch
>
> TIA
>
> Best regards,
>
> --
>
>
> Marco Ciampa
>
> I know a joke about UDP, but you might not get it.
>
>
>
> GNU/Linux User #78271
> FSFE fellow #364
>
Works great for me too, thanks Jeff!
On Sat, Mar 24, 2018 at 9:49 AM, Jeff Young wrote:
> Commit:
>
> Notify clients when GRID_TRICKS toggles checkboxes.
>
> 97fffe875fd9355505a20200bf24f038bf11df51
>
> > On 24 Mar 2018, at 11:49, Jeff Young wrote:
> >
> > Got it. Reproduces on Mac, so I
n
> incorporated to thread '3D search paths and environment variables', but I
> don't see the similarity...
>
>
> Thanks,
>
>
> Simon
>
> On 20/03/2018 1:55, Simon Santesteban wrote:
>
> Hi Jon,
>
> Oh yes I missed some of the code style policy..
. when the last point is the same as the first), and I didn't notice
any obvious other issues, but maybe you can double-check that changing the
behavior of SegmentCount() won't have any strange side-effects.
Thanks,
-Jon
From e9e6303a1174e9cf72d7bc2f90ef723f412f1f32 Mon Sep 17 00:00:00 2
It seems like we are pretty close.
Which of these are critical to get done for RC2 / which could be delayed?
https://launchpad.net/kicad/+milestone/5.0.0-rc2
Are there things that need to be done that aren't on the milestone yet?
Should we publicize this release a bit more than RC1 when it is re
because the new macos packaging
> scripts are not done, and there are some refactoring needed in the windows
> installer which has not been completed yet.
>
> 2018-03-25 18:32 GMT+02:00 Wayne Stambaugh :
>
>> On 03/25/2018 11:16 AM, Jon Evans wrote:
>>
>>> It seem
I think we should measure the amount of time we spend fixing or extending
wxWidgets vs. doing anything else.
I'm not proposing that we should be doing anything else in particular at
this time, but I think it would be good data to have.
-Jon
On Thu, Mar 29, 2018 at 8:55 AM, Jeff Young wrote:
> R
so elegant way, then perhaps a simple condition could be added
> to POLYGON_GEOM_MANAGER::IsSelfIntersecting().
>
> Cheers,
> Orson
>
> On 03/25/2018 04:07 AM, Jon Evans wrote:
> > Hi all (but especially Orson),
> >
> > I wanted to fix the issue Bernhard raised here:
>
I'm not exactly sure what you're planning, but I think before you go too
far down this road we should have a conversation / plan for how we actually
want DRC to work architecturally.
There are definitely lots of reasons to have multiple diff pair rules per
board, and also have those rules only app
Cheers,
> Jeff.
>
>
> On 14 Apr 2018, at 14:12, Jon Evans wrote:
>
> I'm not exactly sure what you're planning, but I think before you go too
> far down this road we should have a conversation / plan for how we actually
> want DRC to work architecturally.
>
&g
eing able to easily reuse them
> >> without having to reenter them every new project or modify the board
> >> file with a text editor would be rather handy. This would also have a
> >> nice side effect of the board file format not changing every time we
> >> want
for discussion. It could be using our kiway messaging or
> it could be a file watcher that updates the constraints when the
> constraint file is edited.
>
> >
> > From first blush I’d prefer the later (as it makes stand-alone files
> > more viable). But, like I sai
Hi all,
I am proposing to remove some behavior from KiCad as part of my bus
connections changes. I know we generally don't remove features in new
releases without good reason, but I think this is an exceptional case.
The user manual describes a way in which you can connect multiple different
bus
double-clicking on the junction and editing
> the mapping table. Then previous users could keep their functionality
> while still allowing the arbitrary member arrays you are building.
>
> Thoughts?
> -S
>
>
> 2018-04-15 16:40 GMT-07:00 Jon Evans :
>
>> Hi a
uses to match the superset bus (ADR->PCA, BUS->PCA)
>
> I believe such method keeps the connectivity data intact. Obviously it
> would have to be approved by the user, no silent changes.
>
> Cheers,
> Orson
>
> On 04/16/2018 05:05 AM, Jon Evans wrote:
> > I though
That sounds like a bug (if there is invalid data like that, we should deal
with it in a better way)
It sounds like it might be easy to make a trivial test case to attach to a
bug report without using your employer's board as-is
(maybe by removing everything manually from the kicad_pcb file except f
he known bug I
>> sincerely apologize for having wasted your time. I did not see a bug that
>> I thought was the same thing. If not, I will mail it to any and all of you
>> to look at. I won't obfuscate, I'd be afraid to disturb the problem. I
>> see no real pro
t;>
>>>> I am using 4.0.7 under Windows 10, if you decode this is the known bug
>>>> I sincerely apologize for having wasted your time. I did not see a bug
>>>> that I thought was the same thing. If not, I will mail it to any and all
>>>> of you
nice GUI for the
migration that lets the user control it, etc), does anyone have any other
concerns with this?
JP, maybe you either created this feature or remember its creation, do you
have any input?
Thanks,
Jon
On Mon, Apr 16, 2018 at 9:48 AM, Jon Evans wrote:
> I think the logic you descr
Hi all,
I've been mostly away from KiCad recently due to other things going on in
life, but I have been trying to follow the mailing list at least. Seems
like progress towards a RC2 release may have stalled, but it's not clear
why. Meanwhile lots of small changes continue to go in to master (I d
Hi all,
In the current netlisting algorithm, pins with no-connects sometimes appear
in the netlist, with auto-generated names like Net-(U1-Pad1).
This seems to not always happen, but I haven't investigated why yet, since
I'm approaching netlisting from a different direction with my new
connectivi
OK, these are good points, it seems a bit like there ought to be a better
way to support those needs but I understand and will maintain that behavior.
On Tue, Jun 5, 2018 at 2:50 AM, jp charras wrote:
> Le 05/06/2018 à 04:38, Jon Evans a écrit :
> > Hi all,
> >
> > In t
ws a “not terminated" marking
> on that NC terminated net ending. Is there a bug filed for this somewhere?
>
>
>
> On June 5, 2018 2:38:24 AM UTC, Jon Evans wrote:
>>
>> Hi all,
>>
>> In the current netlisting algorithm, pins with no-connects sometimes
>&
kept away from another but can
> have a close distance within the net group. Can Pcbnew/Kicad do this? Or is
> this too exotic of an requirement? I know that this can get _very_ complex
> when you have up to over 100 net groups due to isolation requirements…
>
> Regards,
> Andr
FWIW, as someone who is also maintaining parallel feature branches, I agree
with Orson and John. Now that we have committed to this 5.1 idea, we
should just make it happen in master. I think if we keep both master and
5.1 branch running in parallel, inevitably one or the other of them will be
les
If I read between the lines, it seems like the more important thing is to
be able to tell what grid selection is active, not necessarily to change it
through a dropdown (the dropdown is just what is already implemented).
There are other ways of doing this that take up less real-estate. For
exampl
It would be nice to have a fully-scriptable "output job" system so that you
can save all the Gerber generation settings, all the drill generation
settings, etc together, and set up a workflow of generating files, naming
them a certain way, packaging them in a ZIP, etc.
On Tue, Jul 31, 2018 at 10:2
:20 AM jp charras wrote:
> >
> > Le 31/07/2018 à 16:52, Jon Evans a écrit :
> > > It would be nice to have a fully-scriptable "output job" system so
> that you can save all the Gerber
> > > generation settings, all the drill generation settings, etc toget
I think Altium implements this behavior by considering object snap points
to be more important than grid snap points if both are turned on. So you
can drag the kink and snap onto the endpoint of another segment, and it
will stay there even if it's not on a grid point, because of that priority.
On
epend on how close the mouse is to the snap
> point/axis. grid (point), axis (line between two trace vertices)
>
> On Wed, Aug 22, 2018 at 11:30 AM, Jon Evans wrote:
>
>> I think Altium implements this behavior by considering object snap points
>> to be more important than g
VIEW::Update() -> VIEW::invalidateItem() -> VIEW::updateBbox() ? Is that
what you're looking for?
On Fri, Sep 7, 2018 at 11:19 AM Jeff Young wrote:
> When I move a view item, what is supposed to remove it and re-add it to
> the R-tree?
>
> Right now this isn’t happening so the moved objects get
Agreed. Diff pairs should have an associated clearance rule to other
objects and it has nothing to do with the gap.
One place where the gap should be used is in manual tuning of the pair. If
I route a pair and end it on a component that necessarily has non-symmetric
pad fanout, I might want to mov
I bet this is a difference in behavior in GAL, I had to deal with this a
bunch for the GerbView port. GAL vs. legacy handles the last point in a
polyline/polygon differently although I'm not at my code and so I can't
remember which way the difference goes.
On Tue, Sep 18, 2018 at 10:08 AM John Be
I've often seen "NC" used to mean "no connect" which usually is the "X"
symbol you put on pins to prevent ERC warnings.
DNP is also the one I've seen the most. I actually have heard from a
(US-based) assembly vendor that DNP is the most common, DNI is next after
that, and all other options are way
Along these lines, we should probably figure out what attributes/properties
KiCad should store as rigidly-defined fields/data members rather than a
more flexible (key/value) system.
>From what I can tell, some of the commercial EDA software I have used
treats almost everything as an "attribute" in
Works for me.
On Thu, Dec 6, 2018 at 12:05 PM Wayne Stambaugh
wrote:
> I've tried several times today to go the the KiCad user's forum and all
> I get is a blank white page. Anyone else having this issue?
>
> Cheers,
>
> Wayne
>
>
> ___
> Mailing list
Should we also try to set up some kind of developer meetup at KiCon? I can
make it to KiCon but not FOSDEM.
-Jon
On Mon, Dec 17, 2018 at 12:51 PM Wayne Stambaugh
wrote:
> Hey Tom,
>
> On 12/17/2018 12:35 PM, Tomasz Wlostowski wrote:
> > On 17/12/2018 18:25, Adam Wolf wrote:
> >> Hi folks!
> >>
Hi Michal,
First of all, I unfortunately have not yet actually tried out your branch
so I can't comment on the performance/functionality of your code.
There was already a launchpad issue tracking this feature request here:
https://bugs.launchpad.net/kicad/+bug/1678345
I had been working on it a l
Figuring this out is a good idea. Thanks for suggesting it, John!
My branch contains upgrades to the connectivity and netlisting system in
eeschema.
I have been resolving conflicts from time to time as I am able.
It may be a good idea to get it merged before too much work goes into
eeschema moder
I will be there (Thursday night through Saturday night)
-Jon
On Fri, Feb 22, 2019 at 9:28 PM Adam Wolf
wrote:
> I will be there, along with the other person in my side biz. (Matthew
> Beckler)
>
> Adam
>
> On Fri, Feb 22, 2019, 5:18 PM Wayne Stambaugh
> wrote:
>
>> I am trying to get a head cou
Hi Wayne and the rest of the team,
My code is located here:
https://github.com/craftyjon/kicad/tree/bus_upgrades
(I can rebase/format this as a patchset to make review easier if needed)
Documentation updates are in this branch:
https://github.com/craftyjon/kicad-doc/tree/bus_upgrades
Unfortunate
then bring it back with the new file
format. I'm not sure whether or not that would be easier than adding the
field to the old format before you start work on the new format.
-Jon
On Mon, Mar 11, 2019 at 8:54 AM Wayne Stambaugh
wrote:
> Hey Jon,
>
> On 3/9/2019 5:58 PM, Jon Evans
401 - 500 of 847 matches
Mail list logo
