Re: [Kicad-developers] [PATCH] get initial Python 3 support

[Nick Østergaard]

Hi Thomas,

I am happy to see that we port to python3 for various reasons, that
should be obvious to everyone.

I have been testing your branch a bit on windows, just to get an
overview of what changes might be needed. So far I think I made it
work as you have on linux.

A lite installer is available on [link will disappear eventually]
http://downloads.kicad-pcb.org/windows/testing/patched/kicad-patched-88-review-8244-gef7a2fcc3-x86_64.exe

The build is of course with wxpython disabled, as it is my
understanding that it does not support python3, and the next step is
to migrate to wx phoenix which should indeed support python3.

I could start the python.exe inside the kicad/bin dir and import
pcbnew without errors.

I did not try to run any standalone scripts.

I did try a couple of footprint wizards in the footprint editor, and
some of them seemingly worked. But the BARCODE USS-39 errors. It looks
like it needs to be updated to py3k syntax.

Regards
Nick Østergaard
Den lør. 4. aug. 2018 kl. 12.23 skrev Thomas Pointhuber
:
>
> Hi,
>
> I managed to get KiCad to run with Python 3 as well as did some quick
> verification that basic methods are working using CLI (loading boards,
> calling a method of it).
>
> Bugreport: https://bugs.launchpad.net/kicad/+bug/1785119
>
> My Branch: https://github.com/pointhi/kicad-source-mirror/tree/python3
>
> scripting inside of kicad was not tested because I'm not really familiar
> with it right now, as well as because of known wx problems with that stuff.
>
> For now it can be enabled using -DKICAD_SCRIPTING_PYTHON3=ON
> It is not possible to export modules for python 2 and python 3 with one
> build at the moment, but this should a thing which can be fixed in the
> build-script.
>
> I made some small changes to existing python code to get it working on
> both versions. To my knowledge and tests the scripts should not have
> changed behavior.
>
> Regards, Thomas
>
> ___
> 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] big changes to eeschama

[Jeff Young]

Hi Tom,

Was it just the “leakage” into the frames (LIB_EDIT_FRAME and LIB_VIEW_FRAME) 
that caused issue, or all the dialog stuff too?

There are some issues with dialogs still to clean up (around how kill-focus 
validation interacts with the operation that caused the kill-focus), but they 
don’t seem to be causing anyone any great grief so they could probably wait.

Cheers,
Jeff.


> On 14 Aug 2018, at 18:15, Tomasz Wlostowski  wrote:
> 
> On 01/08/18 22:36, Jeff Young wrote:
>> The dialog work is pretty much done.  There was a recent refactoring to push 
>> the ComponentTree down into common so it could be used for the Footprint 
>> Editor & Place Footprint dialogs, but that should be the last of it.
>> 
> Jeff,
> 
> A gentle reminder: I've been asking all the devs to reduce the number of
> changes to eeschema while we work on the GAL stuff critical for v5.1. I
> had quite some trouble rebasing my 2-week old code on the top of today's
> master.
> 
> Tom


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

Re: [Kicad-developers] Is errno defined on MSW?

[Reece R. Pollack]

In any Posix-compliant implementation, errno has been thread-safe for 
decades without any need for special versions of fopen or other stdio 
library functions.


Of course, if we're talking about Microsloth, who can tell.


On 08/13/18 23:54, Mark Roszko wrote:

Yes, errno and fopen behave the same on windows.

You may want to consider looking into fopen_s which Windows and gcc 
using C11 or newer should have. It makes errno threadsafe among other 
safety improvements.


On Mon, Aug 13, 2018 at 5:13 PM Jeff Young > wrote:


While I can’t test it, Microsoft’s doc certainly suggests they
support it equivalently enough for our purposes:

https://msdn.microsoft.com/en-us/library/5814770t.aspx

Cheers,
Jeff.




> On 13 Aug 2018, at 21:30, Jeff Young mailto:j...@rokeby.ie>> wrote:
>
> I’m putting in some more/better error messages to try and catch
a file-save issue some folks are having [1].
>
> Is errno defined on MSW?
>
> Thanks,
> Jeff.
>
> [1] https://bugs.launchpad.net/kicad/+bug/1786512
> ___
> 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



--
Mark


___
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] big changes to eeschama

[Tomasz Wlostowski]

On 01/08/18 22:36, Jeff Young wrote:
> The dialog work is pretty much done.  There was a recent refactoring to push 
> the ComponentTree down into common so it could be used for the Footprint 
> Editor & Place Footprint dialogs, but that should be the last of it.
> 
Jeff,

A gentle reminder: I've been asking all the devs to reduce the number of
changes to eeschema while we work on the GAL stuff critical for v5.1. I
had quite some trouble rebasing my 2-week old code on the top of today's
master.

Tom

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

Re: [Kicad-developers] MSW directory performance patch

[Seth Hillbrand]

Makes sense.  If it were simple, might be worth it but I'm happy to have
that one stick with 5.1+

-Seth

Am Di., 14. Aug. 2018 um 07:48 Uhr schrieb Wayne Stambaugh <
stambau...@gmail.com>:

> I am opposed to ripping apart merges to backport them to the 5.0 branch.
>  There is too much room for error.  It's one thing to fix a merge
> conflict when cherry picking.  It is an altogether different thing to
> backport part of a commit.  This is why you should make commits as
> atomic as possible.  If the time stamping commits could be cherry picked
> unmodified without dragging any other 5.1 work into the 5.0 branch I
> would be OK with that.  The problem is, any edited merges would not be
> tested as they were committed to the development branch which means the
> testing done by users running nightly builds would may not be valid.
> AFAIK, very little testing gets done on the stable branch so we depend
> on the nightly build testing to confirm our bug fixes don't cause any
> other issues.
>
> Cheers,
>
> Wayne
>
> On 8/13/2018 2:50 PM, Jeff Young wrote:
> > Hi Seth,
> >
> > It’s built on top of earlier changes,
> > namely be1d6113d6a81bc414e06c5d080cc4917f5de1f1.
> >
> > While that one's quite large, we could hand-edit out the
> > directory-timestamping part.  It’d be a bit of work as we have to move
> > from timestamping the files in the cache to timestamping the files in
> > the directory, and we have to do that uniformly across save, load, and
> > check-cache.
> >
> > But it could be done.
> >
> > Cheers,
> > Jeff.
> >
> >
> >> On 13 Aug 2018, at 18:06, Seth Hillbrand  >> > wrote:
> >>
> >> Hi Jeff and others-
> >>
> >> Is there anything that would prevent us from merging f6f1c1e94 into
> >> the 5.0.1 branch?  I was talking with an engineer on Twitter[1] about
> >> some performance issues they were having assigning footprints in cvpcb
> >> using MSW.  It sounded like it might be addressed by that work.
> >>
> >> -S
> >>
> >> [1] https://twitter.com/MayaPosch/status/1027660207709728769
> >>
> >> ___
> >> 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] MSW directory performance patch

[Wayne Stambaugh]

I am opposed to ripping apart merges to backport them to the 5.0 branch.
 There is too much room for error.  It's one thing to fix a merge
conflict when cherry picking.  It is an altogether different thing to
backport part of a commit.  This is why you should make commits as
atomic as possible.  If the time stamping commits could be cherry picked
unmodified without dragging any other 5.1 work into the 5.0 branch I
would be OK with that.  The problem is, any edited merges would not be
tested as they were committed to the development branch which means the
testing done by users running nightly builds would may not be valid.
AFAIK, very little testing gets done on the stable branch so we depend
on the nightly build testing to confirm our bug fixes don't cause any
other issues.

Cheers,

Wayne

On 8/13/2018 2:50 PM, Jeff Young wrote:
> Hi Seth,
> 
> It’s built on top of earlier changes,
> namely be1d6113d6a81bc414e06c5d080cc4917f5de1f1.
> 
> While that one's quite large, we could hand-edit out the
> directory-timestamping part.  It’d be a bit of work as we have to move
> from timestamping the files in the cache to timestamping the files in
> the directory, and we have to do that uniformly across save, load, and
> check-cache.
> 
> But it could be done.
> 
> Cheers,
> Jeff.
> 
> 
>> On 13 Aug 2018, at 18:06, Seth Hillbrand > > wrote:
>>
>> Hi Jeff and others-
>>
>> Is there anything that would prevent us from merging f6f1c1e94 into
>> the 5.0.1 branch?  I was talking with an engineer on Twitter[1] about
>> some performance issues they were having assigning footprints in cvpcb
>> using MSW.  It sounded like it might be addressed by that work.
>>
>> -S
>>
>> [1] https://twitter.com/MayaPosch/status/1027660207709728769
>>
>> ___
>> 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

[Kicad-developers] Jenkins build is back to normal : linux-kicad-full-gcc-head #3813

[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 #4471

[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] Build failed in Jenkins: linux-kicad-full-gcc-head #3812

[Miguel Angel Ajo]

See 


Changes:

[jeff] Increase max-units to 'ZZ' (676).

[jeff] Add more/better error messages for file i/o problems.

[jeff] Rewrite Library Symbol Properties dialog.

[jeff] Revert some dialog changes that lost button sizes.

[jeff] Improve document file handling.

--
[...truncated 49.70 KB...]
[ 27%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/rotate_pos_z.cpp.o
[ 27%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/save_as.cpp.o
[ 27%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/save_gerber.cpp.o
[ 27%] Building CXX object 
3d-viewer/3d_cache/sg/CMakeFiles/kicad_3dsg.dir/ifsg_colors.cpp.o
[ 27%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/save_library.cpp.o
[ 28%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/save_project.cpp.o
[ 28%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/save_setup.cpp.o
[ 28%] Building CXX object common/CMakeFiles/gal.dir/gal/hidpi_gl_canvas.cpp.o
[ 28%] Building CXX object bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/save.cpp.o
[ 28%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/select_grid.cpp.o
[ 28%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/select_layer_pair.cpp.o
[ 28%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/select_w_layer.cpp.o
[ 28%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/select_same_sheet.cpp.o
[ 28%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/shape_3d.cpp.o
[ 28%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/sheetset.cpp.o
[ 28%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/simulator.cpp.o
[ 28%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/sim_run.cpp.o
[ 28%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/sim_stop.cpp.o
[ 28%] Building CXX object common/CMakeFiles/gal.dir/gal/stroke_font.cpp.o
[ 28%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/sim_tune.cpp.o
[ 28%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/sim_probe.cpp.o
[ 28%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/sim_add_signal.cpp.o
[ 28%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/sim_settings.cpp.o
[ 28%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/search_tree.cpp.o
[ 28%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/setcolor_3d_bg.cpp.o
[ 28%] Building CXX object 
3d-viewer/3d_cache/sg/CMakeFiles/kicad_3dsg.dir/ifsg_coords.cpp.o
[ 29%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/setcolor_silkscreen.cpp.o
[ 29%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/setcolor_soldermask.cpp.o
[ 29%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/setcolor_solderpaste.cpp.o
[ 29%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/setcolor_copper.cpp.o
[ 29%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/setcolor_board_body.cpp.o
[ 29%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/show_dcodenumber.cpp.o
[ 29%] Building CXX object common/CMakeFiles/gal.dir/geometry/hetriang.cpp.o
[ 29%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/show_footprint.cpp.o
[ 29%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/show_mod_edge.cpp.o
[ 29%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/showtrack.cpp.o
[ 29%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/show_zone.cpp.o
[ 29%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/show_zone_disable.cpp.o
[ 29%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/show_zone_outline_only.cpp.o
[ 29%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/show_all_layers.cpp.o
[ 29%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/show_no_layers.cpp.o
[ 29%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/show_no_copper_layers.cpp.o
[ 29%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/show_all_copper_layers.cpp.o
[ 29%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/spreadsheet.cpp.o
[ 29%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/svg_file.cpp.o
[ 30%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/swap_layer.cpp.o
[ 30%] Building CXX object bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/text.cpp.o
[ 30%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/text_sketch.cpp.o
[ 30%] Building CXX object 
3d-viewer/3d_cache/sg/CMakeFiles/kicad_3dsg.dir/ifsg_faceset.cpp.o
[ 30%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/three_d.cpp.o
[ 30%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/tool_ratsnest.cpp.o
[ 30%] Building CXX object 

[Kicad-developers] Build failed in Jenkins: kicad-qa #4470

[Miguel Angel Ajo]

See 

Changes:

[jeff] Increase max-units to 'ZZ' (676).

[jeff] Add more/better error messages for file i/o problems.

[jeff] Rewrite Library Symbol Properties dialog.

[jeff] Revert some dialog changes that lost button sizes.

[jeff] Improve document file handling.

--
[...truncated 70.05 KB...]
:1198:11: 
warning: declaration of ‘view’ shadows a member of 'this' [-Wshadow]
 auto& view = *getView();
   ^
:1199:11: 
warning: declaration of ‘controls’ shadows a member of 'this' [-Wshadow]
 auto& controls = *getViewControls();
   ^
: In member 
function ‘int EDIT_TOOL::editFootprintInFpEditor(const TOOL_EVENT&)’:
:1361:17: 
warning: declaration of ‘selection’ shadows a member of 'this' [-Wshadow]
 const auto& selection = m_selectionTool->RequestSelection( FootprintFilter 
);
 ^
: In member 
function ‘int EDIT_TOOL::copyToClipboard(const TOOL_EVENT&)’:
:1426:16: 
warning: declaration of ‘selection’ shadows a member of 'this' [-Wshadow]
 SELECTION& selection = m_selectionTool->RequestSelection( 
m_defaultSelectionFilter );
^
: In 
member function ‘void MICROWAVE_TOOL::createInductorBetween(const VECTOR2I&, 
const VECTOR2I&)’:
:221:11:
 warning: declaration of ‘frame’ shadows a member of 'this' [-Wshadow]
 auto& frame = *getEditFrame();
   ^
: In 
member function ‘int MICROWAVE_TOOL::drawMicrowaveInductor(const TOOL_EVENT&)’:
:278:18:
 warning: declaration of ‘view’ shadows a member of 'this' [-Wshadow]
 KIGFX::VIEW& view = *getView();
  ^
:279:27:
 warning: declaration of ‘controls’ shadows a member of 'this' [-Wshadow]
 KIGFX::VIEW_CONTROLS& controls = *getViewControls();
   ^
:280:11:
 warning: declaration of ‘frame’ shadows a member of 'this' [-Wshadow]
 auto& frame = *getEditFrame();
   ^
[ 63%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/pad_tool.cpp.o
:
 In member function ‘int MODULE_EDITOR_TOOLS::EnumeratePads(const TOOL_EVENT&)’:
:157:18:
 warning: declaration of ‘view’ shadows a member of 'this' [-Wshadow]
 KIGFX::VIEW* view = m_toolMgr->GetView();
  ^
:
 In member function ‘int MODULE_EDITOR_TOOLS::ExplodePadToShapes(const 
TOOL_EVENT&)’:
:274:16:
 warning: declaration of ‘selection’ shadows a member of 'this' [-Wshadow]
 SELECTION& selection = 
m_toolMgr->GetTool()->GetSelection();
^
:
 In member function ‘int MODULE_EDITOR_TOOLS::CreatePadFromShapes(const 
TOOL_EVENT&)’:
:323:16:
 warning: declaration of ‘selection’ shadows a member of 'this' [-Wshadow]
 SELECTION& selection = 
m_toolMgr->GetTool()->GetSelection();
^
[ 63%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/pcb_editor_control.cpp.o
[ 63%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/pcbnew_control.cpp.o
[ 63%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/placement_tool.cpp.o
: In member 
function ‘bool PAD_TOOL::haveFootprints()’:
:162:11: 
warning: declaration of ‘board’ shadows a member of 'this' [-Wshadow]
 auto& board = *getModel();
   ^
: In member 
function ‘int PAD_TOOL::pastePadProperties(const TOOL_EVENT&)’:
:208:17: 
warning: declaration 

Re: [Kicad-developers] SPICE models and library symbols

[Maciej Sumiński]

Hi Nhat,

There are fields dedicated to Spice model definitions, try to set a
model with the Spice Model editor dialog (in the Component Properties
dialog [1]) and notice that new fields will appear.

Cheers,
Orson

1. http://docs.kicad-pcb.org/5.0.0/en/eeschema.html#_assigning_models

On 08/13/2018 10:31 PM, Nhat Khai wrote:
> Sorry to a long email and my english. But here is my though. I can be
> wrong, so please don't be angry.
> Here is my case of use:
>   I have a lot of SUBCKT models (100+), and modified/customized SUBCKT
> models with parameters. In KiCad4, I using the default value of
> symbol/component to refer to default model. Later on in project, I can
> change that value point to my own SUBCKT model with some parameter
> specified for special case of simulation. It doable in KiCad4, but text in
> component's value some time look long and ugly. So it would be nice to have
> keep it compatible and following:
>   a. KiCad understand SUBCKT parameter and allow user to set these values
> -- Give KiCad a gateway to support ~90% of most simulation needed without
> understand resistor, voltage, current model ... etc.
>   b. KiCad give user option to stick with value (backward compatible) or
> use alternative field (one or more) for specifications the spice model.
>   c. These alternative field can be hide or visible just like any other
> normal field.
>   d. Using fields, all the model parameters can be just be export as BOM.
> Allow user to ensure they don't make mistake. Great visibility over 100+
> model all at one.
>   e. The .cir file allow user option to how to managing their spice library
> that fit there own workflow. (Using normal editor, look at 100+ model all
> at one in one file, source control in the spice language, no need to learn
> another KiCad language to look at the git diff,...etc).
> 
> I think, embedding spice model into symbol is nice but is have issues:
> 1. Visibility of the model is hard to access (one by one). It is trouble
> some to verify 100 spice model all at once.
> 2. User tent to not trust spice model where I don't know about it, or where
> it comes from. (they will refer to download directly form manufacture, or
> their customized version.
> 
> Also, embedding spice model into the component is nice in eeschema, but is
> have similar issue:
> 1. Visibility of the model have is one by one.
> 2. Here is one of my resistor value for simulation: "{2k*0.9026} tc1=4.21m
> tc2=4.427u dtemp=27". Current KiCad5 don't understand this. However, I
> don't expect it understand it like KiCad4 did. But if it understand the
> simple SUBCKT then I can use it and pass in parameters, and help it more
> readable, and my life easier :-).
> 
> KiCad simulation seem to missing a generic mode for the unexpected
> simulation types. Which again, in my case is temperature sweep or can be
> multi-parameter sweeps. It think the effort to have it recognize are
> beautiful. But generic simulation should be the most importance one to
> cover first. Meaning, it don't event need to understand the simulation type
> and still able to plot the result. My case, I use spice directive to
> specify my unusual simulation, and no matter how I specify it, current
> simulation tool should able to plot result after simulation finished (is
> the best I can dream of). Current it is not, if it don't understand what
> type of simulation I'm doing (witch again I think it don't have to).
> 
> 
> 
> ___
> 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
> 




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