You should be able to check the footprint just by looking at it in a
text editor or online. That will be faster than compiling Kicad.
https://github.com/KiCad/Resistors_SMD.pretty/blob/master/R_2512_HandSoldering.kicad_mod
For the seldom-used stuff you can either go to the individual Edit Field
dialog, or you can make more columns visible in the list (by right-clicking on
the header).
> On 3 Apr 2018, at 08:18, Nick Østergaard wrote:
>
> Are you not missing a lot of properties from that
Sorry for the noise, I'll try to compile the Kicad 5 rc2 and check if
this issue persists in the new library.
Thanks,
Augusto Fraga Giachero.
Nick Østergaard writes:
> The kicad-developers list is not really for detailed library discussions
> like this. You may have better luck reporting the
The kicad-developers list is not really for detailed library discussions
like this. You may have better luck reporting the issue directly on
https://github.com/kicad/kicad-footprints/issues
I am not sure what the plan is, but I don't think the Librarians will
update the old footprints, all
Hi!
I've had a an unpleasant surprise with a 2512 (imperial) smd resistor
footprint (Resistors_SMD:R_2512_HandSoldering) available in the Kicad's
official library (shame on me for not checking the dimensions before
sending the gerbers). When our boards arrived we verified that the pads
of this
More data:
1) The double SynchronizeNetsAndNetClasses() costs almost nothing. We should
leave it.
2) I did some testing having removed the second call to BuildConnectivity().
It’s definitely faster; may or may not be risky.
3) I solved the insert performance penalty. (Since files are
Mark,
I already ran into that so I guess at some point I will have to see if I
can fix this :( It would be nice if the wxwidgets project would use a
build config method that works across platforms like pkg-config or cmake.
Wayne
On 4/3/2018 3:12 PM, Mark Roszko wrote:
> Wayne,
>
> CLion will
Wayne,
CLion will work with MSYS2 btw but the findwxwidgets script in kicad is
broken and can't find the paths correctly because for some reason a define
or two I've never narrowed down keep making it think its win32 rather than
msys2 with a unix tree. I think I normally butchered the script into
On 2018-04-02 06:42 PM, Wayne Stambaugh wrote:
Things have quieted down quit a bit so we should be close to an rc2
release. I saw a 3D viewer crash report but it looks like it might be a
video driver issue. Are there any other outstanding issues we need to
fix before rc2 is tagged?
I am
We also call SynchronizeNetsAndNetClasses() twice (once in
NETINFO_LIST::buildListOfNets() and once immediately after returning from it).
> On 3 Apr 2018, at 15:41, Jeff Young wrote:
>
> With the fix, TRACK::GetBestInsertPoint(BOARD*) takes 6.2% of a file load on
> a
yes it is great indeed. I did experimentally port Inkscape to meson a few
weeks ago.
2018-04-03 14:13 GMT-03:00 Jakub Kozdon :
> Just found this on Linux Mint blog and it is looks promising -
> http://mesonbuild.com/
>
>
> ___
>
Just found this on Linux Mint blog and it is looks promising -
http://mesonbuild.com/
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
Le 03/04/2018 à 14:06, Wayne Stambaugh a écrit :
> On 4/3/2018 7:12 AM, jp charras wrote:
>> Le 03/04/2018 à 00:42, Wayne Stambaugh a écrit :
>>> Things have quieted down quit a bit so we should be close to an rc2
>>> release. I saw a 3D viewer crash report but it looks like it might be a
>>>
With the fix, TRACK::GetBestInsertPoint(BOARD*) takes 6.2% of a file load on a
reasonably dense board.
As points of comparison, BOARD::BuildConnectivity() takes 16.2% and 15.5%, and
PCB_EDIT_FRAME::ReFillLayerWidget() 3.3%.
(We could of course have a faster and more resilient load if we
The track/via insertion routines have two modes: blind-append and
insert-where-appropriate. The board parser current relies on the file being
correct and uses append. Changing it to insert fixes the bug.
I like this change because it makes us more resilient, and because it will fix
any other
On 4/3/2018 9:29 AM, Tomasz Wlostowski wrote:
> On 03/04/18 15:13, Jeff Young wrote:
>> The clean-up algorithms depend on tracks & vias assigned to the same net to
>> be grouped in the segment list. Is that supposed to be guaranteed?
>
> It is/used to be like this (there was/is a special
On 03/04/18 15:13, Jeff Young wrote:
> The clean-up algorithms depend on tracks & vias assigned to the same net to
> be grouped in the segment list. Is that supposed to be guaranteed?
It is/used to be like this (there was/is a special sorting function,
called at least in the TRACK_CLEANER). I
The clean-up algorithms depend on tracks & vias assigned to the same net to be
grouped in the segment list. Is that supposed to be guaranteed?
(I have a file where it is not the case.)
___
Mailing list: https://launchpad.net/~kicad-developers
Post to
On 03.04.2018 01:42, Wayne Stambaugh wrote:
Are there any other outstanding issues we need to
fix before rc2 is tagged?
https://bugs.launchpad.net/kicad/+bug/1678849
Today is one year since bug reported: opening eeschema in standalone mode
ignores page layout description file setting.
Adam,
Let's aim for some time this weekend. If you run into issues, please
let me know and I can push it back until the macos packaging is ready.
Thanks,
Wayne
On 4/2/2018 8:22 PM, Adam Wolf wrote:
> We are making good progress on macOS packaging but are at least a few
> days away from
On 4/3/2018 7:12 AM, jp charras wrote:
> Le 03/04/2018 à 00:42, Wayne Stambaugh a écrit :
>> Things have quieted down quit a bit so we should be close to an rc2
>> release. I saw a 3D viewer crash report but it looks like it might be a
>> video driver issue. Are there any other outstanding
On 4/3/2018 7:33 AM, jp charras wrote:
> Le 03/04/2018 à 13:25, Maciej Sumiński a écrit :
>> On 04/03/2018 01:20 PM, Tomasz Wlostowski wrote:
>>> On 03/04/18 13:17, Nick Østergaard wrote:
I think we should not disable the github plugin, but we may need to
remove it from the wizard in a
Le 03/04/2018 à 13:25, Maciej Sumiński a écrit :
> On 04/03/2018 01:20 PM, Tomasz Wlostowski wrote:
>> On 03/04/18 13:17, Nick Østergaard wrote:
>>> I think we should not disable the github plugin, but we may need to
>>> remove it from the wizard in a way that does not emphasize that this is
>>>
On 04/03/2018 01:20 PM, Tomasz Wlostowski wrote:
> On 03/04/18 13:17, Nick Østergaard wrote:
>> I think we should not disable the github plugin, but we may need to
>> remove it from the wizard in a way that does not emphasize that this is
>> the way to go. Maybe it is ok to remove it completely
On 03/04/18 13:17, Nick Østergaard wrote:
> I think we should not disable the github plugin, but we may need to
> remove it from the wizard in a way that does not emphasize that this is
> the way to go. Maybe it is ok to remove it completely from the wizard,
> but just let the plugin in the
2018-04-03 13:12 GMT+02:00 jp charras :
> Le 03/04/2018 à 00:42, Wayne Stambaugh a écrit :
> > Things have quieted down quit a bit so we should be close to an rc2
> > release. I saw a 3D viewer crash report but it looks like it might be a
> > video driver issue. Are there
Le 03/04/2018 à 00:42, Wayne Stambaugh a écrit :
> Things have quieted down quit a bit so we should be close to an rc2
> release. I saw a 3D viewer crash report but it looks like it might be a
> video driver issue. Are there any other outstanding issues we need to
> fix before rc2 is tagged?
Are you not missing a lot of properties from that dialog with your
screenshot, like the orientation? Or is this only to replace the "Fields"
frame of the dialog?
2018-03-01 17:26 GMT+01:00 Jeff Young :
> Technically yes, but even the existing dialog only lets you edit both.
>
> >
28 matches
Mail list logo