Re: [Kicad-developers] Symbol field editor dialog improvements

[Jeff Young]

Hi Ben,

You probably saw my comments in the bug that 0002 has already been addressed.

Could you change the opening and closing braces to be on their own line in 
0001?  (The rest matches our coding standard so I assume you found it, but if 
not: 
http://kicad.readthedocs.io/en/stable/Documentation/development/coding-style-policy/
 ).

Also, if you could use git format-patch to produce the patch that would be 
great.

Thanks,
Jeff.


> On 23 May 2018, at 20:42, Ben Gamari  wrote:
> 
> N.B. sending this again since the list seems to have eaten them when I
> sent them last weekend.
> 
> 
> Hi everyone,
> 
> Attached are two patches improving the usability of the symbol field
> editor dialog:
> 
> 0001: Teach the schematic editor to jump to a component when a cell in
>   the "Reference" column is clicked. I find this very helpful when
>   reviewing a design. This was in part motivated by #1772169
> 
> 0002: Save checkbox states, as requested by #1747602.
> 
> Hopefully these should be fairly uncontroversial.
> 
> Thanks!
> 
> Cheers,
> 
> - Ben
> 
> From c6d77d20bef7ab6b45fe5c4041cc2d114115 Mon Sep 17 00:00:00 2001
> From: Ben Gamari 
> Date: Sat, 19 May 2018 11:25:28 -0400
> Subject: [PATCH 1/2] field editor: Find components when reference field is
> clicked
> 
> This makes it significantly easier to find a particular component when
> using the field editor, as I often do for part selection.
> ---
> eeschema/dialogs/dialog_fields_editor_global.cpp | 13 +++--
> 1 file changed, 11 insertions(+), 2 deletions(-)
> 
> diff --git a/eeschema/dialogs/dialog_fields_editor_global.cpp 
> b/eeschema/dialogs/dialog_fields_editor_global.cpp
> index d6445f3a6..f7b0784bd 100644
> --- a/eeschema/dialogs/dialog_fields_editor_global.cpp
> +++ b/eeschema/dialogs/dialog_fields_editor_global.cpp
> @@ -166,6 +166,10 @@ public:
> return GetValue( m_rows[ aRow ], aCol );
> }
> 
> +std::vector GetRowReferences( int aRow )
> +{
> +return m_rows[ aRow ].m_Refs;
> +}
> 
> wxString GetValue( DATA_MODEL_ROW& group, int aCol )
> {
> @@ -736,9 +740,14 @@ void DIALOG_FIELDS_EDITOR_GLOBAL::OnRegroupComponents( 
> wxCommandEvent& event )
> 
> void DIALOG_FIELDS_EDITOR_GLOBAL::OnTableCellClick( wxGridEvent& event )
> {
> -if( event.GetCol() == REFERENCE )
> +if( event.GetCol() == REFERENCE ) {
> m_dataModel->ExpandCollapseRow( event.GetRow());
> -else
> +std::vector refs = m_dataModel->GetRowReferences( 
> event.GetRow() );
> +if (refs.size() == 1) {
> +m_parent->FindComponentAndItem( refs[0].GetRef() + 
> refs[0].GetRefNumber(),
> +true, FIND_COMPONENT_ONLY, 
> wxEmptyString, false );
> +}
> +} else
> event.Skip();
> }
> 
> -- 
> 2.16.2
> 
> From da4768860f416168a0c95bcdabdc7c9fac988022 Mon Sep 17 00:00:00 2001
> From: Ben Gamari 
> Date: Sat, 19 May 2018 11:47:39 -0400
> Subject: [PATCH 2/2] field editor: Save checkbox states
> 
> This teaches the field editor dialog to remember the states of the
> "Show" and "Group By" checkboxes, as requested in #1747602.
> ---
> eeschema/dialogs/dialog_fields_editor_global.cpp | 29 +---
> eeschema/dialogs/dialog_fields_editor_global.h   |  1 +
> 2 files changed, 27 insertions(+), 3 deletions(-)
> 
> diff --git a/eeschema/dialogs/dialog_fields_editor_global.cpp 
> b/eeschema/dialogs/dialog_fields_editor_global.cpp
> index f7b0784bd..976aef44d 100644
> --- a/eeschema/dialogs/dialog_fields_editor_global.cpp
> +++ b/eeschema/dialogs/dialog_fields_editor_global.cpp
> @@ -30,6 +30,7 @@
> #include 
> #include 
> #include 
> +#include 
> 
> #include 
> #include 
> @@ -514,6 +515,8 @@ DIALOG_FIELDS_EDITOR_GLOBAL::DIALOG_FIELDS_EDITOR_GLOBAL( 
> SCH_EDIT_FRAME* parent
> DIALOG_FIELDS_EDITOR_GLOBAL_BASE( parent ),
> m_parent( parent )
> {
> +m_config = Kiface().KifaceSettings();
> +
> // Get all components from the list of schematic sheets
> SCH_SHEET_LIST sheets( g_RootSheet );
> sheets.GetComponents( m_componentRefs, false );
> @@ -561,6 +564,14 @@ 
> DIALOG_FIELDS_EDITOR_GLOBAL::DIALOG_FIELDS_EDITOR_GLOBAL( SCH_EDIT_FRAME* 
> parent
> m_grid->UseNativeColHeader( true );
> m_grid->SetTable( m_dataModel, true );
> 
> +// Hide hidden-by-default fields
> +for( int row = 0; row < m_fieldsCtrl->GetItemCount(); ++row )
> +{
> +if( !m_fieldsCtrl->GetToggleValue( row, SHOW_FIELD_COLUMN ) )
> +m_grid->HideCol( row );
> +}
> +
> +
> // add Cut, Copy, and Paste to wxGrid
> m_grid->PushEventHandler( new GRID_TRICKS( m_grid ) );
> 
> @@ -636,6 +647,9 @@ void DIALOG_FIELDS_EDITOR_GLOBAL::AddField( const 
> wxString& aFieldName,
> 
> wxVector fieldsCtrlDataLine;
> 
> +m_config->Read("SymbolFieldEditor/Show/" + aFieldName, );
> +m_config->Read("SymbolFieldEditor/GroupBy/" + 

[Kicad-developers] Symbol field editor dialog improvements

[Ben Gamari]

N.B. sending this again since the list seems to have eaten them when I
sent them last weekend.


Hi everyone,

Attached are two patches improving the usability of the symbol field
editor dialog:

 0001: Teach the schematic editor to jump to a component when a cell in
   the "Reference" column is clicked. I find this very helpful when
   reviewing a design. This was in part motivated by #1772169

 0002: Save checkbox states, as requested by #1747602.

Hopefully these should be fairly uncontroversial.

Thanks!

Cheers,

- Ben



signature.asc
Description: PGP signature
>From c6d77d20bef7ab6b45fe5c4041cc2d114115 Mon Sep 17 00:00:00 2001
From: Ben Gamari 
Date: Sat, 19 May 2018 11:25:28 -0400
Subject: [PATCH 1/2] field editor: Find components when reference field is
 clicked

This makes it significantly easier to find a particular component when
using the field editor, as I often do for part selection.
---
 eeschema/dialogs/dialog_fields_editor_global.cpp | 13 +++--
 1 file changed, 11 insertions(+), 2 deletions(-)

diff --git a/eeschema/dialogs/dialog_fields_editor_global.cpp b/eeschema/dialogs/dialog_fields_editor_global.cpp
index d6445f3a6..f7b0784bd 100644
--- a/eeschema/dialogs/dialog_fields_editor_global.cpp
+++ b/eeschema/dialogs/dialog_fields_editor_global.cpp
@@ -166,6 +166,10 @@ public:
 return GetValue( m_rows[ aRow ], aCol );
 }
 
+std::vector GetRowReferences( int aRow )
+{
+return m_rows[ aRow ].m_Refs;
+}
 
 wxString GetValue( DATA_MODEL_ROW& group, int aCol )
 {
@@ -736,9 +740,14 @@ void DIALOG_FIELDS_EDITOR_GLOBAL::OnRegroupComponents( wxCommandEvent& event )
 
 void DIALOG_FIELDS_EDITOR_GLOBAL::OnTableCellClick( wxGridEvent& event )
 {
-if( event.GetCol() == REFERENCE )
+if( event.GetCol() == REFERENCE ) {
 m_dataModel->ExpandCollapseRow( event.GetRow());
-else
+std::vector refs = m_dataModel->GetRowReferences( event.GetRow() );
+if (refs.size() == 1) {
+m_parent->FindComponentAndItem( refs[0].GetRef() + refs[0].GetRefNumber(),
+true, FIND_COMPONENT_ONLY, wxEmptyString, false );
+}
+} else
 event.Skip();
 }
 
-- 
2.16.2

>From da4768860f416168a0c95bcdabdc7c9fac988022 Mon Sep 17 00:00:00 2001
From: Ben Gamari 
Date: Sat, 19 May 2018 11:47:39 -0400
Subject: [PATCH 2/2] field editor: Save checkbox states

This teaches the field editor dialog to remember the states of the
"Show" and "Group By" checkboxes, as requested in #1747602.
---
 eeschema/dialogs/dialog_fields_editor_global.cpp | 29 +---
 eeschema/dialogs/dialog_fields_editor_global.h   |  1 +
 2 files changed, 27 insertions(+), 3 deletions(-)

diff --git a/eeschema/dialogs/dialog_fields_editor_global.cpp b/eeschema/dialogs/dialog_fields_editor_global.cpp
index f7b0784bd..976aef44d 100644
--- a/eeschema/dialogs/dialog_fields_editor_global.cpp
+++ b/eeschema/dialogs/dialog_fields_editor_global.cpp
@@ -30,6 +30,7 @@
 #include 
 #include 
 #include 
+#include 
 
 #include 
 #include 
@@ -514,6 +515,8 @@ DIALOG_FIELDS_EDITOR_GLOBAL::DIALOG_FIELDS_EDITOR_GLOBAL( SCH_EDIT_FRAME* parent
 DIALOG_FIELDS_EDITOR_GLOBAL_BASE( parent ),
 m_parent( parent )
 {
+m_config = Kiface().KifaceSettings();
+
 // Get all components from the list of schematic sheets
 SCH_SHEET_LIST sheets( g_RootSheet );
 sheets.GetComponents( m_componentRefs, false );
@@ -561,6 +564,14 @@ DIALOG_FIELDS_EDITOR_GLOBAL::DIALOG_FIELDS_EDITOR_GLOBAL( SCH_EDIT_FRAME* parent
 m_grid->UseNativeColHeader( true );
 m_grid->SetTable( m_dataModel, true );
 
+// Hide hidden-by-default fields
+for( int row = 0; row < m_fieldsCtrl->GetItemCount(); ++row )
+{
+if( !m_fieldsCtrl->GetToggleValue( row, SHOW_FIELD_COLUMN ) )
+m_grid->HideCol( row );
+}
+
+
 // add Cut, Copy, and Paste to wxGrid
 m_grid->PushEventHandler( new GRID_TRICKS( m_grid ) );
 
@@ -636,6 +647,9 @@ void DIALOG_FIELDS_EDITOR_GLOBAL::AddField( const wxString& aFieldName,
 
 wxVector fieldsCtrlDataLine;
 
+m_config->Read("SymbolFieldEditor/Show/" + aFieldName, );
+m_config->Read("SymbolFieldEditor/GroupBy/" + aFieldName, );
+
 fieldsCtrlDataLine.push_back( wxVariant( aFieldName ) );
 fieldsCtrlDataLine.push_back( wxVariant( defaultShow ) );
 fieldsCtrlDataLine.push_back( wxVariant( defaultSortBy ) );
@@ -682,19 +696,28 @@ void DIALOG_FIELDS_EDITOR_GLOBAL::OnColumnItemToggled( wxDataViewEvent& event )
 default:
 break;
 
-case SHOW_FIELD_COLUMN:
-if( m_fieldsCtrl->GetToggleValue( row, col ) )
+case SHOW_FIELD_COLUMN: {
+bool value = m_fieldsCtrl->GetToggleValue( row, col );
+wxString fieldName = m_fieldsCtrl->GetTextValue(row, FIELD_NAME_COLUMN);
+m_config->Write( "SymbolFieldEditor/Show/"+fieldName, value );
+
+if( value )

Re: [Kicad-developers] Unconnected vs unrouted

[Jeff Young]

Hi Seth,

I’m pretty sure the status bar still uses the quick method of determining 
unconnected (now unrouted).  I investigated the code before making the change, 
but I could have misunderstood something….

Cheers,
Jeff.


> On 23 May 2018, at 20:31, Seth Hillbrand  wrote:
> 
> 
> ​Hi Jeff-
> 
> I believe that this distinction has been removed for V5 with the new 
> connectivity algorithm (Tom, please correct me if I'm mistaken in this!)
> 
> -S​
> 
> 
> Am So., 29. Apr. 2018 um 02:19 Uhr schrieb Jeff Young  >:
> There was a discussion on the forum regarding the difference between the 
> status line “Unconnected” count (which is actually a count of non-zero-lenght 
> ratsnest lines) and the DRC Unconnected (which is a much more thorough and 
> accurate count) [1].
> 
> PC Wiz suggested naming them differently so that the distinction would be 
> more apparent, which I agree would be an improvement.
> 
> Any objections to me renaming the status line to “Unrouted”?
> 
> Cheers,
> Jeff.
> 
> [1] 
> https://forum.kicad.info/t/unconnected-pad-not-showing-up-as-unconnected-in-status-bar/10494
>  
> 
> ___
> 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] Unconnected vs unrouted

[Seth Hillbrand]

​Hi Jeff-

I believe that this distinction has been removed for V5 with the new
connectivity algorithm (Tom, please correct me if I'm mistaken in this!)

-S​


Am So., 29. Apr. 2018 um 02:19 Uhr schrieb Jeff Young :

> There was a discussion on the forum regarding the difference between the
> status line “Unconnected” count (which is actually a count of
> non-zero-lenght ratsnest lines) and the DRC Unconnected (which is a much
> more thorough and accurate count) [1].
>
> PC Wiz suggested naming them differently so that the distinction would be
> more apparent, which I agree would be an improvement.
>
> Any objections to me renaming the status line to “Unrouted”?
>
> Cheers,
> Jeff.
>
> [1]
> https://forum.kicad.info/t/unconnected-pad-not-showing-up-as-unconnected-in-status-bar/10494
> ___
> 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] Name change in 6.0 pad properties

[Jeff Young]

Essentially pad to copper (which is where the original suggestion came from).

Specifically pad to zone, pad to pad, pad to track, pad to via, and pad to text 
on copper layer.


> On 23 May 2018, at 17:58, Clemens Koller  wrote:
> 
> On 2018-05-23 14:25, Jeff Young wrote:
>> I think "Pad clearance" is even better.
> 
> Hmm... I think it's still not precise enough. Pad-to-what-clearance?
> 
> Pad to Pad, Pad to Solder Mask, Pad to Board Outline, ...?
> 
> Regards,
> 
> Clemens
> 
>> 
>>> On 23 May 2018, at 13:03, Wayne Stambaugh  wrote:
>>> 
>>> On 5/23/2018 5:36 AM, Jeff Young wrote:
 I’ve always found the name “Net pad clearance” odd in the pad properties 
 dialog.
 
 I’m proposing to change it to “Copper clearance” to better match “Solder 
 mask clearance” and “Solder paste clearance”.
>>> 
>>> Perhaps "Pad clearance" would work as well.  Copper doesn't always imply
>>> a pad but given that this is the pad properties dialog, I guess you
>>> could assume copper implied the pad itself.
>>> 
 
 (As a side note I’m also changing “Thermal relief width” to “Thermal 
 relief spoke width”, but I assume that’s non-controversial.)
>>> 
>>> This makes sense to me.
>>> 
 
 Cheers,
 Jeff.
 
 
 ___
 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 
> 
___
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] XDG_CONFIG_HOME environment variable.

[Mike Wodarczyk]

Hi Wayne,

nice to see this is implemented into KiCAD now :)

This [1] should be added to KiCAD for convenience to the 
KICAD_CONFIG_HOME environment variable.


best regards

Mike

[1]: https://lists.launchpad.net/kicad-developers/msg35769.html


___
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] Name change in 6.0 pad properties

[Clemens Koller]

On 2018-05-23 14:25, Jeff Young wrote:
> I think "Pad clearance" is even better.

Hmm... I think it's still not precise enough. Pad-to-what-clearance?

Pad to Pad, Pad to Solder Mask, Pad to Board Outline, ...?

Regards,

Clemens

> 
>> On 23 May 2018, at 13:03, Wayne Stambaugh  wrote:
>>
>> On 5/23/2018 5:36 AM, Jeff Young wrote:
>>> I’ve always found the name “Net pad clearance” odd in the pad properties 
>>> dialog.
>>>
>>> I’m proposing to change it to “Copper clearance” to better match “Solder 
>>> mask clearance” and “Solder paste clearance”.
>>
>> Perhaps "Pad clearance" would work as well.  Copper doesn't always imply
>> a pad but given that this is the pad properties dialog, I guess you
>> could assume copper implied the pad itself.
>>
>>>
>>> (As a side note I’m also changing “Thermal relief width” to “Thermal relief 
>>> spoke width”, but I assume that’s non-controversial.)
>>
>> This makes sense to me.
>>
>>>
>>> Cheers,
>>> Jeff.
>>>
>>>
>>> ___
>>> 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] FreeRouting

[jp charras]

Le 23/05/2018 à 17:18, Brian Piccioni a écrit :
> For what it is worth, and despite knowing it is politically incorrect to 
> admit to using an autorouter, I have used Freeroute in the past and would 
> like to continue using it in the future. As much fun as manual routing is (I 
> treat it like a video game) sometimes you just want a board quickly. You can 
> always clean up dumb routes.
> 
> Moreover, like Geographic reannotation, autorouting is a normal feature for a 
> professional PCB CAD tool and its absence is the sort of thing which is 
> noticed.
> 

I agree with Brian.

And this is the exact reason I added a (poor) autorouter in Pcbnew.


> -Original Message-
> From: Kicad-developers 
>  On 
> Behalf Of Wayne Stambaugh
> Sent: May 23, 2018 9:17 AM
> To: Luca Mini 
> Cc: kicad-developers@lists.launchpad.net
> Subject: Re: [Kicad-developers] FreeRouting
> 
> Hi Luca,
> 
> Thanks for link.  It appears that we may have been a bit premature on the 
> removal of the FreeRouting dialog.  I just downloaded the latest source code 
> from the website below and the latest source file modification date is 
> 10/27/17 so it appears that our assumption that FreeRouting is no longer 
> being maintained is false.  There are even instructions on how to use KiCad 
> with FreeRouting[1] which shows the removed dialog.  Of course, we could ping 
> the FreeRouting folks to update their website to use the KiCad export and 
> import features.  Would someone please check on the user forum and see if we 
> are going to get a lot of backlash for removing this?
> 
> Thanks,
> 
> Wayne
> 
> [1]: https://freerouting.org/freerouting/using-with-kicad
> 
> On 5/23/2018 8:51 AM, Luca Mini wrote:
>> Hi Wayne,
>> I use freerouting and this link seems to be active on the "Freerouting"
>> argument.
>>
>> https://freerouting.org
>>
>> Cheers,
>> Luca
>>
>>
>> *Luca Mini*
>> Via Brione, 11/C
>> 10040 Givoletto (TO)
>> EMAIL: luca.mini.freela...@gmail.com 
>> 
>> Cell: +39 334 2459673
>>
>> 2018-05-21 18:54 GMT+02:00 Wayne Stambaugh > >:
>>
>> Hey JP,
>>
>> On 5/21/2018 12:27 PM, jp charras wrote:
>> > Le 21/05/2018 à 18:09, Seth Hillbrand a écrit :
>> >> ​Hi Wayne-
>> >>
>> >> In https://bugs.launchpad.net/bugs/1567790
>>  you mentioned that we
>> won't be supporting FreeRouting for
>> >> v5.  Should we remove this menu item/icon from the menus?
>> >>
>> >> -S​
>> >>
>> >
>> > Hi Seth,
>> >
>> > Are you talking about .dsn and .ses files export import, or the
>> menu to call FreeRoute from Pcbnew?
>> >
>> > This is really not the same thing.
>> > Many EDA tools support .dsn and .ses files export import (and this
>> import/export feature does not
>> > create issues).
>> >
>>
>> I'm OK with removing the FreeRouting dialog and menu entry.  I don't see
>> any compelling reason to keep it since we already have support for
>> Specctra dsn export and Specctra session import for users who wish to
>> continue using it.  Is FreeRouting even supported any more?  I thought
>> it hasn't been maintained for quite some time.
>>
>> Cheers,
>>
>> Wayne

-- 
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] FreeRouting

[Seth Hillbrand]

Keep in mind that we haven't removed the ability to use Freeroute.  We've
just removed the duplicate import/export dialog.  We still export SPECCTRA
and import session files.  The menu options are just under the
Import/Export menus with the other external interfaces.

-S​


Am Mi., 23. Mai 2018 um 08:18 Uhr schrieb Brian Piccioni <
br...@documenteddesigns.com>:

> For what it is worth, and despite knowing it is politically incorrect to
> admit to using an autorouter, I have used Freeroute in the past and would
> like to continue using it in the future. As much fun as manual routing is
> (I treat it like a video game) sometimes you just want a board quickly. You
> can always clean up dumb routes.
>
> Moreover, like Geographic reannotation, autorouting is a normal feature
> for a professional PCB CAD tool and its absence is the sort of thing which
> is noticed.
>
> -Original Message-
> From: Kicad-developers  documenteddesigns@lists.launchpad.net> On Behalf Of Wayne Stambaugh
> Sent: May 23, 2018 9:17 AM
> To: Luca Mini 
> Cc: kicad-developers@lists.launchpad.net
> Subject: Re: [Kicad-developers] FreeRouting
>
> Hi Luca,
>
> Thanks for link.  It appears that we may have been a bit premature on the
> removal of the FreeRouting dialog.  I just downloaded the latest source
> code from the website below and the latest source file modification date is
> 10/27/17 so it appears that our assumption that FreeRouting is no longer
> being maintained is false.  There are even instructions on how to use KiCad
> with FreeRouting[1] which shows the removed dialog.  Of course, we could
> ping the FreeRouting folks to update their website to use the KiCad export
> and import features.  Would someone please check on the user forum and see
> if we are going to get a lot of backlash for removing this?
>
> Thanks,
>
> Wayne
>
> [1]: https://freerouting.org/freerouting/using-with-kicad
>
> On 5/23/2018 8:51 AM, Luca Mini wrote:
> > Hi Wayne,
> > I use freerouting and this link seems to be active on the "Freerouting"
> > argument.
> >
> > https://freerouting.org
> >
> > Cheers,
> > Luca
> >
> >
> > *Luca Mini*
> > Via Brione, 11/C
> > 10040 Givoletto (TO)
> > EMAIL: luca.mini.freela...@gmail.com
> > 
> > Cell: +39 334 2459673
> >
> > 2018-05-21 18:54 GMT+02:00 Wayne Stambaugh  > >:
> >
> > Hey JP,
> >
> > On 5/21/2018 12:27 PM, jp charras wrote:
> > > Le 21/05/2018 à 18:09, Seth Hillbrand a écrit :
> > >> ​Hi Wayne-
> > >>
> > >> In https://bugs.launchpad.net/bugs/1567790
> >  you mentioned that we
> > won't be supporting FreeRouting for
> > >> v5.  Should we remove this menu item/icon from the menus?
> > >>
> > >> -S​
> > >>
> > >
> > > Hi Seth,
> > >
> > > Are you talking about .dsn and .ses files export import, or the
> > menu to call FreeRoute from Pcbnew?
> > >
> > > This is really not the same thing.
> > > Many EDA tools support .dsn and .ses files export import (and this
> > import/export feature does not
> > > create issues).
> > >
> >
> > I'm OK with removing the FreeRouting dialog and menu entry.  I don't
> see
> > any compelling reason to keep it since we already have support for
> > Specctra dsn export and Specctra session import for users who wish to
> > continue using it.  Is FreeRouting even supported any more?  I
> thought
> > it hasn't been maintained for quite some time.
> >
> > 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] FreeRouting

[Brian Piccioni]

For what it is worth, and despite knowing it is politically incorrect to admit 
to using an autorouter, I have used Freeroute in the past and would like to 
continue using it in the future. As much fun as manual routing is (I treat it 
like a video game) sometimes you just want a board quickly. You can always 
clean up dumb routes.

Moreover, like Geographic reannotation, autorouting is a normal feature for a 
professional PCB CAD tool and its absence is the sort of thing which is noticed.

-Original Message-
From: Kicad-developers 
 On 
Behalf Of Wayne Stambaugh
Sent: May 23, 2018 9:17 AM
To: Luca Mini 
Cc: kicad-developers@lists.launchpad.net
Subject: Re: [Kicad-developers] FreeRouting

Hi Luca,

Thanks for link.  It appears that we may have been a bit premature on the 
removal of the FreeRouting dialog.  I just downloaded the latest source code 
from the website below and the latest source file modification date is 10/27/17 
so it appears that our assumption that FreeRouting is no longer being 
maintained is false.  There are even instructions on how to use KiCad with 
FreeRouting[1] which shows the removed dialog.  Of course, we could ping the 
FreeRouting folks to update their website to use the KiCad export and import 
features.  Would someone please check on the user forum and see if we are going 
to get a lot of backlash for removing this?

Thanks,

Wayne

[1]: https://freerouting.org/freerouting/using-with-kicad

On 5/23/2018 8:51 AM, Luca Mini wrote:
> Hi Wayne,
> I use freerouting and this link seems to be active on the "Freerouting"
> argument.
> 
> https://freerouting.org
> 
> Cheers,
> Luca
> 
> 
> *Luca Mini*
> Via Brione, 11/C
> 10040 Givoletto (TO)
> EMAIL: luca.mini.freela...@gmail.com 
> 
> Cell: +39 334 2459673
> 
> 2018-05-21 18:54 GMT+02:00 Wayne Stambaugh  >:
> 
> Hey JP,
> 
> On 5/21/2018 12:27 PM, jp charras wrote:
> > Le 21/05/2018 à 18:09, Seth Hillbrand a écrit :
> >> ​Hi Wayne-
> >>
> >> In https://bugs.launchpad.net/bugs/1567790
>  you mentioned that we
> won't be supporting FreeRouting for
> >> v5.  Should we remove this menu item/icon from the menus?
> >>
> >> -S​
> >>
> >
> > Hi Seth,
> >
> > Are you talking about .dsn and .ses files export import, or the
> menu to call FreeRoute from Pcbnew?
> >
> > This is really not the same thing.
> > Many EDA tools support .dsn and .ses files export import (and this
> import/export feature does not
> > create issues).
> >
> 
> I'm OK with removing the FreeRouting dialog and menu entry.  I don't see
> any compelling reason to keep it since we already have support for
> Specctra dsn export and Specctra session import for users who wish to
> continue using it.  Is FreeRouting even supported any more?  I thought
> it hasn't been maintained for quite some time.
> 
> 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] FreeRouting

[Wayne Stambaugh]

Hi Luca,

Thanks for link.  It appears that we may have been a bit premature on
the removal of the FreeRouting dialog.  I just downloaded the latest
source code from the website below and the latest source file
modification date is 10/27/17 so it appears that our assumption that
FreeRouting is no longer being maintained is false.  There are even
instructions on how to use KiCad with FreeRouting[1] which shows the
removed dialog.  Of course, we could ping the FreeRouting folks to
update their website to use the KiCad export and import features.  Would
someone please check on the user forum and see if we are going to get a
lot of backlash for removing this?

Thanks,

Wayne

[1]: https://freerouting.org/freerouting/using-with-kicad

On 5/23/2018 8:51 AM, Luca Mini wrote:
> Hi Wayne,
> I use freerouting and this link seems to be active on the "Freerouting"
> argument.
> 
> https://freerouting.org
> 
> Cheers,
> Luca
> 
> 
> *Luca Mini*
> Via Brione, 11/C
> 10040 Givoletto (TO)
> EMAIL: luca.mini.freela...@gmail.com 
> Cell: +39 334 2459673
> 
> 2018-05-21 18:54 GMT+02:00 Wayne Stambaugh  >:
> 
> Hey JP,
> 
> On 5/21/2018 12:27 PM, jp charras wrote:
> > Le 21/05/2018 à 18:09, Seth Hillbrand a écrit :
> >> ​Hi Wayne-
> >>
> >> In https://bugs.launchpad.net/bugs/1567790
>  you mentioned that we
> won't be supporting FreeRouting for
> >> v5.  Should we remove this menu item/icon from the menus?
> >>
> >> -S​
> >>
> >
> > Hi Seth,
> >
> > Are you talking about .dsn and .ses files export import, or the
> menu to call FreeRoute from Pcbnew?
> >
> > This is really not the same thing.
> > Many EDA tools support .dsn and .ses files export import (and this
> import/export feature does not
> > create issues).
> >
> 
> I'm OK with removing the FreeRouting dialog and menu entry.  I don't see
> any compelling reason to keep it since we already have support for
> Specctra dsn export and Specctra session import for users who wish to
> continue using it.  Is FreeRouting even supported any more?  I thought
> it hasn't been maintained for quite some time.
> 
> 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] FreeRouting

[Luca Mini]

Hi Wayne,
I use freerouting and this link seems to be active on the "Freerouting"
argument.

https://freerouting.org

Cheers,
Luca


*Luca Mini*
Via Brione, 11/C
10040 Givoletto (TO)
EMAIL: luca.mini.freela...@gmail.com
Cell: +39 334 2459673

2018-05-21 18:54 GMT+02:00 Wayne Stambaugh :

> Hey JP,
>
> On 5/21/2018 12:27 PM, jp charras wrote:
> > Le 21/05/2018 à 18:09, Seth Hillbrand a écrit :
> >> ​Hi Wayne-
> >>
> >> In https://bugs.launchpad.net/bugs/1567790 you mentioned that we won't
> be supporting FreeRouting for
> >> v5.  Should we remove this menu item/icon from the menus?
> >>
> >> -S​
> >>
> >
> > Hi Seth,
> >
> > Are you talking about .dsn and .ses files export import, or the menu to
> call FreeRoute from Pcbnew?
> >
> > This is really not the same thing.
> > Many EDA tools support .dsn and .ses files export import (and this
> import/export feature does not
> > create issues).
> >
>
> I'm OK with removing the FreeRouting dialog and menu entry.  I don't see
> any compelling reason to keep it since we already have support for
> Specctra dsn export and Specctra session import for users who wish to
> continue using it.  Is FreeRouting even supported any more?  I thought
> it hasn't been maintained for quite some time.
>
> 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] [PATCH] Add python apis: GetLogicalLibs, FootprintsInLib and FootprintInfo

[miles mccoo]

bump.

;-)

To my knowledge this patch hasn't been merged or rejected.

Miles

On Wed, May 9, 2018 at 3:47 PM, Nick Østergaard  wrote:

> See the unittests in the qa folder. Thay are executed by the build job
> also.
>
>
> ons. 9. maj 2018 15.25 skrev miles mccoo :
>
>> Thank you, Jeff, for taking the time to look at my patch.
>>
>> attached is a new version of the patch. I've changed a couple things:
>>
>>- fixed the curly brace issue
>>- added blanks before each of the if statements
>>- I added a short test python function to the checkin comments[1]. It
>>exercises the new functionality[2]
>>- I added an additional function to instantiate a footprint. The only
>>other such function I'm aware of wants a full path to a library. This one
>>just takes the name of the lib
>>
>>
>> I've also posted the patch here: http://mmccoo.com/
>> random/0001-Add-the-python-apis-GetLogicalLibs-FootprintsInLib-I.patch
>>
>>
>> Miles
>>
>> [1] There's a thread on the developer list complaining about the poor
>> comments. That thread focuses on the symbol or footprint libraries. I'd
>> like to take this opportunity to comment that check comment and comments in
>> general in the kicad project they kinda suck. The code itself contains
>> very little in the way of explanation. The checkin comments are terse. I
>> haven't found any kind of design documents or discussion on the mail list.
>>
>> Hopefully someone will correct me.
>>
>>
>> [2] does kicad have anything in the way of a regression? It would be nice
>> to have some python code to be periodically executed. Compile errors is one
>> thing, but a couple APIs have disappeared in the last year. Such scripting
>> might have caught that.
>>
>>
>>
>> On Tue, May 8, 2018 at 5:36 PM, Jeff Young  wrote:
>>
>>> Hi Miles,
>>>
>>> The only coding style issue I saw was that there should be blank lines
>>> above “if” statements.
>>>
>>> Oh, and there’s still a K brace.  Search for "if ( footprint )
>>> {“.  (The brace should be down on its own line.)
>>>
>>> I didn’t correct these and merge your patch as I can’t get scripting to
>>> build on my Mac so there’s no way for me to do a quick sanity test.
>>>
>>> Cheers,
>>> Jeff.
>>>
>>>
>>> On 4 May 2018, at 09:17, miles mccoo  wrote:
>>>
>>>
>>>
>>> I submitted this patch before, but it fell through the cracks.
>>>
>>> This patch makes it possible to query pcbnew for a list of footprint
>>> libraries, and the footprints contained therein. (without reading fp-lib
>>> myself)
>>>
>>>
>>> my previous attempt: https://lists.launchpad.net/kicad-
>>> developers/msg35236.html
>>> It has some implementation notes that may be of interest.
>>>
>>>
>>> I believe I have followed the coding guidelines which I have read
>>> several times. If I missed something, please indicate more than "follow the
>>> guidelines". At least a theme. (trailing space, curlies,...)
>>>
>>>
>>> Since attachments don't seem to make it to the launchpad site, I've also
>>> made the patch file available here:
>>> http://mmccoo.com/random/0001-Add-the-python-apis-GetLogicalLibs-
>>> FootprintsInLib-a.patch
>>>
>>>
>>> Miles
>>> <0001-Add-the-python-apis-GetLogicalLibs-FootprintsInLib-a.patch>__
>>> _
>>> 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] Name change in 6.0 pad properties

[Jeff Young]

I think "Pad clearance" is even better.

> On 23 May 2018, at 13:03, Wayne Stambaugh  wrote:
> 
> On 5/23/2018 5:36 AM, Jeff Young wrote:
>> I’ve always found the name “Net pad clearance” odd in the pad properties 
>> dialog.
>> 
>> I’m proposing to change it to “Copper clearance” to better match “Solder 
>> mask clearance” and “Solder paste clearance”.
> 
> Perhaps "Pad clearance" would work as well.  Copper doesn't always imply
> a pad but given that this is the pad properties dialog, I guess you
> could assume copper implied the pad itself.
> 
>> 
>> (As a side note I’m also changing “Thermal relief width” to “Thermal relief 
>> spoke width”, but I assume that’s non-controversial.)
> 
> This makes sense to me.
> 
>> 
>> Cheers,
>> Jeff.
>> 
>> 
>> ___
>> 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] More default fields in schematic

[Wayne Stambaugh]

You may want to test this just to be sure.  We had a similar issue with
translating board layer names in the old board file format which created
a big headache when we implemented the current board file format.

On 5/23/2018 4:43 AM, Jeff Young wrote:
> Reference/Value/Footprint/Datasheet are translated only in the UI: the
> file always uses the English versions.  (Presumably external tools will
> look at the files, BOMs, netlists, etc.)
> 
>> On 23 May 2018, at 00:41, Wayne Stambaugh > > wrote:
>>
>> Wouldn't translating them defeat the purpose?  I thought the goal was
>> consistency.  If you translate them, they will be different for each
>> language and render code like kicost somewhat useless.
>>
>> On 05/22/2018 05:52 PM, Kristoffer Ödmark wrote:
>>> Yes, the only way to make them translateable is to hard-code these and
>>> other values into kicad, same as the existing hard-coded fields.
>>>
>>> That would be a good solution for me, having similar to layers a large
>>> set of predefined fields, being able to name them and enable them at
>>> will. But storing them in the files as the hard-codes values.
>>>
>>> This means a large change to the code though, at least if we must have
>>> the enable/disable feature for this, along with creating new custom
>>> fields. Not even the PCB editor has this yet. 
>>>
>>> Also, I don't think any of the bom exporter plug-ins are localized, and
>>> at least one of them completely ignores custom fields and adds it own
>>> instead, regardless of what is in the file.
>>>
>>> Meanwhile my patch does not affect existing installations, does not
>>> change any BOM, and does not enforce anything and comes in at a whooping
>>> 3-4 lines of patch in a single file. It will however add 3 lines to two
>>> dialogs (field editor and symbol editor) for new installations, which
>>> can be removed, with 6 clicks of the mouse in eeschema. 
>>>
>>> - Kristoffer 
>>>
>>> On Tue, May 22, 2018, 20:01 Jeff Young >> 
>>> > wrote:
>>>
>>>    I can confirm that default fields only get added when the symbol is
>>>    edited AND the default field’s value is non-empty.  So it doesn’t
>>>    seem to me that the proposed patch would pollute existing BOMs.  Or
>>>    am I missing something?
>>>
>>>    Seth’s comment regarding localisation is an issue, though, as we
>>>    don’t currently translate default fields.
>>>
 On 22 May 2018, at 17:53, Wayne Stambaugh 
>>>    > wrote:

 On 5/22/2018 12:43 PM, Jeff Young wrote:
>> It should output all fields defined in schematic symbols
>>>    regardless if
>> each optional field is defined in every symbol.  If they are
>>>    outputting
>> anything other than that, I would consider this a bug.
>
> I had trouble parsing this.  Are you saying that the list of
>>>    output fields should be the union of all fields which have a value
>>>    somewhere (but excluding default fields which are uniformly blank)?

 Yes.  It should be the equivalent of a logical OR.  If a field
>>>    exists in
 a single symbol, it should get added to the BOM.

>
> As it stands in 5.0, default fields don’t get pushed to symbols
>>>    unless the symbol is edited.  At that point I’m not sure if they’re
>>>    all pushed, or only those with values.
>

 It used to be that fields only get saved when they are added to the
 symbol using the edit symbol properties dialog.  That code has
>>>    changed a
 lot since it was originally written so I cannot confirm this.
>>>
>>>
>>>
>>> ___
>>> 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] Name change in 6.0 pad properties

[Wayne Stambaugh]

On 5/23/2018 5:36 AM, Jeff Young wrote:
> I’ve always found the name “Net pad clearance” odd in the pad properties 
> dialog.
> 
> I’m proposing to change it to “Copper clearance” to better match “Solder mask 
> clearance” and “Solder paste clearance”.

Perhaps "Pad clearance" would work as well.  Copper doesn't always imply
a pad but given that this is the pad properties dialog, I guess you
could assume copper implied the pad itself.

> 
> (As a side note I’m also changing “Thermal relief width” to “Thermal relief 
> spoke width”, but I assume that’s non-controversial.)

This makes sense to me.

> 
> Cheers,
> Jeff.
> 
> 
> ___
> 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] Name change in 6.0 pad properties

[Jeff Young]

I’ve always found the name “Net pad clearance” odd in the pad properties dialog.

I’m proposing to change it to “Copper clearance” to better match “Solder mask 
clearance” and “Solder paste clearance”.

(As a side note I’m also changing “Thermal relief width” to “Thermal relief 
spoke width”, but I assume that’s non-controversial.)

Cheers,
Jeff.


___
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] More default fields in schematic

[Jeff Young]

Reference/Value/Footprint/Datasheet are translated only in the UI: the file 
always uses the English versions.  (Presumably external tools will look at the 
files, BOMs, netlists, etc.)

> On 23 May 2018, at 00:41, Wayne Stambaugh  wrote:
> 
> Wouldn't translating them defeat the purpose?  I thought the goal was
> consistency.  If you translate them, they will be different for each
> language and render code like kicost somewhat useless.
> 
> On 05/22/2018 05:52 PM, Kristoffer Ödmark wrote:
>> Yes, the only way to make them translateable is to hard-code these and
>> other values into kicad, same as the existing hard-coded fields.
>> 
>> That would be a good solution for me, having similar to layers a large
>> set of predefined fields, being able to name them and enable them at
>> will. But storing them in the files as the hard-codes values.
>> 
>> This means a large change to the code though, at least if we must have
>> the enable/disable feature for this, along with creating new custom
>> fields. Not even the PCB editor has this yet. 
>> 
>> Also, I don't think any of the bom exporter plug-ins are localized, and
>> at least one of them completely ignores custom fields and adds it own
>> instead, regardless of what is in the file.
>> 
>> Meanwhile my patch does not affect existing installations, does not
>> change any BOM, and does not enforce anything and comes in at a whooping
>> 3-4 lines of patch in a single file. It will however add 3 lines to two
>> dialogs (field editor and symbol editor) for new installations, which
>> can be removed, with 6 clicks of the mouse in eeschema. 
>> 
>> - Kristoffer 
>> 
>> On Tue, May 22, 2018, 20:01 Jeff Young > >> wrote:
>> 
>>I can confirm that default fields only get added when the symbol is
>>edited AND the default field’s value is non-empty.  So it doesn’t
>>seem to me that the proposed patch would pollute existing BOMs.  Or
>>am I missing something?
>> 
>>Seth’s comment regarding localisation is an issue, though, as we
>>don’t currently translate default fields.
>> 
>>> On 22 May 2018, at 17:53, Wayne Stambaugh >> 
>>>> wrote:
>>> 
>>> On 5/22/2018 12:43 PM, Jeff Young wrote:
> It should output all fields defined in schematic symbols
>>regardless if
> each optional field is defined in every symbol.  If they are
>>outputting
> anything other than that, I would consider this a bug.
 
 I had trouble parsing this.  Are you saying that the list of
>>output fields should be the union of all fields which have a value
>>somewhere (but excluding default fields which are uniformly blank)?
>>> 
>>> Yes.  It should be the equivalent of a logical OR.  If a field
>>exists in
>>> a single symbol, it should get added to the BOM.
>>> 
 
 As it stands in 5.0, default fields don’t get pushed to symbols
>>unless the symbol is edited.  At that point I’m not sure if they’re
>>all pushed, or only those with values.
 
>>> 
>>> It used to be that fields only get saved when they are added to the
>>> symbol using the edit symbol properties dialog.  That code has
>>changed a
>>> lot since it was originally written so I cannot confirm this.
>> 
>> 
>> 
>> ___
>> 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] compiling kicad 4 with python support

[matthew venn]

couldn't get wxPython to work but didn't need it - the python module and
action scripts is enough. I still have problems building in another
directory. This is what I did:

cmake -DKICAD_SCRIPTING_WXPYTHON=OFF -DKICAD_SCRIPTING=ON
-DKICAD_SCRIPTING_ACTION_MENU=ON -DKICAD_SCRIPTING_MODULES=ON ; make ; sudo
make install

Thanks, and thanks again for all the work on kicad.
Matt

On 22 May 2018 at 20:11, matthew venn  wrote:

> Seth, thanks for the reply.
>
>
>> 1) revision ​30455092c is not KiCad 4.  But perhaps you are trying to do
>> something else.  If you wanted KiCad 4, you can checkout the tag with `git
>> checkout 4.0.7`
>>
>> ​​I tried installing kicad4 from the ppa but it didn't have the python
> stuff working. So I checked out the source to the version in my most recent
> .pro files.​
> ​
>
>
>> 2) The variables you show in the build settings after you make and
>> install are just defines.  That is, they will match what your cmake -L
>> outputs.
>>
>> ​I think maybe that forum post is confusing - the part at the end is a
> screenshot from the kicad version window - not the output of cmake -L. So
> cmake -L shows the options as I define and then after compilation and
> (successful sudo) install - the version info still shows they weren't
> enabled.
>
> I have since tried cmaking then compile/install from the root source
> directory (not ./build/release)​
>
> ​and that works! I only enabled the python module but now I have it.​
> ​ So I'm not doing something correctly
> with cmake it seems. To be clear I do this:
>
> mkdir build/release
> cd build/release
> cmake -D all the options ../../
> make
> sudo make install
>
> which doesn't work. But
>
> cmake -D all the options
> make
> sudo make install
>
> does.
> Now I'm trying to compile wxPython against gtk2 so I can have the action
> menu scripts back.
> Thanks,
> Matt​
>
>
>
> --
> Matthew Venn
> web mattvenn.net twitter @matthewvenn 
>



-- 
Matthew Venn
web mattvenn.net twitter @matthewvenn 
___
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] Jenkins build is back to normal : linux-kicad-full-gcc-head #3464

[Miguel Angel Ajo]

See 



___
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] Jenkins build is back to normal : kicad-qa #4164

[Miguel Angel Ajo]

See 


___
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] More default fields in schematic

[Clemens Koller]

Thank you for your feedback:

On 2018-05-22 17:21, Strontium wrote:
> Hello Everyone,
> 
> I like the patch, and hope it makes it in.
> 
> Clemens,  I don't think anything that is being discussed is in any way 
> going to constrain b) or c).  But I think there is a third group, not just
> 
> 1. Big Manufacturers
> 2. Hobbyist/Student
> 
> but
> 
> 3. Small Scale Professional Manufacturer.

You've put up this list of use-cases/organization sizes. This is off course not 
complete of you just take my two examples and make it 1. and 2.

Regards,

Clemens

___
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