Re: [Kicad-developers] [FEATURE] Component table viewer

[Strontium]

Hi Oliver,

On 06/05/17 12:13, Oliver Walters wrote:


And it just so happens that in this schematic NO components have
been edited to include these default fields/values, so, they don't
show up in the component table. 



I have a patch to fix this now - if a field is empty and a template 
value exists, that is placed there instead.


Also, editing Multipart components is a little quirky, If you
change a field for a multi-part component, all "parts" update to
that value, but if any parts have different values, only one is
shown in the table and its not clear that the underlying multipart
field is inconsistent.


This is a hard one as really, multi-part components should /not/ have 
different values in various fields! I had thought about adding another 
level (with an arrow as you suggest) but I think it becomes too 
complicated.
Yes, I agree with you on this, Its confusing that KiCad doesn't 
synchronise those fields.  BUT I think maybe its done that way to help 
facilitate swapping parts between multiple multi-part components.


Maybe a developer who knows more about this can weigh in?  Is having 
different field value/fields in a single multi-part component a 
"Feature" or a "Quirk"?  And if a "Feature" what's its purpose?


Steven


___
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] [FEATURE] Component table viewer

[Oliver Walters]

>
> Perhaps one feature request regarding custom fields would be (if possible)
> to select which field is used for grouping components, instead of just the
> value field. Either a custom field or one of the standard ones like
> footprint name or symbol name. Think editing all 0402 resistors, or all the
> connectors with the same footprint but different value, etc.


The default behaviour is that *all* fields must match for two components to
be considered "equal".

I have added an option for each column to be removed from this check, so
you can specify as many (or as few) columns as you like.

On Fri, May 5, 2017 at 11:50 PM, José Ignacio  wrote:

> Perhaps one feature request regarding custom fields would be (if possible)
> to select which field is used for grouping components, instead of just the
> value field. Either a custom field or one of the standard ones like
> footprint name or symbol name. Think editing all 0402 resistors, or all the
> connectors with the same footprint but different value, etc.
>
> Thank you very much for your excellent work!
> Jose
>
> On Fri, May 5, 2017 at 7:56 AM, Oliver Walters <
> oliver.henry.walt...@gmail.com> wrote:
>
>> Steven,
>>
>> Unless you mean something different to what I think "custom fields"
>> means, then this is already the case - any extra fields (beyond REFERENCE /
>> FOOTPRINT / DATSHEET / VALUE) are preesnt to be edited in the table...
>>
>> On Fri, May 5, 2017 at 10:51 PM, Strontium  wrote:
>>
>>> Hi Oliver,
>>>
>>> Just had a chance to check out your component table viewer, its nice.
>>> Great work.
>>>
>>> Is it on your roadmap to be able to view/edit a components custom fields?
>>>
>>> Regards,
>>> Steven
>>>
>>> On 03/05/17 05:35, Oliver Walters wrote:
>>>
 Wayne,

 Thanks for merging!

 I will address those points at some stage - there are other ideas I
 have too but I thought it was better to get the first iteration done and
 make incremental improvements.

 Regards,
 Oliver

>>>
>>>
>>> ___
>>> 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] [FEATURE] Component table viewer

[Oliver Walters]

>
> And it just so happens that in this schematic NO components have been
> edited to include these default fields/values, so, they don't show up in
> the component table.


I have a patch to fix this now - if a field is empty and a template value
exists, that is placed there instead.


> Also, editing Multipart components is a little quirky, If you change a
> field for a multi-part component, all "parts" update to that value, but if
> any parts have different values, only one is shown in the table and its not
> clear that the underlying multipart field is inconsistent.


This is a hard one as really, multi-part components should *not* have
different values in various fields! I had thought about adding another
level (with an arrow as you suggest) but I think it becomes too
complicated.

On Fri, May 5, 2017 at 11:46 PM, Strontium  wrote:

> Oliver,
>
> This is one of my components:
> http://i.imgur.com/QXyCXXt.png
>
> This is the component table:
> http://i.imgur.com/F2WTRC2.png
>
> The MFG, MPN or EQUIVOK fields in the component aren't shown in the table!
>
> And in doing that I worked out my problem :)
>
> I have MFG/MPN/EQUIVOK defined as "Default Fields" with default values.
> And because the component hasn't been edited, I can edit it and SEE the
> default fields and default values BUT unless I change something they are
> not saved with the component.  And it just so happens that in this
> schematic NO components have been edited to include these default
> fields/values, so, they don't show up in the component table.
>
> It would be nice if the "Default Fields" and their default values show in
> the table if they weren't defined for the component, maybe highlighted in
> some way (Italic, light grey, or something) to indicate they are defaulted
> and not actually set. But now I know why I couldn't see them its not a big
> deal so consider this an Enhancement request.
>
> Also, editing Multipart components is a little quirky, If you change a
> field for a multi-part component, all "parts" update to that value, but if
> any parts have different values, only one is shown in the table and its not
> clear that the underlying multipart field is inconsistent.  Again its not a
> big deal, I just noticed it.  Maybe multipart components should work like
> grouped components, i.e. you can click an arrow and see all the parts and
> edit them individually, or edit the top level component and set them all to
> the same value?  I'm not really sure if this is a good idea or not.
>
> I'm working on an external BOM management tool. It reads a schematic live
> while you edit it in Kicad, and costs it from octopart and/or a database of
> locally defined components, updating in real time.  This tool you have made
> is going to save me an enormous amount of time editing schematics and
> getting all the field metadata consistent.  Thank you.
>
> Two more enhancement ideas:
> 1. A way to update the schematic from edits without closing the table view.
> 2. A way to revert the last edit (undo)
>
> Steven
>
>
> On 05/05/17 20:56, Oliver Walters wrote:
>
> Steven,
>
> Unless you mean something different to what I think "custom fields" means,
> then this is already the case - any extra fields (beyond REFERENCE /
> FOOTPRINT / DATSHEET / VALUE) are preesnt to be edited in the table...
>
> On Fri, May 5, 2017 at 10:51 PM, Strontium  wrote:
>
>> Hi Oliver,
>>
>> Just had a chance to check out your component table viewer, its nice.
>> Great work.
>>
>> Is it on your roadmap to be able to view/edit a components custom fields?
>>
>> Regards,
>> Steven
>>
>> On 03/05/17 05:35, Oliver Walters wrote:
>>
>>> Wayne,
>>>
>>> Thanks for merging!
>>>
>>> I will address those points at some stage - there are other ideas I have
>>> too but I thought it was better to get the first iteration done and make
>>> incremental improvements.
>>>
>>> Regards,
>>> Oliver
>>>
>>
>>
>> ___
>> 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] [FEATURE] Component table viewer

[Thomas Kindler]

Hi Oliver!

I also tried the new component table viewer, and think that it looks very
promising! I'm switching over from Altium which makes extensive use of List and
Property dock panels, so I would like to provide some feedback:


* There should be a warning if there are uncommitted changes. Right now, it's
very easy to loose work by accidentially hitting ESC.

* The text columns should be left-aligned for readability. Numerical columns
(Quantity..) should be right-aligned (easier to compare numbers).

* The side bar takes up a lot of space on small displays. The field selection
could be replaced by a context menu, like in Windows Explorer or Nautilus.

  * This would also be a good place for "Group by this column", "Size column to
fit", and "Size all columns to fit" menu entries.

* It would be nice to be able to edit the Reference column.

* Field selection and column sizes should be saved and restored when reopening
the dialog, possibly across program restarts.

* Column reordering by dragging the column title (I don't know, if wx provides
that feature).



Also, I think making the dialog non-modal would be useful:

* No need for a custom "Apply/Cancel/Revert all Changes" workflow.
All edits could be done on the fly, and use the normal undo/redo functionality.

* Row Selection could be synchronized with sheet object selection (and vice 
versa).

* There could be a "Zoom to selected object" context menu entry.

* In Altium, the schematic list view can show all types of objects (Nets, Pins,
etc.), and also work in the library abd PCB editor. It's often possible to e.g.
select all 144 pins of a microcontroller, and set the signal names by copy and
paste from a spreadsheet.


Woohoo, a lot of points ;) I'm new on the mailing list -- is this the right way
to give feedback? I'm always afraid of sounding rude or demanding, especially
because english is not my native language.

best regards,
Thomas

On 05.05.2017 14:56, Oliver Walters wrote:
> Steven,
> 
> Unless you mean something different to what I think "custom fields" means, 
> then
> this is already the case - any extra fields (beyond REFERENCE / FOOTPRINT /
> DATSHEET / VALUE) are preesnt to be edited in the table...
> 
> On Fri, May 5, 2017 at 10:51 PM, Strontium  > wrote:
> 
> Hi Oliver,
> 
> Just had a chance to check out your component table viewer, its nice.  
> Great
> work.
> 
> Is it on your roadmap to be able to view/edit a components custom fields?
> 
> Regards,
> Steven
> 
> On 03/05/17 05:35, Oliver Walters wrote:
> 
> Wayne,
> 
> Thanks for merging!
> 
> I will address those points at some stage - there are other ideas I 
> have
> too but I thought it was better to get the first iteration done and 
> make
> incremental improvements.
> 
> Regards,
> Oliver
> 
> 
> 
> ___
> 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] ogltest and OSX nightlies

[Chris Pavlina]

On Fri, May 05, 2017 at 09:24:38PM +0200, Bernhard Stegmaier wrote:
> … hmm, not really sure, just a guess.
> It could have started to break with that change:
>   
> https://git.launchpad.net/kicad/commit/utils/kicad-ogltest/CMakeLists.txt?id=7b4ea2a382f949150ea4f145ac9f4d2a59ec2591
>  
> 
> 
> Without the “MACOSX_BUNDLE” it probably didn’t try to build the bundle and 
> thus also didn’t fail in making it relocatable.
> My last build was just before this change (2017-04-02).
> 
> BTW:
> It doesn’t fail during compile, but during “make install”.
> If you don’t do a "make install”, that could be why you don’t see it?

No, I just failed to double-check before sending my email. It is indeed
broken for me too, but it worked the last time I worked on it. A commit
after my own broke it. Still looking at it.

> 
> 
> Regards,
> Bernhard
> 
> > On 5. May 2017, at 21:07, Bernhard Stegmaier  
> > wrote:
> > 
> > Hi,
> > 
> > this seems to be quite incomplete. It is the last step making the bundle 
> > relocatable that fails.
> > 
> > First, what is kicad-ogltest supposed to be?
> > A real application bundle or just a standalone (command line) binary?
> > 
> > For a real application bundle you will probably need a Info.plist like for 
> > the other bundles.
> > Further, you would need to use a CMakeLists.txt like for the other app 
> > bundles, like e.g. for pcb_calculator:
> > <<<
> > if( APPLE )
> > set_target_properties( pcb_calculator PROPERTIES
> > MACOSX_BUNDLE_INFO_PLIST ${CMAKE_CURRENT_SOURCE_DIR}/Info.plist
> > )
> > 
> > # puts binaries into the *.app bundle while linking
> > set_target_properties( pcb_calculator_kiface PROPERTIES
> > LIBRARY_OUTPUT_DIRECTORY ${OSX_BUNDLE_BUILD_KIFACE_DIR}
> > )
> > 
> > # put individual bundle outside of main bundle as a first step
> > # will be pulled into the main bundle when creating main bundle
> > install( TARGETS pcb_calculator
> > DESTINATION ${KICAD_BIN}
> > COMPONENT binary
> > )
> > install( CODE "
> > # override default embedded path settings
> > ${OSX_BUNDLE_OVERRIDE_PATHS}
> > 
> > # do all the work
> > include( BundleUtilities )
> > fixup_bundle( 
> > ${KICAD_BIN}/pcb_calculator.app/Contents/MacOS/pcb_calculator
> > \"\"
> > \"\"
> > )
> > " COMPONENT Runtime
> > )
> > else()
> > >>>
> > If you don’t do it like that (especially the “install( CODE” part) it won’t 
> > find/use the libs copied into the bundle.
> > From the error, I guess that’s exactly the problem you see.
> > 
> > I also didn’t notice this when I did my last build.
> > I can definitely look into it, but I currently don’t have my development 
> > machine up and running… will probably take another week or so.
> > 
> > 
> > Regards,
> > Bernhard
> > 
> >> On 5. May 2017, at 18:24, Chris Pavlina  >> > wrote:
> >> 
> >> Hi,
> >> 
> >> Apologies for my absense. I'm looking into the issue with macOS nightles
> >> not building, which appears to be because of kicad-ogltest which I added
> >> a while ago.
> >> 
> >> I'm still really busy and am having trouble finding real time for this,
> >> but I want to get the nightlies going again. If I can't actually find
> >> the issue, I'm going to just revert all the ogltest commits for now.
> >> 
> >> I would definitely appreciate if someone familiar with the build system
> >> could look into it, because it does build for me on macOS and the error
> >> messages are pretty cryptic to me.
> >> 
> >> Link to the build log from the first failing build:
> >> 
> >> http://ci.kicad-pcb.org/job/osx-kicad-adam-head/264/console 
> >> 
> >> 
> >> -- 
> >> Chris
> >> 
> >> ___
> >> 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] ogltest and OSX nightlies

[Bernhard Stegmaier]

… hmm, not really sure, just a guess.
It could have started to break with that change:
  
https://git.launchpad.net/kicad/commit/utils/kicad-ogltest/CMakeLists.txt?id=7b4ea2a382f949150ea4f145ac9f4d2a59ec2591
 


Without the “MACOSX_BUNDLE” it probably didn’t try to build the bundle and thus 
also didn’t fail in making it relocatable.
My last build was just before this change (2017-04-02).

BTW:
It doesn’t fail during compile, but during “make install”.
If you don’t do a "make install”, that could be why you don’t see it?


Regards,
Bernhard

> On 5. May 2017, at 21:07, Bernhard Stegmaier  wrote:
> 
> Hi,
> 
> this seems to be quite incomplete. It is the last step making the bundle 
> relocatable that fails.
> 
> First, what is kicad-ogltest supposed to be?
> A real application bundle or just a standalone (command line) binary?
> 
> For a real application bundle you will probably need a Info.plist like for 
> the other bundles.
> Further, you would need to use a CMakeLists.txt like for the other app 
> bundles, like e.g. for pcb_calculator:
> <<<
> if( APPLE )
> set_target_properties( pcb_calculator PROPERTIES
> MACOSX_BUNDLE_INFO_PLIST ${CMAKE_CURRENT_SOURCE_DIR}/Info.plist
> )
> 
> # puts binaries into the *.app bundle while linking
> set_target_properties( pcb_calculator_kiface PROPERTIES
> LIBRARY_OUTPUT_DIRECTORY ${OSX_BUNDLE_BUILD_KIFACE_DIR}
> )
> 
> # put individual bundle outside of main bundle as a first step
> # will be pulled into the main bundle when creating main bundle
> install( TARGETS pcb_calculator
> DESTINATION ${KICAD_BIN}
> COMPONENT binary
> )
> install( CODE "
> # override default embedded path settings
> ${OSX_BUNDLE_OVERRIDE_PATHS}
> 
> # do all the work
> include( BundleUtilities )
> fixup_bundle( 
> ${KICAD_BIN}/pcb_calculator.app/Contents/MacOS/pcb_calculator
> \"\"
> \"\"
> )
> " COMPONENT Runtime
> )
> else()
> >>>
> If you don’t do it like that (especially the “install( CODE” part) it won’t 
> find/use the libs copied into the bundle.
> From the error, I guess that’s exactly the problem you see.
> 
> I also didn’t notice this when I did my last build.
> I can definitely look into it, but I currently don’t have my development 
> machine up and running… will probably take another week or so.
> 
> 
> Regards,
> Bernhard
> 
>> On 5. May 2017, at 18:24, Chris Pavlina > > wrote:
>> 
>> Hi,
>> 
>> Apologies for my absense. I'm looking into the issue with macOS nightles
>> not building, which appears to be because of kicad-ogltest which I added
>> a while ago.
>> 
>> I'm still really busy and am having trouble finding real time for this,
>> but I want to get the nightlies going again. If I can't actually find
>> the issue, I'm going to just revert all the ogltest commits for now.
>> 
>> I would definitely appreciate if someone familiar with the build system
>> could look into it, because it does build for me on macOS and the error
>> messages are pretty cryptic to me.
>> 
>> Link to the build log from the first failing build:
>> 
>> http://ci.kicad-pcb.org/job/osx-kicad-adam-head/264/console 
>> 
>> 
>> -- 
>> Chris
>> 
>> ___
>> 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] Move point on pcbnew

[Carlo Maragno]

Too bad! Here you can find a google drive folder with the two small video.

Enjoy,
Carlo

https://drive.google.com/folderview?id=0B-AbX0GoNzEPRjFSY19qQ0JjeFE

On May 3, 2017 10:15 PM, "Carlo Maragno"  wrote:

> Hi Guys,
>
> While I was using an old developer version of Kicad (the build date was
> 28-2-2017), in pcbnew the move tool would grab the component from the point
> closer to the cursor when M was pressed. In other word, if the cursor was
> closer to a pad the center of the pad would become the grabbing point.
>
> On the last developer release from the Ubuntu PPA, this behavior
> disappeared. I'm trying to figure out at which point it was deleted but as
> I was quite far away from master head this could be a very long process.
> Now I am at commit #bbaa29, made by Chris Pavlina.
>
> Can someone of the developers point to me at which point this feature was
> removed?
>
> My ultimate goal would be to make a push request in order to get this
> feature added again. So if someone could help that would be great!
>
> Thanks again to all,
> Carlo
>
___
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] [FEATURE] Component table viewer

[José Ignacio]

Perhaps one feature request regarding custom fields would be (if possible)
to select which field is used for grouping components, instead of just the
value field. Either a custom field or one of the standard ones like
footprint name or symbol name. Think editing all 0402 resistors, or all the
connectors with the same footprint but different value, etc.

Thank you very much for your excellent work!
Jose

On Fri, May 5, 2017 at 7:56 AM, Oliver Walters <
oliver.henry.walt...@gmail.com> wrote:

> Steven,
>
> Unless you mean something different to what I think "custom fields" means,
> then this is already the case - any extra fields (beyond REFERENCE /
> FOOTPRINT / DATSHEET / VALUE) are preesnt to be edited in the table...
>
> On Fri, May 5, 2017 at 10:51 PM, Strontium  wrote:
>
>> Hi Oliver,
>>
>> Just had a chance to check out your component table viewer, its nice.
>> Great work.
>>
>> Is it on your roadmap to be able to view/edit a components custom fields?
>>
>> Regards,
>> Steven
>>
>> On 03/05/17 05:35, Oliver Walters wrote:
>>
>>> Wayne,
>>>
>>> Thanks for merging!
>>>
>>> I will address those points at some stage - there are other ideas I have
>>> too but I thought it was better to get the first iteration done and make
>>> incremental improvements.
>>>
>>> Regards,
>>> Oliver
>>>
>>
>>
>> ___
>> 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] [FEATURE] Component table viewer

[Strontium]

Oliver,

This is one of my components:
http://i.imgur.com/QXyCXXt.png

This is the component table:
http://i.imgur.com/F2WTRC2.png

The MFG, MPN or EQUIVOK fields in the component aren't shown in the table!

And in doing that I worked out my problem :)

I have MFG/MPN/EQUIVOK defined as "Default Fields" with default values.
And because the component hasn't been edited, I can edit it and SEE the 
default fields and default values BUT unless I change something they are 
not saved with the component.  And it just so happens that in this 
schematic NO components have been edited to include these default 
fields/values, so, they don't show up in the component table.


It would be nice if the "Default Fields" and their default values show 
in the table if they weren't defined for the component, maybe 
highlighted in some way (Italic, light grey, or something) to indicate 
they are defaulted and not actually set. But now I know why I couldn't 
see them its not a big deal so consider this an Enhancement request.


Also, editing Multipart components is a little quirky, If you change a 
field for a multi-part component, all "parts" update to that value, but 
if any parts have different values, only one is shown in the table and 
its not clear that the underlying multipart field is inconsistent.  
Again its not a big deal, I just noticed it.  Maybe multipart components 
should work like grouped components, i.e. you can click an arrow and see 
all the parts and edit them individually, or edit the top level 
component and set them all to the same value?  I'm not really sure if 
this is a good idea or not.


I'm working on an external BOM management tool. It reads a schematic 
live while you edit it in Kicad, and costs it from octopart and/or a 
database of locally defined components, updating in real time.  This 
tool you have made is going to save me an enormous amount of time 
editing schematics and getting all the field metadata consistent.  Thank 
you.


Two more enhancement ideas:
1. A way to update the schematic from edits without closing the table view.
2. A way to revert the last edit (undo)

Steven

On 05/05/17 20:56, Oliver Walters wrote:

Steven,

Unless you mean something different to what I think "custom fields" 
means, then this is already the case - any extra fields (beyond 
REFERENCE / FOOTPRINT / DATSHEET / VALUE) are preesnt to be edited in 
the table...


On Fri, May 5, 2017 at 10:51 PM, Strontium > wrote:


Hi Oliver,

Just had a chance to check out your component table viewer, its
nice.  Great work.

Is it on your roadmap to be able to view/edit a components custom
fields?

Regards,
Steven

On 03/05/17 05:35, Oliver Walters wrote:

Wayne,

Thanks for merging!

I will address those points at some stage - there are other
ideas I have too but I thought it was better to get the first
iteration done and make incremental improvements.

Regards,
Oliver



___
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] [FEATURE] Component table viewer

[Oliver Walters]

Steven,

Unless you mean something different to what I think "custom fields" means,
then this is already the case - any extra fields (beyond REFERENCE /
FOOTPRINT / DATSHEET / VALUE) are preesnt to be edited in the table...

On Fri, May 5, 2017 at 10:51 PM, Strontium  wrote:

> Hi Oliver,
>
> Just had a chance to check out your component table viewer, its nice.
> Great work.
>
> Is it on your roadmap to be able to view/edit a components custom fields?
>
> Regards,
> Steven
>
> On 03/05/17 05:35, Oliver Walters wrote:
>
>> Wayne,
>>
>> Thanks for merging!
>>
>> I will address those points at some stage - there are other ideas I have
>> too but I thought it was better to get the first iteration done and make
>> incremental improvements.
>>
>> Regards,
>> Oliver
>>
>
>
> ___
> 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] [FEATURE] Component table viewer

[Strontium]

Hi Oliver,

Just had a chance to check out your component table viewer, its nice.  
Great work.


Is it on your roadmap to be able to view/edit a components custom fields?

Regards,
Steven

On 03/05/17 05:35, Oliver Walters wrote:

Wayne,

Thanks for merging!

I will address those points at some stage - there are other ideas I 
have too but I thought it was better to get the first iteration done 
and make incremental improvements.


Regards,
Oliver



___
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] Move point on pcbnew

[José Ignacio]

The attachments got scrubbed (probably too large), i'd recommend you upload
the videos to youtube or some other video sharing site.

On Fri, May 5, 2017 at 3:07 AM, Carlo Maragno  wrote:

> Hi there,
>
> I done some tests, including a full system wipe and the behavior is still
> the same. I tried to compile 096d9f & c70adc and I got similar results.
>
> In the attachments you can find two video: the kicad_bug one was done with
> 096d9f while the kicad_working one was done on 7034ea.
>
> Cheers,
> Carlo
>
> 2017-05-03 22:15 GMT+02:00 Carlo Maragno :
>
> > Hi Guys,
> >
> > While I was using an old developer version of Kicad (the build date was
> > 28-2-2017), in pcbnew the move tool would grab the component from the
> point
> > closer to the cursor when M was pressed. In other word, if the cursor was
> > closer to a pad the center of the pad would become the grabbing point.
> >
> > On the last developer release from the Ubuntu PPA, this behavior
> > disappeared. I'm trying to figure out at which point it was deleted but
> as
> > I was quite far away from master head this could be a very long process.
> > Now I am at commit #bbaa29, made by Chris Pavlina.
> >
> > Can someone of the developers point to me at which point this feature was
> > removed?
> >
> > My ultimate goal would be to make a push request in order to get this
> > feature added again. So if someone could help that would be great!
> >
> > Thanks again to all,
> > Carlo
> >
>
> ___
> 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] Move point on pcbnew

[Carlo Maragno]

Hi there,

I done some tests, including a full system wipe and the behavior is still
the same. I tried to compile 096d9f & c70adc and I got similar results.

In the attachments you can find two video: the kicad_bug one was done with
096d9f while the kicad_working one was done on 7034ea.

Cheers,
Carlo

2017-05-03 22:15 GMT+02:00 Carlo Maragno :

> Hi Guys,
>
> While I was using an old developer version of Kicad (the build date was
> 28-2-2017), in pcbnew the move tool would grab the component from the point
> closer to the cursor when M was pressed. In other word, if the cursor was
> closer to a pad the center of the pad would become the grabbing point.
>
> On the last developer release from the Ubuntu PPA, this behavior
> disappeared. I'm trying to figure out at which point it was deleted but as
> I was quite far away from master head this could be a very long process.
> Now I am at commit #bbaa29, made by Chris Pavlina.
>
> Can someone of the developers point to me at which point this feature was
> removed?
>
> My ultimate goal would be to make a push request in order to get this
> feature added again. So if someone could help that would be great!
>
> Thanks again to all,
> Carlo
>
___
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