Scratch Pad:
I think this will be easily doable as an additional text box in the dialog,
which is then added to the beginning of the expression for each text box.
The format for the math library is as follows
(a) Initialise x to zero
var x;
(b) Initialise y to three
var y :=
Thoughts on the comments here?
I also expect when porting to a new fab, modifying the stackup, then running
DRC onthe result without changing layout should be possible.
I would expect importing from DRU file would (optionally) overwrite stackup,
DRC,Netclasses, and/or Via/Drill sizes. Saving to
Hi,
I have tested the patch and I really like this feature. This automatic
variable assignment will sure come in handy.
How about adding a kind of scratch pad (a single line should do) to the
footprint editor so that one can add variables (measurements) given in
datasheets?
Like "c1=2.9; e=0.635"
it might be worth timing it with rsvg to see how long it takes to
convert from svg to png (also doing the same timing with using
inkscape) as if we can make the time reasonable then regardless of how
we proceed we could even have multiple sizes of each icon as xpm
arrays, can someone who actually
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
On 31.08.2017 19:59, Simon Küppers wrote:
> Does it make sense to maybe use something like the EAGLE DRU Format?
> Maybe make it fully compatible to it? Some fabs give you the EAGLE DRU File.
>
>
Hi all,
IMHO a warning on unrecognized token while parsing files is a must - in
many cases users
Hi JP,
Is this something new in GerberX2? I had never seen Gerber
jobfiles before...
I've given it a try (export and then load on GerbView) and seems to work
OK, it loads every layer by just loading the jobfile.
Any other gerber viewer which supports it to give it a try? gerbv
The typical terminology I've come across in other EDA suites is either
"border" or frame". I feel "template" could be confused with the "New
project from template" function in the KiCad Manager.
I think the task of integrating these functions into the eeschema/pcbnew is
beyond my ability at the
Could we merge the PNG files into a tilemap like is commonly done for
mobile/web applications?
On Thu, Aug 31, 2017 at 3:04 PM, jp charras wrote:
> Le 31/08/2017 à 20:27, Wayne Stambaugh a écrit :
> > Is it possible to create image libraries with different size images
> >
Le 31/08/2017 à 20:27, Wayne Stambaugh a écrit :
> Is it possible to create image libraries with different size images
> using the method you described below? If so, this could give us a path
> forward for high dpi monitor support. This problem is only going to get
> worse as time goes on so it
Is it possible to create image libraries with different size images
using the method you described below? If so, this could give us a path
forward for high dpi monitor support. This problem is only going to get
worse as time goes on so it would be nice to have a solution.
As for using rsvg for
I also expect when porting to a new fab, modifying the stackup, then running
DRC on the result without changing layout should be possible.
I would expect importing from DRU file would (optionally) overwrite stackup,
DRC, Netclasses, and/or Via/Drill sizes. Saving to DRU file directly might be
The project file is always an option. This would prevent file format
issues and always be available as long as the project is open. This
falls apart when the board is loaded outside of a project so that could
be an issue.
My preference is saving the stack up in the board file with an
I think this is a feasible solution. Having the possibility to import the
values let's you create a database of manufacturing templates.
Am 31.08.2017 7:56 nachm. schrieb "José Ignacio" :
> I don't see why you couldn't have both, an embedded version of the actual
> setup
Does it make sense to maybe use something like the EAGLE DRU Format?
Maybe make it fully compatible to it? Some fabs give you the EAGLE DRU File.
Am 31.08.2017 um 19:56 schrieb José Ignacio:
> I don't see why you couldn't have both, an embedded version of the
> actual setup and the ability to
I don't see why you couldn't have both, an embedded version of the actual
setup and the ability to import/export from/to an external file.
On Thu, Aug 31, 2017 at 12:54 PM, Neal Hollingsworth
wrote:
> Hi all,
> I've mostly been lurking on the list, but thought I would
Hi all,
I've mostly been lurking on the list, but thought I would make a
suggestion regarding the via stack configuration. It might be nice to store
the actual configuration/stack-up/DRC settings in an external file. The
idea is that these are processes paraders that are deaigned to in most
On 8/31/2017 1:21 PM, Bastian Neumannn wrote:
> 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
I would at minimum change the current code to give warnings on recognized
sections/tokens. That way the problem will be mitigated with future additions.
Greg S.
> On Aug 31, 2017, at 12:21 PM, Bastian Neumannn
> wrote:
>
> Hi,
>
> I am currently building a feature
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
converting the png to cpp files can be done the same how it is now
(using cmake), although it would really only be used on linux i would
also look at making it so that they all went into a single cpp file
rather than the numerous files it currently is.
On windows the files would end up as part of
Looks good for importing. I'm not sure how to format the dru if vias connect
non-adjacent layers.
Super!
Greg S.
> On Aug 31, 2017, at 10:37 AM, Bastian Neumannn
> wrote:
>
> It looks like this right now.
>
> now i need to add the information to the kicad_pcb
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 a
On Thursday, August 31, 2017, 6:58:27 AM CDT, Bastian Neumannn
wrote:
"combined with a nice input interface for via types and start/end layer in the
design rules is what I am aiming for"
It would be awesome if the interface or at least the specification within KiCad
On 31.08.2017 15:27, Russell Oliver wrote:
> Hi All.
>
> As a follow up to my earlier post, attached is a patch that implement
> math expressions in the pad editor as well.
>
> A nifty feature is that the fields can be referenced from each other.
> currently the fields are referenced by the
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 Mathias,
I apologize for not replying to the width setting dropbox earlier, now
it seems to be too late to change the idea.
Your patch is a clever solution to the problem, so if there are no more
ideas/patches for setting via sizes, I am going to apply your changes.
Regards,
Orson
On
Hi Jon,
Thank you for the patch, I have just committed it to the master branch.
Making tools more generic is always a good change and the zoom out
function works as advertised.
Regards,
Orson
On 08/31/2017 04:35 AM, Jon Evans wrote:
> Hi all,
>
> The attached patch refactors ZOOM_TOOL to
Hi Jean-Samuel,
Thank you very much for the patch, indeed it fixes the problem. I have
just pushed it to the master branch.
Reards,
Orson
On 08/30/2017 07:43 PM, Jean-Samuel Reynaud wrote:
> Hi all,
>
> There is an incorrect initialisation of variable m_cur_grid in
> DIALOG_SYMBOL_LIB_TABLE
Hi Mathias,
On 08/25/2017 09:55 PM, Mathias Grimmberger wrote:
>
> Hi Maciej,
>
> Maciej Sumiński writes:
>
>> Hi Matthias,
>>
>> Your patch looks good to me. I would love to see the same change done
>> for via hole and diameter text controls.
>
> Let me first
30 matches
Mail list logo