This is a good point, and I totally agree.
KiCad libraries isn't optimal like they are now with new feautures like
simulation added.
But that belongs in another thread, this was to discuss naming in the UI.
Perhaps a discussion on v6 roadmap would be a better place as this will
probably be a
Symbol has been used as long as I can remember.
The proper names should probably be defined to avoid confusion.
In my book:
A "symbol" is a generic repesentation for drawing a schematic,
and that is whats used in eeschema right now.
A "footprint" is the pads and silkscreen ++ used in pcbnew.
tion (between the
nearest two junction points), or delete an entire contiguous net. Maybe
eeschema could have the same or similar functions?
On May 20, 2016 3:00 AM, "Thor-Arne" <l...@thor-arne.net> wrote:
On windows the current behaivior is;
delete-key : delete whole wi
3:00 AM
To: kicad-developers@lists.launchpad.net
Subject: Re: [Kicad-developers] [PATCH] Schematic Cleanup: Split lines at
junctions
Hi,
On 20.05.2016 00:25, Thor-Arne wrote:
Delete wire is on the delete button. and delete segment is on the
backspace key.
Ah, that makes (some) sense. To me
sometimes it might delete just a single little
chunk of the line, or the whole thing. I guess you could say it makes
working with eeschema more exciting ;).
On Thu, May 19, 2016 at 8:00 PM, Simon Richter <simon.rich...@hogyros.de>
wrote:
Hi,
On 20.05.2016 00:25, Thor-Arne wrote:
Delet
It should be listed on the hot-key list.
Perhaps some other key is used.
From: Duane Johnson
Sent: Friday, May 20, 2016 12:36 AM
To: Thor-Arne
Subject: Re: [Kicad-developers] [PATCH] Schematic Cleanup: Split lines at
junctions
I didn't know about this behavior. On the Mac
This delete-wire behavior has been available in KiCad for as long as I've
been using it, which is some time before the 2013-stable release.
Delete wire is on the delete button. and delete segment is on the backspace
key.
Please do NOT change the behavior of the delete buton, it is used all
.
-Original Message-
From: Andy Peters
Sent: Sunday, February 07, 2016 10:20 PM
To: KiCad Developers
Subject: Re: [Kicad-developers] Discussion: Hidden Pins, Net labels
On Feb 6, 2016, at 11:12 AM, Thor-Arne <l...@thor-arne.net> wrote:
Then how is pcbnew supposed to know what's
anything worse, it will make it easier to spot
errors caused by having multiple names on the same net.
Vias loosing their net is a comletly different matter.
From: Lachlan Audas
Sent: Sunday, February 07, 2016 12:12 AM
To: Thor-Arne
Subject: Re: [Kicad-developers] Discussion: Hidden Pins, Net
] Discussion: Hidden Pins, Net labels
Le 06/02/2016 18:12, Thor-Arne a écrit :
I think the multiple netnames on the same net should be included in the
roadmap v5 DRC check.
This should as a minimum throw a warning as this might break the
finished pcb.
Multiple netnames on the same net are a frequent
idden pins, use them. If not, don't.
On 2/6/2016 9:59 AM, Thor-Arne wrote:
I agree with Chris on the hidden pins issue, old design should not be
broken.
That is also a no-no for the project. One of the goals of kicad is to
make every effort to maintain backwards compatibility.
When it comes
I agree with Chris on the hidden pins issue, old design should not be
broken.
When it comes to net names I think they should be forced to be unique.
Anyway, are we going to collect features requests now?
Would it be better to have a wanted-feauture list on github instead of the
mail list so
The BOM feature you are missing is in “pcbnew, File->Fabrication outputs->BOM
file”.
From: Dan Walmsley
Sent: Friday, February 05, 2016 4:59 PM
To: kicad-developers@lists.launchpad.net
Subject: [Kicad-developers] Bill of Materials Generator Feedback
Hello,
We have been using Kicad for
-
From: Andy Peters
Sent: Friday, February 05, 2016 6:19 PM
To: KiCad Developers
Subject: Re: [Kicad-developers] Bill of Materials Generator Feedback
On Feb 5, 2016, at 10:14 AM, Thor-Arne <l...@thor-arne.net> wrote:
I disagree, I find it to be the oposite of what you are saying.
The BOM
of materials that should be ordered.
-Original Message-
From: Andy Peters
Sent: Friday, February 05, 2016 5:52 PM
To: KiCad Developers
Subject: Re: [Kicad-developers] Bill of Materials Generator Feedback
On Feb 5, 2016, at 9:45 AM, Thor-Arne <l...@thor-arne.net> wrote:
T
I approve
From: Marek Roszko
Sent: Wednesday, October 14, 2015 9:03 PM
To: KiCad/kicad-website
Cc: Thor-Arne
Subject: [kicad-website] Licensing addition - need agreement (#78)
We need to license the website to match the kicad documentation.
https://github.com/KiCad/kicad-doc
This means
Relative to board file is a bad idea, it will require 3D models to be
duplicated for each project.
Perhaps this should be handeled by the File->Export->VRML (not that I've
tried that one).
And, yes. Please apply this patch. ;)
-Original Message-
From: Mark Roszko
Sent: Sunday,
I think the absolute adressing should be good enough for those special
cases.
Special cases shouldn't affect the "normal" cases.
-Original Message-
From: Mark Roszko
Sent: Sunday, September 27, 2015 6:38 PM
To: Thor-Arne
Cc: KiCad Developer mail-list
Subject: Re: [Kicad-deve
I also think multiple netnames should be included in the ERC check.
How should this be implemented ?
Should power-nets be excluded as these very often has multiple netnames like
VCC/+5V and GND/VEE ?
Should the handeling of power nets be changed ?
As it is today, I can see that this will
contributed on top.
Thor-Arne
Caerbannog
tfboy
cpavlina
reportingsjr
adamwolf
mangelajo
carycode
marcos-paltatech
The site still needs some fixes here and there, and new people are
still contributing, but I choose to ask Ajo to enable it now, since it
is mostly done and the confluence site has
right
now.
On the other hand, it would be nice if we could have a configurabe toolbox
(floating, dockable) where the most
used footprints could be (via, mounting-hole, etc.), ability to assign a hotkey
to each footprint would be nice.
Regards,
Thor-Arne
From: Mikk Leini
Sent: Wednesday, July 29
21 matches
Mail list logo
