Re: [kicad] Fully custom DRC rules using python

> implementing all (or most) rules from the ECSS-Q-ST-70-12C specification would result in quite a specialised rule set not really that applicable for non-space related projects. I'm not sure how practical this line of thought would be, but my first thought is: can we implement enough rule

Re: [kicad] Fully custom DRC rules using python

> I assume for most requirements this would be possible. I will have to do some proper analysis of the requirements to answer that fully though. I will try and deconstruct each requirement into a minimum set of constraints and conditions and try to find commonalities. Unfortunately the ECSS is not

[kicad] Re: new open-source electromagnetic field solver available (OpenWME)

Hello Steffen, Thanks for sharing this! Fabien Corona started working on KiCad integration with FEM solvers but the work is still in early stages. Perhaps there is some overlap in possible use cases. It is not immediately clear to me: is your library meant to work from "real" geometry (i.e. a

Re: [kicad] Re: Multiple track dragging development

thm and what is needed at least. >>> >>> Appreciate the pointer to looking at component dragger. >>> >>> Hi Stuart, >> >> I encourage you to have a look at this branch: >> https://gitlab.com/twlostow/kicad/-/commits/tom-multidrag-demo

Re: [kicad] bezier track developement

I suggest the first place to start is implementing Bezier shape creation (don't worry about tracks right now). KiCad already has some level of internal support for Beziers, it just isn't fully-supported by the UI. In the current nightlies, graphic shapes can take on nets. -Jon On Fri, Aug 25,

Re: [kicad] eeschema: allow Kicad to talk to a database using EXTERNAL plugins (dll, so etc)

Hi Andre, I think it would be best to have two different discussions here, first about the idea and concept, and second about your proposed implementation. I wanted to lead with this because I think there is a tendency in discussions to mix the two together unnecessarily. This is a real need and

Re: [kicad] eeschema: allow Kicad to talk to a database using EXTERNAL plugins (dll, so etc)

these get signed with the rest of the >> application. So, if the target is to allow ODBC interaction, we can >> probably support a binary plugin interface that explicitly does that. I >> think that this is (#7436 >> <https://gitlab.com/kicad/code/kicad/-/issues/7436>) &

Re: [kicad] eeschema: allow Kicad to talk to a database using EXTERNAL plugins (dll, so etc)

sed >>>> in KiCad, then this needs to be done in a scripting language. >>>> >>>> There are a couple reasons for this. The big one is that MacOS cannot >>>> load a binary plugin from outside the signed application without triggering >>>> Gate

[kicad] Packager alert: unixodbc dependency

Hi all, The initial work to support database libraries will be merged this week, which will introduce a dependency on unixodbc for non-Windows platforms. We've been testing this on Ubuntu, Fedora, and macOS with no issues so far. Please let me know if anyone has any concerns. Thanks, Jon --

Re: [kicad] Verify macOS implementation of the SpaceMouse integration.

9/2016 and all > applicable local data protection laws and regulations of the countries > where the company operates. To revoke your consent or exercise all your > rights with regards to personal data, please contact us at > priv...@3dconnexion.com. > > *From:* Jon Evans >

Re: [kicad] Verify macOS implementation of the SpaceMouse integration.

ib > > [...] > > > > and the build works out of the box with 3D Mouse support. > > > > Can we have a copy of your build log so that we can compare what the > differences are? > > > > Markus > > > > *From:* Jon Evans > *Sent:* Mo

Re: [kicad] What's your idea about a new skin

KiCad supports custom color themes. There is an (unofficial) repository containing a number of options here: https://github.com/pointhi/kicad-color-schemes I'm sure an Altium-inspired theme would be accepted here. On Wed, Sep 14, 2022 at 11:36 AM Seyed Keyarash Ghiasi wrote: > Dear all devs,

Re: [kicad] Verify macOS implementation of the SpaceMouse integration.

I've enabled this for the next build, I'll report back if it has any troubles (I'm currently unable to test locally). But, in any case, the upcoming code freeze is for new features only. Since 3Dconnexion driver support has already been merged, any bugfixes for it on macOS would not be

Re: [kicad] Verify macOS implementation of the SpaceMouse integration.

Hi Markus, I think the build at https://kicad-downloads.s3.cern.ch/osx/nightly/kicad-unified-20220914-003354-f304e2d4f6.dmg should have this enabled. Let me know if you find it does not. -Jon On Thu, Sep 15, 2022 at 11:16 AM Jon Evans wrote: > I've enabled this for the next build, I

Re: [kicad] Verify macOS implementation of the SpaceMouse integration.

I will defer to @Adam Wolf for details, but my guess would be it is not enabled, because: 1) KICAD_USE_3DCONNEXION defaults to off, so must be turned on per-platform. 2) It is not referenced in kicad-mac-builder , so there is nothing

Re: [kicad] wxWidgets 3.2.0 for Fedora

The surface area of wxPython on KiCad critical functionality is fairly low. I would recommend moving forward and seeing what happens. How long do we have to make this decision/recommendation? It seems easy enough to spot-check the most popular KiCad plugins that make use of wxPython to see if

Re: [kicad] wxWidgets 3.2.0 for Fedora

. On Fri, Aug 12, 2022 at 11:50 AM Steven A. Falco wrote: > On 8/12/22 11:36 AM, Jon Evans wrote: > > The surface area of wxPython on KiCad critical functionality is fairly > low. I would recommend moving forward and seeing what happens. > > > > How long do we ha

Re: [kicad] Verify macOS implementation of the SpaceMouse integration.

b6083f4.dmg has 3D Mouse support. > > > > Markus > > > > *From:* Jon Evans > *Sent:* Wednesday, September 21, 2022 2:46 PM > *To:* Markus Bonk > *Cc:* devlist@kicad.org > *Subject:* Re: [kicad] Verify macOS implementation of the SpaceMouse > integration. > >

Re: [kicad] Verify macOS implementation of the SpaceMouse integration.

ocationg parts) > and viewing in the 3D Viewer, nor on exit. > > No crash logs were generated either. > > > > > > --Markus > > > > *From:* devlist@kicad.org *On Behalf Of *Markus Bonk > *Sent:* Monday, December 19, 2022 7:04 AM > *To:* Jon Evans >

Re: [kicad] Verify macOS implementation of the SpaceMouse integration.

(are they created on first use?) -Jon On Mon, Dec 19, 2022 at 9:59 AM Jon Evans wrote: > Hello Markus, > > Thanks for the info, it sounds like there is something particular going on > with that one user. > Does the backtrace below indicate that the user has the 3DxWare software > i

Re: [kicad] Verify macOS implementation of the SpaceMouse integration.

OK, thank you for looking into this. Best, Jon On Wed, Dec 21, 2022 at 3:08 AM Markus Bonk wrote: > We have tried with a clean install as well as with a drifting device and > cannot reproduce the reported issue. > > > > -Markus > > > > *From:* Jon Evans > *S

[kicad] Packager recommendation: require installation of symbols and footprints with KiCad

Hi all, It recently got brought up that on some platforms it is currently easy to install KiCad without also installing the symbols and footprints. This causes issues for unexpecting users, because KiCad doesn't currently do a good job of allowing users to recover from this situation after

Re: [kicad] IDE for KiCad development

I assume you are talking about Qt Creator? It's a perfectly fine IDE but I don't use it for KiCad so I have no advice on what settings to tweak. I think most developers are using Visual Studio on Windows and CLion or XCode on macOS. On Linux I use CLion, but have also used VSCode and Sublime

Re: [kicad] KiCad 4.0.7 does not have a release file error

KiCad 6.x should still be able to open these files even if they used old symbols and footprints. I'm not sure they would need "porting" other than saving in the updated format. New schematics can be made with new symbols/footprints as desired. On Thu, Nov 3, 2022 at 12:10 PM Steven A. Falco

Re: [kicad] KiCad 4.0.7 does not have a release file error

See also https://gitlab.com/kicad/code/kicad/-/issues/12820 If those users want to keep using 4.0.7 they need to host it themselves. -Jon On Thu, Nov 3, 2022 at 11:38 AM Marco Ciampa wrote: > Can somebody address this request or at least point to the right > direction of how to solve it in

Re: [kicad] KiCad 4.0.7 does not have a release file error

> you won't have access to the footprints you had previously used. You can make a project-local library and export the old footprints to it if desired. I think that is a reasonable workflow. On Thu, Nov 3, 2022 at 1:40 PM Steven A. Falco wrote: > On 11/3/22 12:11 PM, Jon Evans

Re: [kicad] GetCharExcludes

I updated the cmake requirements so that this will get caught at configuration time now (for 7.99 only; we'll still support older wxWidgets on the 7.0 branch) -Jon On Sun, Mar 5, 2023 at 9:40 AM Steven A. Falco wrote: > Thanks, Ian. I've turned off the F36 COPR builds. > > Steve > >

Re: [kicad] Any thoughts on Fedora bug 2169876?

We can start by asking the user to type "bt" in the gdb prompt after they get the crash, which will give us a clue (assuming the Fedora packages are compiled with debug symbols) Your other suggestions are good ones. -Jon On Wed, Feb 15, 2023 at 11:52 AM Steven A. Falco wrote: > A user has

Re: [kicad] eeschema: allow Kicad to talk to a database using EXTERNAL plugins (dll, so etc)

key. >>>>> >>>>> >>>>> Please let me know what you think. >>>>> >>>>> Cheers, >>>>> Andre >>>>> >>>>> On Tuesday, 19 July 2022 at 11:47:45 pm UTC+10 se...@kipro-pcb.com >>>>>

Re: [kicad] odcb connector development and usage

Hi Rico, On Thu, Jul 13, 2023 at 11:19 AM Rico Schmitt wrote: > Hi there, > > TLDR: Is the odbc connector here to stay? Of course > Are there any development > plans for it? Yes, can you be more specific? > I tried it and found some issues using it, I have > implemented a draft of my

Re: [kicad] Re: Multiple track dragging development

Hi Stuart, Some general comments on this project: 1) This functionality should be built into the router, not into the edit routines outside the router IMO. So this should be implemented as part of DRAGGER probably. If you look at how the rest of the router works, you should be able to re-use

Re: [kicad] Changes in KiCad nightly coordinates and plot

I'm guessing this is https://gitlab.com/kicad/code/kicad/-/commit/c31b5eb7d8b89cc3e7630fa0550e3a911b1204a5 which was an intentional change. The old numbers were more rounding errors than the new ones. On Fri, Jun 2, 2023 at 9:59 AM Salvador E. Tropea wrote: > Hi All! > > The last nightly run

Re: [kicad] Stable nightly version still 7.0.5

Testing builds have a version string that includes the most recent tag along with further version info. So it is expected and correct that testing builds after 7.0.5 include the string 7.0.5 as *part* of the version info. The testing build version string is platform/package-dependent. The

Re: [kicad] Building on Mac

The makefiles are generated by CMake, you run make in the build root (whatever directory you ran the cmake command in). On Mon, Jul 31, 2023 at 6:43 PM Jeff Berkowitz wrote: > Hello. I'm using KiCad Mac Builder on Mac and trying to follow > https://dev-docs.kicad.org/en/build/macos/. I got the

Re: [kicad] Coroutine stack cleanups

I'm not clear on how all platforms can take the same codepath since there is some fundamentally platform-specific code in here? Anyway, my own personal thoughts are that anyone looking to work on this area: 1) should be prepared to do their own testing on at least Windows + arm64 Mac + amd64

Re: [kicad] 7.0.3 stable release update

We would appreciate further user testing of 7.0 testing builds so that we can be confident in a 7.0.4 release soon. In addition to the Ubuntu PPA that Ian linked, you can grab the latest builds for Windows/Mac here: Windows:

Re: [kicad] 7.0.3 stable release update

before the release. I don't know what you mean by "major problems" so I can't comment on them without more details. On Tue, May 16, 2023 at 1:16 PM Christoph Moench-Tegeder wrote: > ## Jon Evans (j...@craftyjon.com): > > > We would appreciate further user testing of 7.0 testi

Re: [kicad] Code formatting question

Yes, this is a norm. KiCad's code style is not 100% representable in clang-format, and we also have a policy of not doing bulk-reformatting of files. Make sure to configure your editor to not reformat lines that you didn't edit, and you should be OK. Personally I turn off auto-reformatting, and

Re: [kicad] Unable to build

Hi, KiCad is not supported on this platform, so I doubt anyone can provide step-by-step build instructions. It sounds like you are getting stuck at the building wxWidgets stage? If so, you probably will need to step through that cmake and see where it is getting hung up. > P.S. Is it possible

Re: [kicad] dev platform suggestions.

Hi Glen, Debian or Ubuntu are both fine choices. The one thing to be aware of is that modern Ubuntu turns on Wayland by default, and Wayland has issues that cause KiCad bugs / certain features to not work properly. In both cases, you will need to use a newer version of wxWidgets (3.2, the newer

Re: [kicad] Re: Improvements to the http library

Hi Rosy, > I would be happy to invest time in revising the http library so that the > various problems can be solved, but I would like to know who I should talk to > so that the work is not in vain but is then accepted? This list is a good place, please say more about what you propose to do

Re: [kicad] Cannot compile Kicad (branches: master, 8.0, 7.0) due to the gal library

Your CMake output does not show any errors. It ends successfully. What error do you get when you try to build? On Fri, Apr 26, 2024 at 2:44 PM 'Sven Wehrend' via KiCad Developers wrote: > > Hello, I am new to the Kicad project but would like to contribute to give > back to the community. But

Re: [kicad] Cannot compile Kicad (branches: master, 8.0, 7.0) due to the gal library

What happens when you pass KICAD_USE_EGL=ON to cmake? On Fri, Apr 26, 2024 at 3:26 PM Sven Wehrend wrote: > > > I get the following error log: > > [ 7%] Built target pcm_settings > [ 7%] Building CXX object > common/gal/CMakeFiles/gal.dir/__/draw_panel_gal.cpp.o > In file included from >

Re: [kicad] Re: Improvements to the http library

> In particular, with the idea of including volatile fields such as stock count, price or similar in the future. As discussed on previous gitlab MRs, volatile data should not be mixed up with part fields. Fields are specifically non-volatile. If you want to make a proposal for some system to

Re: [kicad] Re: Improvements to the http library

> My idea, which has not yet been thought of, is that the LIB_SYMBOL has a separate list of volatile fields that are only for the symbol chooser and may also be displayed differently, for example with italics or something like that. If volatile data is implemented, it should be supported in more

Re: [kicad] Re: Improvements to the http library

> What is your view on caching? I agree with Seth that HTTP standards should be used where possible. I also think it would be ideal if there is no need for a "version 2" HTTP library, and instead we can make incremental improvements that are backwards-compatible. > However, this would mean that

Re: [kicad] Altium Importer REPORTER for logging

And I agree that we have to do something about the library importing. > > The only place we disagree is what to do in the meantime for schematics and > boards. > > Cheers, > Jeff. > > > On 4 May 2024, at 13:04, Jon Evans wrote: > > > > Jeff, > > > >

Re: [kicad] Altium Importer REPORTER for logging

g a plugin option > (m_warningsShown or something) after reading the library? I think those are > saved per-row in the lib table, but I’m not 100% sure. > > Cheers, > Jeff. > > > On 4 May 2024, at 09:47, 'Stefan Weber' via KiCad Developers > wrote: > > Hi,

Re: [kicad] Altium Importer REPORTER for logging

on is a bit closer to an editing feature. But if > it’s something like pad-stacks, then I’m going to have to make changes > somewhere to get the design right. So I’d rather know about those. > > > On 4 May 2024, at 14:29, Jon Evans wrote: > > > >> The only place we disag

Re: [kicad] Altium Importer REPORTER for logging

es. Complaining about not being able >> to import a datum dimension is a bit closer to an editing feature. But if >> it’s something like pad-stacks, then I’m going to have to make changes >> somewhere to get the design right. So I’d rather know about those. >> >> > On

Re: [kicad] Altium Importer REPORTER for logging

workflow > > Seth > [image: KiCad Services Corporation Logo] > Seth Hillbrand > *Lead Developer* > +1-530-302-5483‬ > Long Beach, CA > www.kipro-pcb.com i...@kipro-pcb.com > > > On Sat, May 4, 2024 at 7:24 AM Jon Evans wrote: > >> Following up, I think it's

Re: [kicad] Altium Importer REPORTER for logging

e the error reporter to a docked AUI window so that it doesn't > > interrupt the workflow > > > > Seth > > KiCad Services Corporation Logo > > Seth Hillbrand > > *Lead Developer* > > +1-530-302-5483‬ > > Long Beach, CA > > www.kipro-pcb.com <ht

Re: [kicad] Some questions to the roadmap for next time

b.com/kicad/code/kicad/-/issues/> - you can > >>>>> > search for related issues there, or start a new one. > >>>>> > > >>>>> > Hope this helps > >>>>> > > >>

Re: [kicad] .step export for all copper layers

> should we simply add an option "export any copper"? or would it be better to > make a layer-list to specify what should be exported? I think it would catch most use cases to just have a single toggle between outer layers and all layers. > how the export-dialog is made. is there a

Re: [kicad] Returning to contributing - high speed design tools

Hi James, I think there are a number of people working on things in this area so it will be important to coordinate. I don't think working on time-based tuning should be started until some other overhauls to the existing length-based system are farther along. I would suggest that if you are

Re: [kicad] Returning to contributing - high speed design tools

h runs these checks. My question is can we do > this before we start routing the board (i.e. query the DRC data structures > for some human-readable list of length / skew rules)? We could then only > run these constraints against the board during routing to potentially > reduce the O(N*M) burde

Re: [kicad] Some questions to the roadmap for next time

; Am 26.02.2024 um 20:08 schrieb 'Rafał Pietrak' via KiCad Developers: > > Hi Oliver, > > > > You've asked for snippet source - it came from this email by Jon. > > > > -R > > > > W dniu 26.02.2024 o 15:47, Jon Evans pisze: > >> Hello

Re: [kicad] Some questions to the roadmap for next time

Hello Oliver, On Mon, Feb 26, 2024 at 9:34 AM 'White Fox' via KiCad Developers < devlist@kicad.org> wrote: > > As far I know, KiCAD has no support for multiboard projects. I looked > out for something like a road map and found something on gitlab, but > maybe outdated. Last edit was 2020. >