A few comments from the peanut gallery using Simon's "497" build...
Some things Seth suggested that I support and don't see:
- Units could be shown once at the top of the panel or in each column
header instead of each cell of the table. That would reduce clutter a bit
and shorten the string that n
Sorry if this is mixing things since Michael replied after me.
Continuing on with the numbering I used above:
8. To clarify, I meant the material name in the Material column, not the
layer name in the Name column. I assume this would fit in with adding
custom materials which is to be done later.
9
Hi all,
http://kicad-pcb.org/libraries/klc/G1.1/ shows a limited set of characters
that can be used in the official library.
https://github.com/KiCad/kicad-symbols/pull/2090 sparked a conversation
about allowing other characters, and as one of the librarians I want to
solicit dev input.
1. Can an
There was a conversation in the kicad/librarian discussion area on GitHub
at https://github.com/orgs/KiCad/teams/librarians/discussions/16.
On Fri, Aug 9, 2019 at 11:25 AM Gonçalo Pereira
wrote:
> Of course, thanks for the input.
>
> On 9 Aug 2019 19:07, Wayne Stambaugh wrote:
>
> Otavio is cor
Hi,
Apologies for the slight tangent...
When I submitted symbols for all V and I sources supported by ngspice at
https://github.com/KiCad/kicad-symbols/pull/1473, I created a
simulation schematic to show off their output waveforms. Some of them can
use the source control features here. I thought
I've also found
https://www.compuphase.com/electronics/LibraryFileFormats.pdf to be useful.
On Mon, Nov 11, 2019 at 4:14 AM Wayne Stambaugh
wrote:
> Take a look at the legacy footprint library file format documentation[1]
> for help. You really should be supporting the new s-expression file
> f
There have been very nice border and title blocks following
industry-standard guidelines merged into the official KiCad library at
https://github.com/KiCad/kicad-templates/pull/25. They now reside at
https://github.com/KiCad/kicad-templates/tree/master/Worksheets.
Is there a path to get these work
wrote:
> On 11/13/19 8:30 AM, Evan Shultz wrote:
>
> There have been very nice border and title blocks following
> industry-standard guidelines merged into the official KiCad library at
> https://github.com/KiCad/kicad-templates/pull/25. They now reside at
> https://github.com/KiC
ng the ISO standard.
The ISO standard only defines A page sizes. I understand your comment about
providing US page sizes but they aren't part of the standard.
Evan
On Wed, Nov 13, 2019 at 10:16 AM Seth Hillbrand wrote:
> On 11/13/19 9:19 AM, Evan Shultz wrote:
>
> Seth,
>
>
t of curiosity, is the Simulation_SPICE
> library shipped with the 5.1 build? If so, I can merger this demo into
> the 5.1 branch. Users might find it useful to demo the sources provided
> by this library. If not, then there is no reason to merge it into 5.1.
>
> Cheers,
>
> Wayne
contributed. Should ASME templates be
contributed that can be reviewed, they would be welcomed.
Evan
On Wed, Nov 13, 2019 at 10:52 AM Seth Hillbrand wrote:
> On 11/13/19 10:36 AM, Evan Shultz wrote:
>
> Thanks Seth!
>
> I didn't find the default template when looking at t
Thanks Seth! It would be great to have more templates available for KiCad
users. You can ping me for the review when you post the PR.
On Wed, Nov 13, 2019 at 9:44 PM Seth Hillbrand wrote:
> On 2019-11-13 15:54, Evan Shultz wrote:
>
> The contributor submitted ISO templates and the l
y way I could help to
get them included in an updated 5.1.5 release or 5.1.6? I know the GitLab
stuff is taking a lot of time from everybody but I don't want to let this
wither away.
On Thu, Nov 14, 2019 at 8:52 AM Evan Shultz wrote:
> Thanks Seth! It would be great to have more template
O5457-1999_ISO7200-2004_ASMEY1435-2014_EN.kicad_wks
> > > /usr/share/kicad/template/A4_ISO5457-1999_ISO7200-2004_EN.kicad_wks
> > > /usr/share/kicad/template/gost_landscape.kicad_wks
> > > /usr/share/kicad/template/gost_portrait.kicad_wks
> > >
custom file
> which wxComboBox allows (arbitrary text entry on top of dropdown).
>
>
> On that note, why are there new separate A# templates instead of
> autoscaling ones like the original kicad ones?
>
>
> On Mon, Dec 2, 2019 at 12:32 AM Evan Shultz wrote:
> >
> >
A few thoughts from the peanut gallery...
I strongly agree with Jon here, as a power user of Allegro's Constraint
Manager. It simply _is_ complicated to navigate a full-featured design rule
system. There will (may?) not be a way of getting around that when a lot of
constraints have been added. Add
Since other ECAD tools are specifically mentioned and I use a new tool I'll
add my 2 cents. I'm a Cadence Design Entry HDL user (oh God, it's so
awful...) working with always hierarchical schematics often having >100
pages.
DEHDL works on a principle where you add symbols and then they're
'package
hese containers to manage all
> errors you can get during block annotation.
>
> With git I usually follow git master head and keep my patch in one
> commit (if I don't have reason to do opposite) In that case it's very
> easy to follow master updates. But I like git :)
>
Carsten,
It was was my PR that was merged (
https://github.com/KiCad/kicad-footprints/pull/1586) which removed these
footprints. In the initial PR comment I noted removing the Multicomp
footprints and it was also discussed in later comments. Those footprints
were deleted with commit
https://github
Awesome! Thanks Jeff!
I'm just starting to look at this and I have something quick to mention
regarding the UI: At Design Rules > Constraints in the 'Zone fill strategy'
section, the options are two checkboxes but they appear to be
mutually-exclusive. Should they be radio buttons instead?
On Mon,
As an Allegro user, There are two-letter violation DRC error types which
give you an idea about the kind of violation. 'P-P' for pin-to-pin
violation, 'P-S' for a pin-to-shape (shape = zone), 'D-S' for
drill-to-shape, 'K-V' for keepout-to-via, etc. One can then drill down into
the details of the vi
Allegro breaks everything down by layer. I can create padstacks with any
given layer count and do something unique on top, internal, and bottom
layers with regards to copper, mask, and paste (not internal). Per layer I
can set zone connection type (solid, thermals, etc.), zone spoke width,
etc. The
There is one library name I'm concerned about. See
https://github.com/KiCad/kicad-symbols/issues/451#issuecomment-378701973.
This would be a breaking change, but if it's important enough to change
it's likely to only affect a small subset of all KiCad users.
It is "correct" to have a library with
Oliver,
I have concerns about greying out the part and being able to see any change
when printed in B&W. This may be why Altium used a big "x", and why the
tools I regularly use also allow an "x" or removing the DNI (I'm most
familiar with this acronym) part.
Another thing to consider is the abil
Yay!
We (librarians) have a few outstanding items in the library we want to
close before 5.0.2, but it should only be a couple of days and well within
the one week timeline you requested. Thanks mostly to Antonio, we're now
using the milestone feature of GH so you can see what's left at
https://gi
x27;t been
intentionally made since 5.0.0 unless it was to fix an issue that might
ruin a design (wrong pinout, footprint pins swapped, etc.).
On Mon, Nov 26, 2018 at 3:08 PM Evan Shultz wrote:
> Yay!
>
> We (librarians) have a few outstanding items in the library we want to
> close before 5.0
While this is tangential to the thurst of this conversation, a
comprehensive constraint system is incredibly important for many projects
and I'm very happy to share and contribute on this topic if it can be of
value. So, here we go...
Netclass to netclass clearance would be a distance that all net
As nothing more than an example, here is another tool facing the same
issue. I've colored one net's ratsnest green (others are still blue) and
you can see pins at orthogonal locations to each other get a zig (or is
that a zag?) so the individual pins on the net can still be easily
identified.
[imag
Here is how another EDA tool handles void control of crosshatched shapes:
[image: image.png]
And the crosshatch fill options, if that is helpful:
[image: image.png]
[image: image.png]
Similarly, I think, shape (zone) suppression is present for non-hatched
shapes because it avoids islands:
[image:
Apologies in advance for what will probably be a long message...
Would 8-way spokes be possible to implement "quickly" (in the algorithmic
sense, not the time to implement sense)? (I don't know if the shortcut
you've (Jeff) devised works for a paired set of 4 thermal spokes.) 8-way
thermals can be
Many options would be better than the current selection color, which as you
mentioned is not noticeable using the default color palette.
Your proposal above sounds good to me. A single color for multiple
elements, if it catches the eye, would be better than not being able to
find the highlighted e
31 matches
Mail list logo
