Hi Markus,
Adding a new icon is certainly possible. There are some guidelines here:
https://dev-docs.kicad.org/en/rules-guidelines/icon-design/
In particular, the icon must be added with an appropriate SVG source file
authored in Inkscape and with the appropriate (CC-BY-SA) license attribute
Thanks for putting in the work to get this integrated, Mark! Having
automated crash dumps will be invaluable to improving KiCad stability.
On Wed, Mar 30, 2022 at 8:32 PM Mark Roszko wrote:
>
> Hey folks,
>
> We are planning to introduce the use of the Sentry platform into KiCad.
> Sentry
@seth - I think the docs need to be re-packed in the manner Christoph says,
IIRC that is a requirement for the Mac packaging.
On Fri, Feb 11, 2022 at 10:09 AM Christoph Moench-Tegeder <
c...@burggraben.net> wrote:
> Hi,
>
> ## Wayne Stambaugh (stambau...@gmail.com):
>
> > All of the repos have
> THE MAIN PROBLEM ARE THE OUTDATED DOCUMENTS!
> NOT THE WAY THEY ARE DISTRIBUTED.
One reason the documents are outdated is that they are hard to contribute
to.
They are hard to contribute to in part because they use a toolchain that
only works well on Linux, and many of our users who might feel
age and then install it via a USB stick
or whatever (but probably not in a secure environment), but you could also
download the docs website.
-Jon
On Wed, Jan 19, 2022 at 5:03 PM Eeli Kaikkonen
wrote:
> On Wed, Jan 19, 2022 at 6:38 PM Jon Evans wrote:
> >
> > What I would propose to imp
On Wed, Jan 19, 2022 at 2:12 PM Steven A. Falco
wrote:
>
> Not to put words in your mouth, but it sounds like the code will be
> changed so that when someone clicks on the Help menu, they will get the
> on-line version, if possible.
> And only if the on-line version cannot be accessed, the code
On Wed, Jan 19, 2022 at 1:05 PM Carsten Schoenert
wrote:
> [ I'm on this list, no need to address me dedicated. ]
>
My email client does this automatically, but if it bothers you I removed it
manually :)
>
> Am 19.01.22 um 18:45 schrieb Jon Evans:
>
> > I think you misunde
On Wed, Jan 19, 2022 at 12:37 PM Carsten Schoenert
wrote:
> Hello Jon,
>
> Am 19.01.22 um 17:38 schrieb Jon Evans:
> > Carsten,
> >
> > There is no reason to remove the ability to package docs offline, I just
> > don't think it should be a focus of the pr
not saying we should remove any way for people in high-security
offline environments to get documentation, but just that it shouldn't be
the default option.
-Jon
On Wed, Jan 19, 2022 at 12:12 PM Steven A. Falco
wrote:
> On 1/19/22 12:00 PM, Jon Evans wrote:
> > That just doesn't seem th
;. I.e., Fedora builds are not a "rolling release" - they are
> tied to tags.
>
> Steve
>
> On 1/19/22 11:38 AM, Jon Evans wrote:
> > Carsten,
> >
> > There is no reason to remove the ability to package docs offline, I just
> don't think
Carsten,
There is no reason to remove the ability to package docs offline, I just
don't think it should be a focus of the project.
The majority of users will be served better by keeping a "rolling release"
online at docs.kicad.org (with a download button, ideally).
> It absolutely doesn't hurt
e documentation site easily downloadable to be viewed in a browser when
> offline.
>
>
> Thanks!
>
> Gabriel Staples
>
> (sent from my Android)
>
> Le mar. 18 janv. 2022, 11:12 AM, Jon Evans a écrit :
>
>> We have decided to update the online documentation
The documentation lives in this git repo:
https://gitlab.com/kicad/services/kicad-doc
The same sources build the version on the website (docs.kicad.org) and the
offline docs.
If keeping the offline docs is important, I think the next best thing is to
insert some extra text in the offline build
ou can access online version
> from the software, so why to include old (probably no more relevant)
> documentation?
>
> Regards,
> Tomas
>
> On Tue, 18 Jan 2022, 17:17 Jon Evans, wrote:
>
>> I don't personally see the point of spamming the list with back and forth
>> abo
I don't personally see the point of spamming the list with back and forth
about setting up Git/Gitlab, installing dependencies, etc.
But, I am not opposed to it if others don't care.
-Jon
On Tue, Jan 18, 2022 at 12:02 PM Marco Ciampa wrote:
> On Tue, Jan 18, 2022 at 09:10:22AM -0500,
Hi Tomas,
I've been loosely coordinating documentation updates for V6. There are not
very many other people working on it. We'd be happy to have your help.
If you contact me off-list I can help you get set up to make changes and we
can figure out where you'd like to start.
Best,
Jon
On Tue,
we try to make KiCad applicable to more
high-end designers, it could become an issue for more people.
-Jon
On Tue, Jan 11, 2022 at 4:46 PM pmx wrote:
>
>
> Le 11/01/2022 à 21:59, Jon Evans a écrit :
>
> The current offerings (e.g. bgfx) are generally multi-platform but without
> the
higher than 2.1.
On Tue, Jan 11, 2022 at 3:57 PM pmx wrote:
>
>
> Le 11/01/2022 à 21:10, Jon Evans a écrit :
> > > IMHO, we shouldn't remove anything that helps to deal gracefully
> > with the diversity of situations (like a virtual machine), graphics
> &
> IMHO, we shouldn't remove anything that helps to deal gracefully with the
diversity of situations (like a virtual machine), graphics hardware and
video drivers... and their possible bugs ! (as stated about X11/Mesa).
The fallback engine we use today does not have feature-parity with the
It looks like your source directory is dirty (not the build dir)
Try "git clean -fx" or similar.
-Jon
On Fri, Dec 31, 2021 at 1:30 PM Marco Ciampa wrote:
> Hello devs!
> I need some help.
>
> Sometimes my cmake configuration goes wrong and I get stuck with this
> kind of error:
>
> Built
I agree, KICAD_PCM can be removed now.
On Sat, Dec 25, 2021 at 7:27 AM Nick Østergaard wrote:
> Having the unused parameters is no harm, it will only generate a
> warning at configure time.
>
> The KICAD_PCM flag already defaults to ON, but I guess it should just
> be removed as an option? Are
Welcome Mikolaj! Happy to have you in this role :)
-Jon
On Fri, Nov 19, 2021 at 9:15 AM Wayne Stambaugh
wrote:
> I am happy to announce that Mikolaj Wielgus has accepted an invitation
> to become a member of the KiCad lead development team. Mikolaj has made
> some significant contributions
2021 um 14:58 -0500 schrieb Jon Evans:
> >> When do you need it by? The docs are nowhere near ready for the
> >> final release, so if this isn't a hard requirement, I would suggest
> >> not bothering to package the docs for now.
> >
> > I hope to get 6.0.0-
Well, the new docs are not translated yet either, so there's that :)
On Thu, Nov 18, 2021 at 3:04 PM Johannes Maibaum wrote:
> Am Donnerstag, dem 18.11.2021 um 14:58 -0500 schrieb Jon Evans:
> > When do you need it by? The docs are nowhere near ready for the
> > final release, s
When do you need it by? The docs are nowhere near ready for the final
release, so if this isn't a hard requirement, I would suggest not bothering
to package the docs for now.
On Thu, Nov 18, 2021 at 2:52 PM Johannes Maibaum wrote:
> Hi Seth & list,
>
> Am Dienstag, dem 16.11.2021 um 12:52
Hi all,
If you develop Python plugins for KiCad, this message is for you!
First of all, as you have probably seen, the new Python API won't be
included in KiCad 6.0. We still want to support the existing SWIG API that
allows the creation of action plugins in the PCB editor and external
scripts,
). However, if we at least know that a problem exists upstream,
than we can track it and volunteer devs who may have time to work on it can
find it.
-Jon
On Mon, Nov 8, 2021 at 11:49 AM Jon Evans wrote:
> I certainly agree with a stability drive, I would just caution to not
> assume that th
t to
> fix them (if possible) anyway because they could be hiding other issues,
> either in a wood-trees way or because of side effects. The same applies to
> warnings from the compiler, etc.
>
> Regards,
>
> Ruth
>
>
> On 08/11/2021 16:38, Jon Evans wrote:
>
> Hi
Hi Ruth,
Thanks for the notes. There is a lot of content in your email, and I worry
it will get lost if it doesn't get split up into multiple issues on the
issue tracker.
Some of the issues you mention (GTK warnings, ASan issues related to
Python, etc) are known issues and we don't plan to fix
Hi Jan and José,
Unfortunately I don't have a status update for you on the pybind11 API.
I'm going to investigate fixing the regressions in the SWIG API so that
your plugins can access the board design settings again.
Best,
Jon
On Mon, Nov 1, 2021 at 6:04 AM Jan Mrázek wrote:
> Hello Wayne
Hi Carsten,
Sorry I was not clear, yes this is a dependency for the main binaries so it
should go in the main package if you have multiple packages.
Best,
Jon
On Mon, Nov 8, 2021 at 2:53 AM Carsten Schoenert
wrote:
> Hello Jon,
>
> Am 08.11.21 um 03:30 schrieb Jon Evans:
&
Hi all,
We just turned the plugin and content manager (PCM) feature on for all
users.
To work properly, this feature needs an additional directory packaged:
$KICAD_DATA/schemas
If your packaging scripts already grab everything inside $KICAD_DATA, you
should not need to do anything. If you
Hi all,
As described in more detail in a forum thread[1], Homebrew no longer
packages opencascade for macOS 10.14. As opencascade is a requirement for
KiCad, this means that we can no longer build on 10.14 and therefore cannot
support 10.14 for the 5.99 nightly builds or the upcoming 6.0 stable
Thanks Holger, I tested a fix and it works now (6b48825a)
Updated
https://gitlab.com/kicad/packaging/kicad-mac-builder/-/merge_requests/344
to bump to ngspice-35.
I guess Mark can do the same in vcpkg for the Windows build.
-Jon
On Mon, Aug 9, 2021 at 1:50 PM Holger Vogt wrote:
> Hi Jon,
>
>
Hi Holger,
Thanks for the notice. I tested this on macOS and had no trouble compiling
or running, although KiCad does not properly display the ngspice version
anymore (probably a KiCad bug)
-Jon
On Sun, Aug 8, 2021 at 4:14 PM Holger Vogt wrote:
> ngspice-35 is available.
>
> Please see
Hi Holger,
Last time Adam and I looked at this, I could not build ngspice-34 and
kicad-nightly on macOS because of the issue with config.h changing.
I have not tried recently; Adam, have you?
-Jon
On Wed, Jul 21, 2021 at 11:14 AM Holger Vogt wrote:
> The nightly for macOS from July 20th is
I think from your screenshots in the issue you're working on that you're on
Windows -- I can second that using Visual Studio / MSVC is significantly
faster than mingw.
Also, if you are testing something over and over in eeschema or pcbnew,
just building that one target and running from the build
gdb ./kicad/kicad is starting KiCad from the build directory.
This isn't a fully-supported way of debugging KiCad, but if you want to do
this, you must set the environment variable
KICAD_RUN_FROM_BUILD_DIR=1
Alternatively, since you are running `make install` above, you can use gdb
to debug
Hi Carsten,
I was reminded of this thread because of this forum post:
https://forum.kicad.info/t/how-install-kicad-6-x-on-debian/30034/4
Is the fact that there is a 6.0.0 tag on experimental also related to this
issue with versioning?
Best,
Jon
On Sun, Apr 11, 2021 at 2:25 AM Carsten Schoenert
https://dev-docs.kicad.org/en/rules-guidelines/code-style/ has been updated
to clarify this point.
-Jon
On Mon, Jul 5, 2021 at 12:32 PM Jon Evans wrote:
> Lines which only contain braces do count as a blank line in this context.
> We should clarify this in the style guide.
>
>
Lines which only contain braces do count as a blank line in this context.
We should clarify this in the style guide.
Best,
Jon
On Mon, Jul 5, 2021 at 2:20 AM Markus Bonk
wrote:
> Hi,
>
>
>
> In my opinion there may be issues with the examples in the KiCAD coding
> style doc relating to 4.2.3
Hi Ruth,
You can build the nightly flatpak (with wx 3.1) by grabbing this repository
and following the instructions in the readme:
https://gitlab.com/kicad/packaging/kicad-flatpak/kicad-nightly-flatpaks/kicad-nightly-flatpak
Johannes can probably answer any detailed questions better than I, but
Please see https://dev-docs.kicad.org/en/build/windows-msvc/ at the bottom,
the "running and debugging" section.
Now that Python is required, you must tell KiCad how to find Python when
running from Visual Studio.
The options are to set the environment variables as explained on that page,
or
The option KICAD_SCRIPTING_PYTHON3 doesn't even exist anymore. I
recommend that people who are having issues get rid of your CMake
cache and start fresh, you have a lot of left over variables that may
be confusing things. When we remove a variable from our CMake
configuration, many times it does
:
> On 2021-06-14 4:34 p.m., Marco Ciampa wrote:
> > On Mon, Jun 14, 2021 at 03:43:54PM -0400, Jon Evans wrote:
> >> You should be able to override what is found by CMake by defining the
> >> PYTHON_EXECUTABLE variable in your cmake command line
> >
> &
already have those cloned separately. 1.3GB is quite a lot
> to download each time one want to try the latest build.
>
> On Mon, Jun 14, 2021 at 8:35 PM Jon Evans wrote:
> >
> > Hi Jonatan,
> >
> > Using your system Python is no longer supported after the recent Python
&g
You should be able to override what is found by CMake by defining the
PYTHON_EXECUTABLE variable in your cmake command line
-Jon
On Mon, Jun 14, 2021 at 3:41 PM Marco Ciampa wrote:
>
> On Fri, Jun 04, 2021 at 02:50:37PM -0400, Kevin Cozens wrote:
> > On 2021-06-04 1:34 p.m., Seth Hillbrand
Hi Jonatan,
Using your system Python is no longer supported after the recent Python changes.
Please see the instructions here: https://dev-docs.kicad.org/en/build/macos/
and obtain kicad-mac-builder for the dependencies here:
https://gitlab.com/kicad/packaging/kicad-mac-builder
Adam has
Steven A. Falco wrote:
>
> I'll have to spin up a VM to play with that. I'll get back to you... :-)
>
> Steve
>
> On 5/30/21 2:34 PM, Jon Evans wrote:
> > You want this one: https://github.com/Mogztter/asciidoctor-web-pdf
> >
> > On Ubuntu I install it w
Steve
>
> On 5/30/21 1:58 PM, Steven A. Falco wrote:
> > Thanks Jon.
> >
> > I'm running a test build now. If it passes, I'll propose a patch for the
> > README. I'll also push the change to the nightly Fedora builds.
> >
> > Steve
> >
> >
Hi Steve,
As the readme notes, I have not yet updated the docs for Fedora or
Manjaro/Arch as I don't use those distros and am not sure of the right
incantations.
If you can advise what should go into the README I'm happy to update it.
Also, please let me know if you run into any snags building
What version of ngspice are you using?
Sourceforge is down right now so I can't check the latest tree easily, but
in my cached version, the ControlledExit function signature in
sharedspice.h is using bool (not BOOL), and so is KiCad.
Is there some version of ngspice where those function
3.9/site-packages/dyldstyle/utils.py",
> line 151, in get_file_magic
> subprocess.check_output(cmd, stderr=subprocess.STDOUT)
> UnicodeDecodeError: 'utf-8' codec can't decode byte 0xd8 in position
> 194: invalid continuation byte
>
> Any ideas?
>
> On Thu, Apr 29, 2
Hi Jonatan,
Adam and I have been bouncing ideas back and forth and he helped me get to
a working setup, most recently with Seth's new_python branch but I think
this should work with current master too.
The key point is that we don't yet have a working way to use your system
Python (but Adam has
The patches are obsolete and will be removed from the documentation/source
tree.
On Wed, Apr 28, 2021 at 7:23 PM Eeli Kaikkonen
wrote:
> On Thu, Apr 29, 2021 at 1:05 AM Knochi.de wrote:
> >
> > I’m using the standard Raspberry OS which is “raspian buster”
> > libcurl4-gnutls-dev was the
Hi Markus,
I assume NL_3D_VIEWER_PLUGIN_IMPL is all your custom code as it doesn't
exist in KiCad's codebase.
Refreshing the display is a separate action that can be called when needed.
Some of the other actions do the refresh for you, but some do not.
It looks like you can send a
> It makes me think the developers need to download a new copy of the
source tree to find out the differences.
Anyone (developers included) can see the differences in the GitLab web
interface when a merge request is created.
Of course, anyone can also check out the branch (with Git you do not
> get the version and paths needed?
>
> On Tue, Mar 23, 2021 at 4:20 PM Jon Evans wrote:
> >
> > It sounds like the preference is to move away from using a config.h at
> all, which means all the KiCad packaging systems would need to update to
> use pkg-config to generate a
It sounds like the preference is to move away from using a config.h at all,
which means all the KiCad packaging systems would need to update to use
pkg-config to generate a header which can then be included in kicad's build
process. Is that correct?
On Tue, Mar 23, 2021 at 11:15 AM Jonatan
Bumping this thread as we don't seem to have a resolution yet.
The Windows vcpkg package works as there is still a config.h with the
version in the "visualc" directory.
But, MacOS doesn't build and I guess some Linux distros don't either.
Can we make pkg-config work for MacOS?
On Wed, Feb 3,
Hi Rigo, here's my thoughts, other devs might have more to add:
> Most significantly, the separate icon set. While everyone is looking
forward to having this small feature, it's still kinda offending the term
feature "freeze". Though we weren't at string freeze, new features are
already annoying
Thu, Mar 18, 2021 at 7:14 PM Seth Hillbrand
>> wrote:
>>
>>> Do we still need spice as a build option? It would be nice to bring
>>> down the number of permutations out there and the SPICE simulator is really
>>> a first-class KiCad citizen nowadays.
>>>
he setting. I suppose I could split out the simulator
> settings code but it would be awkward at best.
>
> On 3/18/21 6:42 PM, Jon Evans wrote:
> > Wayne, I haven't checked this code carefully but I'd recommend building
> > the settings always, and moving the #ifdef
Wayne, I haven't checked this code carefully but I'd recommend building the
settings always, and moving the #ifdef to a different level (i.e. make the
settings not depend on ngspice)
That way if the same settings files are shared between a build with ngspice
and a build without, they won't get
Hi all,
There is a proposal[1] to use the PATHS::GetStockDataPath() instead of
DEFAULT_INSTALL_PATH to set the base path for finding KiCad libraries.
This resolves to the KICAD_DATA CMake variable on Linux, and has
special-casing on Windows and MacOS to handle the packaging setup on those
If this is the first time you are running KiCad 5.99, or you erased your
settings directory, you may be hitting
https://gitlab.com/kicad/code/kicad/-/issues/7900 with that version.
If this is the case, try installing an older nightly (like go back a week
or so, just using the lite installer is
Great, thanks for testing, Steve!
On Thu, Mar 11, 2021 at 5:25 PM Steven A. Falco
wrote:
> On 3/11/21 8:43 AM, Jon Evans wrote:
> > Hi all,
> >
> > As of 18037e2f, a new data file is generated during build that contains
> image resources for KiCad.
> >
>
Hi all,
As of 18037e2f, a new data file is generated during build that contains
image resources for KiCad.
This file should be installed to ${KICAD_DATA}/resources/images.tar.gz (So,
something like /usr/share/kicad/resources/images.tar.gz on Linux).
There is an install target for this in the
ll.cmake:101 (fixup_bundle)
> cmake_install.cmake:67 (include)
>
> On Wed, Mar 10, 2021 at 3:48 AM Adam Wolf
> wrote:
> >
> > I haven't seen that. I can take a look at a bigger build log if you
> want.
> >
> > To be clear for others, I'm not advocating carrying
Hi Jonatan,
I hit the exact same issue (I'm also on 10.15), and after chatting with
Adam about it, decided to try using the 10.14 bottle manually:
Download
https://bintray.com/homebrew/bottles/download_file?file_path=opencascade-7.5.0.mojave.bottle.tar.gz
Install with:
brew install -f
Should be fixed now.
On Sat, Feb 27, 2021 at 7:48 AM Wayne Stambaugh
wrote:
> Looks like a commit in the last 24 hours broke KiCad builds with Python
> enabled. Here is the build error on Linux using gcc 9.3.0.
>
> In file included from
>
libraries no problem. MSYS2 builds would just remain without it.
>
> But just my opinion on this.
>
> On Thu, Feb 25, 2021 at 9:32 AM Jon Evans wrote:
>
>> That is a good point Mark, we could either have this behind a flag so
>> that it only gets enabled/compiled w
.65
>> but that doesn't help :/
>>
>>
>> Regards,
>> Mark
>>
>> On Thu, Feb 25, 2021 at 9:00 AM Jon Evans wrote:
>>
>>> Hello Markus,
>>>
>>> This is exciting news, as some of our users are also big fans of
>>&
Hello Markus,
This is exciting news, as some of our users are also big fans of
3dconnexion products[1]
Others have looked in to what it would take in the past, but there were
some questions about the need for proprietary drivers on some platforms[2]
It sounds like this websocket interface is a
Issue reporting instructions are here:
https://kicad.org/help/report-an-issue/
Best,
Jon
On Fri, Feb 19, 2021 at 12:42 PM David wrote:
> Hi,
>
> Just to let you know that there is a problem with the text on the first
> column fourth row of the board classes tab of the PCB Calculator (Please
>
We don't have CI on the 5.1 branch right now. I'm not sure if there is any
reason other than needing to set up additional runner machines, I agree it
would be a good idea.
On Wed, Feb 17, 2021 at 10:46 AM Marco Ciampa wrote:
> On Wed, Feb 17, 2021 at 08:12:14AM -0500, Jon Evans wrote:
>
Hi Marco,
I am not part of kicad-us...@groups.io but I am part of this list and I can
fix the issue you mention, sorry about that...
Best,
Jon
On Wed, Feb 17, 2021 at 7:34 AM Marco Ciampa wrote:
> Forwarded because nobody answered me...
>
> - Forwarded message from Marco Ciampa -
>
>
We are planning something like this. However I want to also mention that
we need to re-do most of the documentation itself (not just update the
screenshots for the existing documentation) because so much functionality
has changed.
On Sat, Feb 6, 2021 at 8:07 AM Константин Барановский <
Hi Andrew,
The attached file does not open in PcbNew, it appears to be truncated.
It would be helpful if you could attach the full file to a GitLab issue
along with the exported DXF:
https://gitlab.com/kicad/code/kicad/-/issues/new?issue%5Bassignee_id%5D=%5Bmilestone_id%5D=
Thanks,
Jon
On Tue,
I can't see an attached video, but what version do you have?
This behavior sounds like a recently fixed bug:
https://gitlab.com/kicad/code/kicad/-/issues/7002
On Tue, Jan 12, 2021 at 7:45 AM Johann Wilhelm
wrote:
> Hi there!
>
> I have the feeling, there's something wrong with the dragging of
That key is part of the shared configuration class that is inherited by all
the specific application configuration classes.
Not all the applications actually make use of their own key. For example,
the symbol editor will just use the eeschema setting, and the footprint
editor just uses the
Hi folks,
We've got a pile of bugs to fix between now and V6 release.
Some of them we think would be more approachable for those who haven't
contributed to KiCad before or have not contributed frequently. These are
tagged "starter" on GitLab:
Hi all,
I feel kind of bad now, my "Christmas special" email was not supposed to be
taken so seriously.
I don't think there is any huge rush, and if we need more time to prepare
the release, using Wayne's original timeline or something in the middle
(1-January release?) would also be fine, I
The KiCad Christmas special?
On Tue, Dec 22, 2020 at 5:02 PM Nick Østergaard wrote:
> I don't think we need that long. Everything seems to be tagged. I have
> triggered the windows build and it should just be a simple pkgver bump
> for macos and ubuntu ppa as well.
>
>
> On Tue, 22 Dec 2020 at
)
wire to be added in -- this is new and probably related to the recent
dragging changes.
-Jon
On Tue, Oct 27, 2020 at 9:07 PM Jon Evans wrote:
> Any chance you can share your schematic?
>
> I noticed that in your screenshot, your label {SD_SIGNALS} is on a green
> wire.
> By
Any chance you can share your schematic?
I noticed that in your screenshot, your label {SD_SIGNALS} is on a green
wire.
By default, buses are blue and plain wires are green.
Did you change the color theme, or is that not a bus?
-Jon
On Tue, Oct 27, 2020 at 9:04 PM Brian Piccioni
wrote:
>
I think we can define a manual grouping and sort order based on function,
and apply that here as well as in the DRC dialog perhaps
On Wed, Oct 21, 2020 at 1:12 PM Brian wrote:
>
>
> On 10/21/20 12:51 PM, jp charras wrote:
> > Unfortunately, even in a alphabetical order in English, it will be
(The contrast for the current icons is worse on Windows than on other
platforms because the default Windows application color theme uses a darker
panel background)
On Wed, Oct 14, 2020 at 11:06 AM Jon Evans wrote:
> Like I said, the icons (visual style and color) will be changed bef
pretty hard to differentiate.
>
>
> On 2020-10-14 11:00 a.m., Jon Evans wrote:
>
> > FWIW, I find the "open eye", "closed eye" a bit hard to differentiate.
> I'd prefer something like an X or check mark.
>
> The icons are being tweaked before release. Th
are visibility controls -- normally checkboxes are for
enabling/disabling things.
On Wed, Oct 14, 2020 at 10:57 AM Ian McInerney
wrote:
>
>
> On Wed, Oct 14, 2020 at 3:52 PM Jon Evans wrote:
>
>> "Footprint Text" off turns off all footprint text, including refer
"Footprint Text" off turns off all footprint text, including references and
values. This isn't new behavior but I worry that the simplified objects
panel has made it more confusing than it was in 5.1
We could have the Footprint Text control act as a visual override for the
Values and References
as it is very complex format).
> > On the current 3D-Viewer implementation, Cirilo worked alone on the
> model importer code alone and it took some months of work..
> >
> > Mario
> >
> >
> > From: Kicad-developers ua...@lists.launchpad.net> on behalf of Seth Hi
wer implementation, Cirilo worked alone on the model
> importer code alone and it took some months of work..
>
> Mario
>
> ________
> From: Kicad-developers ua...@lists.launchpad.net> on behalf of Seth Hillbrand >
> Sent: 29 September 2020 19:01
> To: Jon Evans
> Cc: ki
Do other EDA tools allow model scaling? Altium doesn't even allow VRML
import in the first place.
On Tue, Sep 29, 2020 at 1:10 PM Seth Hillbrand wrote:
> Well, we've backed ourselves into a bit of a corner. VRML is specified in
> meters, so if we're assuming inches, we're a bit off in left
MSVC works great, I really recommend giving it a try. Much faster compile
time than msys.
Seems like Mark will have a solution for wxPython very soon too :)
On Fri, Sep 25, 2020 at 3:10 PM Wayne Stambaugh
wrote:
> On 9/25/2020 3:04 PM, jp charras wrote:
> >
> > Le 25/09/2020 à 19:11, Wayne
Can you run with ASAN on (KICAD_SANITIZE in CMake) and see if you get some
info about why you get a segfault?
On Fri, Sep 25, 2020 at 10:28 AM Franck Jullien
wrote:
> Hi,
>
> I'm working on the intersheets references functionality and I'm
> struggling with a segfault.
> Until now, I didn't try
Hi Alexander,
For (1) I know Oleg Endo has been doing some work on the Net Inspector to
allow grouping nets for combined length measurement:
https://gitlab.com/kicad/code/kicad/-/merge_requests/187
For (3) the intent was to do this via the new DRC rule system.
The PNS router needs to be updated
I think the people suggesting CSV are missing the point of the database
feature (as I see it): collaboration.
Having 5 different people working from a single CSV file is not fun.
-Jon
On Sat, Aug 29, 2020 at 10:26 AM Jeff Young wrote:
> My point about MySQL wasn’t that *we* should bundle it,
up a Pandora's box of complaints as
>> to why we didn't use database A over database B. ODBC is the most
>> flexible solution that I am aware of and allows users to choose their
>> preferred database.
>>
>> Cheers,
>>
>> Wayne
>>
>> On 8/29/20 8:29
t; I would most likely reject any solution that was tied to a particular
> >> database. All this would do is open up a Pandora's box of complaints as
> >> to why we didn't use database A over database B. ODBC is the most
> >> flexible solution that I am aware of and allows use
1 - 100 of 827 matches
Mail list logo
