Re: [Kicad-developers] rc2 tagged

[Carsten Schoenert]

Hi Wayne,

Am 22.05.18 um 23:06 schrieb Wayne Stambaugh:
> I forgot to push my tags last night.  I just did it so you should be 
> able to clone from rc2 now.  I would rather not move the rc2 tag commit 
> because I would have to move the KiCadVersion.cmake file changes and 
> overwrite the repo because they should be synced.
that's fine too, thanks!

-- 
Regards
Carsten

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] rc2 tagged

[Wayne Stambaugh]

Hey Carsten,

On 05/22/2018 04:40 PM, Carsten Schoenert wrote:

Hello Wayne,

Am 21.05.18 um 13:55 schrieb Wayne Stambaugh:

excellent!
But I can't find the related tag 5.0.0-rc2 in both git trees, not on
Launchpad nor on GitHub. Forgotten to push the tags also?


Ahh!  I forgot to push the tags.  I have it tagged on my system at home.
  I will push the tags tonight when I get home from work.  Sorry about that.


maybe you have forgotten again that have forgotten to push the tags. :P
I'd like to kindly remember again for the missing public tags.

It would be o.k. in my eyes if you remove your local tags and re-tag now
a recent state with '5.0.0-rc2', especially after the removing of the
FreeRouting icon and menu option in
2d812c2827d70bebd03172139226b1f839ea3577 as at least I've already picked
up that change for updating the German l10n strings of KiCad and put
this into a now accepted pull request on kicad-i18n. Thanks!



I forgot to push my tags last night.  I just did it so you should be 
able to clone from rc2 now.  I would rather not move the rc2 tag commit 
because I would have to move the KiCadVersion.cmake file changes and 
overwrite the repo because they should be synced.


Cheers,

Wayne

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] rc2 tagged

[Carsten Schoenert]

Hello Wayne,

Am 21.05.18 um 13:55 schrieb Wayne Stambaugh:
>> excellent!
>> But I can't find the related tag 5.0.0-rc2 in both git trees, not on
>> Launchpad nor on GitHub. Forgotten to push the tags also?
> 
> Ahh!  I forgot to push the tags.  I have it tagged on my system at home.
>  I will push the tags tonight when I get home from work.  Sorry about that.

maybe you have forgotten again that have forgotten to push the tags. :P
I'd like to kindly remember again for the missing public tags.

It would be o.k. in my eyes if you remove your local tags and re-tag now
a recent state with '5.0.0-rc2', especially after the removing of the
FreeRouting icon and menu option in
2d812c2827d70bebd03172139226b1f839ea3577 as at least I've already picked
up that change for updating the German l10n strings of KiCad and put
this into a now accepted pull request on kicad-i18n. Thanks!

-- 
Regards
Carsten

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] RC2 String Freeze Q

[Marco Ciampa]

On Mon, May 21, 2018 at 01:01:12PM -0400, Wayne Stambaugh wrote:
> Hi Seth,
> 
> On 5/21/2018 12:44 PM, Seth Hillbrand wrote:
> > Hi Wayne-
> > 
> > There's a couple minor differences between the strings shown the user in
> > modedit and pcbnew.  I'd like to standardize these.  This involves
> > removing a few strings from modedit and replacing them with the strings
> > from pcbnew.  This does not change anything for our translators as we
> > are only removing strings.  But I would like to check in before doing
> > this and certainly don't intend to continue picking these nits until
> > after 5 is released.
> > 
> > -S
> 
> As long as you are making string changes that that don't result in
> missing translations, I am fine with the changes.
> 
> There certainly are plenty of strings in KiCad that have the same
> meaning with slightly different wording that could use some
> housekeeping.  This would make life easier for translators but that is a
> task for v6 at this point.

From a translator perspective this, merging similar strings in different
context, is not always a good idea. Different languages may translate the
same English words differently, depending on, for example, the fact that
the subject may be male or female ...

For example, depending on the subject, in Italian the English words
"null" or "void" may be traslated as "nullo" (male) or "nulla" (female)

Gettext has a way to differentiate the same string in different context
but, unfortunatly, wxWidgets do not recognize all the gettext features
and this in particular.

So care should be used in choosing too general strings and I suggest that
the developers to be more wordy and less concise to avoid these issues.

Hope that newer versions of wxWidgets will be smarter in this respect.

Sorry for my bad English as usual.

Best regards,

--


Marco Ciampa

I know a joke about UDP, but you might not get it.



 GNU/Linux User #78271
 FSFE fellow #364




___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] RC2 String Freeze Q

[Wayne Stambaugh]

Hi Seth,

On 5/21/2018 12:44 PM, Seth Hillbrand wrote:
> ​Hi Wayne-
> 
> There's a couple minor differences between the strings shown the user in
> modedit and pcbnew.  I'd like to standardize these.  This involves
> removing a few strings from modedit and replacing them with the strings
> from pcbnew.  This does not change anything for our translators as we
> are only removing strings.  But I would like to check in before doing
> this​ and certainly don't intend to continue picking these nits until
> after 5 is released.
> 
> -S

As long as you are making string changes that that don't result in
missing translations, I am fine with the changes.

There certainly are plenty of strings in KiCad that have the same
meaning with slightly different wording that could use some
housekeeping.  This would make life easier for translators but that is a
task for v6 at this point.

Cheers,

Wayne

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] RC2 String Freeze Q

[Seth Hillbrand]

​Hi Wayne-

There's a couple minor differences between the strings shown the user in
modedit and pcbnew.  I'd like to standardize these.  This involves removing
a few strings from modedit and replacing them with the strings from
pcbnew.  This does not change anything for our translators as we are only
removing strings.  But I would like to check in before doing this​ and
certainly don't intend to continue picking these nits until after 5 is
released.

-S
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] rc2 tagged

[Wayne Stambaugh]

I hope it doesn't take more than 3 to 4 weeks to finish everything to be
ready for the stable release but this can be pushed back if necessary.

On 5/21/2018 3:31 AM, Константин Барановский wrote:
> How many time we have for updating translations of i18n and docs before
> release?
> 
> 2018-05-21 10:22 GMT+03:00 Carsten Schoenert  >:
> 
> Hello Wayne,
> 
> Am 21.05.2018 um 03:30 schrieb Wayne Stambaugh:
> > Just a quick heads up, I tagged rc2.  Hopefully the final countdown to 
> > the stable 5 release wont be quite as painful as the rc1 to rc2 cycle. 
> > Thank you to everyone for your hard work.  I cannot be express my 
> > appreciation for all that you do to make KiCad possible.
> 
> excellent!
> But I can't find the related tag 5.0.0-rc2 in both git trees, not on
> Launchpad nor on GitHub. Forgotten to push the tags also?
> 
> https://git.launchpad.net/kicad/refs/tags
> 
> https://github.com/KiCad/kicad-source-mirror/tags
> 
> 
> -- 
> Regards
> Carsten Schoenert
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> 
> Post to     : kicad-developers@lists.launchpad.net
> 
> Unsubscribe : https://launchpad.net/~kicad-developers
> 
> More help   : https://help.launchpad.net/ListHelp
> 
> 
> 
> 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] rc2 tagged

[Wayne Stambaugh]

Hey Carsten,

On 5/21/2018 3:22 AM, Carsten Schoenert wrote:
> Hello Wayne,
> 
> Am 21.05.2018 um 03:30 schrieb Wayne Stambaugh:
>> Just a quick heads up, I tagged rc2.  Hopefully the final countdown to 
>> the stable 5 release wont be quite as painful as the rc1 to rc2 cycle. 
>> Thank you to everyone for your hard work.  I cannot be express my 
>> appreciation for all that you do to make KiCad possible.
> 
> excellent!
> But I can't find the related tag 5.0.0-rc2 in both git trees, not on
> Launchpad nor on GitHub. Forgotten to push the tags also?

Ahh!  I forgot to push the tags.  I have it tagged on my system at home.
 I will push the tags tonight when I get home from work.  Sorry about that.

> 
> https://git.launchpad.net/kicad/refs/tags
> https://github.com/KiCad/kicad-source-mirror/tags
> 

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] rc2 tagged

[Константин Барановский]

How many time we have for updating translations of i18n and docs before
release?

2018-05-21 10:22 GMT+03:00 Carsten Schoenert :

> Hello Wayne,
>
> Am 21.05.2018 um 03:30 schrieb Wayne Stambaugh:
> > Just a quick heads up, I tagged rc2.  Hopefully the final countdown to
> > the stable 5 release wont be quite as painful as the rc1 to rc2 cycle.
> > Thank you to everyone for your hard work.  I cannot be express my
> > appreciation for all that you do to make KiCad possible.
>
> excellent!
> But I can't find the related tag 5.0.0-rc2 in both git trees, not on
> Launchpad nor on GitHub. Forgotten to push the tags also?
>
> https://git.launchpad.net/kicad/refs/tags
> https://github.com/KiCad/kicad-source-mirror/tags
>
> --
> Regards
> Carsten Schoenert
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] rc2 tagged

[Carsten Schoenert]

Hello Wayne,

Am 21.05.2018 um 03:30 schrieb Wayne Stambaugh:
> Just a quick heads up, I tagged rc2.  Hopefully the final countdown to 
> the stable 5 release wont be quite as painful as the rc1 to rc2 cycle. 
> Thank you to everyone for your hard work.  I cannot be express my 
> appreciation for all that you do to make KiCad possible.

excellent!
But I can't find the related tag 5.0.0-rc2 in both git trees, not on
Launchpad nor on GitHub. Forgotten to push the tags also?

https://git.launchpad.net/kicad/refs/tags
https://github.com/KiCad/kicad-source-mirror/tags

-- 
Regards
Carsten Schoenert

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] rc2 tagged

[Wayne Stambaugh]

Just a quick heads up, I tagged rc2.  Hopefully the final countdown to 
the stable 5 release wont be quite as painful as the rc1 to rc2 cycle. 
Thank you to everyone for your hard work.  I cannot be express my 
appreciation for all that you do to make KiCad possible.


I will create a blog post announcement about rc2 in a couple of days to 
give our packagers time to create rc2 packages.


This also marks the UI string freeze so no UI string changes except for 
spelling errors.  I want to be fair to our translators so we can have 
the most complete translations possible.


Let's hope it wont be too much longer until we can celebrate the stable 
5 release which has been a long time coming.


Cheers,

Wayne

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] rc2 last call

[Wayne Stambaugh]

I think we are ready to tag rc2.  I'm giving everyone another day or two 
to make any commits that contain UI string changes before I tag rc2. 
Once rc2 is tagged, no UI string changes will be allowed except for 
spelling errors.  Hopefully there are no more critical bugs and we can 
begin the countdown the stable 5 release.  Thank you everyone for your 
support in making this happen.


Cheers,

Wayne

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] rc2

[Wayne Stambaugh]

On 4/5/2018 1:35 AM, Carsten Schoenert wrote:
> Hello Wayne,
> 
> Am 03.04.2018 um 00:42 schrieb Wayne Stambaugh:
> ...
>> Please note, rc2 is going to be the UI string freeze so no UI string
>> changes other than spelling errors after rc2.  If you have any UI
>> string changes, now is the time.
> please also consider to give the l10n contributes a few days for
> reworking the strings after the rc2 tagging of the KiCad source. I'm
> terrible low on free time for this right now and mostly need a weekend
> to do some work. Thanks!
> 

Carsten,

I don't think you have anything to worry about.  rc2 will just be the UI
string freeze.  Translators will have until the stable release to update
the translations.  I'm guessing this will be a month at a minimum.

Cheers,

Wayne

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] rc2

[Carsten Schoenert]

Hello Wayne,

Am 03.04.2018 um 00:42 schrieb Wayne Stambaugh:
...
> Please note, rc2 is going to be the UI string freeze so no UI string
> changes other than spelling errors after rc2.  If you have any UI
> string changes, now is the time.
please also consider to give the l10n contributes a few days for
reworking the strings after the rc2 tagging of the KiCad source. I'm
terrible low on free time for this right now and mostly need a weekend
to do some work. Thanks!

-- 
Regards
Carsten Schoenert

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] rc2

[Rene Pöschl]

On 03/04/18 19:59, Kevin Cozens wrote:

I am seeing a problem with CvPcb where it fails to show me any DIP package
options when I select a 7400 IC on a board. I need to file a report about
the problem.


What version of the lib have you installed?

Are the footprint and symbol libs from the same version?

What is the footprint filter of the symbol?

What are the filter settings in cvpcb?


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] rc2

[Kevin Cozens]

On 2018-04-02 06:42 PM, Wayne Stambaugh wrote:

Things have quieted down quit a bit so we should be close to an rc2
release.  I saw a 3D viewer crash report but it looks like it might be a
video driver issue.  Are there any other outstanding issues we need to
fix before rc2 is tagged?


I am seeing a problem with CvPcb where it fails to show me any DIP package 
options when I select a 7400 IC on a board. I need to file a report about 
the problem.


--
Cheers!

Kevin.

http://www.ve3syb.ca/| "Nerds make the shiny things that
https://www.patreon.html/KevinCozens | distract the mouth-breathers, and
 | that's why we're powerful"
Owner of Elecraft K2 #2172   |
#include   | --Chris Hardwick

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] rc2

[jp charras]

Le 03/04/2018 à 14:06, Wayne Stambaugh a écrit :
> On 4/3/2018 7:12 AM, jp charras wrote:
>> Le 03/04/2018 à 00:42, Wayne Stambaugh a écrit :
>>> Things have quieted down quit a bit so we should be close to an rc2
>>> release.  I saw a 3D viewer crash report but it looks like it might be a
>>> video driver issue.  Are there any other outstanding issues we need to
>>> fix before rc2 is tagged?  Please note, rc2 is going to be the UI string
>>> freeze so no UI string changes other than spelling errors after rc2.  If
>>> you have any UI string changes, now is the time.  Thanks again everyone
>>> for stepping up and squashing bugs for rc2.  Hopefully, there wont be a
>>> lot of critical bugs and we can roll out v5 by the end of April.
>>>
>>> Cheers,
>>>
>>> Wayne
>>
>> I know 2 non critical bugs, but annoying bugs, in Pcbnew:
>> 1 - In GAL mode, when selecting a zone outline (for instance to edit this 
>> zone parameters), and
>> deselecting it, it is always refilled, even if no change is made.
> 
> Is there a bug report filed against this?  How much effort is required
> to fix this?  The zone should not be refilled if no changes are made.

Not yet.
(I saw that recently, when trying to understand why each time I selected a zone 
outline for edit,
the Zone settings dialog took a while to be displayed for complex zones).

I am not so familiar with events management on GAL, and I'll leave a guy who 
has a better knowledge
of this code to fix this issue.

> 
>> 2 - The Footprint Wizard Library allows downloading and using libraries on 
>> Github.
>> It works only for V4 libraries.
>> Is is no longer compatible with the V5 footprint libraries on Github.
>> It can create serious mistakes for users.
>> (Perhaps the easy way is just to disable the Github library management)
>>
> 
> Now that I think about it, what is the downside to leaving the github
> plugin support in the wizard?  Some users may still want to keep their
> personal footprint libraries on github and continue to use the plugin.

At least, the user interface for the github support in the wizard should be 
modified.
V5 footprint libraries cannot be downloaded by the wizard, only V4 version.
This is due to the way the V5 libs are managed on Github, and this way is not 
compatible with the
current wizard (and the github plugin)

It should be clear for an user the wizard can download personnal libs, but no 
longer the official
kicad libs.

-- 
Jean-Pierre CHARRAS

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] rc2

[Sergey A. Borshch]

On 03.04.2018 01:42, Wayne Stambaugh wrote:

Are there any other outstanding issues we need to
fix before rc2 is tagged?


https://bugs.launchpad.net/kicad/+bug/1678849
Today is one year since bug reported: opening eeschema in standalone mode 
ignores page layout description file setting. Changing any preference stored in 
project file causes page layout description file setting to get lost from project.


--
Regards,
  Sergey A. Borshchmailto: sb...@sourceforge.net
SB ELDI ltd. Riga, Latvia

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] rc2

[Wayne Stambaugh]

Adam,

Let's aim for some time this weekend.  If you run into issues, please
let me know and I can push it back until the macos packaging is ready.

Thanks,

Wayne

On 4/2/2018 8:22 PM, Adam Wolf wrote:
> We are making good progress on macOS packaging but are at least a few
> days away from something other folks can test.  Wanna aim for Friday for
> rc2?  It's probably a bit of a push for us Mac packagers but that's ok :)
> 
> Adam
> 
> On Mon, Apr 2, 2018, 5:43 PM Wayne Stambaugh  > wrote:
> 
> Things have quieted down quit a bit so we should be close to an rc2
> release.  I saw a 3D viewer crash report but it looks like it might be a
> video driver issue.  Are there any other outstanding issues we need to
> fix before rc2 is tagged?  Please note, rc2 is going to be the UI string
> freeze so no UI string changes other than spelling errors after rc2.  If
> you have any UI string changes, now is the time.  Thanks again everyone
> for stepping up and squashing bugs for rc2.  Hopefully, there wont be a
> lot of critical bugs and we can roll out v5 by the end of April.
> 
> Cheers,
> 
> Wayne
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@lists.launchpad.net
> 
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] rc2

[Wayne Stambaugh]

On 4/3/2018 7:12 AM, jp charras wrote:
> Le 03/04/2018 à 00:42, Wayne Stambaugh a écrit :
>> Things have quieted down quit a bit so we should be close to an rc2
>> release.  I saw a 3D viewer crash report but it looks like it might be a
>> video driver issue.  Are there any other outstanding issues we need to
>> fix before rc2 is tagged?  Please note, rc2 is going to be the UI string
>> freeze so no UI string changes other than spelling errors after rc2.  If
>> you have any UI string changes, now is the time.  Thanks again everyone
>> for stepping up and squashing bugs for rc2.  Hopefully, there wont be a
>> lot of critical bugs and we can roll out v5 by the end of April.
>>
>> Cheers,
>>
>> Wayne
> 
> I know 2 non critical bugs, but annoying bugs, in Pcbnew:
> 1 - In GAL mode, when selecting a zone outline (for instance to edit this 
> zone parameters), and
> deselecting it, it is always refilled, even if no change is made.

Is there a bug report filed against this?  How much effort is required
to fix this?  The zone should not be refilled if no changes are made.

> 2 - The Footprint Wizard Library allows downloading and using libraries on 
> Github.
> It works only for V4 libraries.
> Is is no longer compatible with the V5 footprint libraries on Github.
> It can create serious mistakes for users.
> (Perhaps the easy way is just to disable the Github library management)
> 

Now that I think about it, what is the downside to leaving the github
plugin support in the wizard?  Some users may still want to keep their
personal footprint libraries on github and continue to use the plugin.

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] rc2

[Wayne Stambaugh]

On 4/3/2018 7:33 AM, jp charras wrote:
> Le 03/04/2018 à 13:25, Maciej Sumiński a écrit :
>> On 04/03/2018 01:20 PM, Tomasz Wlostowski wrote:
>>> On 03/04/18 13:17, Nick Østergaard wrote:
 I think we should not disable the github plugin, but we may need to
 remove it from the wizard in a way that does not emphasize that this is
 the way to go. Maybe it is ok to remove it completely from the wizard,
 but just let the plugin in the fp-lib-table still work.
>>>
>>> I would rather disable it (with the possibility to re-enable in some
>>> config file for "hardcore" users). Over the last 3 years it brought us
>>> mostly troubles and no big advantage.
>>
>> I second that, the only potential issue we need to deal with is the
>> current plugin users. Once we remove the plugin, they will be stuck with
>> footprint libraries full of broken entries.
>>
>> For v6 we should simply provide a simple library updater taking
>> advantage of generic git interface (e.g. libgit), instead of tying
>> ourselves to Github.
>>
>> Cheers,
>> Orson
> 
> For V5, I was just talking about disabling github option in wizard only to 
> avoid issue.
> The github plugin is an other story.

Please disable it in the wizard only to prevent users from using the
legacy libraries.  Disabling the plugin completely will break existing
users fp-lib-table entries which is not acceptable.  Until we can
provide some type of migration tool, we will have to leave the github
plugin enabled.  Hopefully over time, users will slowly migrate away
from using the github plugin.

> 
> In V6, we will need a library updater for symbol libs, footprint libs, 3d 
> shapes libs, and perhaps
> some other things (python scripts for instance)
> 
> 

Maybe someone could create a git plugin to manage updating libraries.

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] rc2

[jp charras]

Le 03/04/2018 à 13:25, Maciej Sumiński a écrit :
> On 04/03/2018 01:20 PM, Tomasz Wlostowski wrote:
>> On 03/04/18 13:17, Nick Østergaard wrote:
>>> I think we should not disable the github plugin, but we may need to
>>> remove it from the wizard in a way that does not emphasize that this is
>>> the way to go. Maybe it is ok to remove it completely from the wizard,
>>> but just let the plugin in the fp-lib-table still work.
>>
>> I would rather disable it (with the possibility to re-enable in some
>> config file for "hardcore" users). Over the last 3 years it brought us
>> mostly troubles and no big advantage.
> 
> I second that, the only potential issue we need to deal with is the
> current plugin users. Once we remove the plugin, they will be stuck with
> footprint libraries full of broken entries.
> 
> For v6 we should simply provide a simple library updater taking
> advantage of generic git interface (e.g. libgit), instead of tying
> ourselves to Github.
> 
> Cheers,
> Orson

For V5, I was just talking about disabling github option in wizard only to 
avoid issue.
The github plugin is an other story.

In V6, we will need a library updater for symbol libs, footprint libs, 3d 
shapes libs, and perhaps
some other things (python scripts for instance)


-- 
Jean-Pierre CHARRAS

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] rc2

[Maciej Sumiński]

On 04/03/2018 01:20 PM, Tomasz Wlostowski wrote:
> On 03/04/18 13:17, Nick Østergaard wrote:
>> I think we should not disable the github plugin, but we may need to
>> remove it from the wizard in a way that does not emphasize that this is
>> the way to go. Maybe it is ok to remove it completely from the wizard,
>> but just let the plugin in the fp-lib-table still work.
> 
> I would rather disable it (with the possibility to re-enable in some
> config file for "hardcore" users). Over the last 3 years it brought us
> mostly troubles and no big advantage.

I second that, the only potential issue we need to deal with is the
current plugin users. Once we remove the plugin, they will be stuck with
footprint libraries full of broken entries.

For v6 we should simply provide a simple library updater taking
advantage of generic git interface (e.g. libgit), instead of tying
ourselves to Github.

Cheers,
Orson



signature.asc
Description: OpenPGP digital signature
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] rc2

[Tomasz Wlostowski]

On 03/04/18 13:17, Nick Østergaard wrote:
> I think we should not disable the github plugin, but we may need to
> remove it from the wizard in a way that does not emphasize that this is
> the way to go. Maybe it is ok to remove it completely from the wizard,
> but just let the plugin in the fp-lib-table still work.

I would rather disable it (with the possibility to re-enable in some
config file for "hardcore" users). Over the last 3 years it brought us
mostly troubles and no big advantage.

Tom

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] rc2

[Nick Østergaard]

2018-04-03 13:12 GMT+02:00 jp charras :

> Le 03/04/2018 à 00:42, Wayne Stambaugh a écrit :
> > Things have quieted down quit a bit so we should be close to an rc2
> > release.  I saw a 3D viewer crash report but it looks like it might be a
> > video driver issue.  Are there any other outstanding issues we need to
> > fix before rc2 is tagged?  Please note, rc2 is going to be the UI string
> > freeze so no UI string changes other than spelling errors after rc2.  If
> > you have any UI string changes, now is the time.  Thanks again everyone
> > for stepping up and squashing bugs for rc2.  Hopefully, there wont be a
> > lot of critical bugs and we can roll out v5 by the end of April.
> >
> > Cheers,
> >
> > Wayne
>
> I know 2 non critical bugs, but annoying bugs, in Pcbnew:
> 1 - In GAL mode, when selecting a zone outline (for instance to edit this
> zone parameters), and
> deselecting it, it is always refilled, even if no change is made.
> 2 - The Footprint Wizard Library allows downloading and using libraries on
> Github.
> It works only for V4 libraries.
> Is is no longer compatible with the V5 footprint libraries on Github.
> It can create serious mistakes for users.
> (Perhaps the easy way is just to disable the Github library management)
>
>
> I think we should not disable the github plugin, but we may need to remove
it from the wizard in a way that does not emphasize that this is the way to
go. Maybe it is ok to remove it completely from the wizard, but just let
the plugin in the fp-lib-table still work.
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] rc2

[jp charras]

Le 03/04/2018 à 00:42, Wayne Stambaugh a écrit :
> Things have quieted down quit a bit so we should be close to an rc2
> release.  I saw a 3D viewer crash report but it looks like it might be a
> video driver issue.  Are there any other outstanding issues we need to
> fix before rc2 is tagged?  Please note, rc2 is going to be the UI string
> freeze so no UI string changes other than spelling errors after rc2.  If
> you have any UI string changes, now is the time.  Thanks again everyone
> for stepping up and squashing bugs for rc2.  Hopefully, there wont be a
> lot of critical bugs and we can roll out v5 by the end of April.
> 
> Cheers,
> 
> Wayne

I know 2 non critical bugs, but annoying bugs, in Pcbnew:
1 - In GAL mode, when selecting a zone outline (for instance to edit this zone 
parameters), and
deselecting it, it is always refilled, even if no change is made.
2 - The Footprint Wizard Library allows downloading and using libraries on 
Github.
It works only for V4 libraries.
Is is no longer compatible with the V5 footprint libraries on Github.
It can create serious mistakes for users.
(Perhaps the easy way is just to disable the Github library management)

-- 
Jean-Pierre CHARRAS

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] rc2

[Adam Wolf]

We are making good progress on macOS packaging but are at least a few days
away from something other folks can test.  Wanna aim for Friday for rc2?
It's probably a bit of a push for us Mac packagers but that's ok :)

Adam

On Mon, Apr 2, 2018, 5:43 PM Wayne Stambaugh  wrote:

> Things have quieted down quit a bit so we should be close to an rc2
> release.  I saw a 3D viewer crash report but it looks like it might be a
> video driver issue.  Are there any other outstanding issues we need to
> fix before rc2 is tagged?  Please note, rc2 is going to be the UI string
> freeze so no UI string changes other than spelling errors after rc2.  If
> you have any UI string changes, now is the time.  Thanks again everyone
> for stepping up and squashing bugs for rc2.  Hopefully, there wont be a
> lot of critical bugs and we can roll out v5 by the end of April.
>
> Cheers,
>
> Wayne
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] rc2

[Wayne Stambaugh]

Things have quieted down quit a bit so we should be close to an rc2
release.  I saw a 3D viewer crash report but it looks like it might be a
video driver issue.  Are there any other outstanding issues we need to
fix before rc2 is tagged?  Please note, rc2 is going to be the UI string
freeze so no UI string changes other than spelling errors after rc2.  If
you have any UI string changes, now is the time.  Thanks again everyone
for stepping up and squashing bugs for rc2.  Hopefully, there wont be a
lot of critical bugs and we can roll out v5 by the end of April.

Cheers,

Wayne

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] RC2 has been released.

[Wayne Stambaugh]

Thanks.  I'll take a look at it as soon as I get a chance.

On 11/9/2015 7:29 AM, Brian Sidebotham wrote:
> Wayne, You've released the source tarball against the RC1 milestone.
> I'd delete it from there and re-release it against the RC2 milestone.
> 
> Best Regards,
> 
> Brian.
> 
> On 9 November 2015 at 08:17, Nick Østergaard  wrote:
>> I just jumped directly to https://launchpad.net/kicad  and hovering on
>> the download links on the right you can see those links.
>>
>> 2015-11-09 2:37 GMT+01:00 Wayne Stambaugh :
>>> That is strange.  I wonder if the path has something to do with what
>>> page is open when you upload it.  As long as users can download the file
>>> it should be OK.  If I get some time, I'll mess around with it and see
>>> if I can get it in the https://launchpad.net/kicad/4.0 path.
>>>
>>> On 11/8/2015 6:01 PM, Nick Østergaard wrote:
 Hi Wayne

 Thank you for realasing. Although the download link is a bit strange..
 it still partly refers to rc1.

 https://launchpad.net/kicad/4.0/4.0.0-rc1/+download/kicad-4.0.0-rc2.tar.xz

 But anyway, I guess we can just say that the docs, and their
 translations, and the GUI translations shall be done in two weeks if
 they want to be included with the release. The same witht he libs, if
 anything is is left to be done, and we can just take a snapshot of the
 libs and put it on the download page.

 2015-11-08 23:11 GMT+01:00 Wayne Stambaugh :
> I just finished up getting all of the relevant code for RC2 uploaded to
> launchpad so let's fire up those autobuilders and get some rc2 packages
> out there for testing.  I'm hoping this will be the last rc before the
> stable release.  Let's keep our fingers crossed.  We need start thinking
> about branching or tagging the library, documentation, and translation
> repos so that packagers can build consistent packages for their
> respective platforms.  Thanks to everyone who made this possible.  I'm
> going to step away from my computer for a while and enjoy the adult
> beverage of my choice.
>
> Cheers,
>
> Wayne
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>>>
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] RC2 has been released.

[Wayne Stambaugh]

On 11/8/2015 6:01 PM, Nick Østergaard wrote:
> Hi Wayne
> 
> Thank you for realasing. Although the download link is a bit strange..
> it still partly refers to rc1.
> 
> https://launchpad.net/kicad/4.0/4.0.0-rc1/+download/kicad-4.0.0-rc2.tar.xz
> 
> But anyway, I guess we can just say that the docs, and their
> translations, and the GUI translations shall be done in two weeks if
> they want to be included with the release. The same witht he libs, if
> anything is is left to be done, and we can just take a snapshot of the
> libs and put it on the download page.

I'm wondering if we should branch the translation and doc repos.  Once
new features and strings are added to kicad during the next development
cycle, updating the translation and doc repos will not make sense
against the 4.0 stable release of kicad.  Creating 4.0 branches of the
doc and translation repos would allow for new translations and improved
documentation for the 4.0 stable release.  There would be some
cross-over between the 4.0 and development repos which would be a bit
more work.  I'm OK with tagging the current repos as well.  The downside
to that is there will be no new translations or doc improvements until
the next stable release.  I'll leave that up to the doc and translation
folks.  Tagging and a snapshot archive makes sense for the lib repo.

> 
> 2015-11-08 23:11 GMT+01:00 Wayne Stambaugh :
>> I just finished up getting all of the relevant code for RC2 uploaded to
>> launchpad so let's fire up those autobuilders and get some rc2 packages
>> out there for testing.  I'm hoping this will be the last rc before the
>> stable release.  Let's keep our fingers crossed.  We need start thinking
>> about branching or tagging the library, documentation, and translation
>> repos so that packagers can build consistent packages for their
>> respective platforms.  Thanks to everyone who made this possible.  I'm
>> going to step away from my computer for a while and enjoy the adult
>> beverage of my choice.
>>
>> Cheers,
>>
>> Wayne
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] RC2 has been released.

[Brian Sidebotham]

Wayne, You've released the source tarball against the RC1 milestone.
I'd delete it from there and re-release it against the RC2 milestone.

Best Regards,

Brian.

On 9 November 2015 at 08:17, Nick Østergaard  wrote:
> I just jumped directly to https://launchpad.net/kicad  and hovering on
> the download links on the right you can see those links.
>
> 2015-11-09 2:37 GMT+01:00 Wayne Stambaugh :
>> That is strange.  I wonder if the path has something to do with what
>> page is open when you upload it.  As long as users can download the file
>> it should be OK.  If I get some time, I'll mess around with it and see
>> if I can get it in the https://launchpad.net/kicad/4.0 path.
>>
>> On 11/8/2015 6:01 PM, Nick Østergaard wrote:
>>> Hi Wayne
>>>
>>> Thank you for realasing. Although the download link is a bit strange..
>>> it still partly refers to rc1.
>>>
>>> https://launchpad.net/kicad/4.0/4.0.0-rc1/+download/kicad-4.0.0-rc2.tar.xz
>>>
>>> But anyway, I guess we can just say that the docs, and their
>>> translations, and the GUI translations shall be done in two weeks if
>>> they want to be included with the release. The same witht he libs, if
>>> anything is is left to be done, and we can just take a snapshot of the
>>> libs and put it on the download page.
>>>
>>> 2015-11-08 23:11 GMT+01:00 Wayne Stambaugh :
 I just finished up getting all of the relevant code for RC2 uploaded to
 launchpad so let's fire up those autobuilders and get some rc2 packages
 out there for testing.  I'm hoping this will be the last rc before the
 stable release.  Let's keep our fingers crossed.  We need start thinking
 about branching or tagging the library, documentation, and translation
 repos so that packagers can build consistent packages for their
 respective platforms.  Thanks to everyone who made this possible.  I'm
 going to step away from my computer for a while and enjoy the adult
 beverage of my choice.

 Cheers,

 Wayne

 ___
 Mailing list: https://launchpad.net/~kicad-developers
 Post to : kicad-developers@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~kicad-developers
 More help   : https://help.launchpad.net/ListHelp
>>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] RC2 has been released.

[Nick Østergaard]

2015-11-09 14:54 GMT+01:00 Wayne Stambaugh :
> On 11/8/2015 6:01 PM, Nick Østergaard wrote:
>> Hi Wayne
>>
>> Thank you for realasing. Although the download link is a bit strange..
>> it still partly refers to rc1.
>>
>> https://launchpad.net/kicad/4.0/4.0.0-rc1/+download/kicad-4.0.0-rc2.tar.xz
>>
>> But anyway, I guess we can just say that the docs, and their
>> translations, and the GUI translations shall be done in two weeks if
>> they want to be included with the release. The same witht he libs, if
>> anything is is left to be done, and we can just take a snapshot of the
>> libs and put it on the download page.
>
> I'm wondering if we should branch the translation and doc repos.  Once
> new features and strings are added to kicad during the next development
> cycle, updating the translation and doc repos will not make sense
> against the 4.0 stable release of kicad.  Creating 4.0 branches of the
> doc and translation repos would allow for new translations and improved
> documentation for the 4.0 stable release.  There would be some
> cross-over between the 4.0 and development repos which would be a bit
> more work.  I'm OK with tagging the current repos as well.  The downside
> to that is there will be no new translations or doc improvements until
> the next stable release.  I'll leave that up to the doc and translation
> folks.  Tagging and a snapshot archive makes sense for the lib repo.

I think just tagging it should be sufficient to generate a release
tarball on github (4.0.0.0). If we need followup changes we can make a
leaf branch from there or later on the master branch with 4.0.0.1. I
don't think -n is good here, because multiple packaging systems use a
dash number notation to describe revisions of the packaging scripts
themselves. The triplet is reserved to the kicad source, so we must
need some other indicator for auxiliary stuff. But we really need to
align the version numbers across the source code, docs, translations
and libs.

>> 2015-11-08 23:11 GMT+01:00 Wayne Stambaugh :
>>> I just finished up getting all of the relevant code for RC2 uploaded to
>>> launchpad so let's fire up those autobuilders and get some rc2 packages
>>> out there for testing.  I'm hoping this will be the last rc before the
>>> stable release.  Let's keep our fingers crossed.  We need start thinking
>>> about branching or tagging the library, documentation, and translation
>>> repos so that packagers can build consistent packages for their
>>> respective platforms.  Thanks to everyone who made this possible.  I'm
>>> going to step away from my computer for a while and enjoy the adult
>>> beverage of my choice.
>>>
>>> Cheers,
>>>
>>> Wayne
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to : kicad-developers@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : https://help.launchpad.net/ListHelp
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] RC2 has been released.

[Wayne Stambaugh]

No hurry.  Just something to think about before the stable release.  Thanks.

On 11/9/2015 4:26 PM, Nick Østergaard wrote:
> Yes, this can be done very easily. There is already binaries on
> http://docs.kicad-pcb.org/ that can be downloaded as a zip or tar.gz
> file. I might try to tage some with an rc2 tag to prepare everything
> and every packager. I forgot to do that, but probably tomorrow.
> 
> 2015-11-09 22:23 GMT+01:00 Wayne Stambaugh :
>>
>>
>> On 11/9/2015 9:13 AM, Nick Østergaard wrote:
>>> 2015-11-09 14:54 GMT+01:00 Wayne Stambaugh :
 On 11/8/2015 6:01 PM, Nick Østergaard wrote:
> Hi Wayne
>
> Thank you for realasing. Although the download link is a bit strange..
> it still partly refers to rc1.
>
> https://launchpad.net/kicad/4.0/4.0.0-rc1/+download/kicad-4.0.0-rc2.tar.xz
>
> But anyway, I guess we can just say that the docs, and their
> translations, and the GUI translations shall be done in two weeks if
> they want to be included with the release. The same witht he libs, if
> anything is is left to be done, and we can just take a snapshot of the
> libs and put it on the download page.

 I'm wondering if we should branch the translation and doc repos.  Once
 new features and strings are added to kicad during the next development
 cycle, updating the translation and doc repos will not make sense
 against the 4.0 stable release of kicad.  Creating 4.0 branches of the
 doc and translation repos would allow for new translations and improved
 documentation for the 4.0 stable release.  There would be some
 cross-over between the 4.0 and development repos which would be a bit
 more work.  I'm OK with tagging the current repos as well.  The downside
 to that is there will be no new translations or doc improvements until
 the next stable release.  I'll leave that up to the doc and translation
 folks.  Tagging and a snapshot archive makes sense for the lib repo.
>>>
>>> I think just tagging it should be sufficient to generate a release
>>> tarball on github (4.0.0.0). If we need followup changes we can make a
>>> leaf branch from there or later on the master branch with 4.0.0.1. I
>>> don't think -n is good here, because multiple packaging systems use a
>>> dash number notation to describe revisions of the packaging scripts
>>> themselves. The triplet is reserved to the kicad source, so we must
>>> need some other indicator for auxiliary stuff. But we really need to
>>> align the version numbers across the source code, docs, translations
>>> and libs.
>>
>> I just thought of something.  We will need a way to fetch the built
>> documentation for packaging on platforms that don't have the native
>> tools to build the docs from source.  I still have not had any success
>> building the docs from source on windows.  This means that if we do tag
>> the doc repo rather than branch it, we will need to be able provide
>> builds from the tagged version of at least the pdf files for all
>> languages.  I'm assuming this can be done.  If not, we will have to find
>> alternative.
>>
>>>
> 2015-11-08 23:11 GMT+01:00 Wayne Stambaugh :
>> I just finished up getting all of the relevant code for RC2 uploaded to
>> launchpad so let's fire up those autobuilders and get some rc2 packages
>> out there for testing.  I'm hoping this will be the last rc before the
>> stable release.  Let's keep our fingers crossed.  We need start thinking
>> about branching or tagging the library, documentation, and translation
>> repos so that packagers can build consistent packages for their
>> respective platforms.  Thanks to everyone who made this possible.  I'm
>> going to step away from my computer for a while and enjoy the adult
>> beverage of my choice.
>>
>> Cheers,
>>
>> Wayne
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp

 ___
 Mailing list: https://launchpad.net/~kicad-developers
 Post to : kicad-developers@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~kicad-developers
 More help   : https://help.launchpad.net/ListHelp
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : 

Re: [Kicad-developers] RC2 has been released.

[Nick Østergaard]

Yes, this can be done very easily. There is already binaries on
http://docs.kicad-pcb.org/ that can be downloaded as a zip or tar.gz
file. I might try to tage some with an rc2 tag to prepare everything
and every packager. I forgot to do that, but probably tomorrow.

2015-11-09 22:23 GMT+01:00 Wayne Stambaugh :
>
>
> On 11/9/2015 9:13 AM, Nick Østergaard wrote:
>> 2015-11-09 14:54 GMT+01:00 Wayne Stambaugh :
>>> On 11/8/2015 6:01 PM, Nick Østergaard wrote:
 Hi Wayne

 Thank you for realasing. Although the download link is a bit strange..
 it still partly refers to rc1.

 https://launchpad.net/kicad/4.0/4.0.0-rc1/+download/kicad-4.0.0-rc2.tar.xz

 But anyway, I guess we can just say that the docs, and their
 translations, and the GUI translations shall be done in two weeks if
 they want to be included with the release. The same witht he libs, if
 anything is is left to be done, and we can just take a snapshot of the
 libs and put it on the download page.
>>>
>>> I'm wondering if we should branch the translation and doc repos.  Once
>>> new features and strings are added to kicad during the next development
>>> cycle, updating the translation and doc repos will not make sense
>>> against the 4.0 stable release of kicad.  Creating 4.0 branches of the
>>> doc and translation repos would allow for new translations and improved
>>> documentation for the 4.0 stable release.  There would be some
>>> cross-over between the 4.0 and development repos which would be a bit
>>> more work.  I'm OK with tagging the current repos as well.  The downside
>>> to that is there will be no new translations or doc improvements until
>>> the next stable release.  I'll leave that up to the doc and translation
>>> folks.  Tagging and a snapshot archive makes sense for the lib repo.
>>
>> I think just tagging it should be sufficient to generate a release
>> tarball on github (4.0.0.0). If we need followup changes we can make a
>> leaf branch from there or later on the master branch with 4.0.0.1. I
>> don't think -n is good here, because multiple packaging systems use a
>> dash number notation to describe revisions of the packaging scripts
>> themselves. The triplet is reserved to the kicad source, so we must
>> need some other indicator for auxiliary stuff. But we really need to
>> align the version numbers across the source code, docs, translations
>> and libs.
>
> I just thought of something.  We will need a way to fetch the built
> documentation for packaging on platforms that don't have the native
> tools to build the docs from source.  I still have not had any success
> building the docs from source on windows.  This means that if we do tag
> the doc repo rather than branch it, we will need to be able provide
> builds from the tagged version of at least the pdf files for all
> languages.  I'm assuming this can be done.  If not, we will have to find
> alternative.
>
>>
 2015-11-08 23:11 GMT+01:00 Wayne Stambaugh :
> I just finished up getting all of the relevant code for RC2 uploaded to
> launchpad so let's fire up those autobuilders and get some rc2 packages
> out there for testing.  I'm hoping this will be the last rc before the
> stable release.  Let's keep our fingers crossed.  We need start thinking
> about branching or tagging the library, documentation, and translation
> repos so that packagers can build consistent packages for their
> respective platforms.  Thanks to everyone who made this possible.  I'm
> going to step away from my computer for a while and enjoy the adult
> beverage of my choice.
>
> Cheers,
>
> Wayne
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to : kicad-developers@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : https://help.launchpad.net/ListHelp
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] RC2 has been released.

[Wayne Stambaugh]

On 11/9/2015 9:13 AM, Nick Østergaard wrote:
> 2015-11-09 14:54 GMT+01:00 Wayne Stambaugh :
>> On 11/8/2015 6:01 PM, Nick Østergaard wrote:
>>> Hi Wayne
>>>
>>> Thank you for realasing. Although the download link is a bit strange..
>>> it still partly refers to rc1.
>>>
>>> https://launchpad.net/kicad/4.0/4.0.0-rc1/+download/kicad-4.0.0-rc2.tar.xz
>>>
>>> But anyway, I guess we can just say that the docs, and their
>>> translations, and the GUI translations shall be done in two weeks if
>>> they want to be included with the release. The same witht he libs, if
>>> anything is is left to be done, and we can just take a snapshot of the
>>> libs and put it on the download page.
>>
>> I'm wondering if we should branch the translation and doc repos.  Once
>> new features and strings are added to kicad during the next development
>> cycle, updating the translation and doc repos will not make sense
>> against the 4.0 stable release of kicad.  Creating 4.0 branches of the
>> doc and translation repos would allow for new translations and improved
>> documentation for the 4.0 stable release.  There would be some
>> cross-over between the 4.0 and development repos which would be a bit
>> more work.  I'm OK with tagging the current repos as well.  The downside
>> to that is there will be no new translations or doc improvements until
>> the next stable release.  I'll leave that up to the doc and translation
>> folks.  Tagging and a snapshot archive makes sense for the lib repo.
> 
> I think just tagging it should be sufficient to generate a release
> tarball on github (4.0.0.0). If we need followup changes we can make a
> leaf branch from there or later on the master branch with 4.0.0.1. I
> don't think -n is good here, because multiple packaging systems use a
> dash number notation to describe revisions of the packaging scripts
> themselves. The triplet is reserved to the kicad source, so we must
> need some other indicator for auxiliary stuff. But we really need to
> align the version numbers across the source code, docs, translations
> and libs.

I just thought of something.  We will need a way to fetch the built
documentation for packaging on platforms that don't have the native
tools to build the docs from source.  I still have not had any success
building the docs from source on windows.  This means that if we do tag
the doc repo rather than branch it, we will need to be able provide
builds from the tagged version of at least the pdf files for all
languages.  I'm assuming this can be done.  If not, we will have to find
alternative.

> 
>>> 2015-11-08 23:11 GMT+01:00 Wayne Stambaugh :
 I just finished up getting all of the relevant code for RC2 uploaded to
 launchpad so let's fire up those autobuilders and get some rc2 packages
 out there for testing.  I'm hoping this will be the last rc before the
 stable release.  Let's keep our fingers crossed.  We need start thinking
 about branching or tagging the library, documentation, and translation
 repos so that packagers can build consistent packages for their
 respective platforms.  Thanks to everyone who made this possible.  I'm
 going to step away from my computer for a while and enjoy the adult
 beverage of my choice.

 Cheers,

 Wayne

 ___
 Mailing list: https://launchpad.net/~kicad-developers
 Post to : kicad-developers@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~kicad-developers
 More help   : https://help.launchpad.net/ListHelp
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] RC2 has been released.

[Wayne Stambaugh]

This should be correct now.  Thanks for the heads up.

On 11/9/2015 7:29 AM, Brian Sidebotham wrote:
> Wayne, You've released the source tarball against the RC1 milestone.
> I'd delete it from there and re-release it against the RC2 milestone.
> 
> Best Regards,
> 
> Brian.
> 
> On 9 November 2015 at 08:17, Nick Østergaard  wrote:
>> I just jumped directly to https://launchpad.net/kicad  and hovering on
>> the download links on the right you can see those links.
>>
>> 2015-11-09 2:37 GMT+01:00 Wayne Stambaugh :
>>> That is strange.  I wonder if the path has something to do with what
>>> page is open when you upload it.  As long as users can download the file
>>> it should be OK.  If I get some time, I'll mess around with it and see
>>> if I can get it in the https://launchpad.net/kicad/4.0 path.
>>>
>>> On 11/8/2015 6:01 PM, Nick Østergaard wrote:
 Hi Wayne

 Thank you for realasing. Although the download link is a bit strange..
 it still partly refers to rc1.

 https://launchpad.net/kicad/4.0/4.0.0-rc1/+download/kicad-4.0.0-rc2.tar.xz

 But anyway, I guess we can just say that the docs, and their
 translations, and the GUI translations shall be done in two weeks if
 they want to be included with the release. The same witht he libs, if
 anything is is left to be done, and we can just take a snapshot of the
 libs and put it on the download page.

 2015-11-08 23:11 GMT+01:00 Wayne Stambaugh :
> I just finished up getting all of the relevant code for RC2 uploaded to
> launchpad so let's fire up those autobuilders and get some rc2 packages
> out there for testing.  I'm hoping this will be the last rc before the
> stable release.  Let's keep our fingers crossed.  We need start thinking
> about branching or tagging the library, documentation, and translation
> repos so that packagers can build consistent packages for their
> respective platforms.  Thanks to everyone who made this possible.  I'm
> going to step away from my computer for a while and enjoy the adult
> beverage of my choice.
>
> Cheers,
>
> Wayne
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>>>
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] RC2 has been released.

[Nick Østergaard]

I just jumped directly to https://launchpad.net/kicad  and hovering on
the download links on the right you can see those links.

2015-11-09 2:37 GMT+01:00 Wayne Stambaugh :
> That is strange.  I wonder if the path has something to do with what
> page is open when you upload it.  As long as users can download the file
> it should be OK.  If I get some time, I'll mess around with it and see
> if I can get it in the https://launchpad.net/kicad/4.0 path.
>
> On 11/8/2015 6:01 PM, Nick Østergaard wrote:
>> Hi Wayne
>>
>> Thank you for realasing. Although the download link is a bit strange..
>> it still partly refers to rc1.
>>
>> https://launchpad.net/kicad/4.0/4.0.0-rc1/+download/kicad-4.0.0-rc2.tar.xz
>>
>> But anyway, I guess we can just say that the docs, and their
>> translations, and the GUI translations shall be done in two weeks if
>> they want to be included with the release. The same witht he libs, if
>> anything is is left to be done, and we can just take a snapshot of the
>> libs and put it on the download page.
>>
>> 2015-11-08 23:11 GMT+01:00 Wayne Stambaugh :
>>> I just finished up getting all of the relevant code for RC2 uploaded to
>>> launchpad so let's fire up those autobuilders and get some rc2 packages
>>> out there for testing.  I'm hoping this will be the last rc before the
>>> stable release.  Let's keep our fingers crossed.  We need start thinking
>>> about branching or tagging the library, documentation, and translation
>>> repos so that packagers can build consistent packages for their
>>> respective platforms.  Thanks to everyone who made this possible.  I'm
>>> going to step away from my computer for a while and enjoy the adult
>>> beverage of my choice.
>>>
>>> Cheers,
>>>
>>> Wayne
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to : kicad-developers@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : https://help.launchpad.net/ListHelp
>

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] RC2

[Nick Østergaard]

Hi Wayne

Will we have an RC2 this weekend?

Since the issue reported by Andrew can not be reproduced by anyone
anymore, I guess we can disreagard this.

But what about the warnings reported by Mark? I personally don't think
theese should block RC2, they are afterall warnings, and there is
still time to fix them before the stable release.

Nick

2015-11-08 1:12 GMT+01:00 Andrew Zonenberg :
>
> Confirmed to warn, but not crash, in r6302. Guess somebody fixed it
> already.
>
> On 07/11/15 13:04, Wayne Stambaugh wrote:
>> On 11/06/2015 12:25 PM, Andrew Zonenberg wrote:
>>> There's another bug I spent a while hunting for earlier this
>>> week, but couldn't get too far with. Maybe someone else can pick
>>> it up?
>>>
>>> Steps to reproduce: * Open pad editor * Select pad type: SMT *
>>> Select copper layers: none * Uncheck all technical layers
>>>
>>> In the debug build this will display a warning but keep running;
>>> in release it aborts or crashes.
>>>
>>> Although *exiting* the pad editor should not be allowed if the
>>> pad has no layers at all (or possibly pop up a dialog asking if
>>> the user wants to delete it?), having no layers selected should
>>> be a legal intermediate state during editing of a pad stack.
>>
>> I cannot even exit the pad properties dialog using the OK button.
>> I keep getting an error message dialog "Error: no layer selected."
>> every time I hit the OK button.  I'm using r6302 on Debian testing
>> amd64 build.
>>
>>>
>>> On 06/11/15 09:04, Mark Roszko wrote:
 One thing I didn't think was fixed yet was a null dereference
 introduced with the clipper library upgrade. jp fixed the
 uninitialized warnings but theres still a explicit null deref
 in a loop condition. CID 132144. What does it impact? No clue.
>>>
 And speaking of pns, there is still CID 106401 where
 PNS_MEANDERED_LINE::MeanderSegment can memory leak.

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] RC2 has been released.

[Adam Wolf]

Good work team!

I'll cut an RC2 package for OS X.  All I will change is the text in the
Readme.

Adam Wolf
Cofounder and Engineer
W
On Nov 8, 2015 4:29 PM, "Wayne Stambaugh"  wrote:

> I just finished up getting all of the relevant code for RC2 uploaded to
> launchpad so let's fire up those autobuilders and get some rc2 packages
> out there for testing.  I'm hoping this will be the last rc before the
> stable release.  Let's keep our fingers crossed.  We need start thinking
> about branching or tagging the library, documentation, and translation
> repos so that packagers can build consistent packages for their
> respective platforms.  Thanks to everyone who made this possible.  I'm
> going to step away from my computer for a while and enjoy the adult
> beverage of my choice.
>
> Cheers,
>
> Wayne
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] RC2

[Aljaž Srebrnič]

Good work everyone!
Is the rc2 stable enough to include it in MacPorts, or it is better if I wait 
for the official 4.0.0 release?

Thanks,
Aljaž

On 8 novembre 2015 at 21:48:03, Wayne Stambaugh (stambau...@gmail.com) wrote:

Hey Nick,

I just merged lp:kicad into the 4.0 branch and it's in the process of
building now. If all goes well which it should, I'll tag it as rc2 and
commit it. I'll also create a new archive and md5sum and upload them to
Launchpad. Hopefully I'll get this done this evening. If not, I'll
finish up some time tomorrow.

Wayne
--
Aljaž Srebrnič a.k.a g5pw
My public key:  http://bit.ly/g5pw_pubkey___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] RC2

[Bernhard Stegmaier]

Hi,

just out of curiosity… why/how would you want to put it into MacPorts?
IMHO there is really no need to build it via MacPorts, especially due to the 
special patched wxWidgets libraries which are not available in MacPorts anyway.
Downloading ready-made .dmg images from the website is probably much more easy 
than installing via Macports… (and, it doesn’t add another build variant to 
support/maintain).


Regards,
Bernhard

> On 08.11.2015, at 21:50, Aljaž Srebrnič  wrote:
> 
> Good work everyone!
> Is the rc2 stable enough to include it in MacPorts, or it is better if I wait 
> for the official 4.0.0 release?
> 
> Thanks,
> Aljaž
> 
> On 8 novembre 2015 at 21:48:03, Wayne Stambaugh (stambau...@gmail.com 
> ) wrote:
> 
>> Hey Nick,
>> 
>> I just merged lp:kicad into the 4.0 branch and it's in the process of
>> building now. If all goes well which it should, I'll tag it as rc2 and
>> commit it. I'll also create a new archive and md5sum and upload them to
>> Launchpad. Hopefully I'll get this done this evening. If not, I'll
>> finish up some time tomorrow 
>> .
>> 
>> Wayne
> --
> Aljaž Srebrnič a.k.a g5pw
> My public key:  http://bit.ly/g5pw_pubkey 
> ___
> Mailing list: https://launchpad.net/~kicad-developers 
> 
> Post to : kicad-developers@lists.launchpad.net 
> 
> Unsubscribe : https://launchpad.net/~kicad-developers 
> 
> More help   : https://help.launchpad.net/ListHelp 
> 
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] RC2

[Adam Wolf]

Regarding new packaging, please oboy get things ready.  We have already had
some user confusion on if 4.0.0 is already out yet or not.

It won't be long!

Thanks!
On Nov 8, 2015 2:57 PM, "Bernhard Stegmaier" 
wrote:

> Hi,
>
> just out of curiosity… why/how would you want to put it into MacPorts?
> IMHO there is really no need to build it via MacPorts, especially due to
> the special patched wxWidgets libraries which are not available in MacPorts
> anyway.
> Downloading ready-made .dmg images from the website is probably much more
> easy than installing via Macports… (and, it doesn’t add another build
> variant to support/maintain).
>
>
> Regards,
> Bernhard
>
> On 08.11.2015, at 21:50, Aljaž Srebrnič  wrote:
>
> Good work everyone!
> Is the rc2 stable enough to include it in MacPorts, or it is better if I
> wait for the official 4.0.0 release?
>
> Thanks,
> Aljaž
>
> On 8 novembre 2015 at 21:48:03, Wayne Stambaugh (stambau...@gmail.com)
> wrote:
>
> Hey Nick,
>
> I just merged lp:kicad into the 4.0 branch and it's in the process of
> building now. If all goes well which it should, I'll tag it as rc2 and
> commit it. I'll also create a new archive and md5sum and upload them to
> Launchpad. Hopefully I'll get this done this evening. If not, I'll
> finish up some time tomorrow
> .
>
> Wayne
>
> --
> Aljaž Srebrnič a.k.a g5pw
> My public key:  http://bit.ly/g5pw_pubkey
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] RC2

[Bernhard Stegmaier]

> On 08 Nov 2015, at 22:43, Aljaž Srebrnič  wrote:
> 
> On 8 novembre 2015 at 21:59:19, Adam Wolf (adamw...@feelslikeburning.com 
> ) wrote:
>> Hi,
>> 
>> just out of curiosity… why/how would you want to put it into MacPorts?
> 
> Well, for starters, I already have MacPorts on my machine, and it would be 
> simpler for the users to update. Another thing would be that I already have 
> WxWidgets installed on MacPorts, do I wouldn’t like having another copy just 
> for kicad
> 
You currently need a separate copy for KiCad, because it needs overlay support 
which isn’t available in wxWidgets mainline.
That’s one of the main reasons why KiCad build was made to produce a 
(Apple-like) self-contained application bundle and to not rely on any external 
library provided by, e.g., MacPorts (and, like it is on Linux).

If you want to have KiCad the MacPorts way (not including any dependency, but 
only its own libraries), you have to change the build system.
How does your port handle wxWidgets right now? Is it building its own copy of 
wxWidgets?

I also don’t see the point about updates… what is easier than just download a 
new .dmg image and drag the new application to your applications folder? 
My MacPorts updates for sure not… :)
But, I guess that’s only a matter of taste and nothing to discuss further...

>> IMHO there is really no need to build it via MacPorts, especially due to the 
>> special patched wxWidgets libraries which are not available in MacPorts 
>> anyway.
> 
> Well, we can either add them, or you can submit them upstream if they’re 
> useful
> 
They are in the wxWidgets bug tracker since many years now… of course, you can 
add those patches to MacPorts wxWidgets, but I don’t know if there are any 
impacts with other applications not knowing about those patches.

>> Downloading ready-made .dmg images from the website is probably much more 
>> easy than installing via Macports… (and, it doesn’t add another build 
>> variant to support/maintain).
> 
> Easier than ‘port install kicad’? We have some requests for packaging kicad 
> in our bug tracker [1]. What do you mean by having another build variant to 
> support/maintain? It would (should!) be virtually identical to the copy you 
> provide.
> 
Well, I know enough people who don’t even know how a console looks like… :)


Regards,
Bernhard

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] RC2

[Wayne Stambaugh]

Hey Nick,

I just merged lp:kicad into the 4.0 branch and it's in the process of
building now.  If all goes well which it should, I'll tag it as rc2 and
commit it.  I'll also create a new archive and md5sum and upload them to
Launchpad.  Hopefully I'll get this done this evening.  If not, I'll
finish up some time tomorrow.

Wayne

On 11/8/2015 9:10 AM, Nick Østergaard wrote:
> Hi Wayne
> 
> Will we have an RC2 this weekend?
> 
> Since the issue reported by Andrew can not be reproduced by anyone
> anymore, I guess we can disreagard this.
> 
> But what about the warnings reported by Mark? I personally don't think
> theese should block RC2, they are afterall warnings, and there is
> still time to fix them before the stable release.
> 
> Nick
> 
> 2015-11-08 1:12 GMT+01:00 Andrew Zonenberg :
>>
>> Confirmed to warn, but not crash, in r6302. Guess somebody fixed it
>> already.
>>
>> On 07/11/15 13:04, Wayne Stambaugh wrote:
>>> On 11/06/2015 12:25 PM, Andrew Zonenberg wrote:
 There's another bug I spent a while hunting for earlier this
 week, but couldn't get too far with. Maybe someone else can pick
 it up?

 Steps to reproduce: * Open pad editor * Select pad type: SMT *
 Select copper layers: none * Uncheck all technical layers

 In the debug build this will display a warning but keep running;
 in release it aborts or crashes.

 Although *exiting* the pad editor should not be allowed if the
 pad has no layers at all (or possibly pop up a dialog asking if
 the user wants to delete it?), having no layers selected should
 be a legal intermediate state during editing of a pad stack.
>>>
>>> I cannot even exit the pad properties dialog using the OK button.
>>> I keep getting an error message dialog "Error: no layer selected."
>>> every time I hit the OK button.  I'm using r6302 on Debian testing
>>> amd64 build.
>>>

 On 06/11/15 09:04, Mark Roszko wrote:
> One thing I didn't think was fixed yet was a null dereference
> introduced with the clipper library upgrade. jp fixed the
> uninitialized warnings but theres still a explicit null deref
> in a loop condition. CID 132144. What does it impact? No clue.

> And speaking of pns, there is still CID 106401 where
> PNS_MEANDERED_LINE::MeanderSegment can memory leak.


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] RC2

[Andy Peters]

> On Nov 8, 2015, at 2:43 PM, Aljaž Srebrnič  wrote:
> 
> On 8 novembre 2015 at 21:59:19, Adam Wolf (adamw...@feelslikeburning.com) 
> wrote:
>> Hi,
>> 
>> just out of curiosity… why/how would you want to put it into MacPorts?
> Well, for starters, I already have MacPorts on my machine, and it would be 
> simpler for the users to update. Another thing would be that I already have 
> WxWidgets installed on MacPorts, do I wouldn’t like having another copy just 
> for kicad.

Longtime Mac user here, with an opinion:

The average user doesn’t want to deal with MacPorts and building. They want to 
drag files from a disk image to /Applications and get going. Updates are as 
easy as dragging the latest version from a newer disk image over the old 
version. 

Adam’s nightly builds are already packaged into a .dmg, and everything is self 
contained (users don’t need to worry about installing wxWidgets or anything 
else). A disk image is the way to go.

-a
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] RC2

[Aljaž Srebrnič]

On 8 novembre 2015 at 21:59:19, Adam Wolf (adamw...@feelslikeburning.com) wrote:
Hi,

just out of curiosity… why/how would you want to put it into MacPorts?
Well, for starters, I already have MacPorts on my machine, and it would be 
simpler for the users to update. Another thing would be that I already have 
WxWidgets installed on MacPorts, do I wouldn’t like having another copy just 
for kicad.


IMHO there is really no need to build it via MacPorts, especially due to the 
special patched wxWidgets libraries which are not available in MacPorts anyway.
Well, we can either add them, or you can submit them upstream if they’re useful.


Downloading ready-made .dmg images from the website is probably much more easy 
than installing via Macports… (and, it doesn’t add another build variant to 
support/maintain).
Easier than ‘port install kicad’? We have some requests for packaging kicad in 
our bug tracker [1]. What do you mean by having another build variant to 
support/maintain? It would (should!) be virtually identical to the copy you 
provide.



[1]: https://trac.macports.org/ticket/47268


--
Aljaž Srebrnič a.k.a g5pw
My public key:  http://bit.ly/g5pw_pubkey___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] RC2 has been released.

[Wayne Stambaugh]

I just finished up getting all of the relevant code for RC2 uploaded to
launchpad so let's fire up those autobuilders and get some rc2 packages
out there for testing.  I'm hoping this will be the last rc before the
stable release.  Let's keep our fingers crossed.  We need start thinking
about branching or tagging the library, documentation, and translation
repos so that packagers can build consistent packages for their
respective platforms.  Thanks to everyone who made this possible.  I'm
going to step away from my computer for a while and enjoy the adult
beverage of my choice.

Cheers,

Wayne

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] RC2 has been released.

[Nick Østergaard]

Hi Wayne

Thank you for realasing. Although the download link is a bit strange..
it still partly refers to rc1.

https://launchpad.net/kicad/4.0/4.0.0-rc1/+download/kicad-4.0.0-rc2.tar.xz

But anyway, I guess we can just say that the docs, and their
translations, and the GUI translations shall be done in two weeks if
they want to be included with the release. The same witht he libs, if
anything is is left to be done, and we can just take a snapshot of the
libs and put it on the download page.

2015-11-08 23:11 GMT+01:00 Wayne Stambaugh :
> I just finished up getting all of the relevant code for RC2 uploaded to
> launchpad so let's fire up those autobuilders and get some rc2 packages
> out there for testing.  I'm hoping this will be the last rc before the
> stable release.  Let's keep our fingers crossed.  We need start thinking
> about branching or tagging the library, documentation, and translation
> repos so that packagers can build consistent packages for their
> respective platforms.  Thanks to everyone who made this possible.  I'm
> going to step away from my computer for a while and enjoy the adult
> beverage of my choice.
>
> Cheers,
>
> Wayne
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] RC2 has been released.

[Wayne Stambaugh]

That is strange.  I wonder if the path has something to do with what
page is open when you upload it.  As long as users can download the file
it should be OK.  If I get some time, I'll mess around with it and see
if I can get it in the https://launchpad.net/kicad/4.0 path.

On 11/8/2015 6:01 PM, Nick Østergaard wrote:
> Hi Wayne
> 
> Thank you for realasing. Although the download link is a bit strange..
> it still partly refers to rc1.
> 
> https://launchpad.net/kicad/4.0/4.0.0-rc1/+download/kicad-4.0.0-rc2.tar.xz
> 
> But anyway, I guess we can just say that the docs, and their
> translations, and the GUI translations shall be done in two weeks if
> they want to be included with the release. The same witht he libs, if
> anything is is left to be done, and we can just take a snapshot of the
> libs and put it on the download page.
> 
> 2015-11-08 23:11 GMT+01:00 Wayne Stambaugh :
>> I just finished up getting all of the relevant code for RC2 uploaded to
>> launchpad so let's fire up those autobuilders and get some rc2 packages
>> out there for testing.  I'm hoping this will be the last rc before the
>> stable release.  Let's keep our fingers crossed.  We need start thinking
>> about branching or tagging the library, documentation, and translation
>> repos so that packagers can build consistent packages for their
>> respective platforms.  Thanks to everyone who made this possible.  I'm
>> going to step away from my computer for a while and enjoy the adult
>> beverage of my choice.
>>
>> Cheers,
>>
>> Wayne
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] RC2

[Wayne Stambaugh]

On 11/06/2015 12:25 PM, Andrew Zonenberg wrote:
> There's another bug I spent a while hunting for earlier this week, but
> couldn't get too far with. Maybe someone else can pick it up?
> 
> Steps to reproduce:
> * Open pad editor
> * Select pad type: SMT
> * Select copper layers: none
> * Uncheck all technical layers
> 
> In the debug build this will display a warning but keep running; in
> release it aborts or crashes.
> 
> Although *exiting* the pad editor should not be allowed if the pad has
> no layers at all (or possibly pop up a dialog asking if the user wants
> to delete it?), having no layers selected should be a legal
> intermediate state during editing of a pad stack.

I cannot even exit the pad properties dialog using the OK button.  I
keep getting an error message dialog "Error: no layer selected." every
time I hit the OK button.  I'm using r6302 on Debian testing amd64 build.

> 
> On 06/11/15 09:04, Mark Roszko wrote:
>> One thing I didn't think was fixed yet was a null dereference 
>> introduced with the clipper library upgrade. jp fixed the 
>> uninitialized warnings but theres still a explicit null deref in a 
>> loop condition. CID 132144. What does it impact? No clue.
> 
>> And speaking of pns, there is still CID 106401 where 
>> PNS_MEANDERED_LINE::MeanderSegment can memory leak.
> 
>> ___ Mailing list:
>> https://launchpad.net/~kicad-developers Post to :
>> kicad-developers@lists.launchpad.net Unsubscribe :
>> https://launchpad.net/~kicad-developers More help   :
>> https://help.launchpad.net/ListHelp
> 
> 

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] RC2

[Wayne Stambaugh]

On 11/07/2015 11:52 AM, jp charras wrote:
> Le 06/11/2015 19:35, Wayne Stambaugh a écrit :
>> On 11/6/2015 12:04 PM, Mark Roszko wrote:
>>> One thing I didn't think was fixed yet was a null dereference
>>> introduced with the clipper library upgrade. jp fixed the
>>> uninitialized warnings but theres still a explicit null deref in a
>>> loop condition. CID 132144. What does it impact? No clue.
>>
>> There should be at least an assertion for debug builds and a skip branch
>> on release builds.  A null pointer may never occur but I prefer
>> defensive programming whenever possible.  wxCHECK_MSG() and
>> wxCHECK2_MSG() can be useful in this case.
> 
> I had a look at this warning
> For me, this is a false positive.

As long as there is no possible way for this pointer to be null at
runtime then that's fine.  Please mark the Coverity warning as false
positive with a short description as to why it is a false positive.

> 
>>
>>>
>>> And speaking of pns, there is still CID 106401 where
>>> PNS_MEANDERED_LINE::MeanderSegment can memory leak.
>>>
>>
>> Tom or Orson can you please take a look at this?  I typically use an
>> auto_ptr() and auto_ptr::release() in this case just to be safe.  It
>> also covers the case when a exception occurs somewhere in the middle of
>> your code.  If this can never occur because of the design of the code
>> leading up that that point, you may want to tag the Coverity error as
>> such.  However, it does look to me as though you can get to that point
>> in which case you have a memory leak.  Given that MeanderSegment is
>> adding new segments the memory leak could be substantial over long
>> editing sessions.
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
> 
> 

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] RC2

[jp charras]

Le 06/11/2015 19:35, Wayne Stambaugh a écrit :
> On 11/6/2015 12:04 PM, Mark Roszko wrote:
>> One thing I didn't think was fixed yet was a null dereference
>> introduced with the clipper library upgrade. jp fixed the
>> uninitialized warnings but theres still a explicit null deref in a
>> loop condition. CID 132144. What does it impact? No clue.
> 
> There should be at least an assertion for debug builds and a skip branch
> on release builds.  A null pointer may never occur but I prefer
> defensive programming whenever possible.  wxCHECK_MSG() and
> wxCHECK2_MSG() can be useful in this case.

I had a look at this warning
For me, this is a false positive.

> 
>>
>> And speaking of pns, there is still CID 106401 where
>> PNS_MEANDERED_LINE::MeanderSegment can memory leak.
>>
> 
> Tom or Orson can you please take a look at this?  I typically use an
> auto_ptr() and auto_ptr::release() in this case just to be safe.  It
> also covers the case when a exception occurs somewhere in the middle of
> your code.  If this can never occur because of the design of the code
> leading up that that point, you may want to tag the Coverity error as
> such.  However, it does look to me as though you can get to that point
> in which case you have a memory leak.  Given that MeanderSegment is
> adding new segments the memory leak could be substantial over long
> editing sessions.
> 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 


-- 
Jean-Pierre CHARRAS

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] RC2

[Andrew Zonenberg]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Confirmed to warn, but not crash, in r6302. Guess somebody fixed it
already.

On 07/11/15 13:04, Wayne Stambaugh wrote:
> On 11/06/2015 12:25 PM, Andrew Zonenberg wrote:
>> There's another bug I spent a while hunting for earlier this
>> week, but couldn't get too far with. Maybe someone else can pick
>> it up?
>> 
>> Steps to reproduce: * Open pad editor * Select pad type: SMT *
>> Select copper layers: none * Uncheck all technical layers
>> 
>> In the debug build this will display a warning but keep running;
>> in release it aborts or crashes.
>> 
>> Although *exiting* the pad editor should not be allowed if the
>> pad has no layers at all (or possibly pop up a dialog asking if
>> the user wants to delete it?), having no layers selected should
>> be a legal intermediate state during editing of a pad stack.
> 
> I cannot even exit the pad properties dialog using the OK button.
> I keep getting an error message dialog "Error: no layer selected."
> every time I hit the OK button.  I'm using r6302 on Debian testing
> amd64 build.
> 
>> 
>> On 06/11/15 09:04, Mark Roszko wrote:
>>> One thing I didn't think was fixed yet was a null dereference 
>>> introduced with the clipper library upgrade. jp fixed the 
>>> uninitialized warnings but theres still a explicit null deref
>>> in a loop condition. CID 132144. What does it impact? No clue.
>> 
>>> And speaking of pns, there is still CID 106401 where 
>>> PNS_MEANDERED_LINE::MeanderSegment can memory leak.
>> 
>>> ___ Mailing list: 
>>> https://launchpad.net/~kicad-developers Post to : 
>>> kicad-developers@lists.launchpad.net Unsubscribe : 
>>> https://launchpad.net/~kicad-developers More help   : 
>>> https://help.launchpad.net/ListHelp
>> 
>> 
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBAgAGBQJWPpN4AAoJEDRhermzHH18QWUP/37S/Pz38wbXfMzBpGsWztIJ
QlV9f7K/5t3oHOwFXmc7qomJH7iuJxp2Dq/1z8aYM64iXa5X3ce7K1ra1H7skqKV
sedJlHDk2ginjGxGDfQtJZ/YTbOgCz+1LeZT7v3TPhBMZjDh4QiNVxNIIqbL4quU
r/nF0dKy9TOQzLNavGtFaHdX3qstsIs8YvBN7nPV7lSMfk0emJo/H4iZ9eH5gg/Z
SzWd761PnHGyudSeaDp19g6K58PnV0ePn9jrsTZP0DOsLpnRZNV4F3j1NV0NnCUE
ugnI2UV/TOk6aBlOUXhZg0bb6Kv2aKYlxQ/bEc+uaberRnLqybdgPU7qESb3sORd
P/SX298vwqC8q1EeLzebnksoI9iHHvNSIXqWz0R3ETkPVITQYwDwqtrwuu089eXG
sDW78pjsQeMVsTPsoqOeDCeW7SmaiolSPafYUoNuTlpqGSY/cLW5Vq0T2TpYkQBt
pPpPQeE6N5SIgRrSv+gUm80gHMcisvwZkDipgb/mIRusjS6fMq7nm0Glnt6sa6Gb
PB/3VMQzzu2VipXAUHKATcjHJiRASFNyhUCqkCyJL9AJZ8GBjp69TPM+QPyYbedk
Drp58Tk8qui7PZ3zJMUzoqt7iSyZtclAeZUcss9nRah83x3Lq85s/Bs6+Fpwo2I0
hjAmLXnbG+mjGv2AYvHn
=hsnT
-END PGP SIGNATURE-

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] RC2

[Mark Roszko]

One thing I didn't think was fixed yet was a null dereference
introduced with the clipper library upgrade. jp fixed the
uninitialized warnings but theres still a explicit null deref in a
loop condition. CID 132144. What does it impact? No clue.

And speaking of pns, there is still CID 106401 where
PNS_MEANDERED_LINE::MeanderSegment can memory leak.

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] RC2

[Andrew Zonenberg]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

There's another bug I spent a while hunting for earlier this week, but
couldn't get too far with. Maybe someone else can pick it up?

Steps to reproduce:
* Open pad editor
* Select pad type: SMT
* Select copper layers: none
* Uncheck all technical layers

In the debug build this will display a warning but keep running; in
release it aborts or crashes.

Although *exiting* the pad editor should not be allowed if the pad has
no layers at all (or possibly pop up a dialog asking if the user wants
to delete it?), having no layers selected should be a legal
intermediate state during editing of a pad stack.

On 06/11/15 09:04, Mark Roszko wrote:
> One thing I didn't think was fixed yet was a null dereference 
> introduced with the clipper library upgrade. jp fixed the 
> uninitialized warnings but theres still a explicit null deref in a 
> loop condition. CID 132144. What does it impact? No clue.
> 
> And speaking of pns, there is still CID 106401 where 
> PNS_MEANDERED_LINE::MeanderSegment can memory leak.
> 
> ___ Mailing list:
> https://launchpad.net/~kicad-developers Post to :
> kicad-developers@lists.launchpad.net Unsubscribe :
> https://launchpad.net/~kicad-developers More help   :
> https://help.launchpad.net/ListHelp
> 
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBAgAGBQJWPOKkAAoJEDRhermzHH18NfgQAJKIoYj+Yb5P+j4JGBQuZjQK
QF2gXcsn3lCpjaCPTKhZvVtyjXpG+kqy1jYL+TIg5lU4fk1k3LAh/f5VdUE/nPZE
GIgrfT+4pv0GEKdEZ9c8IXjHHInHfxna9qowArVyD2DZWrhCdP749BRrYAGcgprF
4MmCHNAz1P/lfzKY3bbCnYCOpD+uWR+thMr/17FAixH5D9l16GKtYXoXE9CkGZUr
6Rjb3X6cWhNba/ACjF92XZytEI/XcXetX7iHUC9wIdOXgwyELzvZy7i2ptAbD7Ck
RUf4XkNfpM6TW86qmLywFMyt4qfb6BpNud1x9LwFXsMZUl8GIoIUith9FLQwGM3P
HWKJ66WgjE4FmpRTXhnG3ulunIjHY3q7z5U3Ch/IYJNof995KFQP4yLqu/BaYUdw
LnvrL1HJdZDcrvW9p4bbH+/Fijcma8NwXDI/bwCGy75DSiA1QiTVnGHmDXvvWKBk
12ry1Cgf0hZhWO3oS/Tti2lPka8K4vYStjiO7Tp9Odx2Pol0uGQj6B6JrefPeTYr
29R4Qw02hhtldKVqCvFGlyhf7O8ASdmzweGubmYV86z+VMRO302gZ9f0yWAUOCE+
h4XQ5mM2wzzwY4i87PdEV6wPteX717fgX7wUMznpGmmr+u8DZsp2rRJ6Y4OmmM5M
3AiiCjN1eEAUPBzgC3gh
=1C44
-END PGP SIGNATURE-

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] RC2

[jp charras]

Le 06/11/2015 18:25, Andrew Zonenberg a écrit :
> There's another bug I spent a while hunting for earlier this week,
> but couldn't get too far with. Maybe someone else can pick it up?
> 
> Steps to reproduce: * Open pad editor * Select pad type: SMT *
> Select copper layers: none * Uncheck all technical layers
> 
> In the debug build this will display a warning but keep running;
> in release it aborts or crashes.

On Windows, I just have a warning message in a message box in OpenGL
canvas and no issue in legacy mode, but no crash.

What is your OS ?

> 
> Although *exiting* the pad editor should not be allowed if the pad
> has no layers at all (or possibly pop up a dialog asking if the
> user wants to delete it?), having no layers selected should be a
> legal intermediate state during editing of a pad stack.
> 
> On 06/11/15 09:04, Mark Roszko wrote:
>> One thing I didn't think was fixed yet was a null dereference 
>> introduced with the clipper library upgrade. jp fixed the 
>> uninitialized warnings but theres still a explicit null deref in
>> a loop condition. CID 132144. What does it impact? No clue.
> 
>> And speaking of pns, there is still CID 106401 where 
>> PNS_MEANDERED_LINE::MeanderSegment can memory leak.

They are only warnings.

-- 
Jean-Pierre CHARRAS

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] RC2

[Nick Østergaard]

Den 06/11/2015 18.34 skrev "jp charras" :
>
> Le 06/11/2015 18:25, Andrew Zonenberg a écrit :
> > There's another bug I spent a while hunting for earlier this week,
> > but couldn't get too far with. Maybe someone else can pick it up?
> >
> > Steps to reproduce: * Open pad editor * Select pad type: SMT *
> > Select copper layers: none * Uncheck all technical layers
> >
> > In the debug build this will display a warning but keep running;
> > in release it aborts or crashes.
>
> On Windows, I just have a warning message in a message box in OpenGL
> canvas and no issue in legacy mode, but no crash.

Did you try a release build?

> What is your OS ?
>
> >
> > Although *exiting* the pad editor should not be allowed if the pad
> > has no layers at all (or possibly pop up a dialog asking if the
> > user wants to delete it?), having no layers selected should be a
> > legal intermediate state during editing of a pad stack.
> >
> > On 06/11/15 09:04, Mark Roszko wrote:
> >> One thing I didn't think was fixed yet was a null dereference
> >> introduced with the clipper library upgrade. jp fixed the
> >> uninitialized warnings but theres still a explicit null deref in
> >> a loop condition. CID 132144. What does it impact? No clue.
> >
> >> And speaking of pns, there is still CID 106401 where
> >> PNS_MEANDERED_LINE::MeanderSegment can memory leak.
>
> They are only warnings.
>
> --
> Jean-Pierre CHARRAS
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] RC2

[Wayne Stambaugh]

Is anyone working on any high priority bug fixes?  I plan on rolling out
4.0.0-rc2 over the weekend and I don't want to get blindsided by any
important fixes before doing so.

Has anyone had a chance to test the P router including diff pair
routing?  I played around with the P router a bit using the video demo
but not the diff pair routing and it didn't crash.  If you are still
having problems with it, please speak up now.

Thanks,

Wayne

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] RC2

[jp charras]

Le 06/11/2015 18:37, Nick Østergaard a écrit :
> 
> Den 06/11/2015 18.34 skrev "jp charras"  >:
>>
>> Le 06/11/2015 18:25, Andrew Zonenberg a écrit :
>> > There's another bug I spent a while hunting for earlier this week,
>> > but couldn't get too far with. Maybe someone else can pick it up?
>> >
>> > Steps to reproduce: * Open pad editor * Select pad type: SMT *
>> > Select copper layers: none * Uncheck all technical layers
>> >
>> > In the debug build this will display a warning but keep running;
>> > in release it aborts or crashes.
>>
>> On Windows, I just have a warning message in a message box in OpenGL
>> canvas and no issue in legacy mode, but no crash.
> 
> Did you try a release build?

Yes.
On Windows, building a Debug version is painful.

> 
>> What is your OS ?
>>
>> >
>> > Although *exiting* the pad editor should not be allowed if the pad
>> > has no layers at all (or possibly pop up a dialog asking if the
>> > user wants to delete it?), having no layers selected should be a
>> > legal intermediate state during editing of a pad stack.
>> >
>> > On 06/11/15 09:04, Mark Roszko wrote:
>> >> One thing I didn't think was fixed yet was a null dereference
>> >> introduced with the clipper library upgrade. jp fixed the
>> >> uninitialized warnings but theres still a explicit null deref in
>> >> a loop condition. CID 132144. What does it impact? No clue.
>> >
>> >> And speaking of pns, there is still CID 106401 where
>> >> PNS_MEANDERED_LINE::MeanderSegment can memory leak.
>>
>> They are only warnings.
>>
>> --
>> Jean-Pierre CHARRAS
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
> 
>> Post to : kicad-developers@lists.launchpad.net
> 
>> Unsubscribe : https://launchpad.net/~kicad-developers
> 
>> More help   : https://help.launchpad.net/ListHelp
> 


-- 
Jean-Pierre CHARRAS

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] RC2

[Andrew Zonenberg]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I'm on Debian 7 amd64. A couple of other people in #kicad managed to
reproduce the issue as well and I think most were linux based too.

On 06/11/15 09:34, jp charras wrote:
> Le 06/11/2015 18:25, Andrew Zonenberg a écrit :
>> There's another bug I spent a while hunting for earlier this
>> week, but couldn't get too far with. Maybe someone else can pick
>> it up?
>> 
>> Steps to reproduce: * Open pad editor * Select pad type: SMT * 
>> Select copper layers: none * Uncheck all technical layers
>> 
>> In the debug build this will display a warning but keep running; 
>> in release it aborts or crashes.
> 
> On Windows, I just have a warning message in a message box in
> OpenGL canvas and no issue in legacy mode, but no crash.
> 
> What is your OS ?
> 
>> 
>> Although *exiting* the pad editor should not be allowed if the
>> pad has no layers at all (or possibly pop up a dialog asking if
>> the user wants to delete it?), having no layers selected should
>> be a legal intermediate state during editing of a pad stack.
>> 
>> On 06/11/15 09:04, Mark Roszko wrote:
>>> One thing I didn't think was fixed yet was a null dereference 
>>> introduced with the clipper library upgrade. jp fixed the 
>>> uninitialized warnings but theres still a explicit null deref
>>> in a loop condition. CID 132144. What does it impact? No clue.
>> 
>>> And speaking of pns, there is still CID 106401 where 
>>> PNS_MEANDERED_LINE::MeanderSegment can memory leak.
> 
> They are only warnings.
> 
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBAgAGBQJWPO8OAAoJEDRhermzHH188egQAIZXOHxqWcwUQNcmTHCxC+nM
cFwiV8bU/zArqKjyNCm65KBTaCHMyayTVO9i4mLLQpH26wiwmv/OOAzlugmPNpz3
F9p43Uj3g0aXwY4BHPsbEmL89DJ3u0Z9HbLAEUjawE0AOneOfUnn3f2hOlrBqx3j
XxVhkEgHJWKQKmrgfWUHEuI7w78Pj3J6S5C0UrkXJAktMtEw+mIE87Ox2an7Sysp
rjhov2xT1uzKPOiVMOl5M+aRQGgdU3WY44GtOvONXHsaZ+qnv2GRBhKHqoiTM4le
MraUpPetfNvL89cldmccMHcgok6B+IIU5pCVHud/6s1sUmJAX1WiQ6cR3vg7cWZc
hpg0KvEUA9a4VC/NBBW7X1CdexQcZQOYPzqU5NIqgM7xcpBWfxYc8t74cuMjxxKY
+tG0R070NNxAjMpmZ+T+H1eG40+20ZaZoUjK31SkNm95DJjVn1NJNk97HeJx4Mn7
jShFyECCiI55XGW6fc8F0eYT4Ah+NfY2qd3OQdMynYMKDouU4lZI/BgZ87v63Ftm
PaAu0Q+qy4WCC/k00pM9eLSXbB9q9jgjgIMtK/0xrZ7C2tH+/+SPz1I1xtL2WsY9
19wZSUtLOsfcEaEAfcji0KVXjZrhPZRcd9bYfjbnxdD7HCy3oOKrhoRKcTkCc1u/
6HPpnZ6STfIafLy4RveM
=Y9Xs
-END PGP SIGNATURE-

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] RC2

[Wayne Stambaugh]

On 11/6/2015 12:04 PM, Mark Roszko wrote:
> One thing I didn't think was fixed yet was a null dereference
> introduced with the clipper library upgrade. jp fixed the
> uninitialized warnings but theres still a explicit null deref in a
> loop condition. CID 132144. What does it impact? No clue.

There should be at least an assertion for debug builds and a skip branch
on release builds.  A null pointer may never occur but I prefer
defensive programming whenever possible.  wxCHECK_MSG() and
wxCHECK2_MSG() can be useful in this case.

> 
> And speaking of pns, there is still CID 106401 where
> PNS_MEANDERED_LINE::MeanderSegment can memory leak.
> 

Tom or Orson can you please take a look at this?  I typically use an
auto_ptr() and auto_ptr::release() in this case just to be safe.  It
also covers the case when a exception occurs somewhere in the middle of
your code.  If this can never occur because of the design of the code
leading up that that point, you may want to tag the Coverity error as
such.  However, it does look to me as though you can get to that point
in which case you have a memory leak.  Given that MeanderSegment is
adding new segments the memory leak could be substantial over long
editing sessions.


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] RC2

[Wayne Stambaugh]

On 11/6/2015 1:18 PM, Andrew Zonenberg wrote:
> I'm on Debian 7 amd64. A couple of other people in #kicad managed to
> reproduce the issue as well and I think most were linux based too.

If this is the case and there is no report for this already, please
submit one so we can track it.  I use Debain testing and will attempt to
reproduce it on my system when I get a chance.  I doubt I'll have time
to look at it today but I will have time over the weekend.

> 
> On 06/11/15 09:34, jp charras wrote:
>> Le 06/11/2015 18:25, Andrew Zonenberg a écrit :
>>> There's another bug I spent a while hunting for earlier this
>>> week, but couldn't get too far with. Maybe someone else can pick
>>> it up?
>>>
>>> Steps to reproduce: * Open pad editor * Select pad type: SMT * 
>>> Select copper layers: none * Uncheck all technical layers
>>>
>>> In the debug build this will display a warning but keep running; 
>>> in release it aborts or crashes.
> 
>> On Windows, I just have a warning message in a message box in
>> OpenGL canvas and no issue in legacy mode, but no crash.
> 
>> What is your OS ?
> 
>>>
>>> Although *exiting* the pad editor should not be allowed if the
>>> pad has no layers at all (or possibly pop up a dialog asking if
>>> the user wants to delete it?), having no layers selected should
>>> be a legal intermediate state during editing of a pad stack.
>>>
>>> On 06/11/15 09:04, Mark Roszko wrote:
 One thing I didn't think was fixed yet was a null dereference 
 introduced with the clipper library upgrade. jp fixed the 
 uninitialized warnings but theres still a explicit null deref
 in a loop condition. CID 132144. What does it impact? No clue.
>>>
 And speaking of pns, there is still CID 106401 where 
 PNS_MEANDERED_LINE::MeanderSegment can memory leak.
> 
>> They are only warnings.
> 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] RC2

[Nick Østergaard]

Hi, I was one of the persons able to recreate it earlier. I am on
archlinux x86_64, but I can't reproduce it on  6302 release/debug nor
6277 release now. I think I did reproduce the issue on 6277 release when I
previously tested it.  So I don't know it is needs some other
prerequisite for it to happen. I could reproduced 3 of 3 thimes on
each a debug and release build last time. hmm

@Andrew, I think your forgot to mention that it was only on the GAL
canvas, right?

2015-11-06 19:23 GMT+01:00 Wayne Stambaugh :
> On 11/6/2015 1:18 PM, Andrew Zonenberg wrote:
>> I'm on Debian 7 amd64. A couple of other people in #kicad managed to
>> reproduce the issue as well and I think most were linux based too.
>
> If this is the case and there is no report for this already, please
> submit one so we can track it.  I use Debain testing and will attempt to
> reproduce it on my system when I get a chance.  I doubt I'll have time
> to look at it today but I will have time over the weekend.
>
>>
>> On 06/11/15 09:34, jp charras wrote:
>>> Le 06/11/2015 18:25, Andrew Zonenberg a écrit :
 There's another bug I spent a while hunting for earlier this
 week, but couldn't get too far with. Maybe someone else can pick
 it up?

 Steps to reproduce: * Open pad editor * Select pad type: SMT *
 Select copper layers: none * Uncheck all technical layers

 In the debug build this will display a warning but keep running;
 in release it aborts or crashes.
>>
>>> On Windows, I just have a warning message in a message box in
>>> OpenGL canvas and no issue in legacy mode, but no crash.
>>
>>> What is your OS ?
>>

 Although *exiting* the pad editor should not be allowed if the
 pad has no layers at all (or possibly pop up a dialog asking if
 the user wants to delete it?), having no layers selected should
 be a legal intermediate state during editing of a pad stack.

 On 06/11/15 09:04, Mark Roszko wrote:
> One thing I didn't think was fixed yet was a null dereference
> introduced with the clipper library upgrade. jp fixed the
> uninitialized warnings but theres still a explicit null deref
> in a loop condition. CID 132144. What does it impact? No clue.

> And speaking of pns, there is still CID 106401 where
> PNS_MEANDERED_LINE::MeanderSegment can memory leak.
>>
>>> They are only warnings.
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] RC2

[Wayne Stambaugh]

On 11/6/2015 2:45 PM, jp charras wrote:
> 
> 
> Le 06/11/2015 19:23, Wayne Stambaugh a écrit :
>> On 11/6/2015 1:18 PM, Andrew Zonenberg wrote:
>>> I'm on Debian 7 amd64. A couple of other people in #kicad managed to
>>> reproduce the issue as well and I think most were linux based too.
>> If this is the case and there is no report for this already, please
>> submit one so we can track it.  I use Debain testing and will attempt to
>> reproduce it on my system when I get a chance.  I doubt I'll have time
>> to look at it today but I will have time over the weekend.
>>
>>
> 
> I tried Kubuntu 14.04 on KDE and Ubuntu 14.10 on Unity, and I do not
> have any crash, just a warning message (in a wxLogMessage dialog) in
> Opengl canvas, both in Release and Debug version.
> 
> 
> JP Charras

Could this be a video drive issue?

> 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] RC2

[Nick Østergaard]

2015-11-06 21:04 GMT+01:00 Wayne Stambaugh :
> On 11/6/2015 2:45 PM, jp charras wrote:
>>
>>
>> Le 06/11/2015 19:23, Wayne Stambaugh a écrit :
>>> On 11/6/2015 1:18 PM, Andrew Zonenberg wrote:
 I'm on Debian 7 amd64. A couple of other people in #kicad managed to
 reproduce the issue as well and I think most were linux based too.
>>> If this is the case and there is no report for this already, please
>>> submit one so we can track it.  I use Debain testing and will attempt to
>>> reproduce it on my system when I get a chance.  I doubt I'll have time
>>> to look at it today but I will have time over the weekend.
>>>
>>>
>>
>> I tried Kubuntu 14.04 on KDE and Ubuntu 14.10 on Unity, and I do not
>> have any crash, just a warning message (in a wxLogMessage dialog) in
>> Opengl canvas, both in Release and Debug version.
>>
>>
>> JP Charras
>
> Could this be a video drive issue?

I don't think so, I am using the exact same machine as I tested on
earlier. And I have not updated my system in the meantime.

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] RC2

[jp charras]

Le 06/11/2015 19:23, Wayne Stambaugh a écrit :

On 11/6/2015 1:18 PM, Andrew Zonenberg wrote:

I'm on Debian 7 amd64. A couple of other people in #kicad managed to
reproduce the issue as well and I think most were linux based too.

If this is the case and there is no report for this already, please
submit one so we can track it.  I use Debain testing and will attempt to
reproduce it on my system when I get a chance.  I doubt I'll have time
to look at it today but I will have time over the weekend.




I tried Kubuntu 14.04 on KDE and Ubuntu 14.10 on Unity, and I do not 
have any crash, just a warning message (in a wxLogMessage dialog) in 
Opengl canvas, both in Release and Debug version.



JP Charras


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] RC2 blockers?

[Javier Serrano]

On Tue, Nov 3, 2015 at 12:39 AM, Wayne Stambaugh  wrote:
> Yes.  The P router still has a serious segfault issue.  I've talked to
> Tom about it and he is working on it.  As soon as the fixes are
> committed, I will be rolling out rc2.  I'm hoping it will be soon.

Last time I saw Orson and Tom we were in Australia and they both
looked like they could really use a few days/weeks of vacation. They
stayed there and I am back in Geneva. I will talk with them when they
are back, which is the 9th for Tom and the 17th for Orson.

Cheers,

Javier

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] RC2 blockers?

[Wayne Stambaugh]

On 11/3/2015 5:34 AM, Tomasz Wlostowski wrote:
> On 03.11.2015 20:13, Javier Serrano wrote:
>> On Tue, Nov 3, 2015 at 12:39 AM, Wayne Stambaugh  
>> wrote:
>>> Yes.  The P router still has a serious segfault issue.  I've talked to
>>> Tom about it and he is working on it.  As soon as the fixes are
>>> committed, I will be rolling out rc2.  I'm hoping it will be soon.
>>
>> Last time I saw Orson and Tom we were in Australia and they both
>> looked like they could really use a few days/weeks of vacation. They
>> stayed there and I am back in Geneva. I will talk with them when they
>> are back, which is the 9th for Tom and the 17th for Orson.
> 
> Hi guys,
> 
> Here's an updated version of the patch. Wayne, if you haven't committed
> the one I've sent you previously, please take this one. It also fixes
> one more issue and removes the pritnfs() reported by Joseph. Sorry it
> took so long.
> 
> Greetings from AU
> Tom

I committed your patch in r6294.  Thanks for taking time from your
vacation to fix the problem.  If I would have known you were on
vacation, I would have told you to wait until you got back to fix it.  I
think we could have survived a few more days without this fix.  Enjoy
the rest of you vacation.

Folks, please test P router as much as possible.  If there are no more
p router crashes reported in the next few days, I'll try to roll out
rc2 this weekend.

Thanks,

Wayne

> 
> 
>>
>> Cheers,
>>
>> Javier
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
> 

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] RC2 blockers?

[Tomasz Wlostowski]

On 03.11.2015 20:13, Javier Serrano wrote:
> On Tue, Nov 3, 2015 at 12:39 AM, Wayne Stambaugh  wrote:
>> Yes.  The P router still has a serious segfault issue.  I've talked to
>> Tom about it and he is working on it.  As soon as the fixes are
>> committed, I will be rolling out rc2.  I'm hoping it will be soon.
> 
> Last time I saw Orson and Tom we were in Australia and they both
> looked like they could really use a few days/weeks of vacation. They
> stayed there and I am back in Geneva. I will talk with them when they
> are back, which is the 9th for Tom and the 17th for Orson.

Hi guys,

Here's an updated version of the patch. Wayne, if you haven't committed
the one I've sent you previously, please take this one. It also fixes
one more issue and removes the pritnfs() reported by Joseph. Sorry it
took so long.

Greetings from AU
Tom


> 
> Cheers,
> 
> Javier
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 

>From 42f067b8b45aef8826cee8bcf6c1957f295a813b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Tomasz=20W=C5=82ostowski?= 
Date: Tue, 3 Nov 2015 20:21:02 +1000
Subject: [PATCH] Multiple fixes for the P router: - invalidate end item
 after changing layers / ortho mode (fixes a rare segfault) - fixed hidden
 database corrpution in auto-track-width causing assertion fail in pushVia()
 or segfault in release builds. - respect grid when snapping to segments  
   - fixed cursor issue when dragging is invoked from the context menu

---
 pcbnew/router/pns_line_placer.cpp| 11 +--
 pcbnew/router/pns_router.cpp |  6 --
 pcbnew/router/pns_router.h   | 10 --
 pcbnew/router/pns_shove.cpp  |  7 +++
 pcbnew/router/pns_sizes_settings.cpp |  4 +++-
 pcbnew/router/pns_tool_base.cpp  | 11 +++
 pcbnew/router/pns_tool_base.h|  3 +++
 pcbnew/router/router_tool.cpp| 15 +++
 pcbnew/tools/grid_helper.cpp | 37 
 pcbnew/tools/grid_helper.h   |  4 
 10 files changed, 89 insertions(+), 19 deletions(-)

diff --git a/pcbnew/router/pns_line_placer.cpp b/pcbnew/router/pns_line_placer.cpp
index bdc2970..5ff7977 100644
--- a/pcbnew/router/pns_line_placer.cpp
+++ b/pcbnew/router/pns_line_placer.cpp
@@ -952,6 +952,7 @@ void PNS_LINE_PLACER::removeLoops( PNS_NODE* aNode, PNS_LINE& aLatest )
 if ( aLatest.CLine().CPoint( 0 ) == aLatest.CLine().CPoint( -1 ) )
 return;
 
+std::set toErase;
 aNode->Add( , true );
 
 for( int s = 0; s < aLatest.LinkCount(); s++ )
@@ -979,13 +980,16 @@ void PNS_LINE_PLACER::removeLoops( PNS_NODE* aNode, PNS_LINE& aLatest )
 
 if( !( line.ContainsSegment( seg ) ) && line.SegmentCount() )
 {
-aNode->Remove(  );
+BOOST_FOREACH( PNS_SEGMENT *ss, *line.LinkedSegments() )
+toErase.insert(ss);
 removedCount++;
 }
 }
 
 TRACE( 0, "total segs removed: %d/%d\n", removedCount % total );
 }
+BOOST_FOREACH( PNS_SEGMENT *s, toErase )
+aNode->Remove (s);
 
 aNode->Remove(  );
 }
@@ -1034,17 +1038,12 @@ void PNS_LINE_PLACER::updateLeadingRatLine()
 void PNS_LINE_PLACER::SetOrthoMode( bool aOrthoMode )
 {
 m_orthoMode = aOrthoMode;
-
-if( !m_idle )
-Move( m_currentEnd, NULL );
 }
 
 bool PNS_LINE_PLACER::buildInitialLine( const VECTOR2I& aP, PNS_LINE& aHead )
 {
 SHAPE_LINE_CHAIN l;
 
-printf("H-net %d\n", aHead.Net());
-
 if( m_p_start == aP )
 {
 l.Clear();
diff --git a/pcbnew/router/pns_router.cpp b/pcbnew/router/pns_router.cpp
index 8526a64..fd7d911 100644
--- a/pcbnew/router/pns_router.cpp
+++ b/pcbnew/router/pns_router.cpp
@@ -35,6 +35,8 @@
 #include 
 #include 
 
+#include 
+
 #include "trace.h"
 #include "pns_node.h"
 #include "pns_line_placer.h"
@@ -572,8 +574,8 @@ const VECTOR2I PNS_ROUTER::SnapToItem( PNS_ITEM* aItem, VECTOR2I aP, bool& aSpli
 anchor = s.B;
 else
 {
-anchor = s.NearestPoint( aP );
-aSplitsSegment = true;
+anchor = m_gridHelper->AlignToSegment ( aP, s );
+aSplitsSegment = (anchor != s.A && anchor != s.B );
 }
 
 break;
diff --git a/pcbnew/router/pns_router.h b/pcbnew/router/pns_router.h
index 05be228..0541dec 100644
--- a/pcbnew/router/pns_router.h
+++ b/pcbnew/router/pns_router.h
@@ -40,6 +40,7 @@ class BOARD_ITEM;
 class D_PAD;
 class TRACK;
 class VIA;
+class GRID_HELPER;
 class PNS_NODE;
 class PNS_DIFF_PAIR_PLACER;
 class PNS_PLACEMENT_ALGO;
@@ -106,7 +107,6 @@ public:
 
 void StopRouting();
 
-
 int GetClearance( const PNS_ITEM* aA, const PNS_ITEM* aB ) const;
 
 PNS_NODE* 

Re: [Kicad-developers] RC2 blockers?

[Wayne Stambaugh]

Yes.  The P router still has a serious segfault issue.  I've talked to
Tom about it and he is working on it.  As soon as the fixes are
committed, I will be rolling out rc2.  I'm hoping it will be soon.

On 11/2/2015 6:30 PM, Jon Neal wrote:
> Are there currently any RC2 blockers? Nickoe mentioned that the
> scripting stuff that was the previous blocker was finished a couple of
> weeks ago.
> 
> Jon
> 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp