Hi Wayne,
I think, I was present at FOSDEM 2019 when talking about this issue.
From what I understand, the current approach requires KiCad to compile
the units for each package separately (because e.g. mapping IU<->mm is
always different). This has two big problems:
1. the same code has to be
Hi Carlo,
From last year, I know there are many KiCad interested persons, but only
a handful of people involved in the project itself. It would be nice
enough to organize a meetup where more than 4 people show up (compared
to 34c3).
Personally, I plan to do a "KiCad Beginner Workshop" again this
Hi,
if you are curious, Antonio Vázquez Blanco designed a example
ci-pipeline for gitlab. (you need to have a gitlab account to view it):
https://gitlab.com/kicad-mirror/kicad-source-mirror/tree/feature/gitlab-ci
It automatically creates Appimages for example.
Personally, I would really like
Please go for it. The separate DLLs make it hard to design a python api
where eeschema and pcbnew can share resources.
Regards, Thomas
Am 28.08.19 um 16:03 schrieb Simon Richter:
> Hi,
>
> On Wed, Aug 28, 2019 at 10:47:52AM +0200, Ian McInerney wrote:
>
>> I think that the only way to really
Indeed,
there is actually a plan to improve this in the future. Personally, I
even wrote down a very rough idea myself:
https://github.com/pointhi/kicad-python/wiki/swig-interface-idea
I was able to compile eeschema with swig binding
That looks quite like the "Edit Symbol Fields" dialog. I would suggest
to extend this one instead of creating your own one.
What I would like to see is an advanced search for components, having at
least the filter features of cvpcb. This would allow ditching the
redundant dialogs for symbol and
A and B are not filled (width=0)
* zone is not hatched
when you look a bit more on the eagle board, you will certainly find
some more import bugs which are not fixed at the moment :). (DRC,
silk-polygon,...)
Regards, Thomas
Am 12.07.19 um 21:26 schrieb Thomas Pointhuber:
> Hi,
>
>
00:00 2001
From: Thomas Pointhuber
Date: Fri, 12 Jul 2019 21:18:42 +0200
Subject: [PATCH] Fix handling of filled circle in eagle importer (was only
partly fixed)
Partly fixed in 4fc692f04b447f77c75f4538982f6b739d08c4e8, but missed
that there is a loadPlain where I need to handle this ca
5df6e279c635a888a1087a11f0d24d94fb64 Mon Sep 17 00:00:00 2001
From: Thomas Pointhuber
Date: Fri, 12 Jul 2019 20:11:21 +0200
Subject: [PATCH] Add support for hatched zones in eagle import
---
pcbnew/eagle_plugin.cpp | 13 -
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git
On the long run, what about improving the fill algorithm to be able to
only update affected regions?
e.g. As long as an update cannot split the zone and the update has no
overlap with other zones it should be possible to only recalculate parts
of the zone fill and ignoring the rest.
I know this
Hi,
I would like to drop in this website to the discussion: https://utf8everywhere.org/
There are good points, and I would suggest either storing them internally with 8 or 32 bit.
Regards, Thomas
Gesendet: Dienstag, 30. April 2019 um 11:52 Uhr
Von: "Andrew Lutsenko"
An: "Jeff
Hi,
I made a KiCad beginner workshop yesterday (with about 45 people), and at least two of the participants appared to run into serious issues regarding netlist handling. One of my colleguages as well (I hope he creates an bug-report soon).
The Issue appeared on KiCad 5.1.1, but it could
Hi,
out of curiosity I'm currently trying to register a new tool, but no
success for now.
I noticed that "tool-framework.md" is no longer up-to-date (referring to
the Tutorial):
For example:
* "SetTransitions" is now "setTransitions"
* m_menu seems to be managed by PCB_TOOL now
* ...
It would
ing the defined
default line width.
Regards, Thomas
From 7bf281cdec3614300b0fdf3b9ecf11eb6f6e72cf Mon Sep 17 00:00:00 2001
From: Thomas Pointhuber
Date: Sat, 26 Jan 2019 16:16:35 +0100
Subject: [PATCH] [eagle-import] fix handling of filled circle and default
layer width
---
pcbnew/eagle_plugin.cpp |
Hi Wayne,
I would like to attend this year again.
Regards,
Thomas
Gesendet: Montag, 07. Januar 2019 um 18:40 Uhr
Von: "Wayne Stambaugh"
An: "KiCad Developers"
Betreff: [Kicad-developers] FOSDEM KiCad dinner.
For those of you who don't know, the last few years at FOSDEM we have
had
newer GLM versions.
Regards,
Thomas
From 59fd03a63949d16b67c789038f681abbd9e67dfb Mon Sep 17 00:00:00 2001
From: Thomas Pointhuber
Date: Sun, 6 Jan 2019 11:55:15 +0100
Subject: [PATCH] Fix check for incompatible glm version in cmake
Build fails on GCC, but not with Clang. Modify the check to
My ERC Proposal was more like a: we should at least think about it a bit
instead of writing the pin type near style and number/name. We can
specify ERC hints in a future-proof way without extending the current
implementation. Like:
(erc_hints (pin_type power_in))
This would allow us to specify
Hi,
I didn't unterstand the reason for the proposal at the start due to new schematic format, new dependencies,...
But thinking about it a bit more it really makes sense to me now. In the past, I wrote importer as well as exporter for the footprint file format, and using protobuf would
11:05 schrieb Carsten Schoenert:
> Hello Thomas,
>
> Am 02.01.19 um 10:39 schrieb Thomas Pointhuber:
>> * I do not see anything related to SPICE in this document. I would vote
>> to add it including the possibility to embedded spice models
>> (BASE64-encoded) into the sym
Hi,
nice to see that the new file format is shaping up now. Some comments
from my side:
* I do not see anything related to SPICE in this document. I would vote
to add it including the possibility to embedded spice models
(BASE64-encoded) into the symbol itself.
* pin type as it is currently
Hi,
some reminder for next month: Starting with January 15th, mentoring
organizations can start submitting applications for the GSoC:
https://developers.google.com/open-source/gsoc/timeline
It would be a nice idea to apply this year, and get some students to
help with the development of KiCad
Hi,
I'm in favor of managing the scripts like the library in a distinct
repository, but I would wait after 5.1 release, as well as not simply
copying the existing scripts into that repository.
I made a RFC on the forum some time ago how I would think such a
repository could look like, which
Stupid question:
why not use long instead of int? Most computer systems nowadays are
64bit anyway. Are there Speed/Memory considerations which would block
this? I think having an unified codebase without unit quirks would be an
important improvement.
Regards, Thomas
Am 21.11.18 um 20:35 schrieb
Hi Wayne,
The console crash is already fixed in the merge request:
https://code.launchpad.net/~pointhi/kicad/+git/kicad/+merge/357605
Regards,
Thomas
Am 22.10.18 um 18:36 schrieb Wayne Stambaugh:
> Hey Thomas,
>
> I looked over you merge request and it changes seem fine. I still need
> to
Hi,
I think this topic will have many different point of views, but I think
it is important to discuss it anyway.
I'm now about 5 years on the project, started as library maintainer and
now sometimes with code contributions as well. I experienced at least a
few different types of how software
Hi,
Now with Python 3 merged it would be nice to get support for (optional)
wxPhoenix support into 5.1 as well. I have a preliminary branch running,
which works on Linux quite well (wx3.0.4+GTK3+python3.7+wxPhoenix). It's
mainly based on
patch-sets @mmccoo wrote some time ago.
Hi,
I made an GTK3 build with wx3.0.4 and didn't noticed more bugs than with
wx3.1.1 and GTK3 on a quick glance.
I'm using X11 as display manager, and run a Arch based system.
Regards,
Thomas
Am 19.10.18 um 11:53 schrieb Carsten Schoenert:
> Hello Seth,
>
> Am 18.10.18 um 21:52 schrieb
Hi,
I agree that GTK3 should be a first class citizen of supported toolkit
in the future.
I have gtk3 builds running for testing purpose, and at the moment
scrolling is the most annoying issue in my opinion, which makes it
nearly unusable to simply zoom in/out reliable:
Hi,
I rebased the branch and fixed the few bracket issues I found:
* https://github.com/pointhi/kicad-source-mirror/tree/python3
Now with eeschema-gal merged, it would be nice to get this into upstream
as well.
Regards,
Thomas
> I noticed some K curly bracket placement that needs to be fixed
a
> much-too-long list it looks like GTK wants a smaller padding like MSW, and
> only OSX needs the larger.
>
> Thanks,
> Jeff.
>
>
>> On 27 Sep 2018, at 18:44, Thomas Pointhuber wrote:
>>
>> Hi Jeff,
>>
>> I like the idea, but it
Hi Jeff,
I like the idea, but it still has some problems on my system:
* I cannot enter any text into the filter field
* It still expands to the bottom of screen (at least there are now
scroll bars)
As sidenote, I was required to revert e456ecd0a15d3fb to get it actually
built on wx3.1:
```
> full crash dump can be included as part of the report, I see what other
> choice there is.
>
> Cheers,
>
> Wayne
>
> On 9/22/2018 5:02 AM, Thomas Pointhuber wrote:
>> Hi,
>>
>> I fixed the mysn bug on my branch:
>> * https://github.com/pointhi/
Hi,
I fixed the mysn bug on my branch:
* https://github.com/pointhi/kicad-source-mirror/tree/crash_report
Allowing people to enable/disable this feature sounds like a good idea.
I tried gcore on linux to create coredumps of an running process, but
because it needs root privileges it cannot
1]:
> http://docs.kicad-pcb.org/doxygen/md_Documentation_development_coding-style-policy.html
>
> On 9/20/2018 5:49 AM, Thomas Pointhuber wrote:
>> Hi Tom,
>>
>> based on your proposal I fixed the Stack Walker (I think it should also
>> be fixed upstream). I was required to duplicate q
.
Regards,
Thomas
Am 19.09.18 um 20:36 schrieb Tomasz Wlostowski:
> On 19/09/18 20:13, Thomas Pointhuber wrote:
>>
>> I rewrote it to use wxDebugReport and wxHandleFatalExceptions. What I
>> noticed (at least for my build setup), the stack-trace is unusable in
>> this vers
independent).
Regards, Thomas
Am 19.09.18 um 19:48 schrieb Simon Richter:
> Hi,
>
> On 19.09.2018 18:38, Thomas Pointhuber wrote:
>
>> For now, it uses the glibc backtrace function to print a basic
>> stack-trace onto the console, and if possible a crash dump file i
than nothing at all. And it could be
especially helpful to find rare crashes which are hard to reproduce.
Regards, Thomas
From 36b475a828e0587069a31c4163908bcfefb7 Mon Sep 17 00:00:00 2001
From: Thomas Pointhuber
Date: Wed, 19 Sep 2018 17:45:27 +0200
Subject: [PATCH] Print stacktrace when SIGSEGV
Hi,
Navigating in the schematic hierarchy seems to be broken a bit. Just
zoom in a bit and enter/leave sub-sheets. You will see the cursor
warping to some weird position, and the sheet is not displayed as whole.
In my case often a blank area appears after entering/leaving the
sub-sheet. The
Hi,
I posted this proposal on launchpad, but no answers so far:
* see: https://bugs.launchpad.net/kicad/+bug/1785119
As some already noticed, I made patches to get Python 3 working with
KiCad (has to be explicit enabled). Windows and Linux tests were
successful and I think it can be merged to
Ping: please review and merge this little patch
On 30.08.18 14:23, Thomas Pointhuber wrote:
> Hi,
>
> a small follow-up patch for
> https://bugs.launchpad.net/kicad/+bug/1788873 which fixes some remaining
> issues
>
Hi,
a small follow-up patch for
https://bugs.launchpad.net/kicad/+bug/1788873 which fixes some remaining
issues
Regards, Thomas
From 7599429256c815142272db6bc1f0e8be64f174de Mon Sep 17 00:00:00 2001
From: Thomas Pointhuber
Date: Thu, 30 Aug 2018 14:21:01 +0200
Subject: [PATCH] Fix focus bug
-source-mirror/commits/action_plugin_panel
Regards, Thomas
From 6a94d1baa506272565fe1959cb1950ba62be66fe Mon Sep 17 00:00:00 2001
From: Thomas Pointhuber
Date: Mon, 27 Aug 2018 13:37:11 +0200
Subject: [PATCH] Modify style of the action plugin panel to follow common
style
and fix of an assert:
* m_grid
Hi,
while poking around the code I apparently found some missing #ifdef
statements.
Regards, Thomas
From 41dc18ac5c96313a465c2b721dc756bb7a2be79b Mon Sep 17 00:00:00 2001
From: Thomas Pointhuber
Date: Sat, 25 Aug 2018 18:30:34 +0200
Subject: [PATCH] Do not show footprint wizard menu when
Hi,
I managed to get KiCad to run with Python 3 as well as did some quick
verification that basic methods are working using CLI (loading boards,
calling a method of it).
Bugreport: https://bugs.launchpad.net/kicad/+bug/1785119
My Branch:
Hi
As Nick already mentioned, I did one of the last attempts of a
high-level abstraction. The goal would be to have this as proposal for
an official API in the KiCad 6 release (and I will likely carry on with
the work on July).
My goal would be to have a "pythonic" and natural to use API, which
I agree that it would be very beneficial (especially for 3rd-party
tools) to have a standardized naming convention.
Related discussions:
*
https://forum.kicad.info/t/default-manufacturers-part-number-field-in-kicad-libraries/4387/65
* https://github.com/KiCad/kicad-library/issues/808
I don't
t;
> Thanks,
>
> Wayne
>
From 8fd84d7b122235af0a0cabec41e5379f41006ae8 Mon Sep 17 00:00:00 2001
From: Thomas Pointhuber <thomas.pointhu...@gmx.at>
Date: Thu, 26 Apr 2018 20:58:49 +0200
Subject: [PATCH 1/2] Adjust Menubar of 3D Viewer to common style
---
3d-viewer/3d_viewer/3d_menubar.cpp | 96
Hi Jeff,
I think the regex you want is: ".*\$(\{.+\}|\(.+\)).*" (Note, I didn't
escape anything)
The best way to develop regex would be by using tools like
https://www.debuggex.com or https://regexr.com
For example, the regex I gave you:
https://www.debuggex.com/r/MTdQVK1dJHXhXtsF
Basics:
.
so I should change it to CW and CCW? I assume the tooltip text of the
panel should also be change accordingly.
Regards, Thomas
Am 2018-05-03 um 19:44 schrieb Wayne Stambaugh:
> On 5/3/2018 1:28 PM, jp charras wrote:
>> Le 03/05/2018 à 18:44, Wayne Stambaugh a écrit :
>>> I did notice one thing
it would be cool to merge this before rc2 :)
Regards, Thomas
Am 2018-04-26 um 21:58 schrieb Thomas Pointhuber:
> Hi,
>
> I did some rebase and rewrite of the patch and removed for now the
> changes in "file" and "edit" to have something hopefully mergab
ting
dialog and thus removes some complexity from the menus.
Available also on GitHub:
https://github.com/pointhi/kicad-source-mirror/tree/3d_viewer_menu-2
Regards,
Thomas
From e07d87ae41db6c64c65aba91b95d1d28b6960e8a Mon Sep 17 00:00:00 2001
From: Thomas Pointhuber <thomas.pointhu...@gm
the menu options that are in the Display Options dialog.
>
> Cheers,
> Jeff.
>
>
>> On 4 Apr 2018, at 13:34, Thomas Pointhuber <thomas.pointhu...@gmx.at> wrote:
>>
>> Hi,
>>
>> some time ago there were adjustments to have a common design of the
>&g
7 00:00:00 2001
From: Thomas Pointhuber <thomas.pointhu...@gmx.at>
Date: Wed, 4 Apr 2018 14:17:20 +0200
Subject: [PATCH] Adjust Menubar of 3D Viewer to common style
---
3d-viewer/3d_viewer/3d_toolbar.cpp | 124 +
1 file changed, 112 insertions(+), 12 deletion
Hi Jeff,
it looks more clear than the current version.
I would hide the text properties (with the exception of Show) by
default. I don't think many people would change for example the position
or orientation using this dialog. Every text attribute also has its own
menu as well which can be used
Hi,
at least in the nightly it is still possible to add GitHub libraries
using "Append with Wizard".
Will this change? Because when someone uses this feature, it only
references to the old legacy repositories, without a clue about that.
Regards, Thomas
signature.asc
Description: OpenPGP
Hi,
as librarian I would also note that an improved Edge:Cuts behaviour
should take in account footprints which define Edge Connectors or cutouts.
At the moment, cutouts are incorrectly rendered in the 3d-viewer when
showing a single footprint, because there is no difference to a board
outline
about 1), I would suggest to change the selection behaviour of locked
footprints, to only select when parts of the footprint (line, pad,...)
are explicitly selected (not the area between). Area selection should
also not include locked footprints. This is likely something where users
want to
I think using "zoom as center of zoom" by default would be the better
default choise, because it's the one most users are used too by other
software as well. From the people I know, everyone changes this settings
as one of their first actions.
Am 2017-07-03 um 16:52 schrieb Greg Smith:
> Thank
What about storing undo information per sheet as done now, but allow
optional grouping of such a operation across sheets.
When KiCad detects the user want's to undo a operation which affects
multiple sheets, he get's a message to chose about reverting the change
only in the the current sheet / or
Hi Oliver,
I can confirm the issue is now fixed.
Some other issues found:
* Please update all duplicated references when someone changes a value,
to show that more than one reference was updated by this edit (as
already done for group edit).
* undo/redo operation of symbols update by your
Hi Oliver,
nice work, and I hope it get merged into master soon.
Some issues I found so far (using your github branch):
* References are not displayed correctly when using duplicated
subschematics.
* Search functionality (using Ctrl+F) does not work with collapsed
grouped references
* Even when
occurring in
> KiCad as well?
>
> Regards,
> Orson
>
> On 02/24/2017 12:28 AM, Thomas Pointhuber wrote:
>> Hy,
>>
>> I think the "select Copper" and "select Net" feature should also select
>> zones, and not only track's and via's.
>&g
s/YxqNpq4NxebmJGW
Regards, Thomas
From fa155e76d34430c14069ed76a03031febb3c37b1 Mon Sep 17 00:00:00 2001
From: Thomas Pointhuber <thomas.pointhu...@gmx.at>
Date: Thu, 23 Feb 2017 22:32:51 +0100
Subject: [PATCH] Select zones using selectCopper or selectNet command
---
pcbnew/tools/selection_tool.cpp | 17
lso allow us to
display those
footprints correctly inside the 3d viewer)
Regards,
Thomas Pointhuber
signature.asc
Description: OpenPGP digital signature
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-develop
64 matches
Mail list logo
