Good stuff; I like most of these changes.
A few issues:
Show/Hide Layers Manager and Show/Hide Microwave Toolbar should be changed to
checkable items (with just the show version of the text). They should also
probably move down the menu so they’re in the same order as the toolbar buttons.
I’ve got it enabled now on my build. I’ll continue to play with it a bit….
> On 13 Feb 2018, at 22:44, Wayne Stambaugh wrote:
>
> I'm sure this was done for a reason. What that reason is I cannot say for
> sure. I'm not opposed to enabling this assuming it isn't broken
I'm sure this was done for a reason. What that reason is I cannot say
for sure. I'm not opposed to enabling this assuming it isn't broken
which I'm guessing was the case which is why it's turned off on macos
builds.
On 02/13/2018 04:35 PM, Jeff Young wrote:
Pcbnew; Place Footprint Tool;
Pcbnew; Place Footprint Tool; click on canvas.
Mac only has “Search by Keyword” and “List All” buttons. No “Select by
Browser”.
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe :
On 2018-02-13 10:50 AM, Adam Wolf wrote:
I am trying to build from master, but even with -DKICAD_SPICE=OFF, I'm getting:
CMake Error: The following variables are used in this project, but
they are set to NOTFOUND.
I ran across the same problem. If you run cmake without setting the SPICE
That could be it. I'll report back.
On Tue, Feb 13, 2018 at 9:53 AM, Nick Østergaard wrote:
> Did you make a clean build? I don't think the cmake module works well if it
> was configured with it enabled first, and then disabling it.
>
> Den 13. feb. 2018 4.50 PM skrev "Adam
Did you make a clean build? I don't think the cmake module works well if it
was configured with it enabled first, and then disabling it.
Den 13. feb. 2018 4.50 PM skrev "Adam Wolf" :
Hi folks!
I am trying to build from master, but even with -DKICAD_SPICE=OFF, I'm
Hi folks!
I am trying to build from master, but even with -DKICAD_SPICE=OFF, I'm getting:
CMake Error: The following variables are used in this project, but
they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the
CMake files:
NGSPICE_LIBRARY
linked by
Yes, thank you.
2018-02-13 15:42 GMT+01:00 Wayne Stambaugh :
> Nick,
>
> I updated the development focus to the 5.0 branch and remove the
> product-git branch. Is this what you were looking for?
>
> Cheers,
>
> Wayne
>
> On 2/13/2018 8:50 AM, Nick Østergaard wrote:
> >
Nick,
I updated the development focus to the 5.0 branch and remove the
product-git branch. Is this what you were looking for?
Cheers,
Wayne
On 2/13/2018 8:50 AM, Nick Østergaard wrote:
> Yes, but that is the users fault interpreting stuff not intended for the
> end user.
>
> But on a related
Russell,
I going to defer this patch to v6 since we are currently in feature
freeze. I would ask that you please change the source naming to match
the feature name "save project as" and resubmit it when you get a
chance. You are using "save as project" for source names but the
feature and UI
Just a quick notice to all of the package devs that may impact kicad
version strings used for packaging. I have changed the way the version
strings are generated in my development repo and I am planning on
pushing this on Friday. By default git will always be used to generate
the version string
Great, thank you Russell! That is exactly what I had in mind.
Regards,
Orson
On 02/13/2018 01:56 AM, Russell Oliver wrote:
> Updated patch.
>
> On Tue, Feb 13, 2018 at 9:41 AM Wayne Stambaugh
> wrote:
>
>> On 02/12/2018 05:21 PM, Russell Oliver wrote:
>>> So a file
Yes, but that is the users fault interpreting stuff not intended for the
end user.
But on a related note to that, could you make the 5.0 series the active
focus of development? I can not edit that property.
https://launchpad.net/kicad/5.0
such we can delete the product-git series which makes no
Nick,
This seems logical given our current versioning scheme. Although, it
may give users a false sense that v6 is just around the corner.
As for a 5.1 version, I'm still not convinced we have the manpower to
back port features from the development branch to create point releases.
I know I
Jose,
You are correct. The only regression would be for boards create between
the original patch and the bug fix which would be a fairly short period.
Other than fixing broken older board files, the rotation feature
remains in tact so I don't think any changes are required.
Cheers,
Wayne
On
Since someone asked: This is
latest origin/master, specifically
commit a1af13f34de361bf9f136e2d0eb24425a4bdaf45.
On Tue, 13 Feb 2018, Julius Schmidt wrote:
Sorry, forgot to mention this crucial little detail: It happens on "Edit
Symbol Library Links".
On Tue, 13 Feb 2018, Julius Schmidt
You also forgot the part about version info.
Den 13. feb. 2018 12.43 PM skrev "Julius Schmidt" :
> Sorry, forgot to mention this crucial little detail: It happens on "Edit
> Symbol Library Links".
>
> On Tue, 13 Feb 2018, Julius Schmidt wrote:
>
> If a component cannot be found
Sorry, forgot to mention this crucial little detail: It happens on "Edit
Symbol Library Links".
On Tue, 13 Feb 2018, Julius Schmidt wrote:
If a component cannot be found it currently generates an assertion failure in
SCH_REFERENCE::SCH_REFERENCE. It gets called by
If a component cannot be found it currently generates an assertion failure
in SCH_REFERENCE::SCH_REFERENCE. It gets called by
SCH_SHEET_PATH::GetComponents with part==NULL.
It seems to work fine on continue so maybe that assertion shouldn't check
for the part to non-null?
(I came across this
Hello All,
I have created a 6.0.0-rc1 milestone in launchpad which we can use for bugs
we want to postpone to after the 5.0.0 stable release. We can always rename
this if we don't feel the next stable release will be 6.0.0. Do we want to
use 5.1.x?
Regards
Nick Østergaard
21 matches
Mail list logo