don't use branches for that.
>>>
>>> Branches are to track separate development efforts or release
>>> cycles/stabilization.
>>>
>>> Using branches, while it's possible was not the intent when git was
>>> designed.
>>>
>>> If
I really like the idea of having one repo with all the .pretty folders in
different branches. The master can have meta data about the branches.
That also gives the ability to manage library downloads as you can download
the branch as a zip.
Using git for library management is ideally implemented
I use KDevelop under Linux for building and debugging. It works pretty well
with cmake.
2017-09-08 7:07 GMT+02:00 Bernhard Stegmaier :
> You can run it from build directory also on macOS, no need to install (I
> do this all the time).
> You have to run the project manager (=> kicad.app) and eesch
> Am 07.09.2017 um 11:29 schrieb Bastian Neumannn:
> > Hi,
> >
> > I ususlly work with schematics of around 5 to 15 pages. A3 sized that
> > is. Using A4 for schematics that easily bloats up to 30 pages.
> >
> > For those schematics I am not using KiCad sinc
Hi,
I ususlly work with schematics of around 5 to 15 pages. A3 sized that is.
Using A4 for schematics that easily bloats up to 30 pages.
For those schematics I am not using KiCad since they are in a professional
environment.
Given the situation that I am currently working on a big design in KiCa
Hi,
I did something similar, but added a little bit more to it.
It is not yet done so no patch but a link to the Github Repo.
https://github.com/DasBasti/KiCad/tree/via_types_in_design_rules
The goal is to have a list of all used vias in the design in your design
rules. So you can enable micro v
Hi,
I am quite new to C++ and can not wrap my head around the issue I
encountered in the code below.
To give a littel background:
I am currently adding information to the via list saved as user_via in the
kicad_pcb file.
Adding more values to the keyword causes the compatibility to break
backwa
Having the design rules imported from eagle via a python script is the way
to go IMHO. I don't see the benefit of adapting to a proprietary file
format.
Having a warning shown is a better way than not starting up at all.
I might have a look at it tomorrow.
Cheers,
Basti
Am 31.08.2017 10:18 nach
on file for
>> a specific board house and price point. The board file would then only need
>> to store a reference to the configuration file. Just a thought, take it for
>> whatever it's worth!
>> Neal Hollingsworth
>>
>> On Thu, Aug 31, 2017 at 12:44
Hi,
I am currently building a feature that lets you input a via stack
configuration.
This information needs to be saved with the pcb data. So I tried putting it
into
the kicad_pcb file.
Now older versions will not load the file because it has additional values
that
it did not expect.
How do you
It looks like this right now.
now i need to add the information to the kicad_pcb file so it gets saved.
2017-08-31 16:42 GMT+02:00 Greg Smith :
> On Thursday, August 31, 2017, 6:58:27 AM CDT, Bastian Neumannn <
> neumann.bast...@gmail.com> wrote:
>
>
> "combined with
I am currently trying something similar to that idea.
The ammount of different drill sizes influenced the cost of a board. the
acual size of your copper restring around the drill not so much.
so having the ability to input different values for the drill _can_ make
your board much more expensive.
Hi,
I attached a small patch that fixes a bug with the design editor.
Loading a design with micro vias enabled loads the flag and sets the
checkbox.
The two input fields are not enabled when the design is loaded.
Cheers
From 102a83b8919d3bb0042c736e1dfbbf5e64746492 Mon Sep 17 00:00:00 2001
From:
KiCad does come with a python interface.
Moving to python as native system and other web technologies are not a good
idea imho.
Not every software is better with web and cloud stuff.
2017-08-28 18:04 GMT+02:00 Arun Kumar :
> Documentation of code or the usage of Kicad? I see that there is alread
Hi
> Ultimately is it useful to design a board, if you cannot make it?
Right now I can fabricate boards, I can not design. That is also not a good
solution.
via constraints are tricky bussiness as they are very specific to the
manufacturer.
> PS:
> The current "tracks and vias editor" dialog is
g/Blind-and-buried-vias
>
> and like you can see, "make start- and end-layers arbitrarily selectable"
> is not a very good idea.
>
> >
> > 2017-08-19 16:47 GMT+02:00 jp charras jp.char...@wanadoo.fr>>:
> >
> > Le 19/08/2017 à 15:20
Hi,
the last patch for this function was not correct I am sorry. This patch
gives the correct functionality to notify the user when die via size is
smaller than the minimum size given in the net class.
Cheers
From 07756c6c7d28aac83cf9ee7b0e087c8b6b09bd01 Mon Sep 17 00:00:00 2001
From: Bastian Neu
Hi,
I added a check to the dialog that notifies the user if the via type was
changed into a type that has bigger minimal sizes.
The user can select to update from the minimal sizes from the netclass of
the via.
Cheers
From 281ff1b94df4c10fc1d43542dc2bc0c78664da9d Mon Sep 17 00:00:00 2001
From: B
Hi,
My Name is Bastian Neumann from Germany. I am working with KiCad for some
time now.
It is a great piece of software and beeing free and open source is what me
brought me to it in 2008.
I am an EE and usually using KiCad for PCB design.
Writing software is usually some embedded C or stuff like
19 matches
Mail list logo
