Heikki,
What is the purpose of the "stitch" token added to the file format?
Vias already have a netcode field so adding "stitch" to the file format
seems to serve no purpose.
I would prefer that you avoid the term stitching. Vias could just as
easily be thermal vias. I don't think the generic t
I tested the patches and both the legacy and GAL canvases appear to
behave the same way so if no one objects, I'm going to commit the changes.
In the future, please commit your changes and use git format-patch to
generate patches. It makes my life easier.
On 1/16/2017 1:38 PM, Константин Баранов
Yes. This is a useful piece of information in case we suddenly get a
rash of python scripting bug reports.
On 1/16/2017 2:15 PM, Simon Wells wrote:
> Should this option be added to the about box->copy version info for
> completeness?
>
> On Tue, Jan 17, 2017 at 8:08 AM, Jean-Samuel Reynaud
> wr
Should this option be added to the about box->copy version info for
completeness?
On Tue, Jan 17, 2017 at 8:08 AM, Jean-Samuel Reynaud
wrote:
> Hi all,
>
> Please find attached the patch for the action plugin menu.
>
> There is a build option to enable/disable this feature:
> KICAD_SCRIPTING_ACTI
Hi all,
Please find attached the patch for the action plugin menu.
There is a build option to enable/disable this feature:
KICAD_SCRIPTING_ACTION_MENU
=> It's disabled by default
Now there is a refresh button. It took new plugins, update existing ...
like in footprint wizard dialog.
I had remov
Thank you, Wayne, for your response. I'm attached the checked patches.
2017-01-16 20:07 GMT+02:00 Wayne Stambaugh :
> You are not being ignored. I can't speak for all of the lead developers
> but I've been really busy so pretty much everyone has been getting
> ignored by me. It's not intentiona
You are not being ignored. I can't speak for all of the lead developers
but I've been really busy so pretty much everyone has been getting
ignored by me. It's not intentional, it's just the reality of my
current work load.
Patch is giving me an unexpected eof with 3d_viewer-pan_step.patch.
Did
Hello! good initiative checking for use cases!
I use ratsnest initially to populate the board, checking where everything goes
etc.
I would like to be able to hide nets like GND and 3V3 since I most often do 4
layers desgin with each of these as an entire plane.
Then to be able to select a gro
Le 16/01/2017 à 17:53, Wayne Stambaugh a écrit :
> On 1/16/2017 10:30 AM, jp charras wrote:
>> Le 16/01/2017 à 14:18, Kristoffer Ödmark a écrit :
>>> For basic work, maybe reusing zones functionality in the footprint editor
>>> will be enough, and then the anchors would be added by regular circula
On 1/16/2017 10:30 AM, jp charras wrote:
> Le 16/01/2017 à 14:18, Kristoffer Ödmark a écrit :
>> For basic work, maybe reusing zones functionality in the footprint editor
>> will be enough, and then the anchors would be added by regular circular or
>> rectangular pads. Similar to how one would add
Hi Orson,
the usecase for me is information reduction; sometimes you can loose the overview when too much at once is displayed.
For instance if you want to optimize only the placement of a component group, such as a DC-DC converter, the ratnest of other
components is uninteresting and cou
I can see the value in both per net visibility and local ratsnest.
Having local ratsnest (the current footprint selected) visibility is
handy when placing footprints to minimize the number of signal
crossings. Having per net visibility is handy in complex designed so
you can turn off nets to preve
Hi Orson,
It is useful for me when start a new project when there are no much "mechanical
component placement constraints" so it helps to optimize the component
placement to achieve the smaller board and component orientation.
Also as there is no intelligent component auto-placement, it helps m
Hello. I'm sorry for disturbing you, but I'm not understand why my messages
are ignored. Proposed feature not needed for no one, except me? Or I'm made
something wrong? Please, give any comment.
2017-01-06 12:03 GMT+02:00 Константин Барановский <
baranovskiykonstan...@gmail.com>:
> 2016-11-23 0:2
One of the features that are available in the legacy canvas, but not in
GAL is local ratsnest. Now, we need to decide whether we would like the
same functionality in the GAL canvas, or perhaps should it be modified.
Do you use it? If so, what are your use cases? Do you think it would be
better to
On 01/16/2017 04:30 PM, jp charras wrote:
[snip]
> Hi, CERN guys,
> I remember someone at CERN worked on (or was willing to work on) SVG import.
>
> Is it a work in progress?
Actually, the task has been undertaken by our friends from Brazil during
the last hackathon. The basic import should be wo
>One constraint is the fact a custom pad shape (which can be build from a set
>of basic shapes: lines,
>circles, rings, polygon) is the fact the final shape should be only one
>polygon (with holes).
>Otherwise it is not *one* pad shape.
>So all pad shape edition must be made from the pad editor d
Le 16/01/2017 à 14:18, Kristoffer Ödmark a écrit :
> For basic work, maybe reusing zones functionality in the footprint editor
> will be enough, and then the anchors would be added by regular circular or
> rectangular pads. Similar to how one would add custom paste layers today.
>
> For more adva
For basic work, maybe reusing zones functionality in the footprint editor
will be enough, and then the anchors would be added by regular circular or
rectangular pads. Similar to how one would add custom paste layers today.
For more advanced, I vote svg or gerber import.
SVG is a common file form
Le 03/05/2016 à 14:40, Tomasz Wlostowski a écrit :
> Hi all,
>
> Recently there has been a lot of discussion on these features. Here's a
> short proposal how we could hit all three birds with one stone:
>
> Changes to SCH:
> - none
>
> Changes to netlist import:
> - auto_generate flag for SCH co
Hello again from 2017.
Did any decisions arrive from this work that werent made public? I would
sure like to see this added.
- Kristoffer
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
U
Hey everyone,
Very excited to see design reuse capability discussion. This could also be seen
as a stepping stone to a panelization feature/tool inside KiCad.
Just my 2¢ :)
Cheers,
Piotr
> On Jan 15, 2017, at 6:32 PM, Clemens Koller wrote:
>
> Hello, Kristoffer!
>
> On 2017-01-14 11:43, Kri
22 matches
Mail list logo