On Mon, Jul 23, 2018 at 2:53 PM, Simon Richter
wrote:
> Hi,
>
> I've started collecting a few ideas on use cases for the new component
> format. I suspect others have done the same.
>
> Is there a good place to collect all of these and/or collaboratively
> edit them?
>
>Simon
What you are
Hi,
I've started collecting a few ideas on use cases for the new component
format. I suspect others have done the same.
Is there a good place to collect all of these and/or collaboratively
edit them?
Simon
# KiCad Schematic Components: Use Cases
This document tries to capture the use cases
On 07/23/2018 08:04 PM, Wayne Stambaugh wrote:
[snip]
> I wondered about that. Orson may be using a later version of wxWidgets.
> I'm currently using 3.0.4. I only use 3.1 when I'm messing around with
> the gtk3 fix stuff.
>
> A quick reminder developers, 3.0 is the currently supported version
John,
I merged your patch into the development and 5.0 branches.
Thanks,
Wayne
On 7/23/2018 10:05 AM, John Beard wrote:
> Hi,
>
> Another small fix for a -Wcatch-value warning that I noticed during a
> clean build.
>
> Cheers,
>
> John
>
>
>
>
As long as I am the project leader the chances are zero. I cannot speak
on behalf of my successor. ;) Unless someone volunteers to maintain the
4 branch, I think it's pretty safe to assume there will not be another 4
branch. I have no intention of spending valuable developer resources
On 7/23/2018 2:00 PM, jp charras wrote:
> Le 23/07/2018 à 18:29, Wayne Stambaugh a écrit :
>> Orson,
>>
>> On 7/23/2018 12:03 PM, Maciej Sumiński wrote:
>>> Hi Wayne,
>>>
>>> On 07/23/2018 05:40 PM, Wayne Stambaugh wrote:
In the process of fixing this bug
Le 23/07/2018 à 18:29, Wayne Stambaugh a écrit :
> Orson,
>
> On 7/23/2018 12:03 PM, Maciej Sumiński wrote:
>> Hi Wayne,
>>
>> On 07/23/2018 05:40 PM, Wayne Stambaugh wrote:
>>> In the process of fixing this bug
>>> https://bugs.launchpad.net/kicad/+bug/1782708 I discovered that the
>>> KIDIALOG
Hi folks!
The macOS build process for V4 was somewhat made of shoe strings and
bubble gum and crossed fingers, and I am not confident that my
hand-tweaked dependencies were reproducible, so the V4 build machine
does literally nothing else but wait for me to tell it to make another
release.
At
Adam,
I merged your patch into the development branch. I'm assuming these
changes apply to the 5.0 branch as well but I want to confirm before
merging into the 5.0 branch.
Thanks,
Wayne
On 7/23/2018 9:18 AM, Adam Wolf wrote:
> Hi folks!
>
> Attached is a docs patch. Please let me know if it
Orson,
On 7/23/2018 12:03 PM, Maciej Sumiński wrote:
> Hi Wayne,
>
> On 07/23/2018 05:40 PM, Wayne Stambaugh wrote:
>> In the process of fixing this bug
>> https://bugs.launchpad.net/kicad/+bug/1782708 I discovered that the
>> KIDIALOG object called when editing an externally defined environment
Thanks Mark, I'll be able to test this out next week.
-S
Am Mo., 23. Juli 2018 um 01:52 Uhr schrieb :
> Hello Seth,
>
> As requested an example eagle project using variants.
>
> regards
>
> Mark.
>
___
Mailing list:
Also being reported here:
https://bugs.launchpad.net/kicad/+bug/1782999
(FWIW, I do think we should store the settings in the config, rather than just
for the session.)
Cheers,
Jeff.
> On 23 Jul 2018, at 17:03, Maciej Sumiński wrote:
>
> Hi Wayne,
>
> On 07/23/2018 05:40 PM, Wayne
Hi Wayne,
On 07/23/2018 05:40 PM, Wayne Stambaugh wrote:
> In the process of fixing this bug
> https://bugs.launchpad.net/kicad/+bug/1782708 I discovered that the
> KIDIALOG object called when editing an externally defined environment
> variable will completely lock up kicad on windows. Clicking
In the process of fixing this bug
https://bugs.launchpad.net/kicad/+bug/1782708 I discovered that the
KIDIALOG object called when editing an externally defined environment
variable will completely lock up kicad on windows. Clicking the dialog
OK button or hitting the escape keep does not close
Hi,
Another small fix for a -Wcatch-value warning that I noticed during a
clean build.
Cheers,
John
From eebe86ea52c028b42389db6139b3b2b4f9bd Mon Sep 17 00:00:00 2001
From: John Beard
Date: Thu, 19 Jul 2018 17:15:36 +0100
Subject: [PATCH] Fix -Wcatch-value in sexpr.cpp
This is fixed by
I'm fine with creating a packaging document. We could add it to the
developers documentation or it could also be an external document with a
link in the compiling doc.
Wayne
On 7/23/2018 8:40 AM, Adam Wolf wrote:
> Agreed, Wayne. The macOS 5.0.0-1 build is uploading right now. It is a
> Release
Hi folks!
Attached is a docs patch. Please let me know if it needs any tweaks
or if you have any questions.
0001-Aim-macOS-users-at-kicad-mac-builder-and-make-buildi.patch
Description: Binary data
___
Mailing list:
Thanks for the info. Repology is now showing Fedora Rawhide as having 5.0.0
available.
Steve
On 07/22/2018 10:18 PM, Mark Roszko wrote:
> For the record, the little badges on the kicad website for linux
> distro package versions come from https://repology.org which scans the
> repos of
I would prefer that we create release builds (CMAKE_BUILD_TYPE=Release)
for the stable releases. Debug builds are fine for nightly builds.
On 7/23/2018 12:07 AM, Mark Roszko wrote:
> Done.
>
> Wouldn't be bad if the wxAsserts were squashed :X
> But then again some of them come from wx
Hi Tom,
Understood. Is there anything I can help with? Or will that just get in the way?
Otherwise, what should I be looking for when test-driving (i.e. what's
helpful to report)? So far:
* Some tools seem to work \o/
* Some tools don't (global labels, for example)
* As noted, some colours
On 23/07/18 12:48, John Beard wrote:
> Hi Tom,
>
> It's now building on 621206fdd, thanks!
>
> I get the following asserts. Let me know if you rather I reported this
> kind of thing in separate emails/threads/on another platform!
>
Hi John,
It's a work in progress, I'm aware of this assert (I
Le 23/07/2018 à 12:18, Jeff Young a écrit :
> Here’s the exception:
>
>
> It’s in the std C++ library, but it throws again trying to generate a stack
> trace and kills the
> debugger.
>
> However, I think I did discover the issue: the layer popup in the Import DXF
> File dialog defaults to
>
Hi Tom,
It's now building on 621206fdd, thanks!
I get the following asserts. Let me know if you rather I reported this
kind of thing in separate emails/threads/on another platform!
1) When pressing Escape:
ASSERT INFO:
./src/gtk/cursor.cpp(234): assert "Assert failure" failed in
Here’s the exception:
It’s in the std C++ library, but it throws again trying to generate a stack
trace and kills the debugger.
However, I think I did discover the issue: the layer popup in the Import DXF
File dialog defaults to Dwgs_User, but if your board doesn’t define that layer
then it
Hi Tom,
I tried to build this (commit 4eb9a3c51), and CMake failed with a
missing file (eeschema/libedit/controller.cpp).
Removing that from the CMakeLists.txt resulted in (predictably enough)
a link failure:
Le 22/07/2018 à 23:53, Jeff Young a écrit :
> Hi JP,
>
> I get an exception when trying to import the various BoardOnly_* files from
> https://bugs.launchpad.net/kicad/+bug/1594607.
>
> Cheers,
> Jeff.
Thanks Jeff, for your test.
I tested these imports both on W7 32 and Linux 64bits (Ubuntu
On 23/07/18 05:27, Mark Roszko wrote:
Is it because the installer exe is huge?
That's because the footprint libraries are now part of the installers
and they are absolutely massive. (4GB uncompressed)
The whole repo (including git history) only has ~90MB
If any libs are to blame then it will
Hello Seth,
As requested an example eagle project using variants.
regards
Mark.
eagle_variant.tgz
Description: Binary data
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe :
Well done, Adam!
> On 23 Jul 2018, at 04:47, Adam Wolf wrote:
>
> Thanks, Wayne!
>
> After two long days, I was able to solve the Python issue. I looked
> for a root cause, and stopped when I got into a CMake module that is
> causing other problems and I was already planning to fix after the
29 matches
Mail list logo
