Re: [Kicad-developers] 5.1.0 package builds

[Andrew Lutsenko]

Hi Adam,

10.14 build and 10.13 (normal) builds for Mac are identical. They both
md5sum to f392321af0513a5c6920bb89ca7831c7. Forum users are reporting that
it doesn't work on pre-Sierra OSX.
https://forum.kicad.info/t/kicad-5-1-0-released/15751/6?u=qu1ck

Regards,
Andrew

On Thu, Mar 14, 2019 at 5:36 PM Adam Wolf 
wrote:

> Thanks everyone!
>
> On Thu, Mar 14, 2019, 3:53 PM Nick Østergaard  wrote:
>
>> Release annoncement live now.
>>
>> On Thu, 14 Mar 2019 at 18:15, Wayne Stambaugh 
>> wrote:
>>
>>> Nick,
>>>
>>> I just pushed the last few changes to the release announcement so once
>>> the website download links are updated everything should be ready to go.
>>>
>>> Thanks,
>>>
>>> Wayne
>>>
>>> On 3/14/2019 11:21 AM, Nick Østergaard wrote:
>>> > Hi
>>> >
>>> > Essentially ready, meaning windows, PPA and macos builds are
>>> done/sanity
>>> > checked, but not moved to stable folder yet. Please push your tweaks
>>> for
>>> > the draft of the announcement ASAP.
>>> >
>>> > I intend to fixup the other things in a couple of hours.
>>> >
>>> > Nick
>>> >
>>> > On Thu, 14 Mar 2019 at 15:28, Wayne Stambaugh >> > > wrote:
>>> >
>>> > How are we doing on the 5.1.0 packaging?  I've only heard from
>>> > Jean-Samuel thus far.  Are the windows and macos packages ready to
>>> go
>>> > yet?  I have a few minor tweaks to make to the release
>>> announcement and
>>> > it's ready to go.  Please let me know so I can make the official
>>> release
>>> > announcement.
>>> >
>>> > 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] 5.1.0 package builds

[Adam Wolf]

Thanks everyone!

On Thu, Mar 14, 2019, 3:53 PM Nick Østergaard  wrote:

> Release annoncement live now.
>
> On Thu, 14 Mar 2019 at 18:15, Wayne Stambaugh 
> wrote:
>
>> Nick,
>>
>> I just pushed the last few changes to the release announcement so once
>> the website download links are updated everything should be ready to go.
>>
>> Thanks,
>>
>> Wayne
>>
>> On 3/14/2019 11:21 AM, Nick Østergaard wrote:
>> > Hi
>> >
>> > Essentially ready, meaning windows, PPA and macos builds are done/sanity
>> > checked, but not moved to stable folder yet. Please push your tweaks for
>> > the draft of the announcement ASAP.
>> >
>> > I intend to fixup the other things in a couple of hours.
>> >
>> > Nick
>> >
>> > On Thu, 14 Mar 2019 at 15:28, Wayne Stambaugh > > > wrote:
>> >
>> > How are we doing on the 5.1.0 packaging?  I've only heard from
>> > Jean-Samuel thus far.  Are the windows and macos packages ready to
>> go
>> > yet?  I have a few minor tweaks to make to the release announcement
>> and
>> > it's ready to go.  Please let me know so I can make the official
>> release
>> > announcement.
>> >
>> > 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] [PATCH] Option to not render 3D models for footprints

[Frank Severinsen]

Relateret bug report is here:bugs.launchpad.net/kicad/+bug/1766323The model preview does not remove it from the 3d view. Only in the footprint editor ___
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] Option to not render 3D models for footprints

[Kevin Cozens]

On 2019-03-14 4:30 a.m., Oliver Walters wrote:
This has gone unresolved for a while now - if I put in some effort to rebase 
this, is there any likelihood it will be accepted?Â


This patchset does involve a file format change to the PCB file but it is 
backwards compatible and introduces a useful new feature.


What feature is being added? AFAIK, you can control the display of 3D models 
in the dialog that lets you select a model and you can disable the display 
of 3D part models in the 3D viewer.


--
Cheers!

Kevin.

http://www.ve3syb.ca/   | "Nerds make the shiny things that
https://www.patreon.com/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] 5.1.0 package builds

[Nick Østergaard]

Release annoncement live now.

On Thu, 14 Mar 2019 at 18:15, Wayne Stambaugh  wrote:

> Nick,
>
> I just pushed the last few changes to the release announcement so once
> the website download links are updated everything should be ready to go.
>
> Thanks,
>
> Wayne
>
> On 3/14/2019 11:21 AM, Nick Østergaard wrote:
> > Hi
> >
> > Essentially ready, meaning windows, PPA and macos builds are done/sanity
> > checked, but not moved to stable folder yet. Please push your tweaks for
> > the draft of the announcement ASAP.
> >
> > I intend to fixup the other things in a couple of hours.
> >
> > Nick
> >
> > On Thu, 14 Mar 2019 at 15:28, Wayne Stambaugh  > > wrote:
> >
> > How are we doing on the 5.1.0 packaging?  I've only heard from
> > Jean-Samuel thus far.  Are the windows and macos packages ready to go
> > yet?  I have a few minor tweaks to make to the release announcement
> and
> > it's ready to go.  Please let me know so I can make the official
> release
> > announcement.
> >
> > 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 for spice netlist

[Seth Hillbrand]

Am 2019-03-14 16:02, schrieb BERTRAND Joël:



Maybe we have to use my patch with some other directives ($config and
$if for example). Indeed, following example doesn't work as expected :



Hi Joël-

You may find better application with a patch to the ngspice repository.  
We'll end up supporting this function through the library.


-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] Patch for spice netlist

[BERTRAND Joël]

BERTRAND Joël a écrit :
> Maciej Suminski a écrit :
>> Hi Bertrand,
>>
>> On 3/12/19 8:21 PM, BERTRAND Joël wrote:
>>> Hello everyone,
>>>
>>> I have written a patch for Spice netlist exporter. I spend a lot of
>>> time when I want to switch from .AC analysis to .TRAN or .NOISE. This
>>> patch allows spice exporter to use different configurations with two new
>>> instructions .if and .config.
>>>
>>> Usage :
>>> .config 
>>> .if : 
>>
>> It seems to me that ngspice already provides such means, please check
>> the ngspice manual [1], section 2.12.
>>
>> Cheers,
>> Orson
> 
>   I didn't know this ngspice feature. Thanks and forgot my patch ;-)


Maybe we have to use my patch with some other directives ($config and
$if for example). Indeed, following example doesn't work as expected :

.param ac=0
.options method=gear reltol=1m minbreak=200ps
.if (ac==1)
.ac dec 1000 1 1MEG
.control
run
.endc
.else
.tran 1u 100m 0 1u
.control
write results.raw
run
fourier 1k v("/VS+")
fourier 1k v("/VS-")
quit
.endc
.endif

Both .control/.endc blocks are run  by ngspice. That's being said only
.tran is reached ;-)

Best regards,

JB

___
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] Option to not render 3D models for footprints

[Mitja Nemec]

Or you have a multi project PCB stack and you are working on a middle board and 
would like to have an option to hide top/bottom board to get better view in 3D 
viewer. It would make the component placement faster as there would be no need 
for syncing between FreeCad and KiCad.
Mitja Nemec




  From: Marco Ciampa 
 To: kicad-developers@lists.launchpad.net 
 Sent: Thursday, 14 March 2019, 16:15
 Subject: Re: [Kicad-developers] [PATCH] Option to not render 3D models for 
footprints
   
On Thu, Mar 14, 2019 at 02:26:53PM +, Jeff Young wrote:
> Hi Wayne,
> 
> No, it would need to be saved in the file.  Think of it as Units for 3D
> models: for instance you might have 30mm, 35mm and 40mm tall capacitors
> all assigned to the single 20mm diameter 7.5mm pitch footprint.

... or the colors of LEDs? Cool!!!


--


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


   ___
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: Extract LIB_PART read/write from SCH_LEGACY_PLUGIN_CACHE

[Brian]

One more thing, actually:

Wayne, please take a look at the method 
SCH_LEGACY_PLUGIN_CACHE::checkForDuplicates() and the code in 
SCH_LEGACY_PLUGIN_CACHE::loadPart on lines 2734 - 2770.


It seems to me that the latter code does, in effect, exactly the same 
thing that checkForDuplicates() does (renaming an alias with an 
incremental number on the end).  In making loadPart static, the cache 
isn't visible so duplicate checks can't be done until the part is fully 
parsed.


I suppose the code can explain what I'm saying itself; take a look at 
the patch I've attached, wherein I've removed the checkForDuplicates 
method altogether in addition to moving the cache actions out of 
loadPart into its caller, SCH_LEGACY_PLUGIN_CACHE::Load.


Note that I've also changed several places from using std::unique_ptr< 
OUTPUTFORMATTER > & to simply OUTPUTFORMATTER &, as forcing the use of a 
unique_ptr means a caller can't safely provide a local (i.e. on the 
stack) OUTPUTFORMATTER.


Cheers,
-Brian


>From 4a1b2cde505c7a1678664710f733d5fb3f18b34e Mon Sep 17 00:00:00 2001
From: Brian Henning 
Date: Thu, 14 Mar 2019 14:57:16 -0400
Subject: [PATCH 2/2] Made LIB_PART parsing and formatting (from/to string)
 static and public

---
 eeschema/sch_legacy_plugin.cpp | 321 +
 eeschema/sch_legacy_plugin.h   |   3 +
 2 files changed, 169 insertions(+), 155 deletions(-)

diff --git a/eeschema/sch_legacy_plugin.cpp b/eeschema/sch_legacy_plugin.cpp
index 6a54953b3..ab3654e04 100644
--- a/eeschema/sch_legacy_plugin.cpp
+++ b/eeschema/sch_legacy_plugin.cpp
@@ -142,7 +142,7 @@ static bool strCompare( const char* aString, const char* aLine, const char** aOu
  * @throw An #IO_ERROR on an unexpected end of line.
  * @throw A #PARSE_ERROR if the parsed token is not a valid integer.
  */
-static int parseInt( FILE_LINE_READER& aReader, const char* aLine, const char** aOutput = NULL )
+static int parseInt( LINE_READER& aReader, const char* aLine, const char** aOutput = NULL )
 {
 if( !*aLine )
 SCH_PARSE_ERROR( _( "unexpected end of line" ), aReader, aLine );
@@ -184,7 +184,7 @@ static int parseInt( FILE_LINE_READER& aReader, const char* aLine, const char**
  * @throw IO_ERROR on an unexpected end of line.
  * @throw PARSE_ERROR if the parsed token is not a valid integer.
  */
-static unsigned long parseHex( FILE_LINE_READER& aReader, const char* aLine,
+static unsigned long parseHex( LINE_READER& aReader, const char* aLine,
const char** aOutput = NULL )
 {
 if( !*aLine )
@@ -230,7 +230,7 @@ static unsigned long parseHex( FILE_LINE_READER& aReader, const char* aLine,
  * @throw IO_ERROR on an unexpected end of line.
  * @throw PARSE_ERROR if the parsed token is not a valid integer.
  */
-static double parseDouble( FILE_LINE_READER& aReader, const char* aLine,
+static double parseDouble( LINE_READER& aReader, const char* aLine,
const char** aOutput = NULL )
 {
 if( !*aLine )
@@ -271,7 +271,7 @@ static double parseDouble( FILE_LINE_READER& aReader, const char* aLine,
  * @throw IO_ERROR on an unexpected end of line.
  * @throw PARSE_ERROR if the parsed token is not a a single character token.
  */
-static char parseChar( FILE_LINE_READER& aReader, const char* aCurrentToken,
+static char parseChar( LINE_READER& aReader, const char* aCurrentToken,
const char** aNextToken = NULL )
 {
 while( *aCurrentToken && isspace( *aCurrentToken ) )
@@ -311,7 +311,7 @@ static char parseChar( FILE_LINE_READER& aReader, const char* aCurrentToken,
  * @throw IO_ERROR on an unexpected end of line.
  * @throw PARSE_ERROR if the \a aCanBeEmpty is false and no string was parsed.
  */
-static void parseUnquotedString( wxString& aString, FILE_LINE_READER& aReader,
+static void parseUnquotedString( wxString& aString, LINE_READER& aReader,
  const char* aCurrentToken, const char** aNextToken = NULL,
  bool aCanBeEmpty = false )
 {
@@ -373,7 +373,7 @@ static void parseUnquotedString( wxString& aString, FILE_LINE_READER& aReader,
  * @throw IO_ERROR on an unexpected end of line.
  * @throw PARSE_ERROR if the \a aCanBeEmpty is false and no string was parsed.
  */
-static void parseQuotedString( wxString& aString, FILE_LINE_READER& aReader,
+static void parseQuotedString( wxString& aString, LINE_READER& aReader,
const char* aCurrentToken, const char** aNextToken = NULL,
bool aCanBeEmpty = false )
 {
@@ -476,45 +476,33 @@ class SCH_LEGACY_PLUGIN_CACHE
 int m_versionMinor;
 int m_libType;  // Is this cache a component or symbol library.
 
-LIB_PART*   loadPart( FILE_LINE_READER& aReader );
 voidloadHeader( FILE_LINE_READER& aReader );
-voidloadAliases( std::unique_ptr< LIB_PART >& aPart, FILE_LINE_READER& aReader );
-voidl

Re: [Kicad-developers] Patch: Extract LIB_PART read/write from SCH_LEGACY_PLUGIN_CACHE

[Wayne Stambaugh]

Brian,

On 3/14/2019 2:34 PM, Brian wrote:
> Wayne,
> 
> On 3/14/19 1:24 PM, Wayne Stambaugh wrote:
>> I thought so.  I take it your are storing a LIB_PART as string in each
>> row and that the database itself is acting like the library.
> Precisely.
>> Two things I forget to mention about your last patch.  Please use the
>> version test macros rather than a passing single passed to loadPart().
>> Pass the major and minor file versions and use the version macro to make
>> it clear that what your are testing.
> Fair enough.  Will do.
> 
>> Also, please don't put all of the
>> switch case statements on the same line.  It makes harder to read unless
>> you tidy them up by aligning them vertically.
> I'm not sure what you're talking about, but if you mean this:
> 
>     case 'I': pin->m_type = PIN_INPUT; break;
> 
> That's not code I wrote, and that's not my typical form (I would write
> that as three lines).  What may have happened is when I did a
> copy/paste, Kate (my editor of choice at the moment) "helpfully" sucked
> out some "excess" horizontal whitespace from what was formerly "tidied
> up" as you say.  At any rate, since this new approach doesn't involve
> moving any code between files, that particular problem shouldn't crop up.

If it's already like that, leave it as is.

> 
> On the topic of vertical alignment across lines, what do you suggest for
> this situation?
> 
> void    someFn;
> void    someOtherFn;
> wordy_return_type    outlyingFn();
> void    theLastFn();
> 
> What would you suggest for where to align the name of "outlyingFn",
> since its return type doesn't fit the column of space the rest of the
> nearby declarations need?  Should all of the names be pushed out far
> enough to accommodate "wordy_return_type"?  Or should the declaration
> for outlyingFn be moved so that it's not in the middle of the others?

I don't have a preference on this.  I typically don't align them because
I can never be sure if the next person will go through the enter file
and realign everything when they add an_even_more_wordy_return_type.

Wayne

> 
> Thanks,
> -Brian
> 
> 
> ___
> 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: Extract LIB_PART read/write from SCH_LEGACY_PLUGIN_CACHE

[Brian]

Wayne,

On 3/14/19 1:24 PM, Wayne Stambaugh wrote:

I thought so.  I take it your are storing a LIB_PART as string in each
row and that the database itself is acting like the library.

Precisely.

Two things I forget to mention about your last patch.  Please use the
version test macros rather than a passing single passed to loadPart().
Pass the major and minor file versions and use the version macro to make
it clear that what your are testing.

Fair enough.  Will do.


Also, please don't put all of the
switch case statements on the same line.  It makes harder to read unless
you tidy them up by aligning them vertically.

I'm not sure what you're talking about, but if you mean this:

    case 'I': pin->m_type = PIN_INPUT; break;

That's not code I wrote, and that's not my typical form (I would write 
that as three lines).  What may have happened is when I did a 
copy/paste, Kate (my editor of choice at the moment) "helpfully" sucked 
out some "excess" horizontal whitespace from what was formerly "tidied 
up" as you say.  At any rate, since this new approach doesn't involve 
moving any code between files, that particular problem shouldn't crop up.


On the topic of vertical alignment across lines, what do you suggest for 
this situation?


void    someFn;
void    someOtherFn;
wordy_return_type    outlyingFn();
void    theLastFn();

What would you suggest for where to align the name of "outlyingFn", 
since its return type doesn't fit the column of space the rest of the 
nearby declarations need?  Should all of the names be pushed out far 
enough to accommodate "wordy_return_type"?  Or should the declaration 
for outlyingFn be moved so that it's not in the middle of the others?


Thanks,
-Brian


___
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 for spice netlist

[BERTRAND Joël]

Maciej Suminski a écrit :
> Hi Bertrand,
> 
> On 3/12/19 8:21 PM, BERTRAND Joël wrote:
>>  Hello everyone,
>>
>>  I have written a patch for Spice netlist exporter. I spend a lot of
>> time when I want to switch from .AC analysis to .TRAN or .NOISE. This
>> patch allows spice exporter to use different configurations with two new
>> instructions .if and .config.
>>
>>  Usage :
>> .config 
>> .if : 
> 
> It seems to me that ngspice already provides such means, please check
> the ngspice manual [1], section 2.12.
> 
> Cheers,
> Orson

I didn't know this ngspice feature. Thanks and forgot my patch ;-)

Best regards,

JB

___
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: Extract LIB_PART read/write from SCH_LEGACY_PLUGIN_CACHE

[Wayne Stambaugh]

Brian,

On 3/14/2019 10:54 AM, Brian wrote:
> Good morning, Wayne.
> 
> After sleeping on it, I think I can take another crack at this idea
> that'll fit better with the points you've raised.
> 
> A couple things to clear up, just for the sake of same-pageness:
> 
>> That being said, I still don't know exactly what
>> your are parsing and formatting.  Is it the full symbol library file
>> format definition or just LIB_PART definition?  If it's just LIB_PART
>> (which I suspect it is), then there is no need to break out all of the
>> symbol library file parser code.  Only loadPart(), savePart(), and its
>> dependencies need to be broken out.
> Correct.  Just the LIB_PART parts, not the whole schematic.  It is only
> the LIB_PART parse/format code that I had split out into the static
> classes, not the code related to reading schematics.

I thought so.  I take it your are storing a LIB_PART as string in each
row and that the database itself is acting like the library.

>> You could make them static in the SCH_LEGACY_PLUGIN_CACHE as well and
>> access them through the SCH_LEGACY_PLUGIN as static.
> Agreed.  After chewing on the ideas a while, I think this makes plenty
> of sense for a second revision of my idea.

Two things I forget to mention about your last patch.  Please use the
version test macros rather than a passing single passed to loadPart().
Pass the major and minor file versions and use the version macro to make
it clear that what your are testing.  Also, please don't put all of the
switch case statements on the same line.  It makes harder to read unless
you tidy them up by aligning them vertically.

Thanks,

Wayne

> 
> I'll have a new patch for review sometime soon.
> 
> Cheers,
> -Brian
> 
> ___
> 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] 5.1.0 package builds

[Wayne Stambaugh]

Nick,

I just pushed the last few changes to the release announcement so once
the website download links are updated everything should be ready to go.

Thanks,

Wayne

On 3/14/2019 11:21 AM, Nick Østergaard wrote:
> Hi 
> 
> Essentially ready, meaning windows, PPA and macos builds are done/sanity
> checked, but not moved to stable folder yet. Please push your tweaks for
> the draft of the announcement ASAP.
> 
> I intend to fixup the other things in a couple of hours.
> 
> Nick
> 
> On Thu, 14 Mar 2019 at 15:28, Wayne Stambaugh  > wrote:
> 
> How are we doing on the 5.1.0 packaging?  I've only heard from
> Jean-Samuel thus far.  Are the windows and macos packages ready to go
> yet?  I have a few minor tweaks to make to the release announcement and
> it's ready to go.  Please let me know so I can make the official release
> announcement.
> 
> 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] afe0221d build error in eeschema/pin_numbers.cpp

[Seth Hillbrand]

Am 2019-03-14 12:18, schrieb Brian:

Wayne,

wxIsdigit is reported as an undefined symbol when compiling
eeschema/pin_numbers.cpp.

One possible solution is to add

#include 

to eeschema/pin_numbers.cpp

Patch attached.


Thanks Brian.  Patch pushed with minor modification to get the crt.h 
header that includes the system defs.


-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

[Kicad-developers] afe0221d build error in eeschema/pin_numbers.cpp

[Brian]

Wayne,

wxIsdigit is reported as an undefined symbol when compiling 
eeschema/pin_numbers.cpp.


One possible solution is to add

#include 

to eeschema/pin_numbers.cpp

Patch attached.

Cheers,
-Brian
>From c7a9dc14dc11ab0436d636e84970357e495ab2dc Mon Sep 17 00:00:00 2001
From: Brian Henning 
Date: Thu, 14 Mar 2019 12:17:02 -0400
Subject: [PATCH] Added an include to tell the compiler where to find wxIsdigit

---
 eeschema/pin_number.cpp | 1 +
 1 file changed, 1 insertion(+)

diff --git a/eeschema/pin_number.cpp b/eeschema/pin_number.cpp
index 440fe7c3c..f0e14ad1a 100644
--- a/eeschema/pin_number.cpp
+++ b/eeschema/pin_number.cpp
@@ -23,6 +23,7 @@
  */
 
 #include "pin_number.h"
+#include 
 
 namespace {
 
-- 
2.20.1

___
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] Option to not render 3D models for footprints

[Marco Ciampa]

On Thu, Mar 14, 2019 at 02:26:53PM +, Jeff Young wrote:
> Hi Wayne,
> 
> No, it would need to be saved in the file.  Think of it as Units for 3D
> models: for instance you might have 30mm, 35mm and 40mm tall capacitors
> all assigned to the single 20mm diameter 7.5mm pitch footprint.

... or the colors of LEDs? Cool!!!


--


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] 5.1.0 package builds

[Nick Østergaard]

Thank you Steven!

tor. 14. mar. 2019 16.27 skrev Steven A. Falco :

> On 3/14/19 10:26 AM, Wayne Stambaugh wrote:
> > How are we doing on the 5.1.0 packaging?  I've only heard from
> > Jean-Samuel thus far.  Are the windows and macos packages ready to go
> > yet?  I have a few minor tweaks to make to the release announcement and
> > it's ready to go.  Please let me know so I can make the official release
> > announcement.
>
> I have built 5.1.0 for Fedora Rawhide, and it is available through the
> official Fedora repository.  It has gtk3, all scripting, and ngspice
> enabled.
>
> I have also built 5.1.0 for Fedora 30 (with the same configuration as
> above), but that package won't be available for a while, because Fedora 30
> is currently in "beta freeze".
>
> Steve
>
> ___
> 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] 5.1.0 package builds

[Steven A. Falco]

On 3/14/19 10:26 AM, Wayne Stambaugh wrote:
> How are we doing on the 5.1.0 packaging?  I've only heard from
> Jean-Samuel thus far.  Are the windows and macos packages ready to go
> yet?  I have a few minor tweaks to make to the release announcement and
> it's ready to go.  Please let me know so I can make the official release
> announcement.

I have built 5.1.0 for Fedora Rawhide, and it is available through the official 
Fedora repository.  It has gtk3, all scripting, and ngspice enabled.

I have also built 5.1.0 for Fedora 30 (with the same configuration as above), 
but that package won't be available for a while, because Fedora 30 is currently 
in "beta freeze".

Steve

___
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] 5.1.0 package builds

[Nick Østergaard]

Hi

Essentially ready, meaning windows, PPA and macos builds are done/sanity
checked, but not moved to stable folder yet. Please push your tweaks for
the draft of the announcement ASAP.

I intend to fixup the other things in a couple of hours.

Nick

On Thu, 14 Mar 2019 at 15:28, Wayne Stambaugh  wrote:

> How are we doing on the 5.1.0 packaging?  I've only heard from
> Jean-Samuel thus far.  Are the windows and macos packages ready to go
> yet?  I have a few minor tweaks to make to the release announcement and
> it's ready to go.  Please let me know so I can make the official release
> announcement.
>
> 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: Extract LIB_PART read/write from SCH_LEGACY_PLUGIN_CACHE

[Brian]

Good morning, Wayne.

After sleeping on it, I think I can take another crack at this idea 
that'll fit better with the points you've raised.


A couple things to clear up, just for the sake of same-pageness:


That being said, I still don't know exactly what
your are parsing and formatting.  Is it the full symbol library file
format definition or just LIB_PART definition?  If it's just LIB_PART
(which I suspect it is), then there is no need to break out all of the
symbol library file parser code.  Only loadPart(), savePart(), and its
dependencies need to be broken out.
Correct.  Just the LIB_PART parts, not the whole schematic.  It is only 
the LIB_PART parse/format code that I had split out into the static 
classes, not the code related to reading schematics.

You could make them static in the SCH_LEGACY_PLUGIN_CACHE as well and
access them through the SCH_LEGACY_PLUGIN as static.
Agreed.  After chewing on the ideas a while, I think this makes plenty 
of sense for a second revision of my idea.


I'll have a new patch for review sometime soon.

Cheers,
-Brian

___
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] 5.1.0 package builds

[Wayne Stambaugh]

How are we doing on the 5.1.0 packaging?  I've only heard from
Jean-Samuel thus far.  Are the windows and macos packages ready to go
yet?  I have a few minor tweaks to make to the release announcement and
it's ready to go.  Please let me know so I can make the official release
announcement.

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] [PATCH] Option to not render 3D models for footprints

[Jeff Young]

Hi Wayne,

No, it would need to be saved in the file.  Think of it as Units for 3D models: 
for instance you might have 30mm, 35mm and 40mm tall capacitors all assigned to 
the single 20mm diameter 7.5mm pitch footprint.

Cheers,
Jeff.


> On 14 Mar 2019, at 13:38, Wayne Stambaugh  wrote:
> 
> Jeff,
> 
> I haven't looked at Oliver's patch so I'm flying blind here.  My
> question is why does this require a board change.  Is this a state we
> really need to save in the board file or could it be some 3D viewer
> visibility state option saved in a config file?  I would prefer the
> latter if possible.  I guess I don't understand the purpose of this.
> 
> Cheers,
> 
> Wayne
> 
> On 3/14/2019 6:44 AM, Jeff Young wrote:
>> @Wayne, this builds on top of my m_Preview addition so I’m happy to
>> review it and merge it after Oliver re-bases.  But where do we stand on
>> PCBNew file format changes for 6.0?  (There are also some hold-overs I
>> have from 5.1; namely storing defined diff pair dimensions and the
>> courtyard DRC settings in the files.
>> 
>>> On 14 Mar 2019, at 08:30, Oliver Walters
>>> mailto:oliver.henry.walt...@gmail.com>
>>> >> >> wrote:
>>> 
>>> This has gone unresolved for a while now - if I put in some effort to
>>> rebase this, is there any likelihood it will be accepted? 
>>> 
>>> This patchset does involve a file format change to the PCB file but it
>>> is backwards compatible and introduces a useful new feature.
>>> 
>>> On Tue, Oct 30, 2018 at 11:27 PM Oliver Walters
>>> mailto:oliver.henry.walt...@gmail.com>
>>> >> >> wrote:
>>> 
>>>The attached patchset expands on the "Preview" checkbox in the 3D
>>>model tab in the footprint editor. 
>>> 
>>>This "Preview" option currently only applies to the preview
>>>window. However if the user wishes to disable display of a given
>>>3D model in the PCB renderer they must delete the 3D model from
>>>the footprint entirely.
>>> 
>>>The new patchset does the following:
>>> 
>>>1) The state of the m_Preview parameter for each 3D model is
>>>observed in the various 3D renderers and exporters
>>> 
>>>2) The m_Preview parameter is saved to file (both .kicad_mod and
>>>.kicad_pcb)
>>> 
>>>With regard to file saving, if the 3D model is "enabled" (default
>>>state) then the file is unchanged making this change largely
>>>backwards compatible. If the 3D model is disabled, then the
>>>keyword "(disabled)" is added to the file.
>>> 
>>>You can now quickly toggle 3D models on/off on an individual basis
>>>and this is statefully saved between sessions.
>>> 
>>>Patch-set is rebased and compiled
>>>from b445b0fab28f7dd41273801d06d7705215c57c0f
>>> 
>>>Regards,
>>> 
>>> ___
>>> 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] [PATCH] Option to not render 3D models for footprints

[Wayne Stambaugh]

Jeff,

I haven't looked at Oliver's patch so I'm flying blind here.  My
question is why does this require a board change.  Is this a state we
really need to save in the board file or could it be some 3D viewer
visibility state option saved in a config file?  I would prefer the
latter if possible.  I guess I don't understand the purpose of this.

Cheers,

Wayne

On 3/14/2019 6:44 AM, Jeff Young wrote:
> @Wayne, this builds on top of my m_Preview addition so I’m happy to
> review it and merge it after Oliver re-bases.  But where do we stand on
> PCBNew file format changes for 6.0?  (There are also some hold-overs I
> have from 5.1; namely storing defined diff pair dimensions and the
> courtyard DRC settings in the files.
> 
>> On 14 Mar 2019, at 08:30, Oliver Walters
>> > > wrote:
>>
>> This has gone unresolved for a while now - if I put in some effort to
>> rebase this, is there any likelihood it will be accepted? 
>>
>> This patchset does involve a file format change to the PCB file but it
>> is backwards compatible and introduces a useful new feature.
>>
>> On Tue, Oct 30, 2018 at 11:27 PM Oliver Walters
>> > > wrote:
>>
>> The attached patchset expands on the "Preview" checkbox in the 3D
>> model tab in the footprint editor. 
>>
>> This "Preview" option currently only applies to the preview
>> window. However if the user wishes to disable display of a given
>> 3D model in the PCB renderer they must delete the 3D model from
>> the footprint entirely.
>>
>> The new patchset does the following:
>>
>> 1) The state of the m_Preview parameter for each 3D model is
>> observed in the various 3D renderers and exporters
>>
>> 2) The m_Preview parameter is saved to file (both .kicad_mod and
>> .kicad_pcb)
>>
>> With regard to file saving, if the 3D model is "enabled" (default
>> state) then the file is unchanged making this change largely
>> backwards compatible. If the 3D model is disabled, then the
>> keyword "(disabled)" is added to the file.
>>
>> You can now quickly toggle 3D models on/off on an individual basis
>> and this is statefully saved between sessions.
>>
>> Patch-set is rebased and compiled
>> from b445b0fab28f7dd41273801d06d7705215c57c0f
>>
>> Regards,
>>
>> ___
>> 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] Feedback on 5.1

[Wayne Stambaugh]

I'm not opposed to CAD like snapping features.  They certainly can be
useful.  It probably wont happen any time soon.  V6 is about getting the
schematic editor modernized and adding some missing board layout
features so I doubt there will be time to fit this into the schedule.
It could be a V7 road map item.

Wayne

On 3/14/2019 5:04 AM, José Ignacio wrote:
> One good example of a really flexible snapping system is what Autocad
> does with OSNAP and OTRACK modes
> 
> Object snap (OSNAP) creates snap points from many features in the
> objects or interaction between objects. an important feature is that the
> different classes of snapping points active at any time are user-selectable:
> 
> image.png
> 
> Most types are self explanatory, endpoints of lines and arcs, center
> points, midpoints and quadrants. extensions from endpoints and
> intersection between lines, arcs, circles or combinations. When they are
> activated they work as a simple "magnet" for the active tool. another
> very useful feature is that the UI shows a distinctive icon for each
> kind of different snapping point, so it is easy to tell if you are
> snapping to the correct thing. Eg squares for endpoints, triangles for
> midpoints, diamonds for quadrants, circles for centers, etc.
> 
> Object Snap Tracking (OTRACK) is the really delicious thing. if you
> hover over an object snap point for a couple seconds, it "sticks", now
> tracks shooting out of those points are snapping guides, and you can
> snap to the intersection of such, it is hard to explain how much it
> improves the drafting experience but this page does a pretty good job of
> describing it with pictures:
> http://www.ccadinc.com/autocad-tutorials-otrack.html
> 
> 
> I'm not saying we have to copy autocad... but the tools are a bit of an
> industry standard in the drafting world and they really improve
> productivity when you have to lay down lines, arcs and have all of them
> line up perfectly, with some practice you can make very complex shapes
> using construction geometry and the snapping system.
> 
> 
> 
> On Thu, Mar 14, 2019 at 3:48 AM Eeli Kaikkonen  > wrote:
> 
> ke 13. maalisk. 2019 klo 19.51 Wayne Stambaugh (stambau...@gmail.com
> ) kirjoitti:
> 
> On 3/12/2019 1:21 PM, Ruth Ivimey-Cook wrote:
> 
> >  4. Pcb: is there a chance of a smart snap - where the editor
> looks for
> >     things to line up the cursor with (e.g. while moving 1
> wire it looks
> >     to see if there is another wire nearly in line with it, or
> while
> >     moving a component it checks to see when this component is
> 1/2 way
> >     between two other components?)
> 
> I'm not sure what you mean precisely mean by this.
> 
> 
> I have given thought to something like this. Technically my
> proposition would be a bit more generic.
> 
> There could be an "alternative grid" which would consist of lines
> going through special points of items. Now the grid can be thought
> of as horizontal and vertical lines and each grid point has one of
> each. In a regular grid most of the lines converge, i.e. points 1,0
> and 2,0 have the same horizontal line but different vertical lines.
> 
> The proposed alternative grid would be activated with for example a
> hotkey. The normal grid would disappear. Instead there would be an
> irregular grid where every horizontal and vertical line would go
> through at least one special point of some item. Special points
> would be for example anchor points of footprints and end/start
> points of lines or track segments. When moving an item the beginning
> point of the movement would be a special point, too (like it is even
> now, I think, so that you can move horizontally without changing
> vertical coordinate or vice versa). The grid would consist of all
> those special points and all crossings of these alternative grid lines.
> 
> To be really useful this should be configurable with regards to
> special points. Many footprints would be simple enough that all
> special points could be active. I would include corner points of
> pads to the special points (and would like to have an ability to
> grab a pad from a corner or from the mid point of an edge). But for
> most boards the alternative grid would soon become too crowded to be
> practical. Therefore the user should be able to select which points
> are used as special points. For example only center points of
> footprints or only vias or only track segments or some combination.
> 
> This wouldn't help with finding the mid point ("1/2 way") between
> two points. But I have missed such a feature many times, especially
> when drawing outlines and other graphics. It's quite tedious to
> calculate mid points and hit or mark them.
> 
> Eeli Kaikkonen

Re: [Kicad-developers] [PATCH] Option to not render 3D models for footprints

[Jeff Young]

@Wayne, this builds on top of my m_Preview addition so I’m happy to review it 
and merge it after Oliver re-bases.  But where do we stand on PCBNew file 
format changes for 6.0?  (There are also some hold-overs I have from 5.1; 
namely storing defined diff pair dimensions and the courtyard DRC settings in 
the files.

> On 14 Mar 2019, at 08:30, Oliver Walters  
> wrote:
> 
> This has gone unresolved for a while now - if I put in some effort to rebase 
> this, is there any likelihood it will be accepted? 
> 
> This patchset does involve a file format change to the PCB file but it is 
> backwards compatible and introduces a useful new feature.
> 
> On Tue, Oct 30, 2018 at 11:27 PM Oliver Walters 
> mailto:oliver.henry.walt...@gmail.com>> 
> wrote:
> The attached patchset expands on the "Preview" checkbox in the 3D model tab 
> in the footprint editor. 
> 
> This "Preview" option currently only applies to the preview window. However 
> if the user wishes to disable display of a given 3D model in the PCB renderer 
> they must delete the 3D model from the footprint entirely.
> 
> The new patchset does the following:
> 
> 1) The state of the m_Preview parameter for each 3D model is observed in the 
> various 3D renderers and exporters
> 
> 2) The m_Preview parameter is saved to file (both .kicad_mod and .kicad_pcb)
> 
> With regard to file saving, if the 3D model is "enabled" (default state) then 
> the file is unchanged making this change largely backwards compatible. If the 
> 3D model is disabled, then the keyword "(disabled)" is added to the file.
> 
> You can now quickly toggle 3D models on/off on an individual basis and this 
> is statefully saved between sessions.
> 
> Patch-set is rebased and compiled from 
> b445b0fab28f7dd41273801d06d7705215c57c0f
> 
> Regards,
> 
> ___
> 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 for spice netlist

[Maciej Suminski]

Hi Bertrand,

On 3/12/19 8:21 PM, BERTRAND Joël wrote:
>   Hello everyone,
> 
>   I have written a patch for Spice netlist exporter. I spend a lot of
> time when I want to switch from .AC analysis to .TRAN or .NOISE. This
> patch allows spice exporter to use different configurations with two new
> instructions .if and .config.
> 
>   Usage :
> .config 
> .if : 

It seems to me that ngspice already provides such means, please check
the ngspice manual [1], section 2.12.

Cheers,
Orson

1. https://ftp.cs.up.ac.za/gentoo/distfiles/ngspice-27-manual.pdf

___
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] Feedback on 5.1

[Eeli Kaikkonen]

to 14. maalisk. 2019 klo 11.04 José Ignacio (jose.cyb...@gmail.com)
kirjoitti:

> One good example of a really flexible snapping system is what Autocad does
> with OSNAP and OTRACK modes
>


> On Thu, Mar 14, 2019 at 3:48 AM Eeli Kaikkonen 
> wrote:
> I have given thought to something like this. Technically my proposition
> would be a bit more generic.
>
>
Well, it looks like if you've never seen a vehicle you end up inventing a
square wheel... But maybe this shows that the idea is basically good. I
don't know the internals of KiCad but I can see how it works and am
inclined to think that my proposition would only extend the existing
functionalities like the grid system and special snapping points, so it
wouldn't need rewriting the application.

Eeli Kaikkonen
___
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] Feedback on 5.1

[José Ignacio]

One good example of a really flexible snapping system is what Autocad does
with OSNAP and OTRACK modes

Object snap (OSNAP) creates snap points from many features in the objects
or interaction between objects. an important feature is that the different
classes of snapping points active at any time are user-selectable:

[image: image.png]

Most types are self explanatory, endpoints of lines and arcs, center
points, midpoints and quadrants. extensions from endpoints and intersection
between lines, arcs, circles or combinations. When they are activated they
work as a simple "magnet" for the active tool. another very useful feature
is that the UI shows a distinctive icon for each kind of different snapping
point, so it is easy to tell if you are snapping to the correct thing. Eg
squares for endpoints, triangles for midpoints, diamonds for quadrants,
circles for centers, etc.

Object Snap Tracking (OTRACK) is the really delicious thing. if you hover
over an object snap point for a couple seconds, it "sticks", now tracks
shooting out of those points are snapping guides, and you can snap to the
intersection of such, it is hard to explain how much it improves the
drafting experience but this page does a pretty good job of describing it
with pictures: http://www.ccadinc.com/autocad-tutorials-otrack.html


I'm not saying we have to copy autocad... but the tools are a bit of an
industry standard in the drafting world and they really improve
productivity when you have to lay down lines, arcs and have all of them
line up perfectly, with some practice you can make very complex shapes
using construction geometry and the snapping system.



On Thu, Mar 14, 2019 at 3:48 AM Eeli Kaikkonen 
wrote:

> ke 13. maalisk. 2019 klo 19.51 Wayne Stambaugh (stambau...@gmail.com)
> kirjoitti:
>
>> On 3/12/2019 1:21 PM, Ruth Ivimey-Cook wrote:
>>
>> >  4. Pcb: is there a chance of a smart snap - where the editor looks for
>> > things to line up the cursor with (e.g. while moving 1 wire it looks
>> > to see if there is another wire nearly in line with it, or while
>> > moving a component it checks to see when this component is 1/2 way
>> > between two other components?)
>>
>> I'm not sure what you mean precisely mean by this.
>>
>>
> I have given thought to something like this. Technically my proposition
> would be a bit more generic.
>
> There could be an "alternative grid" which would consist of lines going
> through special points of items. Now the grid can be thought of as
> horizontal and vertical lines and each grid point has one of each. In a
> regular grid most of the lines converge, i.e. points 1,0 and 2,0 have the
> same horizontal line but different vertical lines.
>
> The proposed alternative grid would be activated with for example a
> hotkey. The normal grid would disappear. Instead there would be an
> irregular grid where every horizontal and vertical line would go through at
> least one special point of some item. Special points would be for example
> anchor points of footprints and end/start points of lines or track
> segments. When moving an item the beginning point of the movement would be
> a special point, too (like it is even now, I think, so that you can move
> horizontally without changing vertical coordinate or vice versa). The grid
> would consist of all those special points and all crossings of these
> alternative grid lines.
>
> To be really useful this should be configurable with regards to special
> points. Many footprints would be simple enough that all special points
> could be active. I would include corner points of pads to the special
> points (and would like to have an ability to grab a pad from a corner or
> from the mid point of an edge). But for most boards the alternative grid
> would soon become too crowded to be practical. Therefore the user should be
> able to select which points are used as special points. For example only
> center points of footprints or only vias or only track segments or some
> combination.
>
> This wouldn't help with finding the mid point ("1/2 way") between two
> points. But I have missed such a feature many times, especially when
> drawing outlines and other graphics. It's quite tedious to calculate mid
> points and hit or mark them.
>
> Eeli Kaikkonen
> ___
> 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] Feedback on 5.1

[Eeli Kaikkonen]

ke 13. maalisk. 2019 klo 19.51 Wayne Stambaugh (stambau...@gmail.com)
kirjoitti:

> On 3/12/2019 1:21 PM, Ruth Ivimey-Cook wrote:
>
> >  4. Pcb: is there a chance of a smart snap - where the editor looks for
> > things to line up the cursor with (e.g. while moving 1 wire it looks
> > to see if there is another wire nearly in line with it, or while
> > moving a component it checks to see when this component is 1/2 way
> > between two other components?)
>
> I'm not sure what you mean precisely mean by this.
>
>
I have given thought to something like this. Technically my proposition
would be a bit more generic.

There could be an "alternative grid" which would consist of lines going
through special points of items. Now the grid can be thought of as
horizontal and vertical lines and each grid point has one of each. In a
regular grid most of the lines converge, i.e. points 1,0 and 2,0 have the
same horizontal line but different vertical lines.

The proposed alternative grid would be activated with for example a hotkey.
The normal grid would disappear. Instead there would be an irregular grid
where every horizontal and vertical line would go through at least one
special point of some item. Special points would be for example anchor
points of footprints and end/start points of lines or track segments. When
moving an item the beginning point of the movement would be a special
point, too (like it is even now, I think, so that you can move horizontally
without changing vertical coordinate or vice versa). The grid would consist
of all those special points and all crossings of these alternative grid
lines.

To be really useful this should be configurable with regards to special
points. Many footprints would be simple enough that all special points
could be active. I would include corner points of pads to the special
points (and would like to have an ability to grab a pad from a corner or
from the mid point of an edge). But for most boards the alternative grid
would soon become too crowded to be practical. Therefore the user should be
able to select which points are used as special points. For example only
center points of footprints or only vias or only track segments or some
combination.

This wouldn't help with finding the mid point ("1/2 way") between two
points. But I have missed such a feature many times, especially when
drawing outlines and other graphics. It's quite tedious to calculate mid
points and hit or mark them.

Eeli Kaikkonen
___
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] Option to not render 3D models for footprints

[Oliver Walters]

This has gone unresolved for a while now - if I put in some effort to
rebase this, is there any likelihood it will be accepted?

This patchset does involve a file format change to the PCB file but it is
backwards compatible and introduces a useful new feature.

On Tue, Oct 30, 2018 at 11:27 PM Oliver Walters <
oliver.henry.walt...@gmail.com> wrote:

> The attached patchset expands on the "Preview" checkbox in the 3D model
> tab in the footprint editor.
>
> This "Preview" option currently only applies to the preview window.
> However if the user wishes to disable display of a given 3D model in the
> PCB renderer they must delete the 3D model from the footprint entirely.
>
> The new patchset does the following:
>
> 1) The state of the m_Preview parameter for each 3D model is observed in
> the various 3D renderers and exporters
>
> 2) The m_Preview parameter is saved to file (both .kicad_mod and
> .kicad_pcb)
>
> With regard to file saving, if the 3D model is "enabled" (default state)
> then the file is unchanged making this change largely backwards compatible.
> If the 3D model is disabled, then the keyword "(disabled)" is added to the
> file.
>
> You can now quickly toggle 3D models on/off on an individual basis and
> this is statefully saved between sessions.
>
> Patch-set is rebased and compiled
> from b445b0fab28f7dd41273801d06d7705215c57c0f
>
> Regards,
>
>
___
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 for spice netlist

[BERTRAND Joël]

Seth Hillbrand a écrit :
> Am 2019-03-12 15:21, schrieb BERTRAND Joël:
>> Hello everyone,
>>
>> I have written a patch for Spice netlist exporter. I spend a lot of
>> time when I want to switch from .AC analysis to .TRAN or .NOISE. This
>> patch allows spice exporter to use different configurations with two new
>> instructions .if and .config.
> 
> Hi Joël-
> 
> Thank you for the patch.  I am not sure I understand the full use case,
> however.  Normally, I would simply have the .ac and .tran lines in two
> separate lines and add/remove the '.' at the beginning to denote which I
> want to run.  I think that ngspice already supports 'ternary_fcn' for an
> if/then/else condition.
> 
> Maybe Holger can weigh in on the pro/cons of adding directives in KiCad?
> 
> -Seth

Hello Seth,

It's not only for .ac or .tran directive, but to use .if in control
statement block. That's being said, it is possible to write several
control blocks in differents text blocks.

Best regards,

JB

___
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