I suspect as the interface to Python develops and perhaps more tools are
added to the KiCad source repository, the documentation will grow and
is perhaps best kept as a stand-alone "KiCad Scripting Manual". Other
things which makes me favor a separate manual are (1) many (most?)
users will not want
On Mon, 31 Aug 2015 22:02:08 +0200
Attila Kinali wrote:
> i would select the part, either "generic opamp" to be specified later,
> an "AD8602*" for which i'd select a footprint later, or an "AD"
> which is the variant in a SOIC-8 case. And automagically, it would adjust
> the pin numbering in the
Hoi Tomasz,
On Mon, 31 Aug 2015 18:40:14 +0200
Tomasz Wlostowski wrote:
> @both: don't forget that some of the improvements that look simple (
> retaining nets for vias/traces, property editor or undo while drawing a
> trace) require some substantial rework of PCBnew internals (e.g.
> redesign o
David,
The FreeRoute icon should now tells you to put the right jar in the right
place and then it launches Freerouter--the integration is even better than
it was before, because for some reason Freerouter knows where all my files
should go!
Adam Wolf
Cofounder and Engineer
Wayne and Layne
On Mo
I've just been playing with V6132 of PCBNEW. I have a number of small
observations.
1/ In the layer manager toolbar the Top and Bottom layer are named
Composant and Cuivre. Why is this even though I am using English as my
language?
2/ The same words are used for the top and bottom layer in th
In response to a message written on 31.08.2015, 19:01, from Marco Ciampa:
in linux the right place is ~/.kicad_plugins
Not even more. That need cleanup… Should be:
${HOME}/.local/share/kicad/plugins
and of course user templates should land on:
${HOME}/.local/share/kicad/templates
but I don't kn
On Tue, Aug 25, 2015 at 04:27:01PM +0200, easyw wrote:
> Hi Marco,
>
> I still cannot find any mention to the path and any howto to use the
> very useful footprint wizard.
>
> I went in the .adoc file and the only mention to the wizard I found is in:
> Pcbnew_managing_libs.adoc
> but is a mere de
On 31.08.2015 17:23, Mário Luzeiro wrote:
> Good work on that list!
>
> I just give an quick overlook on that, I think one thing was not mentioned
> was the consistency on the edition of parameters.
> (For example the way that you insert a value of some type (ex a diameter, or
> a position) is d
Hi Chris,
On 08/31 15:46, Chris Goddard wrote:
> On 31/08/15 15:15, Attila Kinali wrote:
> >An example where Kicad fails with external consistency is the use of the
> >mouse wheel. While all EDA, CAD and simple drawing applications I've used
> >in the past have the following mapping:
> >
> >wheel
Le 31/08/2015 16:46, Chris Goddard a écrit :
On 31/08/15 15:15, Attila Kinali wrote:
An example where Kicad fails with external consistency is the use of the
mouse wheel. While all EDA, CAD and simple drawing applications I've
used
in the past have the following mapping:
wheel ->
I would like to add an idea : would be great to have a way to select
precisely the insertion point when copying a block in pcbnew or modedit.
Like you have in most CAD drawing tools.
Le 31/08/2015 16:15, Attila Kinali a écrit :
On Wed, 12 Aug 2015 00:09:06 +0200
Attila Kinali wrote:
So, I
On Mon, 31 Aug 2015 15:23:02 +
Mário Luzeiro wrote:
> I just give an quick overlook on that, I think one thing was not mentioned
> was the consistency on the edition of parameters.
> (For example the way that you insert a value of some type (ex a diameter, or
> a position) is different depend
Just for evaluation.
Mentor Designer Schematic Capture > wheel zoom
Mentor Designer Layout > ctrl+wheel zoom
PCBWeb > wheel zoom
Diptrace > wheel zoom
NI Ultiboard > wheel zoom
Upverter > wheel zoom
EasyEDA > wheel zoom
Eagle > Wheel zoom
Altium > ctrl+wheel zoom
On Mon, Aug 31, 2015 at 9:53 AM
I vote for having a qualifier key to tweek the meaning of the mouse wheel.
Touching the mouse wheel and having the design zoom to 3 pixel size or
huge size is not productive.
Bob G
On 08/31/2015 09:53 AM, Mark Roszko wrote:
The mouse wheel and navigation (as mentioned above).
Make it con
Good work on that list!
I just give an quick overlook on that, I think one thing was not mentioned was
the consistency on the edition of parameters.
(For example the way that you insert a value of some type (ex a diameter, or a
position) is different depending of the function/dialog.)
One thing
>The mouse wheel and navigation (as mentioned above).
Make it consistent with other EDA, CAD and drawing applications:
wheel -> up/down, shift-wheel -> left/right, ctrl-wheel -> zoom
I disagree, EAGLE uses mouse wheel zoom and it is by far one of the
most widely used tools these days.
On Mon
On 31/08/15 15:15, Attila Kinali wrote:
An example where Kicad fails with external consistency is the use of the
mouse wheel. While all EDA, CAD and simple drawing applications I've used
in the past have the following mapping:
wheel -> up/down
shift-wheel -> left/right
ctrl-whe
On Wed, 12 Aug 2015 00:09:06 +0200
Attila Kinali wrote:
> So, I would like to ask, whether there would be any interest of the
> developers to work on the UI. If so, I would start collecting
> points on the UI that are worth to work on and how to improve them.
Ok, here is a list of the things I s
Hi,
I attached a patch that is implementing epad and thermal vias on qfp_wizard.
the script is almost completed ...
I have three kind of questions:
1) how could I eliminate front silk on thermal via (pads)? I couldn't
find a class to do it
2) is there a way to reduce solder Mask on bottom layer
Le 29/08/2015 23:21, Michael Beardsworth a écrit :
> Small fix-up attached.
>
> Thanks,
> Michael Beardsworth
>
Committed. Thanks.
--
Jean-Pierre CHARRAS
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists
Le 28/08/2015 04:54, Joseph Chen a écrit :
> This is a resubmitting of a patch file (attached) that fixes the issue
> of [Bug 1487945]. This time it it more coding style compliant as
> suggested in other developer's comments.
>
> The fix passed tests on Ubuntu 15.04, based off KiCAD BZR 6133
>
Hi Cirilo,
I agree in generally with the necessities you pointed. Except the ones I will
comment below :)
Still don't agree with the necessity of tracking a pointer to display data in
S3D_ENTRY, special if you also agree that we need decoupling.
Your S3D_ENTRY, the (current/old) S3D_MASTER was
22 matches
Mail list logo
