I don't really use the page templates myself much. But I think it may
be time to rethink the page template concept to help it be easier for
the user to also select the correct paper size matching the template.
But I think that is better kept in an issue, but I guess keeping the
thoughts here are
Are you re-adding it under code?
On Mon, 2 Dec 2019 at 05:38, Seth Hillbrand wrote:
>
> On 2019-12-01 13:43, Nick Østergaard wrote:
>
> > The one under code
> >
> > søn. 1. dec. 2019 22.40 skrev Steven A. Falco :
> >
> >> I see two separate projects for kicad-i18n on gitlab:
> >>
> >>
Hi all,
I would say, pin swapping is just will be an another tool (you
probably need some specific piece of GUI for that).
The reason I want back-annotation is to have proper geometrical
(geographical) re-annotation. We have contractor who ask if possible
renumber passive components in geometrical
On 2019-12-01 13:43, Nick Østergaard wrote:
The one under code
søn. 1. dec. 2019 22.40 skrev Steven A. Falco :
I see two separate projects for kicad-i18n on gitlab:
g...@gitlab.com:kicad/code/kicad-i18n.git
g...@gitlab.com:kicad/kicad-translations/kicad-i18n.git
They have two different
My original request was misinterpreted or otherwise derailed and I'd like
to refocus things back to my original question.
It was: "Is there a path to get these worksheets added into KiCad so they
appear along with the other options in the 'Size' pulldown menu in the Page
Settings dialog in
Hi Tedd^2
Yeah, I probably didn't specify a proper ttl for some objects in some
directories, but you should definitely architect your mirroring
solution to handle that upstream has more data than you would like to
mirror, if it is an issue for you to keep up with the amount of data
upstream.
On
It uses -G "Visual Studio 15 2017" as the generator.
On Sun, 1 Dec 2019 at 23:45, Jon Evans wrote:
>
> What environment does that build use? My patches were necessary for VS2019
> using default compiler settings
>
> On Sun, Dec 1, 2019, 17:32 Nick Østergaard wrote:
>>
>> Oh, ok. Then I wonder
Summa sumarum, from a packaging point of view it is included as it is
on other platforms.
On Sun, 1 Dec 2019 at 23:42, Wayne Stambaugh wrote:
>
> I downloaded and installed 5.1.5 on my windows box and it looked like
> these worksheets were in the template folder. I didn't check the entire
>
What environment does that build use? My patches were necessary for VS2019
using default compiler settings
On Sun, Dec 1, 2019, 17:32 Nick Østergaard wrote:
> Oh, ok. Then I wonder why Jon needed to patch it.
>
> On Sun, 1 Dec 2019 at 20:14, Simon Richter
> wrote:
> >
> > Hi Nick,
> >
> > On
I downloaded and installed 5.1.5 on my windows box and it looked like
these worksheets were in the template folder. I didn't check the entire
list so maybe I got it wrong.
On 12/1/19 5:34 PM, Nick Østergaard wrote:
> The templates are packaged like everything else with cmake, so if it is
> not
The templates are packaged like everything else with cmake, so if it is not
included it is a bug in the templates repo.
On Thu, 28 Nov 2019 at 03:16, Ian McInerney
wrote:
> They appear to be packaged in the update to Fedora, but I don't have a
> Windows install handy to test on to verify what I
Oh, ok. Then I wonder why Jon needed to patch it.
On Sun, 1 Dec 2019 at 20:14, Simon Richter wrote:
>
> Hi Nick,
>
> On 01.12.19 20:07, Nick Østergaard wrote:
>
> > OK, cool, it looks like the msvc builds on jenkins are back in green again
> > :)
>
> >
Andy Peters kirjoitti 1.12.2019 klo 21.45:
> Anyway, it’s a lot easier to update the schematic with the new part and then
> forward-annotate, and this keeps both schematic and layout in sync.
Assuming there is the schematic to start with. Sometimes it happens that
there is just PCB data and one
> On 01.12.19 21:06, Jon Evans wrote:
1)
some cases (critical controlled impedance, small BGA decoupling, etc) we
may decide during layout that it is best to switch to the "high density"
(minimal pad size) version of the 0402.
This is alternate footprint. Implementation by reference in new
I see two separate projects for kicad-i18n on gitlab:
g...@gitlab.com:kicad/code/kicad-i18n.git
g...@gitlab.com:kicad/kicad-translations/kicad-i18n.git
They have two different project IDs, so they appear to be different
repositories. Which one should we pull from when building KiCad?
As a complete amateur user I change footprints in layout all the time in order to experiment with spacing, how things look, modfy footprints, etc.. Sometimes you want to make a change to a library part, flag that part as a new part (I.e. BriansSOIC8), then update all SOIC8 in the layout. The way
Hi,
Evan's patch was merged, but mine with code change for those sources is
not included in master currently. Can I kindly ask for update, is there
something wrong with my code?
https://drive.google.com/file/d/1x_YDsIw6FhgJFEsDgteEl5L5PGwSsCiz/view?usp=sharing
Best regards,
Sylwester
On
Ahh… yes, if you try to log a but at the top level you get a green button
“Select project to create issue”.
Cheers,
Jeff.
> On 1 Dec 2019, at 20:54, Ian McInerney wrote:
>
> Issues must live in a project, so the issues for the KiCad code must go in
> the Kicad/code/kicad list. The other
Issues must live in a project, so the issues for the KiCad code must go in
the Kicad/code/kicad list. The other lists (KiCad and KiCad/code) just show
all issues for all the projects underneath that folder.
-Ian
On Sun, Dec 1, 2019 at 8:51 PM Jeff Young wrote:
> Kicad, Kicad/code or
I would think kicad/code/kicad for KiCad source issues. It looks to me
like ./kicad is all of the issues for all of the repos but maybe I'm not
seeing this correctly.
On 12/1/19 3:51 PM, Jeff Young wrote:
> Kicad, Kicad/code or Kicad/code/kicad?
>
>
Kicad, Kicad/code or Kicad/code/kicad?
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp
> On Dec 1, 2019, at 1:06 PM, Jon Evans wrote:
>
> From another professional user, I have to disagree. There are at least two
> cases I can think of where changing the footprint during layout is important:
>
> 1) In my experience, it's common to keep multiple variants of IPC standard
> SMD
>From another professional user, I have to disagree. There are at least two
cases I can think of where changing the footprint during layout is
important:
1) In my experience, it's common to keep multiple variants of IPC standard
SMD footprints, especially for passives. By default, we specify the
> On Dec 1, 2019, at 6:59 AM, Vesa Solonen wrote:
>
> Eeli Kaikkonen kirjoitti 1.12.2019 klo 0.08:
>
>> BTW, about the possibility of changing the footprint - I have always found
>> being able to change footprints in pcbnew strange because then it's out of
>> sync with the schematic and it
Hi Nick,
On 01.12.19 20:07, Nick Østergaard wrote:
> OK, cool, it looks like the msvc builds on jenkins are back in green again :)
> https://jenkins.simonrichter.eu/job/windows-kicad-msvc-head/
They were broken at the same time as the Linux builds :)
Simon
signature.asc
Description:
OK, cool, it looks like the msvc builds on jenkins are back in green again :)
https://jenkins.simonrichter.eu/job/windows-kicad-msvc-head/
On Sat, 30 Nov 2019 at 03:19, Jon Evans wrote:
>
> Hi Brian,
>
> I will try to write a better guide, especially if I can get a full (all
> options) KiCad
Eeli Kaikkonen kirjoitti 1.12.2019 klo 0.08:
> BTW, about the possibility of changing the footprint - I have always found
> being able to change footprints in pcbnew strange because then it's out of
> sync with the schematic and it has to be changed in the schematic manually
> and updated to
Hi all,
I moved my patch at the top of kicad master again, so there shouldn't
be build problems anymore.
That's link.
https://github.com/jasuramme/kicad-source-mirror/commit/c00d66bbf943cc29aa2db3b50c6647341ca81969
> I noticed one problem. It's possible to add a footprint to PCB without
>
28 matches
Mail list logo
