Hi Mark
It is not a kicad feature, in fact it doesn't
even run inside kicad. It's better off on the FreeCAD's website as a
feature than KiCad because its entirely a freecad plugin.
at the moment the script cannot be easily invoked from inside pcbnew
because of some missing python API
Hi Jose,
good to know! :)
I think that FreeCAD would be a very useful companion for KiCad...
It is open source and works an the same platforms on which KiCad works
I'm also building a 3D mechanical library that is based on KiCad
official '.pretty' modules, that will let users to benefit of 3D
Your patch was committed to the product branch r6375. Thank you for
your contribution to KiCad.
Cheers,
Wayne
On 12/14/2015 6:02 PM, Kristian Nielsen wrote:
> Ok, looking further, I think it is just an oversight, GLM_INCLUDE_DIR is
> missing in 3d-viewer/CMakeLists.txt. Adding it as per the
Hello all,
Here are some screenshots of my WIP for a new 3d-viewer, this time it is a
render based on openGL (legacy):
https://meocloud.pt/link/6f7c5d91-80ec-48a3-808f-09e5ba3b99b3/kicad_3d-viewer-hackrf-one.brd-01.png/
On Mon, Dec 14, 2015 at 03:37:16PM +0100, Nick Østergaard wrote:
> Hi Fabien
>
> What make you think that "Internationalisation" is wrong? That is
> perfectly valid english (british).
>
Seems that even British people are not so "monolithic" on its correct usage:
On 12/14/2015 10:04 AM, Mark Roszko wrote:
> The problem was he was trying to push it into the features section of
> the website previously. It is not a kicad feature, in fact it doesn't
> even run inside kicad. It's better off on the FreeCAD's website as a
> feature than KiCad because its
Hi,
I've ran into an issue whenever I had to use the StepUp tools on Freecad to
open a footprint and do the alignment of 3D model.
I would get an open file dialog but nothing would happen after selecting
the .kicad_mod file.
Inside kicad-StepUp-tools.FCMacro:
The name[0] variable would return
Hence why I am asking, is it intended that we no longer enforce a
single optimization mode at all? It seems like a can of worms because
previously we could assume everyone is -O2. Now with people compiling
at different levels, who knows level dependent bugs could crop up.
On Mon, Dec 14, 2015 at
Stupid question, doesn't this change remove -O2 entirely for all gcc
builds? Previously it defaulted to -O2 if the bug wasn't present. Now
it never optimizes as -O0 is the default.
On Sat, Dec 12, 2015 at 2:59 PM, Wayne Stambaugh wrote:
> I committed your patch in the
The problem was he was trying to push it into the features section of
the website previously. It is not a kicad feature, in fact it doesn't
even run inside kicad. It's better off on the FreeCAD's website as a
feature than KiCad because its entirely a freecad plugin.
I was going to create a more
I assume I have to update the libcurl patch to add to the
CopyVersionInfoToClipboard mess.
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
On 12/13/2015 8:00 PM, Lachlan Audas wrote:
> You can't set text rotation angle of part reference's and vale's in
> pcbnew, only part rotation angle,
The code for supporting rotated text is already in the pcbnew file
format. I just don't know how well Pcbnew itself will handle rotated
text so
I also assumed something like that and therefore had a look yesterday.
On OSX it seems to default to -O3, at least that's what I have seen with
"make VERBOSE=1".
Regards,
Bernhard
On 2015-12-14 16:01, Mark Roszko wrote:
Stupid question, doesn't this change remove -O2 entirely for all gcc
Optimization levels have typically been at the discretion of the builder
in other projects. I never liked the idea of us forcing an optimization
level even though it resolved an issue related to the boost polygon
library. You are correct. There may be some optimization level bugs
but I haven't
The only boost patch that is not mingw or osx specific is
boost_cstdint.patch and I'm not sure this patch makes any difference.
There is one way to find out. Build kicad with stock boost on 14.04 and
see there are any issues. Would someone please test this since there
seems to be a lot of ubuntu
This should depend on your platforms gcc default setting or spec file if
you use one. I'm not sure how this done with clang. On Debain testing,
-O2 is the default build optimization setting and -O3 on msys2/mingw32
and msys2/mingw64.
On 12/14/2015 10:32 AM, Bernhard Stegmaier wrote:
> I also
Now that the series 4 stable release is out an we are starting to move
forward again with new development, I have two policy announcements
regarding KiCad development moving forward.
1) It will no longer be acceptable to allow new features to be added to
only the Pcbnew legacy canvas. The
I'll use 1.54 until the next Ubuntu LTS is released then I'll bump it to
1.55 which is the current Debian stable version.
On 12/13/2015 7:36 PM, Mark Roszko wrote:
> Debian never had 1.54 in stable.. It has 1.55 now(jessie) and the last release
> was 1.49 (wheezy).
>
> Debian had 1.54 as
Are you sure this is a good idea? We do patch boost 1.54 anyway, or do
you remember what the consequences was and we can just ignore them if
of on ubuntu 14.04 (LTS)?
2015-12-14 14:36 GMT+01:00 Wayne Stambaugh :
> I'll use 1.54 until the next Ubuntu LTS is released then I'll
Hi Nick
On 14/12/2015 15:37, Nick Østergaard wrote:
> Hi Fabien
>
> What make you think that "Internationalisation" is wrong? That is
> perfectly valid english (british).
Ok. I've just seen that wikipedia use 'z':
https://en.wikipedia.org/wiki/Internationalization
But english is not my first
On 12.12.2015 02:41, Strontium wrote:
> This change should not break or modify any current behaviour, EXCEPT to
> retain the nets of tracks/vias which Kicad is otherwise incapable of
> determining automatically.
Hi Steven,
Thanks for the patch, it also (partially) fixes the via stitching issue
Hi Thomas,
I considered this, but tracking zones is non trivial.
For example, imagine the stackup:
GND
VCC
GND
VCC
A Through Via, from top to bottom could be connected validly connected
to either GND or VCC.
Once the net is removed from the via by the reassignment pass, there is
no longer
On 14.12.2015 14:40, Strontium wrote:
> Hi Thomas,
>
> I considered this, but tracking zones is non trivial.
>
> For example, imagine the stackup:
>
> GND
> VCC
> GND
> VCC
>
> A Through Via, from top to bottom could be connected validly connected
> to either GND or VCC.
>
> Once the net is
Hi all,
Here just some spelling fixies to learn how to submit patch for kicad
Regards.
Martoni
>From 1210bc60f646b1b80969a78f878a2a67c6eb58b8 Mon Sep 17 00:00:00 2001
From: Fabien Marteau
Date: Thu, 10 Dec 2015 21:46:26 +0100
Subject: [PATCH] some spelling fix
Hi Fabien
What make you think that "Internationalisation" is wrong? That is
perfectly valid english (british).
2015-12-14 14:58 GMT+01:00 FabienM :
> Hi all,
>
> Here just some spelling fixies to learn how to submit patch for kicad
>
> Regards.
>
> Martoni
>
>
My 2 cents:
In my experience, I sometimes use the optimizations levels as a "verification
tool".
Ex: If I run it in debug (or without optimization) and it works and then I
switch to optimizations and it doesn't produce the same results, then, there is
a bug somewhere (as it was in boost)
I
On 12/14/2015 11:20 AM, Mark Roszko wrote:
> I assume I have to update the libcurl patch to add to the
> CopyVersionInfoToClipboard mess.
>
Yes please. CopyVersionInfoToClipboard may be a mess but it's damn
useful mess. Before it's existence, getting worth while build and
platform information
Hi Jose,
if you post the .kicad_mod file I will check it
(better if zipped)
PS which is the version of kicad StepUp tools you are using?
Maurice
On 14/12/2015 16.43, Jose A. Saumell wrote:
Hi,
I've ran into an issue whenever I had to use the StepUp tools on Freecad
to open a footprint and
There is something weird that goes on with that section of the code base.
I was messing around with it before when doing the eagle importer stuff.
For whatever reason text is limited to less than around 90 degrees of
rotation.
There are 5+ places in the pcbnew code where the rotation of text is
On Sun, Dec 13, 2015 at 12:17 AM, easyw wrote:
> Hi Wayne,
>
> following your previously mail
>
>> I haven't had a chance to use this yet but it sounds really interesting
>> so it will be near the top of my list of things to include during the
>> next development cycle.
>>
>
Wayne Stambaugh writes:
> The only boost patch that is not mingw or osx specific is
> boost_cstdint.patch and I'm not sure this patch makes any difference.
> There is one way to find out. Build kicad with stock boost on 14.04 and
> see there are any issues. Would someone
What is the result of `grep GLM < CMakeCache.txt` when run from your
build folder? You should see something like:
$ grep GLM < CMakeCache.txt
//GLM library header path.
GLM_INCLUDE_DIR:PATH=C:/MinGW/include
//Details about finding GLM
I tested this last patch on the build box for OS X by adding a part from
github to a board, and downloaded a few with the wizard. Everything worked
as expected.
Good work, folks.
Adam Wolf
Cofounder and Engineer
W
On Fri, Dec 11, 2015 at 12:04 AM, Mark Roszko wrote:
>
Hi folks,
We should probably remove the
"""WARNING: You decided to skip building boost library.
KiCad developers strongly advise you to build the bundled boost library,
as
it is known to work with KiCad.
Other versions may contain bugs that may result in KiCad errors."""
warning soon,
It will get removed when download_boost.cmake is removed. I just need
an answer on whether or not the 1.54 boost on ubuntu 14.04 will work or not.
On 12/14/2015 1:35 PM, Adam Wolf wrote:
> Hi folks,
>
> We should probably remove the
>
> """WARNING: You decided to skip building boost library.
Hi,
I'm a KiCad for Windows user.
I use my own libraries, so when installing KiCad I deselect both
Schematic and Footprint libraries. Required space for installation goes
from 1.1GB to 366.3MB. Fine.
But if I deselect the help files it goes to 177.3MB. So more than half
of the installation
Hi Wayne,
As in accord with my email:
https://lists.launchpad.net/kicad-developers/msg21844.html
I might have influenced the choice of the version number,
so I suggested that you can use at this moment whichever version you believe it
serves the best purposes and kicad interests.
Then, in a
On 14.12.2015 21:27, Wayne Stambaugh wrote:
Mario,
However (this is a notice to all
developers), I do not want the progress of the development branch to be
hindered because we are trying to support building on older distros.
This is what the stable releases are for. If you are using older
Possibly, but please set that as an issue on
https://github.com/nickoe/KiCad-Winbuilder instead.
2015-12-14 20:07 GMT+01:00 Iñigo :
> Hi,
>
> I'm a KiCad for Windows user.
> I use my own libraries, so when installing KiCad I deselect both Schematic
> and Footprint
Hi,
Am 14.12.2015 um 16:01 schrieb Mark Roszko:
> Stupid question, doesn't this change remove -O2 entirely for all gcc
> builds? Previously it defaulted to -O2 if the bug wasn't present. Now
> it never optimizes as -O0 is the default.
The default depends on the build type -- if your source tree
Mario,
The minimum version was based on your input and the current Debian
stable glm version. If you can get by with an earlier version, let me
know and I will adjust it accordingly. However (this is a notice to all
developers), I do not want the progress of the development branch to be
Hi Jose,
I can reproduce it in OSX Lion, so I can debug :)
Thank you for reporting it and also for the solution-workaround you have
found!
keep in touch
Maurice :)
On 14/12/2015 16.43, Jose A. Saumell wrote:
Hi,
I've ran into an issue whenever I had to use the StepUp tools on Freecad
to
Hi Maurice,
It is not related to the .kicad_mod file. Failed with with many I tried.
The Macro did not load the 'name' variable from the opendialog window. It
came back empty and thus the next if statement gave false result:
if len(name) > 0:
txtFile = open(name,"r")
On 14.12.2015 18:15, Wayne Stambaugh wrote:
The only boost patch that is not mingw or osx specific is
boost_cstdint.patch and I'm not sure this patch makes any difference.
There is one way to find out. Build kicad with stock boost on 14.04 and
see there are any issues. Would someone please
On 12/14/2015 1:31 PM, Sergey Borshch wrote:
> On 14.12.2015 18:15, Wayne Stambaugh wrote:
>> The only boost patch that is not mingw or osx specific is
>> boost_cstdint.patch and I'm not sure this patch makes any difference.
>> There is one way to find out. Build kicad with stock boost on 14.04
That shouldn't be a problem; something like this would do it:
wxFloatingPointValidator< float > valRotate( 1 );
valRotate.SetRange( -180.0, 180.0 );
Then it's just a matter of (a) specifying a max. character length in the
input box, (b) using the constructor with the validator specified,
Patch committed in product branch r6373. Thanks.
On 12/9/2015 8:02 PM, Cirilo Bernardo wrote:
> I was inspired to check sources for trailing white space and found a few
> - in fact
> very few for a project the size of kicad. Naturally all the
> auto-generated code
> was ignored.
>
> This patch
Ok, looking further, I think it is just an oversight, GLM_INCLUDE_DIR is
missing in 3d-viewer/CMakeLists.txt. Adding it as per the attached patch
fixes the error for me. The problem will only be seen when GLM is in a
different location from other libraries already included in CMakeLists.txt.
48 matches
Mail list logo