Hi Wayne, Seth,
Here is the patchset with:
* A default ctor param and get/setters
* Trace mask in the header. I somehow haven't noticed this file before, sorry!
Cheers,
John
On Sun, Nov 25, 2018 at 9:35 PM Wayne Stambaugh wrote:
>
> Hey John,
>
> On 11/23/2018 8:26 AM, John Beard wrote:
> >
Hello, I have little to add to what Wayne said. Just a few clarifications:
- Donors to KiCad donate because they trust we will use the money
correctly. For practical reasons, they cannot decide what specifically will
be done with the money, even if we are always happy to read their
suggestions.
Fixes https://bugs.launchpad.net/kicad/+bug/1789960.
Adam
0001-Fix-macOS-scripting-plugins-path-per-Dan-Green.-Fixe.patch
Description: Binary data
___
Mailing list: https://launchpad.net/~kicad-developers
Post to :
Hi Adam,
Please note that current paths are actually correct for previous versions
of MacOS. I'm not sure exactly when the change happened but the paths you
are suggesting are valid for latest versions of MacOS and kicad.
Maybe it's worth to add a note stating that these paths are correct for
Hmm. Interesting. I don't know what package ever had
/Applications/kicad/Kicad/Contents/SharedSupport/scripting/plugins missing
a .app in /Applications/kicad.app/, but the Mac package has had a lot of
history.
What's the next step here... add some words saying "Modern macOS installs
likely have
That sounds good to me.
There is also that MacOS security feature that turns /Applications/...
paths into some obfuscated virtual paths (as seen by the app, even though
those dirs don't exist) and that may spook an uninformed average user. So I
would also add that it's best to stick to the paths
On 11/26/2018 7:02 AM, John Beard wrote:
> Hi,
>
> Having just found the trace_helpers header (which I totally missed
> when making a list of the trace strings...), I have a couple of ideas.
I was the person who started adding them in a common file a few months
back. I did it so I didn't have
Hello KiCad Developers!
As Seth alluded to earlier in the year on this list, we are indeed having a
KiCad user conference in 2019. In contrast to FOSDEM, which is the primary
place that KiCad developers gather, this will be focused on the people who
use KiCad for hobby projects, education and
On Mon, Nov 26, 2018 at 2:06 PM Wayne Stambaugh wrote:
> I did it so I didn't have to grep the entire source tree to find
> the trace string.
Indeed!
> I can see the utility of adding the strings to the trace variable docs.
> I agree that digging through the source file can be time consuming.
Oliver,
I have concerns about greying out the part and being able to see any change
when printed in B This may be why Altium used a big "x", and why the
tools I regularly use also allow an "x" or removing the DNI (I'm most
familiar with this acronym) part.
Another thing to consider is the
Since I am one of the packagers for KiCad for Fedora, I get "abort" reports
that Fedora has collected from users.
I'm forwarding one of the reports to see if there is any interest in this data
by any KiCad developers. Please let me know if it is helpful, or if I should
just disregard these
John,
I merged your patch set. Thanks.
Cheers,
Wayne
On 11/26/2018 5:56 AM, John Beard wrote:
> Hi Wayne, Seth,
>
> Here is the patchset with:
>
> * A default ctor param and get/setters
> * Trace mask in the header. I somehow haven't noticed this file before, sorry!
>
> Cheers,
>
> John
>
Hi,
On 26.11.18 17:52, Steven A. Falco wrote:
> Since I am one of the packagers for KiCad for Fedora, I get "abort" reports
> that Fedora has collected from users.
> I'm forwarding one of the reports to see if there is any interest in this
> data by any KiCad developers. Please let me know
Am 2018-11-26 13:37, schrieb Wayne Stambaugh:
Anyone have any objections to this patch? If not, I will merge it into
the dev branch.
Cheers,
Wayne
Looks good from my tests.
-S
___
Mailing list: https://launchpad.net/~kicad-developers
Post to
I just noticed a few last minute changes were made to the 5.0 branch.
Is there anything else pending or am I good to go with tagging 5.0.2?
Cheers,
Wayne
On 11/25/2018 2:01 PM, Wayne Stambaugh wrote:
> I plan on tagging 5.0.2 tomorrow unless is a show stopper bug that I am
> not aware of. My
Hi,
Having just found the trace_helpers header (which I totally missed
when making a list of the trace strings...), I have a couple of ideas.
First: is there milage to add the strings to the trace variable docs?
This means you can easily see what you should be writing in WXTRACE
without having
Oliver,
On 11/26/2018 4:03 AM, Oliver Walters wrote:
> I'd like some direction from a project leader on how I should progress,
> rather than wasting my efforts:
>
> 1. Adding "DNP" option to schematic components.
>
> This can be achieved now, without breaking the .sch file format. It
> allows
I hope everyone can attend. It would be nice to meet more of the state
side developers and users. I've only met a few of you at FOSDEM so here
is your chance to meet up with the US devs and users. If you can,
please consider giving a talk. Developers have insight most users do
not so maybe you
Anyone have any objections to this patch? If not, I will merge it into
the dev branch.
Cheers,
Wayne
On 11/26/2018 5:56 AM, John Beard wrote:
> Hi Wayne, Seth,
>
> Here is the patchset with:
>
> * A default ctor param and get/setters
> * Trace mask in the header. I somehow haven't noticed
Le 26/11/2018 à 19:57, Seth Hillbrand a écrit :
> Am 2018-11-26 13:37, schrieb Wayne Stambaugh:
>> Anyone have any objections to this patch? If not, I will merge it into
>> the dev branch.
>>
>> Cheers,
>>
>> Wayne
>
> Looks good from my tests.
>
> -S
>
Looks also good to me.
--
Are we expecting to tag 5.0.1 as 5.0.2 for the libraries or are we
getting a minor library update as well?
On Mon, 26 Nov 2018 at 20:32, Wayne Stambaugh wrote:
>
> I just noticed a few last minute changes were made to the 5.0 branch.
> Is there anything else pending or am I good to go with
I just tagged and pushed 5.0.2 so we need to decide what we want to do
about tagging the library and translation repos. Rene, any thoughts on
the library repos. I know there have been a lot of changes since 5.0.1
but as long as the existing symbols have changed too significantly, I'm
fine with
On 11/26/18 3:30 PM, Simon Richter wrote:
> Hi,
>
> On 26.11.18 17:52, Steven A. Falco wrote:
>
>> Since I am one of the packagers for KiCad for Fedora, I get "abort" reports
>> that Fedora has collected from users.
>
>> I'm forwarding one of the reports to see if there is any interest in this
Yay!
We (librarians) have a few outstanding items in the library we want to
close before 5.0.2, but it should only be a couple of days and well within
the one week timeline you requested. Thanks mostly to Antonio, we're now
using the milestone feature of GH so you can see what's left at
I should have also mentioned that the outstanding items milestoned for
5.0.2 are actual fixes which we would like to include. We've been careful
not to pushing breaking changes flippantly so tagging the head of each
library should be safe and an improvement. Breaking changes haven't been
25 matches
Mail list logo
