Actually My aim is that, if we draw a circuit in the simulator for
simulation purpose the footprints of all the components should be included
in the PCB layout of KiCad.
Regards,
Babar Malik.
Best Regards,
Muhammad Babar Malik
Namal College Mianwali
An Associate College of University of Bradford
Hi Oliver, your thoughts?
On Mon, Jan 15, 2018 at 09:09:48AM +0100, jp charras wrote:
> Le 15/01/2018 à 08:51, Marco Ciampa a écrit :
> > Hi Oliver,
> > about the bikeshedding thing I am not even a developer and I have the
> > audacity to say my thoughts about the icons!!!
> >
> > Follows my
In case you didn't get to try it yet, the development version of kicad
already includes integration with a very good simulator, ngspice. That may
already do everything you need.
On Tue, Jan 16, 2018 at 12:10 AM, Babar Malik wrote:
> Hi Everyone,
> Hopefully you people are
Hi Everyone,
Hopefully you people are doing good, I need assistance related to Kicad
development. My aim is to develop Kicad in such a way that we can simulate
the circuits along with PCB designing. As far as I know , Kicad is
developed in C++ basically, Moreover there is another software named
Please use the new attached patch instead of the first one I sent; the old
one failed to include the change to selection_area.cpp
On Mon, Jan 15, 2018 at 11:09 PM, Jon Evans wrote:
> SELECTION_AREA::ViewDraw() doesn't set the line width. I thought about
> fixing it by
SELECTION_AREA::ViewDraw() doesn't set the line width. I thought about
fixing it by adding a call to set some kind of arbitrary width, but decided
to do it a different way to be more generally applicable. Despite my
saying that, this is still more of a workaround than a real fix.
Note that this
Hi Orson, patch is attached again, hopefully it goes through this time.
Thanks,
Jon
On Mon, Jan 15, 2018 at 4:24 AM, Rene Pöschl wrote:
> On 15/01/18 10:00, Maciej Sumiński wrote:
>
>> Perhaps we should have an ERC rule
>> that warns about invisible pins being connected to
This was just intended as a tidy-up of the existing script/GUI I have been
using myself for a while. There are at least two other attempts, the one that
Andy refers to, and also KRen
I was editing a symbol this evening and went to save it. Probably the first
time I didn’t have to hover and wait for the tooltips. ;)
Cheers,
Jeff.
___
Mailing list: https://launchpad.net/~kicad-developers
Post to :
I like our font. It looks professional, like it belongs in an
engineering drawing - waaay better than a certain other package that
defaults to some serif font (Times New Roman maybe? blehhh). Would be
nice to be able to change fonts though.
On Mon, Jan 15, 2018 at 11:00:22PM +, Jeff Young
I agree that it’s not the best, but I’d rather have a better schematic fonts
than sharper icons. ;)
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe :
I tried taking an actual photo of my screen, since I figured screenshots
weren't very useful unless you can view them on a display of the
relevant DPI, but apparently taking a good photo of an LCD under these
lighting conditions with this potato^Wcamera is harder than it sounds.
Anyway, here's a
I'm somewhere in between you two. It's very true that the icons were
carefully designed to look right at one resolution, which is why this is
only a stopgap for 5.0. They don't look _that_ good scaled to me, but
they're tons better scaled than completely illegible because they're too
small.
OK, I was not sure that you intended it as a functional mock-up or proff of
concept.
I have not yet had time to test it.
2018-01-15 18:17 GMT+01:00 Andy Peters :
>
> On Jan 15, 2018, at 12:22 AM, Nick Østergaard wrote:
>
> Also, it is hard to argue this to
Hey Carsten,
On 1/15/2018 11:14 AM, Carsten Schoenert wrote:
> Hello Wayne,
>
> Am 15.01.2018 um 14:56 schrieb Wayne Stambaugh:
>> I though we were using version tags on the library repos that matched
>> the kicad stable release version to ensure that packagers would be able
>> to provide the
We should tag stable 5 for all of the library repos and that should be
used for *all* stable 5 releases. Changing libraries during a stable
version series (5.0.0, 5.0.1, ...) doesn't make sense to me. I don't
think users expect their libraries to change for bug fix releases of KiCad.
Any other
On 1/15/2018 10:23 AM, Matthijs Kooijman wrote:
> Hi folks,
>
>>> 3. What are the plans for providing coherent library names and the
>>> introducing new libraries?
>> We will try to limit such problems. But it might still happen that a library
>> will be split up into multiple libs if the library
> On Jan 15, 2018, at 12:22 AM, Nick Østergaard wrote:
>
> Also, it is hard to argue this to be used in KiCad when it uses PyQt.
What I mean is that the functionality should be part of Kicad, not this
particular implementation.
For those wondering why this is important —
On 15/01/18 17:53, Carsten Schoenert wrote:
Am 15.01.2018 um 12:09 schrieb Rene Pöschl:
...
1. Is there some release time strategy planned?
Are there any release dates planned for the newly created repositories
and what are the planes for releasing updates of these.
The only discussion i know
Hello Wayne,
Am 15.01.2018 um 14:56 schrieb Wayne Stambaugh:
> I though we were using version tags on the library repos that matched
> the kicad stable release version to ensure that packagers would be able
> to provide the same libraries. I don't want a situation where each
> packager uses
The version number is not the real question here.
We can tag the libs monthly to allow users more fine grained control
over which
version they want to use.
One option to still have the release information is to add an additional tag
(with the kicad version) to the monthly release that coincides
Hi folks,
> > 3. What are the plans for providing coherent library names and the
> > introducing new libraries?
> We will try to limit such problems. But it might still happen that a library
> will be split up into multiple libs if the library gets too large.
I had an idea on solving this. Not
On 1/15/2018 5:55 AM, Carsten Schoenert wrote:
> Hi,
>
> adding some notes here for the planned Debian packaging.
> Jean-Samuel emailed my some days ago already about his planes and we
> have tried to stay in contact about a consistent packaging schema
> between Ubuntu and Debian which makes
LAYER_VIAS_NETNAMES color was not initialized which resulted in black
text, not visible in outline mode.
This patch sets color to gray, similar to that on tracks when they have
bright color.
>From 811184477d0113f48fd18e6cbf4d4b72936c8617 Mon Sep 17 00:00:00 2001
From: Andrzej Wolski
I though we were using version tags on the library repos that matched
the kicad stable release version to ensure that packagers would be able
to provide the same libraries. I don't want a situation where each
packager uses different commits from the library repos to create
packages. I don't
Hi,
> In terms of Debian and Ubuntu there is only Recommends and Suggests
> available. The difference between both is simple that a Suggests will
> never be installed automatically, a Recommends will be installed unless
> the user is turning this globally off (default in on) or while calling
>
On 15/01/18 11:16, Carsten Schoenert wrote:
Hi,
as the packaging for Debian will change as well for the next KiCad
release I've some questions pointed to the contributors and admins of
the libraries to be able to prepare the needed package transitions as
also mentioned by Jean-Samuel.
1. Is
Hi,
adding some notes here for the planned Debian packaging.
Jean-Samuel emailed my some days ago already about his planes and we
have tried to stay in contact about a consistent packaging schema
between Ubuntu and Debian which makes absolutely sense in my eyes.
Am 15.01.2018 um 09:40 schrieb
Den 15. jan. 2018 11.16 skrev "Carsten Schoenert" :
Hi,
as the packaging for Debian will change as well for the next KiCad
release I've some questions pointed to the contributors and admins of
the libraries to be able to prepare the needed package transitions as
also
Ahh, ok I didn't notice. I thought it was going back in history since some
commits it missed on the first downtime got handled when you restarted it.
Den 15. jan. 2018 08.59 skrev "Maciej Sumiński" :
> Hi,
>
> Please note that the commit has been pushed on 5th January,
Hi,
as the packaging for Debian will change as well for the next KiCad
release I've some questions pointed to the contributors and admins of
the libraries to be able to prepare the needed package transitions as
also mentioned by Jean-Samuel.
1. Is there some release time strategy planned?
Are
Hi Jean-Samuel,
Thank you for the update. I will probably copy paste this information to a
blog post on the website to help inform the users.
Nick
Den 15. jan. 2018 09.40 skrev "Jean-Samuel Reynaud" :
Dear All,
A big job is done currently on KiCad libraries. Footprints
I confirm your patch fixes the problem, so I pushed it to the master
branch. Many thanks for solving another issue!
Regards,
Orson
On 01/12/2018 04:13 AM, Jon Evans wrote:
> Fix another cause of https://bugs.launchpad.net/kicad/+bug/1741357
>
> Using the "add via" hotkey was causing an
Hi,
Can anybody with a high DPI monitor post some pics at different scaling
setting please.
An enormous effort was put in making this icons look good in they actual
fixed resolution. I am curious how a >250DPI monitor can display icons well
regardless of this effort.
Cheers
Fabrizio
On Thu,
For the record: this patch was committed on 10th January.
On 01/06/2018 11:47 PM, kristoffer Ödmark wrote:
> Attached patch that implements the via choices, they seem to render fine
> and work as expected under linux.
>
> I guess that not many tests with different vias, since they have been
>
Hi,
Am 15.01.2018 um 00:56 schrieb Wayne Stambaugh:
>> 1) Branch name
>> wxWidgets has a lot of branches (I’ll see if we can delete what we don’t
>> need).
>> To be consistent to the usual development flow, I’d propose to add the
>> patches new branches.
>> I’d name them
>> KiCad_
>> If we
Thank you Jon, I have just pushed your patch.
Regards,
Orson
On 01/12/2018 04:32 AM, Jon Evans wrote:
> Fixes: https://bugs.launchpad.net/kicad/+bug/1673792
>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to :
On 15/01/18 10:00, Maciej Sumiński wrote:
Perhaps we should have an ERC rule
that warns about invisible pins being connected to a wire, any thoughts?
Invisible pins are used for three distinct applications.
The first one is to remove clutter by hiding pins that should not be
connected. ERC
Why can invisible pins be connected at all?
On Mon, Jan 15, 2018 at 3:00 AM, Maciej Sumiński
wrote:
> Hi Jon,
>
> It seems there is no patch attached to this message. I realize it is
> better to hide invisible pins when they obscure the view, but I wonder
> whether the
Hi Jon,
It seems there is no patch attached to this message. I realize it is
better to hide invisible pins when they obscure the view, but I wonder
whether the user should be at least aware of their presence.
In case a symbol does not follow the KLC and has invisible pins exposed,
then it can
Dear All,
A big job is done currently on KiCad libraries. Footprints are now on a
same repo [1], dedicated repo for templates [2], symbols [3], 3D
packages [4]...
So it's now time to change PPA libraries package also...
*Previous situation:*
There is only one package for libs: kicad-library
Le 15/01/2018 à 08:51, Marco Ciampa a écrit :
> Hi Oliver,
> about the bikeshedding thing I am not even a developer and I have the
> audacity to say my thoughts about the icons!!!
>
> Follows my 0.002 euro cents
>
> My very humble opinion is that the import icon is not that clear and can
>
Hi,
Please note that the commit has been pushed on 5th January, when the
server was down. Please let me know if there are any new problems.
Regards,
Orson
On 01/13/2018 01:49 PM, Nick Østergaard wrote:
> Hi again,
>
> Is it time for me to get it up and running, or what happened here? There is
43 matches
Mail list logo