Re: [Kicad-developers] Change in Library Team Leadership

[Fabrizio Tappero]

Hi Rene,
good luck with your new undervoir and who knows, maybe one day you will be
back.

cheers
Fabrizio


On Wed, Aug 26, 2020 at 10:01 PM Rene Pöschl  wrote:

> Hi all,
>
>
> the bad news up front, I no longer have the time to properly handle
> leading the library team as i am now working full time and still have my
> education to finish (Covid isn't much help either as it makes me lose a
> bit of time as i try to avoid public transport at peak hours).
>
>
> And now the good news. Christian Schlüter has volunteered to take over
> as the team leader. I personally plan to be around and help as much as i
> can with reviews but simply feel that i should give somebody a chance to
> grow who has more time on their hand. To be honest i think he already
> took on part of my roles as i had been absent for quite some time
> (partly hoping i will find more time and partly just not wanting to
> admit that i don't have it anymore).
>
>
> Kind regards Rene
>
>
> ___
> 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] Who did the save-to-board icon?

[Fabrizio Tappero]

Hi guys,
Seth, I apologize for not getting back to you in all this time.
Years ago I redesigned about 85% of all 380 kicad icons and during the
years people have freely improved or resigned some of them.
All submits I was responsible with have been done via Dick, JP, Wayne.

If you think you have a better idea or implementation of any icon please go
ahead. If you like you can send us a png preview here.
Cheers
Fabrizio



The save to board iconin particula


On Sun, Nov 3, 2019, 7:50 PM Seth Hillbrand  wrote:

> On 2019-11-03 08:25, Jeff Young wrote:
>
> > I'd like to update the load-from-board and add-to-board icons (last two
> > below) to match.
> >
> > Thanks,
> > Jeff.
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
>
> Hi Jeff-
>
> I was working through the icon licensing a while back and have script
> that may help.  Here's the history of those two icons.
>
> That said, it doesn't catch re-names, so JP will have to mention whether
> he generated the original or not.
>
> Best-
> Seth
>
> Seth Hillbrand
> KiCad Services Corporation
> https://www.kipro-pcb.com
> +1 530 302 5483 | +1 212 603
> 9372___
> 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] Project annuouncement.

[Fabrizio Tappero]

Hey Wayne,
Congratulations!!! I am really happy for you!

Cheers,
Fabrizio

On Sun, May 5, 2019 at 1:51 AM Wayne Stambaugh  wrote:

> Nick,
>
> Thanks.  I will actually have spare time now which I plan to use doing
> things outside of KiCad.  Prior to the new job, there really wasn't any
> free time to speak of.
>
> Cheers,
>
> Wayne
>
> On 5/4/19 4:16 PM, Nick Østergaard wrote:
> > Congratulations Wayne. That sounds like good news for everyone. But
> > remember not to burn yourself out, just the opportunity to take a
> > break from kicad in your "spare" time then :)
> >
> > On Sat, 27 Apr 2019 at 20:05, Wayne Stambaugh 
> wrote:
> >>
> >> For those you who haven't heard yet, I made the announcement yesterday
> >> at KiCon that I am now work for WIT and I will be working full time on
> >> KiCad.  I really excited about the possibilities for KiCad going
> >> forward.  Here is the moment when I made the announcement at KiCon.
> >>
> >>
> https://www.facebook.com/dfustini/posts/10219431437645036?notif_id=1556317416870013_t=mention
> >>
> >> 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] Sponsoring KiCad development

[Fabrizio Tappero]

Hello,
I find feature 2-d something that would be really useful.
Cheers
Fabrizio


On Fri, Feb 1, 2019, 6:57 PM Schaarschmidt Wolf  Dear KiCad developers,
>
> our company Dorabot is an enthusiastic KiCad user,
> so we would like to *sponsor *some improvements:
>
> *1. Schematic design part*
> a. provide off-page connection for a parallel bus.
> b. provide customized power ports that can be edited by netlabel in case
> there are several power rails.
> c. provide a convenient way to duplicate circuitry partially from another
> project.
> d. provide a convenient way to combine two different schematic-libs.
> e. provide a way to import schematic designs from other popular EDA tools,
> such as Altium Designer or Orcad.
>
> *2. PCB layout part*
> a. provide teardrop connection methods, including mass and individual way.
> b. provide a method to mass align REF numbers.
> c. provide a method to mass edit the size of REF numbers.
> d. provide a method to move multiple components in *PCB* when selected in
> the schematic.
> e. provide a method to add arc traces.
> f.  provide a method to add polygons with arc corners.
> g. have a specified rule to constrain the clearance between the edge and
> polygons or traces locally (not only globally).
> h. provide a way to import PCB designs from other popular EDA tools, such
> as Altium Designer or Allegro.
> i.  provide a convenient way to fanout BGA footprints with certain VIA
> size and Trace width.
> j.  provide region constraint for small pitch size BGA footprint.
>
> Please let us know whether you see an opportunity for us to *sponsor* (i.e.
> financially support)
> some or all of these improvements. We are looking forward to hearing from
> you!
>
> Best regards,
>
> *Wolf Schaarschmidt*｜Robot Engineer
>
> w...@dorabot.com 
>
>
> No. 2 Zuopaotai Rd, H6-2, Nanshan District｜Shenzhen, Guangdong 518000,
> China
>
> 0755-21650236｜ i...@dorabot.com｜
> www.dorabot.com
>
>
> ---
>
> CONFIDENTIALITY NOTICE: The contents of this email message and any
> attachments are intended solely for the addressee(s) and contain
> confidential and/or privileged information and are legally protected from
> disclosure unless otherwise indicated. If you are not the intended
> recipient of this message or their agent, or if this message has been
> addressed to you in error, please immediately alert the sender by reply
> email and then delete this message and any attachments. If you are not the
> intended recipient, you are hereby notified that any use, dissemination,
> copying, or storage of this message or its attachments is strictly
> prohibited. Thank you.
>
>
> ___
> 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] RFC: toolbar button support for action plugins

[Fabrizio Tappero]

I really like it!! Very cool work. Thank you.

Fabrizio

On Aug 22, 2018 1:29 PM, "Andrew Lutsenko"  wrote:

Hi Seth,

I built the settings dialog for action plugins. You can reorder and
enable/disable buttons for each plugin individually.

Short demo:
https://i.imgur.com/33iJC7b.gif

Squashed patch is attached. I've tested it on win, debian8 and debian9.
If it's easier to review diff can be viewed here as well:
https://github.com/KiCad/kicad-source-mirror/compare/
master...qu1ck:plugin-icon

Also I've attached few dummy plugins to play with, 3 out of 4 have icons.

Let me know if you have any comments.

Thanks,
Andrew

On Fri, Aug 17, 2018 at 3:02 PM Andrew Lutsenko 
wrote:

> Hi Seth,
>
> That makes sense. I will keep working on this feature and will ping this
> thread again once user configuration is implemented.
>
> Thanks,
> Andrew
>
> On Fri, Aug 17, 2018 at 10:03 AM Seth Hillbrand 
> wrote:
>
>> Hi Andrew-
>>
>> I like the patch idea and your implementation approach is good.
>>
>> The coding style policy is located at https://kicad-source-
>> mirror.readthedocs.io/en/stable/Documentation/development/coding-style-
>> policy/  We're not totally consistent but we try to ensure any new code
>> follows it and clean up the old code as we go.
>>
>> On the errors, please don't throw an error to the user.  It may be useful
>> to insert a wxLog() call that we could utilize in the future but that is
>> ignored for now.
>>
>> I'm opposed to merging patches that are partially complete.  And I would
>> consider the lack of user control over this feature problematic.  This is
>> not a judgement on the patch as you've implemented it.  I really like the
>> functionality and think KiCad users will appreciate it as well.  However, a
>> partially implemented feature creates the opportunity for problems down the
>> road that will distract developer time from the other tasks they are
>> working on.  If you do not have the time to fully implement user control
>> over this feature (I completely understand competing time pressures), you
>> may consider opening a bug report and attaching your patch there for
>> interested future developers.  Squashing the patchset for review is also a
>> good idea.
>>
>> Overall this looks really promising.
>>
>> Best-
>> Seth
>>
>> Am Do., 16. Aug. 2018 um 23:02 Uhr schrieb Andrew Lutsenko <
>> anlutse...@gmail.com>:
>>
>>> Hi Seth
>>>
>>> I just checked out new preferences in pcbnew, looks much more organized
>>> than before.
>>> I totally can add a new tab there "pcbnew->Action plugins" and list the
>>> plugins there with option
>>> to remove toolbar icon. But that is a non-negligible amount of work.
>>> Will you hold off on merging
>>> my current patches until I implement that too?
>>> By default plugins will not show any buttons on toolbar, plugin writers
>>> will have to explicitly update
>>> their plugins and provide an icon for them to show up so you will not
>>> run into an issue with full
>>> toolbar for a while. See my screenshot in second email of the chain, it
>>> has 4 plugins but only
>>> 2 of them register with an icon and toolbar button.
>>>
>>> > headers get 1 space between function defs
>>> I tried to follow existing style in each file and didn't notice that
>>> it's not consistent across different files.
>>> action_plugin.h has two new lines between most functions but I can
>>> change it to one.
>>>
>>> What do you think about throwing an error to user if icon failed to
>>> load? Andrey Kuznetsov made a
>>> point that user can't do anything about it anyway. I agree that asking
>>> users to fix plugin icon declaration
>>> is a bit much and developer will be able to see that icon didn't load
>>> without the error too.
>>>
>>> Andrew
>>>
>>> On Thu, Aug 16, 2018 at 10:22 PM Seth Hillbrand 
>>> wrote:
>>>
 Hi Andrew-

 I like the idea.  Aside from minor formatting (headers get 1 space
 between function defs, need a space before the if block), the patch looks
 good.

 However, I wouldn't want everything showing on my toolbar (speaking as
 someone who has 10 plugins installed, 5 of which get regular use).  I'd
 prefer the option to be configurable.  This should probably be in the
 preferences pane that Jeff has been re-working.

 -Seth

 Am Do., 16. Aug. 2018 um 22:11 Uhr schrieb Andrew Lutsenko <
 anlutse...@gmail.com>:

> Hi Clemens,
>
> See sample plugin attached. Extract it into kicad's
> share/scripting/plugins folder.
> One of other scanned directories that are documented in kicadplugins.i
> 
>  should
> work too.
>
> Or are you asking to update docs in the repo?
> Documentation/development/pcbnew-plugins.md seems like the right
> place.
> I will update it once committers agree with the path I've chosen to
> implement this.
>

Re: [Kicad-developers] [RFC] Op-amp symbol icons

[Fabrizio Tappero]

Hello,
sharp 1px or 2px lines cause icon to look sharp (obviously). This does not
normally lead to a pleasant GUI experience unless we consider a GUI from
the 90s.

According the the overall style chosen it might be a good idea to add a a
second line next to the 1px (2px) line of a much lower (or higher)
saturation. More sophisticated options exists too. Some guidance here:

http://tango.freedesktop.org/Tango_Icon_Theme_Guidelines

cheers
Fabrizio




On Thu, Jul 26, 2018 at 12:01 PM Andrey Kuznetsov 
wrote:

> Hmm, tough choice, I wish I could see the set for the rest of the icons in
> these 3 styles: 6[BCD]
>
> The reason I kept 6C is because the other icons might only look good in
> 1px body.
>
> 6D looks too close and 6B looks too far, so unless there's an intermediate
> that'll look good (doesn't matter if it's on the grid or not) then the
> concession has to be made towards one or the other based again on how the
> other icons might look.
>
> On Thu, Jul 26, 2018 at 2:26 AM, Jeff Young  wrote:
>
>> 6B is my new fave.
>>
>>
>>
>>
>
>
> --
> Remember The Past, Live The Present, Change The Future
> Those who look only to the past or the present are certain to miss the
> future [JFK]
>
> kandre...@gmail.com
> Live Long and Prosper,
> Andrey
> ___
> 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] Board setup icon

[Fabrizio Tappero]

it sounds good.

cheers
Fabrizio


On Wed, Jul 25, 2018 at 3:19 PM Jeff Young  wrote:

> Hi Fabrizio,
>
> I think we’re moving in both directions at once.  Where there is only a
> single context, I favour the generic icons (for instance, we’re moving to
> using a generic save icon in contexts where that isn’t ambiguous).
> However, where multiple contexts are visible at once (such as in LibEdit
> where we had both Edit Symbol Fields and Place Text using the ’T’ icon), I
> favour making them specific.
>
> Cheers,
> Jeff.
>
>
> On 25 Jul 2018, at 14:05, Fabrizio Tappero 
> wrote:
>
> Hi Guys,
> I just wold like to remind you that if you decide to personalize kicad
> icons, kicad will end up with a lot of icons to maintain.
>
> Currently kicad is using really a lot of icons and few years ago we
> tried to simplified them so that icons could be reused. This is useful
> when you try to give consistancy to the overall looks of KiCad GUI.
>
> What you guys are doing is maybe going back to what was kicad few
> years ago. I am not saying that this is a bad thing, mine is just a
> very generic comment and might not even apply to these icons in
> particular. I just would like to give you guys a larger overview of
> the icon situation.
>
> The "property" option is (often) defined with a cog wheel. It is not
> unusual for open source projects to quickly develop 25 property icons
> made with a smaller cog wheel overlaid an other icon. How, this visual
> technique might not be the best option. Overlay tiny images to convey
> specific meaning might not lead to a present use of the GUI.
>
> Also, I will not enter into tiny image pixel alignment problem because
> we did it so many time in the last 5 years here but instead I would
> love to propose to begin talking about the use of vector format icons
> and possible the use of script to combine icons.
>
> Just my 2c
>
> Cheers
> Fabrizio
>
> On Wed, Jul 25, 2018 at 12:45 PM John Beard 
> wrote:
>
>
> Hi Jeff,
>
> Sure thing! Here they are.
>
> I have modified part_properties (patch 1) and create field_properties
> and used in the menu and toolbar (patch 2).
>
> Attached are the PNGs for reference.
>
> Cheers,
>
> John
>
> On Tue, Jul 24, 2018 at 8:35 PM, Jeff Young  wrote:
>
> Hi John,
>
> When you get a chance could you also edit the part_properties_xpm icon to
> be the op-amp with a gear over it?
>
> Oh, and a new icon with the op-amp with a little ’T’ in the bottom right
> corner would be great.
>
> (Both are for the symbol editor.  They’re currently just a generic gear
> and a generic ’T’.)
>
> Thanks,
> Jeff.
>
>
> On 24 Jul 2018, at 16:56, Jeff Young  wrote:
>
> I’ve merged your icon, John.  Thanks for your contribution!
>
> On 24 Jul 2018, at 12:35, John Beard  wrote:
>
> Hi,
>
> Here is a new icon for the board setup toolbar and menu item. The
> generic gear icon is no clear, as it looks like "Preferences" rather
> than board setup.
>
> PNG included for reference only.
>
> Cheers,
>
> John
>
> <0001-Pcbnew-add-new-icon-for-board-setup.patch>___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
>
___
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] KiCad 5 release announcement update

[Fabrizio Tappero]

Hey guys,
I really would like to express my gratitude to all the people who have
made this possible. This is a fantastic step forward.

Cheers
Fabrizio

On Sun, Jul 22, 2018 at 11:21 PM Tomasz Wlostowski
 wrote:
>
> On 22/07/18 18:44, Wayne Stambaugh wrote:
> > I just pushed the updated version of the v5 release announcement[1].
> > Please let me know if you find any missing features.
>
> Hi Wayne,
>
> Great news. Let's have a drink!
>
> 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

___
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] KiCad logo author

[Fabrizio Tappero]

Hi Wayne,
How are you? I'm the author of the kicad logo and everything is of course
fine with me.

Cheers
Fabrizio


On Jul 18, 2018 7:36 PM, "Wayne Stambaugh"  wrote:

I've been getting a few requests recently about using the KiCad logo[1]
for merchandising and other uses that benefit the project.  I just want
to be sure the author of the logo (please refresh my memory who this is)
is OK with the project using the logo in this manner.  Thanks in advance
for the update.

Cheers,

Wayne

[1]:
https://github.com/KiCad/kicad-website/blob/master/static/
img/kicad_logo_paths.svg

___
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] python plugin folder misplaced?

[Fabrizio Tappero]

Hi Carsten,
thank you for the clarification.

cheers
Fabrizio


On Wed, May 30, 2018 at 5:22 PM, Carsten Schoenert 
wrote:

> Hello Fabrizio,
>
> Am 30.05.2018 um 16:42 schrieb Fabrizio Tappero:
> > ​Hello,
> > I recently discovered the existence of some useful BOM python plugins in
> > this folder:
> > /usr/lib/x86_64-linux-gnu/kicad/plugins/
> >
> > Wouldn't be recommendable to have the installer put the plugins folder
> in:
> > /usr/share/kicad/
>
> this depends if the plugin has a binary format or has a platform
> independent format.
>
> platform specific code -> /u/l/$platform/kicad/plugins
>
> platform independent code -> /u/s/kicad/plugins
>
> > In this way people might actually find a use these scripts easily.
> >
> > Additionally, it might be great to have the BOM menu button "Add Plugin"
> to
> > point to /usr/share/kicad/
>
> Well, this wouldn't be LSB conform. Python based plugins which also have
> some other usable functions which could be imported into my scripts need
> to go to a Python specific folder.
> And also binary based plugins need to go to a folder which is respecting
> the rules of the LSB.
>
> --
> Regards
> Carsten Schoenert
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] python plugin folder misplaced?

[Fabrizio Tappero]

​Hello,
I recently discovered the existence of some useful BOM python plugins in
this folder:
/usr/lib/x86_64-linux-gnu/kicad/plugins/

Wouldn't be recommendable to have the installer put the plugins folder in:
/usr/share/kicad/

In this way people might actually find a use these scripts easily.

Additionally, it might be great to have the BOM menu button "Add Plugin" to
point to /usr/share/kicad/

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

Re: [Kicad-developers] More default fields in schematic

[Fabrizio Tappero]

Hello,
I'd like to contribute with my 2c.

I completely agree with Kristoffer, there is a need for a "MPN" field hard
coded exactly as "Value" field is hard coded in Kicad.

As Wayne mentions the current "Preferences - General Options - Default
Fields" is not a bad option to add a "MPN" field. This is what I do and
this is what all my PCB colleges at work do.

Above solution will however not help the majority to do the same. I would
actually bet 2c that nearly nobody uses the Default Fields feature (most of
the people probably do it component by component). And this makes it a not
so useful feature.

Kicost is a god-made tool and for sure Dave will soon add MPN as a default
field in Kicad.

Cheers
Fabrizio





On Tue, May 22, 2018 at 3:41 PM, kristoffer ödmark <
kristofferodmar...@gmail.com> wrote:

> My updated patch forgot to add the files before doing the --amend.
>
> So it only updated the commit message. Here is the real file
>
> On Tue, 2018-05-22 at 07:52 -0500, Ben Hest wrote:
> > From a Digi-Key KiCad library standpoint, as we're still in beta, I
> > would
> > gladly change the fields to whatever would be decided.  Uniformity
> > for
> > plugins use would definitely be an advantage.
> >
> > -Ben
> >
> > On Tue, May 22, 2018 at 5:38 AM kristoffer ödmark <
> > kristofferodmar...@gmail.com> wrote:
> >
> > > Thanks! This is exactly what i was going for, non-intrusive
> > > oppurtunity
> > > for uniformity!
> > >
> > > I tested the bom2csv plugin, It did not include the empty fields.
> > >
> > > I also tested the bom_csv_sorted_by_ref, it did not include the
> > > empty
> > > values, but it included some values I had not specified, such as
> > > Manufacturer and Vendor even if they were not provided in the
> > > schematic.
> > >
> > > - Kristoffer
> > >
> > > On Tue, 2018-05-22 at 11:05 +0100, Jeff Young wrote:
> > > > I think I like this new patch.  It provides the /opportunity/ for
> > > > uniformity, without getting in the way of those who want to go
> > > > their
> > > > own way.
> > > >
> > > > Do the BOM generators automatically output all default fields or
> > > > only
> > > > those with values?
> > > >
> > > > > On 22 May 2018, at 09:22, kristoffer ödmark  > > > > @gma
> > > > > il.com> wrote:
> > > > >
> > > > > Please disregard my previous mail, it got mangled badly
> > > > > somehow, it
> > > > > did
> > > > > not look like that in my editor at least.
> > > > >
> > > > > On Mon, 2018-05-21 at 18:22 -0400, Wayne Stambaugh wrote:
> > > > > > Eeschema already supports creating default optional fields in
> > > > > > the
> > > > > > configuration settings dialog.  Used correctly, these will
> > > > > > give
> > > > > > you
> > > > > > the
> > > > > > same optional field names for every project without having to
> > > > > > add
> > > > > > them
> > > > > > by hand to each symbol and possibly typing in different field
> > > > > > names
> > > > > > by
> > > > > > accident.
> > > > >
> > > > > Different users will still type in different field names for
> > > > > the
> > > > > same
> > > > > things though. What you describe works as long as there is only
> > > > > one
> > > > > person in the entire projects lifetime, using only one
> > > > > computer.
> > > > >
> > > > > > The proposed patch would intermingle the default fields
> > > > > > with
> > > > > > existing schematic symbol fields which would break existing
> > > > > > BOMs
> > > > > > which I
> > > > > > don't think users will appreciate.
> > > > >
> > > > > The proposed patch will only change default settings, existing
> > > > > users
> > > > > with a config already in place will not be affected. I realised
> > > > > that
> > > > > the fields now accept empty values as well, so existing boms on
> > > > > new
> > > > > installations will not be affected either. I updated the patch,
> > > > > so
> > > > > it
> > > > > will not affect anyone that doesnt use the fields.
> > > > >
> > > > > > [...] As I've stated before, I can set 10
> > > > > > different designers down and I will get 10 different sets of
> > > > > > default
> > > > > > field names.  This really seems like me to be a configuration
> > > > > > issue.
> > > > >
> > > > > This is the problems I want to address, because those 10
> > > > > designers
> > > > > will
> > > > > by experience also spell the same field in 10 different ways.
> > > > > Making
> > > > > their fields incompatable. MPN, MFPN, #mfg, ManufPart, etc etc.
> > > > > Let
> > > > > those 10 designers remove the fields they do not want instead.
> > > > >
> > > > > > The only possible solution that I would accept is to move the
> > > > > > default
> > > > > > field definitions from the eeschema configuration file into
> > > > > > the
> > > > > > default
> > > > > > kicad project file.  This way existing projects would not be
> > > > > > polluted
> > > > > > with the proposed default fields and users could define their
> > > > > > own
> > > > > > default fields in a custom project file.
> > > > >
> > > > > Default 

Re: [Kicad-developers] Generate Drill File window and its buttons

[Fabrizio Tappero]

The "Generate" button label has made it but the colon inconsistency problem
is still there.

cheers
Fabrizio


On Tue, Apr 24, 2018 at 1:11 PM, Fabrizio Tappero <
fabrizio.tapp...@gmail.com> wrote:

> Hi JP,
> just to clarify. I think the "Generate" the colon inconsistency has not
> made it to v 5.0.
>
>
>
> Regards
> Fabrizio
>
>
>
>
>
>
> On Mon, Apr 23, 2018 at 4:45 PM, jp charras <jp.char...@wanadoo.fr> wrote:
>
>> Le 23/04/2018 à 15:56, Fabrizio Tappero a écrit :
>> > cheer Jeff, wouldn't be great if we could fix these text issues in the
>> 5.0 too
>> >
>> > cheers
>> > Fabrizio
>> >
>>
>> They are fixed (by Jeff) in commit 0bbf961 (2 months ago).
>>
>> >
>> > On Mon, Apr 23, 2018 at 11:49 AM, Jeff Young <j...@rokeby.ie > j...@rokeby.ie>> wrote:
>> >
>> > Hi Fabrizio,
>> >
>> > Some of these issues have been fixed in my 6.0 tree, but I’m not
>> sure I got all of them.  (It
>> > takes me a few hours to switch between 5.0 and 6.0, so I’ll check
>> later and post some screen
>> > shots for feedback.)
>> >
>> > Cheers,
>> > Jeff.
>> >
>> > PS: while it’s a couple of weeks out-of-date, a public version of
>> my 6.0 tree can be found
>> > here: https://git.launchpad.net/~jeyjey/kicad/log/?h=6.0
>> > <https://git.launchpad.net/%7Ejeyjey/kicad/log/?h=6.0>
>> >
>> >
>> >> On 23 Apr 2018, at 10:19, Fabrizio Tappero <
>> fabrizio.tapp...@gmail.com
>> >> <mailto:fabrizio.tapp...@gmail.com>> wrote:
>> >>
>> >> Hello,
>> >> in the latest KiCad this is what the Generate Drill Files window
>> looks like.
>> >>
>> >> 
>> >>
>> >> I wonder if "Drill File" should be changed to "*Generate Drill
>> Files*" and maybe do the same
>> >> fro Map and Report file.
>> >>
>> >> Also, I believe that the colon (":") in the section title is
>> totally superfluous. I the
>> >> previous window  (Print Window) colon is
>> >> used (not really sure why) only in some sections.
>> >>
>> >> 
>> >>
>> >> I have proposed these kind of changes in the past but I feel we
>> keep repeating the same mistakes.
>> >>
>> >> Just my 2C
>> >> Fabrizio
>> >>
>> >> ___
>> >> Mailing list: https://launchpad.net/~kicad-developers <
>> https://launchpad.net/%7Ekicad-developers>
>> >> Post to : kicad-developers@lists.launchpad.net > kicad-developers@lists.launchpad.net>
>> >> Unsubscribe : https://launchpad.net/~kicad-developers <
>> https://launchpad.net/%7Ekicad-developers>
>> >> More help   : https://help.launchpad.net/ListHelp <
>> 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
>> >
>>
>>
>> --
>> Jean-Pierre CHARRAS
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Generate Drill File window and its buttons

[Fabrizio Tappero]

Hi JP,
just to clarify. I think the "Generate" the colon inconsistency has not
made it to v 5.0.



Regards
Fabrizio






On Mon, Apr 23, 2018 at 4:45 PM, jp charras <jp.char...@wanadoo.fr> wrote:

> Le 23/04/2018 à 15:56, Fabrizio Tappero a écrit :
> > cheer Jeff, wouldn't be great if we could fix these text issues in the
> 5.0 too
> >
> > cheers
> > Fabrizio
> >
>
> They are fixed (by Jeff) in commit 0bbf961 (2 months ago).
>
> >
> > On Mon, Apr 23, 2018 at 11:49 AM, Jeff Young <j...@rokeby.ie  j...@rokeby.ie>> wrote:
> >
> > Hi Fabrizio,
> >
> > Some of these issues have been fixed in my 6.0 tree, but I’m not
> sure I got all of them.  (It
> > takes me a few hours to switch between 5.0 and 6.0, so I’ll check
> later and post some screen
> > shots for feedback.)
> >
> > Cheers,
> > Jeff.
> >
> > PS: while it’s a couple of weeks out-of-date, a public version of my
> 6.0 tree can be found
> > here: https://git.launchpad.net/~jeyjey/kicad/log/?h=6.0
> > <https://git.launchpad.net/%7Ejeyjey/kicad/log/?h=6.0>
> >
> >
> >> On 23 Apr 2018, at 10:19, Fabrizio Tappero <
> fabrizio.tapp...@gmail.com
> >> <mailto:fabrizio.tapp...@gmail.com>> wrote:
> >>
> >> Hello,
> >> in the latest KiCad this is what the Generate Drill Files window
> looks like.
> >>
> >> 
> >>
> >> I wonder if "Drill File" should be changed to "*Generate Drill
> Files*" and maybe do the same
> >> fro Map and Report file.
> >>
> >> Also, I believe that the colon (":") in the section title is
> totally superfluous. I the
> >> previous window  (Print Window) colon is
> >> used (not really sure why) only in some sections.
> >>
> >> 
> >>
> >> I have proposed these kind of changes in the past but I feel we
> keep repeating the same mistakes.
> >>
> >> Just my 2C
> >> Fabrizio
> >>
> >> ___
> >> Mailing list: https://launchpad.net/~kicad-developers <
> https://launchpad.net/%7Ekicad-developers>
> >> Post to : kicad-developers@lists.launchpad.net  kicad-developers@lists.launchpad.net>
> >> Unsubscribe : https://launchpad.net/~kicad-developers <
> https://launchpad.net/%7Ekicad-developers>
> >> More help   : https://help.launchpad.net/ListHelp <
> 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
> >
>
>
> --
> Jean-Pierre CHARRAS
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Generate Drill File window and its buttons

[Fabrizio Tappero]

cheer Jeff, wouldn't be great if we could fix these text issues in the 5.0
too

cheers
Fabrizio


On Mon, Apr 23, 2018 at 11:49 AM, Jeff Young <j...@rokeby.ie> wrote:

> Hi Fabrizio,
>
> Some of these issues have been fixed in my 6.0 tree, but I’m not sure I
> got all of them.  (It takes me a few hours to switch between 5.0 and 6.0,
> so I’ll check later and post some screen shots for feedback.)
>
> Cheers,
> Jeff.
>
> PS: while it’s a couple of weeks out-of-date, a public version of my 6.0
> tree can be found here: https://git.launchpad.net/~jeyjey/kicad/log/?h=6.0
>
>
> On 23 Apr 2018, at 10:19, Fabrizio Tappero <fabrizio.tapp...@gmail.com>
> wrote:
>
> Hello,
> in the latest KiCad this is what the Generate Drill Files window looks
> like.
>
> 
>
> I wonder if "Drill File" should be changed to "*Generate Drill Files*"
> and maybe do the same fro Map and Report file.
>
> Also, I believe that the colon (":") in the section title is totally
> superfluous. I the previous window  (Print Window) colon is
> used (not really sure why) only in some sections.
>
> 
>
> I have proposed these kind of changes in the past but I feel we keep
> repeating the same mistakes.
>
> Just my 2C
> Fabrizio
>
> ___
> 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] Kicad looks on high res monitor

[Fabrizio Tappero]

Hi Wayne,
thanks for the clarification.

Cheers
Fabrizio


On Wed, Apr 11, 2018 at 9:10 PM, Wayne Stambaugh <stambau...@gmail.com>
wrote:

> Fabrizio,
>
> We are aware of the issue but it will not be addressed for v5.  Chris'
> fix was a stop gap measure until we can implement something better.  As
> of right now, wxWidgets doesn't support drawing buttons with SVG so we
> will most likely have to provide multiple bitmap sizes for each image.
>
> Cheers,
>
> Wayne
>
> On 4/11/2018 7:32 AM, Fabrizio Tappero wrote:
> > Hello,
> > I had the change to test the latest kicad on a 3k 15" monitor and the
> > result is not very good.
> >
> > With a high res monitor, current kicad toolbar icons (and other elements
> > like layer selecting checkpoints) are painfully small and when scaled at
> > X2, for instnace, the overall KiCad app looks is much better (thanks
> > Chris Pavlina for this) but very far from its normal look.
> >
> > BTW the current icons scaling is not global but indipendent for cvpcb,
> > eeschema, etc. Maybe making it global could make more sense. Also the
> > same scaling is not applied to Kicad window. Maybe it should?
> >
> > thinking about elegant solutions, Gimp suffer the same problem
> > <https://www.youtube.com/watch?v=LR8dQsD9P5Y> but it could be fixed
> > since it uses SVG icons, I tihnk.
> >
> > Is there any change we could think about doing the same? Alternatively
> > we could generated two or 3 sets of icons (raster format) just for the
> > toolbar icons.
> >
> > Opinions?
> >
> > Cheers
> > Fabrizio
> >
> >
> >
> >
> > ___
> > 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] Kicad looks on high res monitor

[Fabrizio Tappero]

Hello,
I had the change to test the latest kicad on a 3k 15" monitor and the
result is not very good.

With a high res monitor, current kicad toolbar icons (and other elements
like layer selecting checkpoints) are painfully small and when scaled at
X2, for instnace, the overall KiCad app looks is much better (thanks Chris
Pavlina for this) but very far from its normal look.

BTW the current icons scaling is not global but indipendent for cvpcb,
eeschema, etc. Maybe making it global could make more sense. Also the same
scaling is not applied to Kicad window. Maybe it should?

thinking about elegant solutions, Gimp suffer the same problem
 but it could be fixed since
it uses SVG icons, I tihnk.

Is there any change we could think about doing the same? Alternatively we
could generated two or 3 sets of icons (raster format) just for the toolbar
icons.

Opinions?

Cheers
Fabrizio
___
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] What is the purpose of multiple 3D models?

[Fabrizio Tappero]

Multiple 3d shapes is actually great.
I use it when i have a component that is a second PCB that can be mounted
in two different orientations.



On Mar 31, 2018 7:39 PM, "jp charras"  wrote:

> Le 31/03/2018 à 19:28, Kevin Cozens a écrit :
> > On 2018-03-31 01:04 PM, jp charras wrote:
> >> A TO3 package with its heat-sink needs six 3D shapes (for guys who
> really *like* realistic 3D views
> >> of course...):
> >> the TO3 package.
> >> its heat-sink.
> >> 2 nuts.
> >> 2 bolts.
> >
> > Add one more if the TO-3 is in a socket. :)
> >
>
> Yes!
>
> And I forgot the washers.
>
> --
> Jean-Pierre CHARRAS
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [RFC] Able to install KiCad stable and "daily build" in same computer

[Fabrizio Tappero]

Hi,
As for freecad I think it is a great idea to have v5 and kicad-nightly.

Cheers
Fabrizio


On Apr 6, 2018 8:02 AM, "Strontium"  wrote:

> Hi Wayne,
>
> I agree with you about scope creep, however I do see issues for users.
>
> From an end user perspective V5 is a big change. I noticed big changes
> just from missing nightly updates for 2 months.  There may be an extended
> period of time when a user will want to run both versions, for many reasons.
>
>
> On 06/04/18 01:54, Wayne Stambaugh wrote:
>
>> We should defer this to v6 unless the fix is simple with little or no
>> risk of introducing new bugs.  I know it would be nice to have but I
>> could say that about a lot of things.  Scope creep will prevent us from
>> ever delivering v5.
>>
>> Cheers,
>>
>> Wayne
>>
>> On 4/5/2018 12:25 PM, Seth Hillbrand wrote:
>>
>>> If we are going to support multiple versions, on the developer side, we
>>> should add a preference versioning to the user configuration directory.
>>> Otherwise, fp-lib-table will being either pointing to v4 or v5
>>> footprints.  Likewise, there are a few preferences that only exist in v5
>>> and will be lost when v4 saves the preference file.
>>>
>>> To avoid cluttering the config directory, we could place the v5
>>> configurations in a v5 sub directory.  Configurations would be
>>> preferentially loaded from the v5 directory with a fall-back to the v4
>>> items if v5 items were not found.  Configurations would only be saved to
>>> the v5 subdir.
>>>
>> I agree with this, except I think we should ONLY read the V4 config once,
> when the program detects there is no V5 config sub directory at all.  After
> the V5 config is made and saved, the V4 config should be ignored, and they
> should diverge from that point.
>
> I don't know this code at all, but If no one else is doing it, I can try
> and look at it over the weekend.  But I wont waste time if the decision is
> already final.
>
> If we don't do this can I propose that the V5 packaging make a backup of
> the V4 config so that end users at least have the option of reverting
> without their config being lost.
>
> 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
>
___
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] Proposed roadmap changes

[Fabrizio Tappero]

Hello,
as Andy mentioned, I consider quite important to have schematic components
embedded into schematic file. This will allow people to share small
schematic sheets and schematic snippets without painful  lib cache file. In
Eagle and in Altium the "make library from schematic" capability is/was a
great feature.

In my opinion, the limitation of not being able to copy and paste schematic
portions (outside a kicad project) is a big limitation for anybody who
makes/reuse/share a lot of schematics.

Am I the only one suffering from the inability to reuse schematics?

my 2c
Fabrizio


On Tue, Mar 6, 2018 at 9:03 PM, Jon Evans  wrote:

> I will be sure to send a proposed update to the official doc after there
> is no more churn on my scratch pad doc.
> I am not allowing anyone to edit, only I can edit (anyone can comment, and
> I have been incorporating changes based on people's comments)
>
> I think the next pass (now that it has been a day with no one making any
> more comments on my doc) is to think about who is going to do what to make
> sure the manpower thing makes sense.
>
> -Jon
>
> On Tue, Mar 6, 2018 at 2:33 PM, Wayne Stambaugh 
> wrote:
>
>> I'm fine with using this for bike shedding as long as the results get
>> updated in the actual road map and this is not the official road map.
>> One caveat, by allowing anyone to edit this file, you may loose control
>> of it's content.  That's one of the things I don't like about launchpads
>> blueprints.  I also don't want this to turn into a popularity contest.
>> We have to make sensible decisions based upon project requirements and
>> manpower limitations so all final decisions are made by the lead
>> development team.
>>
>> On 3/5/2018 12:57 PM, Jon Evans wrote:
>> > Hi all,
>> >
>> > Since my day job involves a lot of engineering planning/timelines/etc,
>> > I've had this rolling around in my head...
>> > I started brainstorming some proposed changes to the roadmaps.
>> >
>> > I am using Google drive because that's what is easiest for me to play
>> > with; I'm happy to send patches against the official roadmaps if get
>> > some buy-in for this.
>> >
>> > Feel free to comment (either directly on the doc or by email) with
>> > thoughts on this.
>> >
>> > https://docs.google.com/document/d/1mpxqvxLv497cyfk8KTQijhyS
>> SpFxF7ooTtcT_HU86kw/edit#
>> >
>> > Basically what I am proposing is to put most of the energy into Eeschema
>> > for 6.0, with changes to other parts of the software basically being
>> > "whatever people have time left over for".  Everything else has been
>> > bumped to 7.0
>> >
>> > -Jon
>> >
>> >
>> > ___
>> > Mailing list: https://launchpad.net/~kicad-developers
>> > Post to : kicad-developers@lists.launchpad.net
>> > Unsubscribe : https://launchpad.net/~kicad-developers
>> > More help   : https://help.launchpad.net/ListHelp
>> >
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
> ___
> 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] Libedit and Modedit Icons

[Fabrizio Tappero]

The attached image shows a comparison between a poorly designed icons
and a well
designed icon .

thank you
Fabrizio



On Sat, Jan 13, 2018 at 2:19 AM, Nick Østergaard  wrote:

> IMHO the new icon collection looks awful. They are not pixel aligned and
> renders quite fuzzy in many details.
>
> http://storage4.static.itmages.com/i/18/0113/h_
> 1515804843_8735496_c1a004f249.png
>
> Looking at the the new ones are part of the red circles and renders fuzzy,
> while the green one looks more like the old one and renders more sharply.
>
> Some of the simplification made are an improvement, but the icons are not
> ready.
>
> In addition to that a white boarder has been added to overlay icons even
> when there is already a black border. I think only one of those should be
> there, and probably not a black and white. Usually a darker color of the
> same color as the overlay icon makes a better apperance when we are talking
> these sizes of icons. But this is really dependent on the icon composition.
> Some of the old icons with arrows also had this white boarder, but not the
> black one. When removing the white boarder it looked better.
>
> I don't like that so many icons are change without specific justification.
> or example the reload.svg was changed. The direction of the arrows changed
> and the color. Why? See attached image.
> The export STEP icon, you can't even read the P in STP.
>
> 2018-01-12 20:11 GMT+01:00 Wayne Stambaugh :
>
>> Oliver,
>>
>> The new icons look great.  They are far more coherent than what we had.
>> I merged your patch into the development branch.  Thank you for
>> contribution to KiCad.
>>
>> Cheers,
>>
>> Wayne
>>
>> On 01/11/2018 02:54 AM, Oliver Walters wrote:
>> > Wayne,
>> >
>> > I have taken further suggestions and final icon set is shown below:
>> >
>> > Inline image 1
>> >
>> > The attached patch incorporates all of the icon changes thus far
>> > implemented.
>> >
>> > Thanks,
>> > Oliver
>> >
>> > On Thu, Jan 11, 2018 at 1:58 AM, Wayne Stambaugh > > > wrote:
>> >
>> > I see scope creep happening here.  I thought the original goal was
>> to
>> > make some minor tweaks to our existing icons not wholesale
>> replacement
>> > of the them.  I don't like the camera either.  I'm not a big fan of
>> the
>> > calculator icon.  Both of these icons looks completely out of place
>> with
>> > our other icons.  Please keep the scope of these changes in check.
>> If
>> > we want to discuss an entirely new icon theme for v6, that's fine
>> at the
>> > appropriate time but not for v5.
>> >
>> > On 1/10/2018 9:42 AM, Jeff Young wrote:
>> > > Splendid!
>> > >
>> > > Although I agree with Kristoffer that the new bitmap2component
>> icon
>> > > isn’t much help.  Import/Export is the one area where we’ve kept
>> the
>> > > arrows (which I think is fine).  Given that, the pixelated “a”
>> with an
>> > > import arrow would be perfect.
>> > >
>> > > FWIW, this is one area where I disagree with Nick.  I did user
>> interface
>> > > design and software architecture for Adobe for 25 years and in my
>> > > professional opinion, these icons are a HUGE improvement.
>> > >
>> > > Cheers,
>> > > Jeff
>> > >
>> > >
>> > >> On 10 Jan 2018, at 14:28, Oliver Walters
>> > >> > mail.com>
>> > >> > > >> wrote:
>> > >>
>> > >> Also, would it be too much to ask for getting the arrows, the
>> > >> diskette and the folder in the repo with the patch,
>> basically if
>> > >> someone wants to create future icons. They could use the same
>> > >> arrows for any kind of export, import, save, inspect or view.
>> > >>
>> > >>
>> > >> I have created a set of "common icons" for exactly this purpose
>> :)
>> > >>
>> > >>
>> > >> On Thu, Jan 11, 2018 at 1:27 AM, Kristoffer Ödmark
>> > >> > > 
>> > > > >>
>> > >> wrote:
>> > >>
>> > >> Wow, really nice! Although, the icon for the bitmap2component
>> > >> basically looks like a screenshot symbol to me, or something
>> > >> related to a webcam.
>> > >>
>> > >> The old one isnt as polished, but I think it fits better.
>> > >>
>> > >> Also, would it be too much to ask for getting the arrows, the
>> > >> diskette and the folder in the repo with the patch,
>> basically if
>> > >> someone wants to create future icons. They could use the same
>> > >> arrows for any kind of export, import, save, inspect or view.

Re: [Kicad-developers] Libedit and Modedit Icons

[Fabrizio Tappero]

Hi,
I do not mean to offend anybody but, for years, there have been people
working very hard on the look of KiCad UI (see credits for details).

I have designed, and mediated with, the looks of KiCad for several years
and I am afraid the icons that have been submitted are not a step forward.
When it is about icons, everybody has an opinion and, in general, that is a
good thing.

Kicad Icons are 26pix for 26pix, if you want to adventure in designing an
icon for KiCad I suggest to open Inkscape with a 26X26 preview and try to
put stuff in it and see how it looks. Additionally, generally speaking,
colors cannot be too poppy and edges cannot be too sharp. In 2018 it is not
recommendable to write things in a 26pX26p icon nor overlay one image on
top of an other. Edges should be highlighter with an additional negative
edge. All this is just common sense (not even knowledge) in the practice of
designing icons.

Not to offend anybody but to an mildly trained eye, all the icons that you
submitted are not even close to the quality of what, for instance,
Konsantin has posted few mails up.

An other thing is documentation, Kicad looks cannot be changed in one go
but changes must happen slowly so that documentation does not stay out of
sync.

There are many icons that I know are not so good but I also know that now
there are really a lot of icons that are not so good.

My humble opinion, but it is just my humble opinion is to reverse all this
icon changes and if there is anybody interested in adventuring into icon
design and submit new icons, please go ahead and submit these icons to
myself and/or Konstantin so that we review them. Once again, this is just
my opinion.

I know that all these icons you submitted in the last 7 days seem better
and pop out more and are more meaningful to you. I think they are not.

I hope I have not offended anybody with the rant.


Cheers
Fabrizio










On Fri, Jan 12, 2018 at 6:46 PM, Michael Kavanagh <
mich...@michaelkavanagh.me> wrote:

> Can I suggest after v5 UI/graphic design is split off into a separate
> group with a suitably qualified person in charge (e.g. like the lib/docs
> maintainers)? With a core team and a UI policy it might make for a more
> cohesive look and feel rather than several people having a crack at
> different bits in different applications.
>
> Just a thought.
>
> On 12 January 2018 at 12:46, Константин Барановский <
> baranovskiykonstan...@gmail.com> wrote:
>
>> Forgot to attach the source of bitmap2component icon.
>>
>> 2018-01-12 14:39 GMT+02:00 Jeff Young :
>>
>>> Agreed.  Your bitmap2component idea is excellent.
>>>
>>> > On 12 Jan 2018, at 12:37, jp charras  wrote:
>>> >
>>> > Le 12/01/2018 à 13:27, Константин Барановский a écrit :
>>> >> Thanks for your answers. What are you think about this icon for
>>> bitmap2component?
>>> >
>>> > I do like the pcb calculator and the bitmap2component icons.
>>> >
>>> >>
>>> >> 2018-01-12 13:00 GMT+02:00 Simon Wells > swel...@gmail.com>>:
>>> >>
>>> >>I agree with Jeff, Not a fan of the pcbnew/modedit/gerbview icons,
>>> I don’t mind the eeschema
>>> >>icon, but also not a fan of the bmp2cmp icon, the only way i can
>>> see bmp2cmp being better would
>>> >>be a (well known) bitmap looking square with an arrow pointing to
>>> a footprint and/or symbol
>>> >>
>>> >>Simon
>>> >>
>>> >>
>>> >>>On 12/01/2018, at 11:47 PM, Jeff Young > j...@rokeby.ie>> wrote:
>>> >>>
>>> >>>I like the more subdued colours in Oliver’s, although I do like
>>> your calculator icon (perhaps
>>> >>>with Oliver’s pcb colouring in the background).
>>> >>>
>>> >>>Cheers,
>>> >>>Jeff.
>>> >>>
>>> >>>
>>> On 12 Jan 2018, at 10:22, Константин Барановский <
>>> baranovskiykonstan...@gmail.com
>>> > wrote:
>>> 
>>> Hi Everybody!
>>> As you know (or not) I'm work on new icons for KiCad for a long
>>> time:
>>> https://code.launchpad.net/~baranovskiykonstantin/kicad/+git
>>> /kicad/+ref/new_icons_rebased
>>> >> git/kicad/+ref/new_icons_rebased>
>>> 
>>> And inspired by changes in app icons I made my variant.
>>> Please, leave feedback.
>>> 
>>> 2018-01-12 5:28 GMT+02:00 Andrey Kuznetsov >> >:
>>> 
>>> Awesome, thanks!
>>> 
>>> Looks good.
>>> 
>>> On Thu, Jan 11, 2018 at 7:27 PM Oliver Walters <
>>> oliver.henry.walt...@gmail.com
>>> > wrote:
>>> 
>>> Andrey,
>>> 
>>> Here's all I can provide currently (at work!)
>>> 
>>> 
>>> 
>>> I have sent the entire patch to Wayne and JP privately
>>> so the merging is now in their
>>>    

Re: [Kicad-developers] [PATCH] Implement primitive icon scaling for high DPI

[Fabrizio Tappero]

Hi Thomas,
thanks for the pics. All icons seem out of focus to me. I however
understand that if you need bigger icons you need bigger incons

 It might make sense to chose a 200% magnification only. In this case
sharpness is preserved.

I shall also say that if your monitor has a higher enough DPI sharpness due
to icon magnification should not be visible.

Cheers
Fabrizio

On Mon, Jan 15, 2018 at 4:51 PM, Thomas Figueroa <tom_figue...@hotmail.com>
wrote:

> I’ve attached scaling at 150%, 225%, and 250% (W10, 4k screen with DPI
> around 280 like Chris). The icons all look fine at all of these scalings.
> Before Chris’s patch, I manually created bitmaps from the SVGs at higher
> resolution (2.25x) and they not only scaled very well, they looked very
> nice. So based on these two experiences, the icons are very capable of
> scaling appropriately.
>
>
>
>
> --
> *From:* Kicad-developers <kicad-developers-bounces+tom_figueroa=
> hotmail@lists.launchpad.net> on behalf of Fabrizio Tappero <
> fabrizio.tapp...@gmail.com>
> *Sent:* Monday, January 15, 2018 3:52:32 AM
> *To:* Chris Pavlina
> *Cc:* KiCad Developers
> *Subject:* Re: [Kicad-developers] [PATCH] Implement primitive icon
> scaling for high DPI
>
> Hi,
> Can anybody with a high DPI monitor post some pics at different scaling
> setting please.
>
> An enormous effort was put in making this icons look good in they actual
> fixed resolution. I am curious how a >250DPI monitor can display icons well
> regardless of this effort.
>
> Cheers
> Fabrizio
>
>
> On Thu, Jan 11, 2018 at 6:06 PM, Chris Pavlina <pavlina.ch...@gmail.com>
> wrote:
>
>> Yup. For reference my own display is around 280 DPI.
>>
>> On Thu, Jan 11, 2018 at 10:35:15AM +, Jeff Young wrote:
>> > 2560x1440 @ 24” is only 122 DPI.
>> >
>> > Apple’s Retina displays are 220 or 227, and the Surface Book in the
>> original bug report is 267 DPI.
>> >
>> > > On 11 Jan 2018, at 09:54, kristoffer Ödmark <
>> kristofferodmar...@gmail.com> wrote:
>> > >
>> > > I have 2560x1440, 24" screens, I think those qualifies as high DPI?
>> > >
>> > > The slider value is at 100, and the diag value is at 23. The icons
>> are ish 5mm large.
>> > >
>> > > But i guess that is uneccesary since It seems the scaling works as
>> intended, I was just doing it wrong, so no errors, sorry :)
>> > >
>> > > The scaling seems correct as well, 100 = 5mm, 150 = 7.5, 200 = 11,
>> measured with a tape measure, so variance in size is expected.
>> > >
>> > >
>> > > Application: kicad
>> > > Version: (2018-01-11 revision a5b3d8e57)-master, debug build
>> > > Libraries:
>> > > wxWidgets 3.0.3
>> > > libcurl/7.57.0 OpenSSL/1.1.0g zlib/1.2.11 libidn2/2.0.4
>> libpsl/0.19.1 (+libidn2/2.0.4) libssh2/1.8.0 nghttp2/1.29.0
>> > > Platform: Linux 4.9.74-2-MANJARO x86_64, 64 bit, Little endian, wxGTK
>> > > Build Info:
>> > > wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8) GTK+
>> 2.24
>> > > Boost: 1.65.1
>> > > Curl: 7.57.0
>> > > Compiler: GCC 7.2.1 with C++ ABI 1011
>> > >
>> > > Build settings:
>> > > USE_WX_GRAPHICS_CONTEXT=OFF
>> > > USE_WX_OVERLAY=OFF
>> > > KICAD_SCRIPTING=ON
>> > > KICAD_SCRIPTING_MODULES=ON
>> > > KICAD_SCRIPTING_WXPYTHON=ON
>> > > KICAD_SCRIPTING_ACTION_MENU=OFF
>> > > BUILD_GITHUB_PLUGIN=ON
>> > > KICAD_USE_OCE=ON
>> > > KICAD_SPICE=ON
>> > >
>> > >
>> > > On 2018-01-11 01:13, Chris Pavlina wrote:
>> > >> If your system DPI is already within a certain range it won't do
>> > >> anything. Are you using a high DPI display? If it's not scaled
>> > >> correctly, would you please share with me the diagnostic number
>> reported
>> > >> by the scale slider in eeschema prefs as well as a rough indication
>> of
>> > >> the icons' physical size? Thanks.
>> > >>
>> > >> On Wed, Jan 10, 2018 at 11:16:46PM +, kristoffer Ödmark wrote:
>> > >>> Tried the patch, didnt really notice anything different though, I
>> guess you
>> > >>> need to add some custom scaling for this to take effect?
>> > >>>
>> > >>>
>> > >>> On 2018-01-10 22:23, Chris Pavlina wrote:
>&

Re: [Kicad-developers] [PATCH] Implement primitive icon scaling for high DPI

[Fabrizio Tappero]

Hi,
Can anybody with a high DPI monitor post some pics at different scaling
setting please.

An enormous effort was put in making this icons look good in they actual
fixed resolution. I am curious how a >250DPI monitor can display icons well
regardless of this effort.

Cheers
Fabrizio


On Thu, Jan 11, 2018 at 6:06 PM, Chris Pavlina 
wrote:

> Yup. For reference my own display is around 280 DPI.
>
> On Thu, Jan 11, 2018 at 10:35:15AM +, Jeff Young wrote:
> > 2560x1440 @ 24” is only 122 DPI.
> >
> > Apple’s Retina displays are 220 or 227, and the Surface Book in the
> original bug report is 267 DPI.
> >
> > > On 11 Jan 2018, at 09:54, kristoffer Ödmark <
> kristofferodmar...@gmail.com> wrote:
> > >
> > > I have 2560x1440, 24" screens, I think those qualifies as high DPI?
> > >
> > > The slider value is at 100, and the diag value is at 23. The icons are
> ish 5mm large.
> > >
> > > But i guess that is uneccesary since It seems the scaling works as
> intended, I was just doing it wrong, so no errors, sorry :)
> > >
> > > The scaling seems correct as well, 100 = 5mm, 150 = 7.5, 200 = 11,
> measured with a tape measure, so variance in size is expected.
> > >
> > >
> > > Application: kicad
> > > Version: (2018-01-11 revision a5b3d8e57)-master, debug build
> > > Libraries:
> > > wxWidgets 3.0.3
> > > libcurl/7.57.0 OpenSSL/1.1.0g zlib/1.2.11 libidn2/2.0.4
> libpsl/0.19.1 (+libidn2/2.0.4) libssh2/1.8.0 nghttp2/1.29.0
> > > Platform: Linux 4.9.74-2-MANJARO x86_64, 64 bit, Little endian, wxGTK
> > > Build Info:
> > > wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8) GTK+
> 2.24
> > > Boost: 1.65.1
> > > Curl: 7.57.0
> > > Compiler: GCC 7.2.1 with C++ ABI 1011
> > >
> > > Build settings:
> > > USE_WX_GRAPHICS_CONTEXT=OFF
> > > USE_WX_OVERLAY=OFF
> > > KICAD_SCRIPTING=ON
> > > KICAD_SCRIPTING_MODULES=ON
> > > KICAD_SCRIPTING_WXPYTHON=ON
> > > KICAD_SCRIPTING_ACTION_MENU=OFF
> > > BUILD_GITHUB_PLUGIN=ON
> > > KICAD_USE_OCE=ON
> > > KICAD_SPICE=ON
> > >
> > >
> > > On 2018-01-11 01:13, Chris Pavlina wrote:
> > >> If your system DPI is already within a certain range it won't do
> > >> anything. Are you using a high DPI display? If it's not scaled
> > >> correctly, would you please share with me the diagnostic number
> reported
> > >> by the scale slider in eeschema prefs as well as a rough indication of
> > >> the icons' physical size? Thanks.
> > >>
> > >> On Wed, Jan 10, 2018 at 11:16:46PM +, kristoffer Ödmark wrote:
> > >>> Tried the patch, didnt really notice anything different though, I
> guess you
> > >>> need to add some custom scaling for this to take effect?
> > >>>
> > >>>
> > >>> On 2018-01-10 22:23, Chris Pavlina wrote:
> >  Sure, assign me to it. I should have time to work on it tonight or
> >  tomorrow.
> > 
> >  On Wed, Jan 10, 2018 at 04:20:21PM -0500, Wayne Stambaugh wrote:
> > > FYI, the edit footprint dialog in Pcbnew is not sized properly (at
> least
> > > on windows) which I'm pretty sure is related to your recent HiDPI
> work.
> > > Do you want me to file a bug report for it?
> > >
> > > On 1/10/2018 2:01 PM, Chris Pavlina wrote:
> > >> By the way, I'm going to go ahead and push this tonight-ish if
> nobody
> > >> objects. I know it's on the big side, but due to my limited
> number of
> > >> machines to test on I really want time for user feedback. I'll be
> around
> > >> to put out any fires.
> > >>
> > >> On Wed, Jan 10, 2018 at 11:07:49AM -0700, Chris Pavlina wrote:
> > >>> Rebased patch attached.
> > >>>
> > >>> On Tue, Jan 09, 2018 at 01:27:16PM +, Maciej Sumiński wrote:
> >  Hi Chris,
> > 
> >  The patch does not apply cleanly on the current master, would
> you rebase
> >  it? Thanks in advance.
> > 
> >  Cheers,
> >  Orson
> > 
> >  On 01/09/2018 03:43 AM, Chris Pavlina wrote:
> > > Hi,
> > >
> > > As discussed with Wayne earlier, I've attached a patch which
> adds simple
> > > toolbar icon scaling so the toolbars are readable on high-DPI
> systems.
> > >
> > > This is meant as a stopgap for 5.0, with plans to add proper
> scaled
> > > icons in the 6.0 cycle. A function KiScaledBitmap() is added,
> which
> > > works like KiBitmap() except it scales the bitmap according to
> the
> > > calling window's font size. Controls have been added to all
> the main
> > > applications to let the user select scaling manually (these
> were omitted
> > > from smaller apps that didn't already have a place to put
> them).
> > >
> > > In addition, in eeschema only, the pixel height of the system
> font is
> > > shown in the options dialog for diagnostics. This is only for
> collecting
> > > feedback before 5.0 release from users with different 

Re: [Kicad-developers] Modeless dialog action buttons

[Fabrizio Tappero]

Hi,

Jeff, when you say "Drill File Generation"... what do you mean?

talking about button labels (see below) I have an issue with "Drill File"
as well as "Map File" and "Report File". I feel they should be changed into
"Generate Drill File" and "Generate Map File", etc.

Am I wrong? Suggestions?

Cheers
Fabrizio



[image: Inline image 1]

On Sun, Dec 24, 2017 at 12:24 AM, Bernhard Stegmaier <
stegma...@sw-systems.de> wrote:

> … same for the new remap dialog in eeschema.
>
> Regards,
> Bernhard
>
> > On 23. Dec 2017, at 17:28, Andy Peters  wrote:
> >
> >
> >> On Dec 23, 2017, at 9:17 AM, Jeff Young  wrote:
> >>
> >> Found another one: Drill Files Generation.
> >
> > In pcbnew, the netlist import dialog has a “cancel” button, which is
> useful for when you decide you don’t want to do the import, but once the
> import has completed, that button should change to “close.”
> >
> > I’m not sure that the position of the “cancel” button in that dialog
> makes sense; perhaps it should be at the bottom of the buttons.
> >
> > -a
> >
> >
> >
> >>
> >>> On 21 Dec 2017, at 14:33, Wayne Stambaugh 
> wrote:
> >>>
> >>> They should be "Close".  I'll will try to get them fixed soon.
> >>>
> >>> On 12/21/2017 8:00 AM, Jeff Young wrote:
>  There are several modeless dialogs in pcbnew (for instance, Exchange
> Footprint and Plot) which have action buttons and a “Cancel” button.
> 
>  These shouldn’t be called “Cancel” as they don’t cancel the action.
> They should be either “Done” or “Close”.
> 
>  Comments?
> 
>  (Resending to fix bogus thread link.)
>  ___
> >
> > ___
> > 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] Eeschema Line Styles

[Fabrizio Tappero]

Hi Seth,
Thanks a lot for this! I will definetly use it a lot!

Maybe millimeters should be mm?

Cheers
Fabrizio


On Nov 15, 2017 2:18 PM, "jp charras"  wrote:

Le 15/11/2017 à 01:27, Seth Hillbrand a écrit :
> Attached is the updated line styles patchset.  This implements the
COLOR4D_PICKER_DIALOG and ensures
> that the alpha channel remains opaque.
>
> The dotted line, I agree doesn't look too dotted.  This is the wxDOT
style but apparently, it
> doesn't account for the line caps.  I've replaced this with a
user-defined dotted line.  This is the
> smallest length of dot that we are allowed in wx.  Better than the
default even if it isn't quite
> "dotted".
>
> -Seth
>

Thanks.

I committed your patch.

I also modified the way the style parameters are stored in files, because
the style was not very
user readable, and did not work in some non English countries.

--
Jean-Pierre CHARRAS

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

Re: [Kicad-developers] [PATCH] LIB_TABLE tweaks

[Fabrizio Tappero]

Hey Wayne,
thanks for the link. I have read it and followed the steps. All is working
now.

Thanks a lot for the info.

cheers
Fabrizio


On Thu, Nov 16, 2017 at 1:38 PM, Wayne Stambaugh <stambau...@gmail.com>
wrote:

> Did you follow the instructions I provided on the kicad website blog post?
>
> http://kicad-pcb.org/post/symbol-lib-table/
>
> On 11/16/2017 5:20 AM, Fabrizio Tappero wrote:
> > hi Guys,
> > I can confirm that the recent lib table commits have made my working
> > version of kicad totally unable to open recent schematics
> >
> >
> > Inline image 1
> > Inline image 3
> >
> >
> > all components seem visible and usable (if a new schematic is created)
> > but kicad is unable to load ALL symbols
> > from a schematic that was done one month ago.
> >
> > Inline image 2
> >
> > I do not know how to fix this any idea?
> >
> > cheers
> > Fabrizio
> >
> >
> >
> >
> > On Thu, Nov 16, 2017 at 11:00 AM, Fabrizio Tappero
> > <fabrizio.tapp...@gmail.com <mailto:fabrizio.tapp...@gmail.com>> wrote:
> >
> > Hi Guys,
> > hum... my version of kicad is a nightly buid that I heavily use at
> > work and that keep update every now and then. Probably all this
> > started a two years ago or so.
> >
> > I have deleted the lib table and let kicad propose the new one so
> > now all is fine.
> >
> > The only problem I experienced is that the "RESCUE" rename action
> > has screwed up all my schematics. Thank god git was made.
> >
> > I noticed some lib issues with the cache lib file that trigger a
> > rescue menu too. I am sorry I cant really ping point the problem. I
> > just wanted to get this email out there for future reference. I
> > realise however that I am not really providing good info
> >
> > cheers
> > Fabrizio
> >
> >
> >
> >
> > On Wed, Nov 15, 2017 at 10:42 PM, Oliver Walters
> > <oliver.henry.walt...@gmail.com
> > <mailto:oliver.henry.walt...@gmail.com>> wrote:
> >
> >
> > On Thu, Nov 16, 2017 at 1:42 AM, Wayne Stambaugh
> > <stambau...@gmail.com <mailto:stambau...@gmail.com>> wrote:
> >
> > Gentlemen,
> >
> > I'm not sure about breaking the library table file format
> > for the
> > version 5 release.  If we do, the footprint library table
> > will not be
> > compatible with older versions.  I would prefer that we push
> > this change
> > into version 6.
> >
> >
> > I'm not sure I understand why it would be ok to break it in v6
> > but not v5? We are already introducing the sym-lib-table. If we
> > waited until v6 to make this change, then we would break *both*
> > tables (instead of just one).
> >
> >
> >
> > I'm OK with the progress dialog.  If you split that out as
> > separate
> > patch, I will merge it.
> >
> > Cheers,
> >
> > Wayne
> >
> > On 11/15/2017 9:38 AM, Tomasz Wlostowski wrote:
> > > On 15/11/17 15:30, Maciej Suminski wrote:
> > >> Hi Oliver,
> > >>
> > >> Thank you for restoring the progress bar dialog. While
> > the library load
> > >> time has recently decreased a lot, the UI freeze still
> > happens with long
> > >> library lists.
> > >> Disclaimer: I have not looked at the code yet, I am just
> > praising the idea.
> > >>
> > >> As you are looking on the Symbol Library Table dialog, I
> > suppose you
> > >> might be also tempted to add a file browser to add new
> > libraries. If
> > >> that is the case, please refrain from doing so - it is
> > done in the
> > >> library editor refactor branch. If you had no such
> > intention, then
> > >> simply ignore this message.
> > >
> > > Hi Olivier & Orson,
> > >
> > > I partially implemented the simplified dialog I proposed
> > on the dev list
> > > a few 

Re: [Kicad-developers] [PATCH] LIB_TABLE tweaks

[Fabrizio Tappero]

Hi Guys,
hum... my version of kicad is a nightly buid that I heavily use at work and
that keep update every now and then. Probably all this started a two years
ago or so.

I have deleted the lib table and let kicad propose the new one so now all
is fine.

The only problem I experienced is that the "RESCUE" rename action has
screwed up all my schematics. Thank god git was made.

I noticed some lib issues with the cache lib file that trigger a rescue
menu too. I am sorry I cant really ping point the problem. I just wanted to
get this email out there for future reference. I realise however that I am
not really providing good info

cheers
Fabrizio




On Wed, Nov 15, 2017 at 10:42 PM, Oliver Walters <
oliver.henry.walt...@gmail.com> wrote:

>
> On Thu, Nov 16, 2017 at 1:42 AM, Wayne Stambaugh 
> wrote:
>
>> Gentlemen,
>>
>> I'm not sure about breaking the library table file format for the
>> version 5 release.  If we do, the footprint library table will not be
>> compatible with older versions.  I would prefer that we push this change
>> into version 6.
>>
>
> I'm not sure I understand why it would be ok to break it in v6 but not v5?
> We are already introducing the sym-lib-table. If we waited until v6 to make
> this change, then we would break *both* tables (instead of just one).
>
>
>>
>> I'm OK with the progress dialog.  If you split that out as separate
>> patch, I will merge it.
>>
>> Cheers,
>>
>> Wayne
>>
>> On 11/15/2017 9:38 AM, Tomasz Wlostowski wrote:
>> > On 15/11/17 15:30, Maciej Suminski wrote:
>> >> Hi Oliver,
>> >>
>> >> Thank you for restoring the progress bar dialog. While the library load
>> >> time has recently decreased a lot, the UI freeze still happens with
>> long
>> >> library lists.
>> >> Disclaimer: I have not looked at the code yet, I am just praising the
>> idea.
>> >>
>> >> As you are looking on the Symbol Library Table dialog, I suppose you
>> >> might be also tempted to add a file browser to add new libraries. If
>> >> that is the case, please refrain from doing so - it is done in the
>> >> library editor refactor branch. If you had no such intention, then
>> >> simply ignore this message.
>> >
>> > Hi Olivier & Orson,
>> >
>> > I partially implemented the simplified dialog I proposed on the dev list
>> > a few days ago. Would anyone be interested in helping me finish it?
>> >
>> > Tom
>> >
>> >>
>> >> Cheers,
>> >> Orson
>> >>
>> >> On 15/11/2017 12:41 PM, Oliver Walters wrote:
>> >>> Wayne, et al,
>> >>>
>> >>> I am really liking the way that the new symbol table works! Thanks for
>> >>> the huge effort that has gone into this.
>> >>>
>> >>> One thing that I have noticed is that when opening (for e.g.) the
>> >>> component chooser, the UI hangs while all the libraries load.
>> Previously
>> >>> there was a progress dialog which at least informed the user what was
>> >>> going on.
>> >>>
>> >>> I have re-implemented this dialog in the attached patch set.
>> >>>
>> >>> Further, I have also implemented a way to individually enable /
>> disable
>> >>> each row in the library tables (this works for SYMBOL_LIB and FP_LIB).
>> >>>
>> >>> This is based on the idea by Tomasz. Example screenshot below:
>> >>>
>> >>> Inline image 1
>> >>>
>> >>> I have tweaked the base LIB_TABLE_GRID code such that disabled entries
>> >>> are greyed out and made italic. The enabled / disabled status is
>> >>> persistent in the sym/fp_lib_table files. Older version of
>> xxx_lib_table
>> >>> files are read with all rows enabled by default.
>> >>>
>> >>> Please find patch set attached.
>> >>>
>> >>> 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
>> >
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : 

Re: [Kicad-developers] [PATCH] Add live footprint filtering in modview window

[Fabrizio Tappero]

hi Guys,
this is a great feature. It would be a good thing to have a gray suggestion
often used in webpages and phone apps. Example here:

https://storage.googleapis.com/material-design/publish/material_v_12/assets/0B5ZSepuCX1xOOURmSHNjdktDR28/discoverable-extracted-label1.png


cheers
Fabrizio



On Tue, Oct 31, 2017 at 1:32 PM, Wayne Stambaugh 
wrote:

> On 10/31/2017 1:25 AM, Oliver Walters wrote:
> > Hmm, I had thought that there was a way to load only the *names* of
> > footprints, rather than individually parsing each footprint file. It
> > appears that this is not the case. Any suggestions on how the speed
> > could be improved? Currently I'm reading out all the footprint names in
> > each footprint library and only storing the names (wxString) rather than
> > the MODULE* objects. However, I still have to parse the entire library
> > on load.
> >
> > Ideally, I think it would be good to just read in the names, and then
> > load and display individual MODULE objects on demand.. Is this possible?
>
> This is possible (although not implemented) for library types (kicad,
> geda) that use one file per footprint.  You could just read the file
> names from the folder and load the files as required.  If you want to
> search any other properties of the footprint, then you will have to load
> all of the footprints anyway.  I don't know if this would be worth the
> effort.
>
> For library types that contain multiple footprints per file (legacy,
> Eagle), this wouldn't make much sense.  Parsing the entire file just to
> pick out the footprint names probably isn't going to save you very much
> time.
>
> >
> > On Tue, Oct 31, 2017 at 10:40 AM, Wayne Stambaugh  > > wrote:
> >
> > On 10/30/2017 5:23 PM, Oliver Walters wrote:
> > > Thanks for the suggestions on fixing the text. I have that sorted.
> > >
> > > I will look into different ways of caching footprint data so it is
> quicker.
> > >
> > > Wayne, I didn't know about FOOTPRINT_FILTER I will switch to using
> that
> > > instead (and provide regex search).
> >
> > Thanks Oliver!
> >
> > >
> > > On 31 Oct 2017 06:55, "Seth Hillbrand"  
> > > >>
> wrote:
> > >
> > > On Mon, Oct 30, 2017 at 11:42 AM, Wayne Stambaugh
> > > 
> > >>wrote:
> > >
> > > On 10/30/2017 1:16 PM, Seth Hillbrand wrote:
> > > > Oliver, this is neat and very helpful.
> > > >
> > > > The greyed-out thing is a wx2.8 bug.  You can work
> > around it by setting
> > > > the foreground color when updating the filter like this:
> > > >
> > > >  void FOOTPRINT_VIEWER_FRAME::OnFilterUpdated(
> > wxCommandEvent& event )
> > > >  {
> > > > +// Workaround wx2.8 bug showing greyed color
> > > > +if( m_searchBox->GetValue() !=
> > m_searchBox->GetDescriptiveText() )
> > > > +m_searchBox->SetForegroundColour(
> > > > m_searchBox->GetDefaultAttributes().colFg );
> > > > +
> > > >  // Filter is non case sensitive
> > > >  wxString filter = m_searchBox->GetValue().Lower();
> > > >
> > > > The searchbox handles resetting it to grey on idle()
> > when the text is empty.
> > >
> > > Don't you mean wx 3.0?  CMake should not even generate the
> > build
> > > configuration files without wx 3.0 or greater.
> > >
> > >
> > > Hmm... This was an issue back in 2.8 that appears to be only
> > partly
> > > fixed.  The workaround I suggest above is functional but, for
> > this,
> > > we can also execute a cleaner fix by setting the descriptive
> > text in
> > > the declaration:
> > >
> > > @@ -67,9 +67,10 @@ void FOOTPRINT_VIEWER_FRAME::
> ReCreateHToolbar()
> > >  KiBitmap( module_xpm ),
> > >  _( "Select footprint to
> > browse" ) );
> > >
> > > -m_searchBox = new wxSearchCtrl( m_mainToolBar,
> > > ID_MODVIEW_SEARCH_TEXT );
> > > +m_searchBox = new wxSearchCtrl( m_mainToolBar,
> > > ID_MODVIEW_SEARCH_TEXT,
> > > +_( "Enter filter string" ) );
> > >  m_searchBox->SetMinSize( wxSize( 250, 30 ) );
> > > -m_searchBox->SetDescriptiveText( _( "Enter filter
> > string" ) );
> > >
> > >
> > >
> > > ___
> > > Mailing list: 

Re: [Kicad-developers] Datasheet confusion

[Fabrizio Tappero]

Hi Kristoffer,
I am a big supporter of this option. I am often in need of showing a
datasheet with a right click on component. It would be great to be able to
do it in the completed schematic as well as in the completed pcb layout.

cheers
Fabrizio



On Fri, Oct 13, 2017 at 2:18 PM, Kristoffer Ödmark <
kristofferodmar...@gmail.com> wrote:

> There is a "show documentation" context field, but it only uses the
> documentation string, so if i put a value into the datasheet field. The
> menu doesnt show, I do not think that adding a "Show documentation" and a
> "Show Datasheet" is a good solution.
>
> I will create a patch, probably this weekend and submit, I think it will
> highlight the problem better. I believe its a trivial fix.
>
> - Kristoffer
>
>
> On 10/13/2017 01:54 PM, Wayne Stambaugh wrote:
>
>> On 10/13/2017 6:19 AM, Kristoffer Ödmark wrote:
>>
>>> Thanks you very much for that clarification, I for one would really
>>> enjoy a clarification of the documentation and Datasheet string. KiCad
>>> has been around for quite a while now, interesting how technology has
>>> changed during that time.
>>>
>>> For another question, would It be okay to redirect the context menu in
>>> eeschema, so that the "Show documentation" context menu would use the
>>> Field "Datasheet"? And use the "documentation" string to fill the
>>> "Datasheet" field when adding the symbol to the schematic?
>>>
>>
>> I'm OK with adding both a "Show Documentation" (should be visible only
>> when the field is not empty) to the symbol context menu and an "Edit
>> Datasheet Field" entry to the "Properties" sub-menu.
>>
>>
>>> I guess this would be considered a temporary fix if okay?
>>>
>>> On 10/13/2017 08:51 AM, jp charras wrote:
>>>
>>> FYI, in fact this confusion comes from a bug introduced a long time ago:

 Initially, the field name was "Sheet" not "Datasheet".
 It should be "SchematicSheet"

 The purpose was to be able to create a component acting as a
 hierarchical sheet:
 The component in a root sheet, and its internal sheet
 ("SchematicSheet") similar to a sub sheet.

 But unfortunately, it was never done, and one day the word "Sheet"
 became "Datasheet", thus creating
 a serious confusion.

 Perhaps the "DATASHEET" field (attached to the symbol) and the
 "documentation" string (attached to a
 alias) should be clearly redefined for the V5.

 By the way, do you know why the .dcm file exists?
 It is similar to the .idx index file of old spice libs.

 In the early time of eeschema, Kicad was stored on a server and was
 used in classrooms and on PCs
 connected by a "slow" network link: network cards were ISA cards and
 the link speed was roughly 2400
 bps.

 So loading all needed schematic libraries to choose a symbol was a too
 time costly process, making
 Eeschema barely usable.
 Using small .dcm files to display a list of symbols and some info
 fixed this issue.

 Nowadays, link speed, PC speed and memory sizes have 3 order of
 magnitude, and .dcm files (a relic
 of this time) is more an annoying feature.


>>>
>>>
>>
>> ___
>> 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
>>
>>
> --
>  -Kristoffer
>
>
> ___
> 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] Right click option to change layer and render color

[Fabrizio Tappero]

Hi,
since we talk about the "Visibles" menus. I find current naming a little
unusual.

I would like to propose the following change.

"Visible" -> Eliminate this tirle
"Layer" -> "Visible Layers"
"Render" -> "Others"

Is it just me that I find this naming strange? Does anybody have a better
idea?

cheers
Fabrizio




On Fri, Sep 22, 2017 at 3:12 PM, Seppe Stas  wrote:

> Hey Wayne
>
> I fixed the coding policy violations. I blame my text-editor's trailing
> whitespace detector being broken all of a sudden
>  and the spaces
> thing being weird XD.
>
> The updated patches are attached to this mail. Let me know if you find any
> other issues.
>
> Greetings
> Seppe
>
> 2017-09-22 13:35 GMT+02:00 Wayne Stambaugh :
>
>> Seppe,
>>
>> Please fix your coding policy[1] violations.  I saw some missing spaces
>> between brackets and function call arguments along with some trailing
>> white space.
>>
>> Thanks,
>>
>> Wayne
>>
>> [1]:
>> http://docs.kicad-pcb.org/doxygen/md_Documentation_developme
>> nt_coding-style-policy.html
>>
>> On 9/22/2017 5:21 AM, Maciej Sumiński wrote:
>> > Hi Seppe,
>> >
>> > This is a very good idea. I would have merged the patch, but you need to
>> > implement GERBER_LAYER_WIDGET::OnLayerRightClick(), as in the current
>> > state the code does not compile.
>> >
>> > Regards,
>> > Orson
>> >
>> > On 09/21/2017 06:25 PM, Seppe Stas wrote:
>> >> This patch makes it possible to change the color of layers and render
>> >> options using the right click menu. See attached picture:
>> >> [image: Inline afbeelding 1]
>> >>
>> >> The motivation for this is the current "double left click / middle
>> click"
>> >> being somewhat obscure. I've been using KiCad for over 2 years and
>> recently
>> >> found out about the double click method by looking at KiCad's source
>> code
>> >> (I stumbled on the middle mouse button method earlier). At one point I
>> even
>> >> borrowed a mouse from my colleague to change layer colors when I
>> needed to
>> >> open a 6 layer board since I typically use a trackpad without a middle
>> >> mouse button. My colleagues, most of whom have been using KiCad for
>> longer
>> >> than me, didn't even know changing the layer/render color is possible.
>> >>
>> >> Being able to change properties of a selected item using the right
>> mouse
>> >> button is a lot more common in modern GUI applications and is more
>> >> consistent with how the rest of pcbnew works.
>> >>
>> >> Greetings
>> >> Seppe Stas
>> >>
>> >>
>> >>
>> >> ___
>> >> Mailing list: https://launchpad.net/~kicad-developers
>> >> Post to : kicad-developers@lists.launchpad.net
>> >> Unsubscribe : https://launchpad.net/~kicad-developers
>> >> More help   : https://help.launchpad.net/ListHelp
>> >>
>> >
>> >
>> >
>> >
>> > ___
>> > Mailing list: https://launchpad.net/~kicad-developers
>> > Post to : kicad-developers@lists.launchpad.net
>> > Unsubscribe : https://launchpad.net/~kicad-developers
>> > More help   : https://help.launchpad.net/ListHelp
>> >
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] minor icon improvements

[Fabrizio Tappero]

gentle reminder.



On Thu, Sep 14, 2017 at 12:59 PM, Fabrizio Tappero
<fabrizio.tapp...@gmail.com> wrote:
> Hi Wayne,
> reviewed the patch and re-submit here. Changes are:
>
> 1) "Edit PCB" is now "Edit PCB Layout"
> 2) "View GERBER" is now "View Gerber Files"
> 3) "Edit Schematic Symbol" is now "Manage Symbol Libraries"
> 4) "Edit Sheet Layout" is now "Edit Page Layout"
> 5) "Convert Bitmap to Footprint" is now "Convert Image"
>
> This should include all the suggestions in this email chain.
> Thanks a lot
> Fabrizio
>
>
>
> On Tue, Sep 12, 2017 at 5:00 PM, Wayne Stambaugh <stambau...@gmail.com>
> wrote:
>>
>> Fabrizio,
>>
>> Did you submit a revised patch with the suggestions that I made?  I just
>> looked in the mailing list archives and all I see is the original patch.
>>
>> Cheers,
>>
>> Wayne
>>
>> On 9/12/2017 8:57 AM, Fabrizio Tappero wrote:
>> > gentle reminder
>> >
>> > cheers
>> > Fabrizio
>> >
>> >
>> > On Tue, Aug 29, 2017 at 7:12 PM, Wayne Stambaugh <stambau...@gmail.com
>> > <mailto:stambau...@gmail.com>> wrote:
>> >
>> > On 8/29/2017 12:44 PM, Simon Küppers wrote:
>> > > -Run Pcbnew
>> > >
>> > > +   Edit PCB
>> > >
>> > > What about "Edit PCB Layout" orientiert "Edit PCB Design"? Sounds
>> > more
>> > > professional imho.
>> >
>> > I'm fine with "Edit PCB Layout".
>> >
>> > >
>> > >
>> > > Am 29. August 2017 10:04:19 MESZ schrieb Fabrizio Tappero
>> > > <fabrizio.tapp...@gmail.com <mailto:fabrizio.tapp...@gmail.com>>:
>> > >
>> > > Hi Wayne,
>> > > it sound good.
>> > > I think "Run" should go and I think "Edit Schematic" in place
>> > of
>> > > "Run Eeschema" is a great step up.
>> > >
>> > > The considerations about the use of the words "Symbol" and
>> > "Table"
>> > > sound good too.
>> > >
>> > > I changed the patch accordingly and resubmitted here. Just as
>> > > reference, this is what I came up with:
>> > >
>> > > -Run Eeschema
>> > > +   Edit Schematic
>> > >
>> > > -Run Library Editor
>> > > +   Edit Schematic Symbol
>> > >
>> > > -Run Pcbnew
>> > > +   Edit PCB
>> > >
>> > > -Run Footprint Editor
>> > > +   Edit PCB Footprint
>> > >
>> > > -Run Gerbview
>> > > +   View GERBER
>> > >
>> > > -Run Bitmap2Component
>> > > +   Convert Bitmap to Footprint
>> > >
>> > > -Run Pcb Calculator
>> > > +   Run PCB Calculator
>> > >
>> > > -Run Page Layout Editor
>> > > +   Edit Sheet Layout
>> > >
>> > > Wayne, please feel free to change the content of this patch as
>> > you
>> > > think it is best.
>> > >
>> > > cheers
>> > > Fabrizio
>> > >
>> > >
>> > >
>> > >
>> > >
>> > > On Mon, Aug 28, 2017 at 9:00 PM, Wayne Stambaugh
>> > > <stambau...@gmail.com <mailto:stambau...@gmail.com>
>> > <mailto:stambau...@gmail.com <mailto:stambau...@gmail.com>>> wrote:
>> > >
>> > > Fabrizio,
>> > >
>> > > I'm fine with the icon changes.  The menu entry changes
>> > could
>> > > use some
>> > > improvement.  I'm not sure removing "Run" from the KiCad
>> > > launcher menu
>> > > entries is a good idea.  Generally (at least in most of
>> > the
>> > > applications
>> > > that I've looked at), actions are used in menu string when
>> > the
>> > &g

Re: [Kicad-developers] [PATCH] Field editor buttons

[Fabrizio Tappero]

Hi Oliver,
hups, sorry my bad. Please forget what I said ;-)

cheers
Fabrizio


On Fri, Sep 15, 2017 at 11:35 PM, Oliver Walters
<oliver.henry.walt...@gmail.com> wrote:
> Hi Fabrizio,
>
> The icons I used were already in the bitmap_src directory, I didn't create
> any new ones? Or do I misunderstand what you mean?
>
>
> On 15 Sep 2017 23:45, "Fabrizio Tappero" <fabrizio.tapp...@gmail.com> wrote:
>
> Dear Oliver,
>
> this patch add 4 new arrow icons (left, right, up, down) that where
> already present in kicad. Green button is also present, just need to
> be renamed appropriately.
>
> I would propose to make use of present icons whenever possible. kicad
> has now 494 icons that are very difficult to manage.
>
> cheers
> Fabrizio
>
>
> On Thu, Sep 14, 2017 at 3:16 PM, Wayne Stambaugh <stambau...@gmail.com>
> wrote:
>> Oliver,
>>
>> I merged your patch set into the master branch.  Thank you for your
>> contribution to KiCad.  FYI, I fixed a few coding policy violations:
>>
>> +m_FieldsBuf[fieldNdx + 1].SetId(fieldNdx + 1);
>>
>>  ^   ^
>>  missing spaces
>>
>> Cheers,
>>
>> Wayne
>>
>> On 9/12/2017 3:50 AM, Oliver Walters wrote:
>>> Attached is a patch set that simplifies the UI buttons for organising
>>> component fields, both in the symbol editor and the schematic viewer.
>>>
>>> Screenshot: http://i.imgur.com/YFjASPT.png
>>>
>>> Cheers,
>>>
>>> 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] [PATCH] Field editor buttons

[Fabrizio Tappero]

Dear Oliver,

this patch add 4 new arrow icons (left, right, up, down) that where
already present in kicad. Green button is also present, just need to
be renamed appropriately.

I would propose to make use of present icons whenever possible. kicad
has now 494 icons that are very difficult to manage.

cheers
Fabrizio


On Thu, Sep 14, 2017 at 3:16 PM, Wayne Stambaugh  wrote:
> Oliver,
>
> I merged your patch set into the master branch.  Thank you for your
> contribution to KiCad.  FYI, I fixed a few coding policy violations:
>
> +m_FieldsBuf[fieldNdx + 1].SetId(fieldNdx + 1);
>
>  ^   ^
>  missing spaces
>
> Cheers,
>
> Wayne
>
> On 9/12/2017 3:50 AM, Oliver Walters wrote:
>> Attached is a patch set that simplifies the UI buttons for organising
>> component fields, both in the symbol editor and the schematic viewer.
>>
>> Screenshot: http://i.imgur.com/YFjASPT.png
>>
>> Cheers,
>>
>> 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] [PATCH] minor icon improvements

[Fabrizio Tappero]

Hi Wayne,
reviewed the patch and re-submit here. Changes are:

1) "Edit PCB" is now "Edit PCB Layout"
2) "View GERBER" is now "View Gerber Files"
3) "Edit Schematic Symbol" is now "Manage Symbol Libraries"
4) "Edit Sheet Layout" is now "Edit Page Layout"
5) "Convert Bitmap to Footprint" is now "Convert Image"

This should include all the suggestions in this email chain.
Thanks a lot
Fabrizio



On Tue, Sep 12, 2017 at 5:00 PM, Wayne Stambaugh <stambau...@gmail.com>
wrote:

> Fabrizio,
>
> Did you submit a revised patch with the suggestions that I made?  I just
> looked in the mailing list archives and all I see is the original patch.
>
> Cheers,
>
> Wayne
>
> On 9/12/2017 8:57 AM, Fabrizio Tappero wrote:
> > gentle reminder
> >
> > cheers
> > Fabrizio
> >
> >
> > On Tue, Aug 29, 2017 at 7:12 PM, Wayne Stambaugh <stambau...@gmail.com
> > <mailto:stambau...@gmail.com>> wrote:
> >
> > On 8/29/2017 12:44 PM, Simon Küppers wrote:
> > > -Run Pcbnew
> > >
> > > +   Edit PCB
> > >
> > > What about "Edit PCB Layout" orientiert "Edit PCB Design"? Sounds
> more
> > > professional imho.
> >
> > I'm fine with "Edit PCB Layout".
> >
> > >
> > >
> > > Am 29. August 2017 10:04:19 MESZ schrieb Fabrizio Tappero
> > > <fabrizio.tapp...@gmail.com <mailto:fabrizio.tapp...@gmail.com>>:
> > >
> > > Hi Wayne,
> > > it sound good.
> > > I think "Run" should go and I think "Edit Schematic" in place
> of
> > > "Run Eeschema" is a great step up.
> > >
> > > The considerations about the use of the words "Symbol" and
> "Table"
> > > sound good too.
> > >
> > > I changed the patch accordingly and resubmitted here. Just as
> > > reference, this is what I came up with:
> > >
> > > -Run Eeschema
> > > +   Edit Schematic
> > >
> > > -Run Library Editor
> > > +   Edit Schematic Symbol
> > >
> > > -Run Pcbnew
> > > +   Edit PCB
> > >
> > > -Run Footprint Editor
> > > +   Edit PCB Footprint
> > >
> > > -Run Gerbview
> > > +   View GERBER
> > >
> > > -Run Bitmap2Component
> > > +   Convert Bitmap to Footprint
> > >
> > > -Run Pcb Calculator
> > > +   Run PCB Calculator
> > >
> > > -Run Page Layout Editor
> > > +   Edit Sheet Layout
> > >
> > > Wayne, please feel free to change the content of this patch as
> you
> > > think it is best.
> > >
> > > cheers
> > > Fabrizio
> > >
> > >
> > >
> > >
> > >
> > > On Mon, Aug 28, 2017 at 9:00 PM, Wayne Stambaugh
> > > <stambau...@gmail.com <mailto:stambau...@gmail.com>
> > <mailto:stambau...@gmail.com <mailto:stambau...@gmail.com>>> wrote:
> > >
> > > Fabrizio,
> > >
> > > I'm fine with the icon changes.  The menu entry changes
> could
> > > use some
> > > improvement.  I'm not sure removing "Run" from the KiCad
> > > launcher menu
> > > entries is a good idea.  Generally (at least in most of the
> > > applications
> > > that I've looked at), actions are used in menu string when
> the
> > > entry is
> > > an action.  I also think it's probably time to get rid of
> > the old
> > > Eeschema/Pcbnew application names.  Since KiCad normally
> > runs in a
> > > single process, better menu entries might be "Edit
> Schematic"
> > > and "Edit
> > > Board (or PCB)".  New users aren't going to know what
> > Eeschema and
> > > Pcbnew are.
> > >
> > > I would also would not refer to the footprint library
> &q

Re: [Kicad-developers] [PATCH] minor icon improvements

[Fabrizio Tappero]

gentle reminder

cheers
Fabrizio


On Tue, Aug 29, 2017 at 7:12 PM, Wayne Stambaugh <stambau...@gmail.com>
wrote:

> On 8/29/2017 12:44 PM, Simon Küppers wrote:
> > -Run Pcbnew
> >
> > +   Edit PCB
> >
> > What about "Edit PCB Layout" orientiert "Edit PCB Design"? Sounds more
> > professional imho.
>
> I'm fine with "Edit PCB Layout".
>
> >
> >
> > Am 29. August 2017 10:04:19 MESZ schrieb Fabrizio Tappero
> > <fabrizio.tapp...@gmail.com>:
> >
> > Hi Wayne,
> > it sound good.
> > I think "Run" should go and I think "Edit Schematic" in place of
> > "Run Eeschema" is a great step up.
> >
> > The considerations about the use of the words "Symbol" and "Table"
> > sound good too.
> >
> > I changed the patch accordingly and resubmitted here. Just as
> > reference, this is what I came up with:
> >
> > -Run Eeschema
> > +   Edit Schematic
> >
> > -Run Library Editor
> > +   Edit Schematic Symbol
> >
> > -Run Pcbnew
> > +   Edit PCB
> >
> > -Run Footprint Editor
> > +   Edit PCB Footprint
> >
> > -Run Gerbview
> > +   View GERBER
> >
> > -Run Bitmap2Component
> > +   Convert Bitmap to Footprint
> >
> > -Run Pcb Calculator
> > +   Run PCB Calculator
> >
> > -Run Page Layout Editor
> > +   Edit Sheet Layout
> >
> > Wayne, please feel free to change the content of this patch as you
> > think it is best.
> >
> > cheers
> > Fabrizio
> >
> >
> >
> >
> >
> > On Mon, Aug 28, 2017 at 9:00 PM, Wayne Stambaugh
> > <stambau...@gmail.com <mailto:stambau...@gmail.com>> wrote:
> >
> > Fabrizio,
> >
> > I'm fine with the icon changes.  The menu entry changes could
> > use some
> > improvement.  I'm not sure removing "Run" from the KiCad
> > launcher menu
> > entries is a good idea.  Generally (at least in most of the
> > applications
> > that I've looked at), actions are used in menu string when the
> > entry is
> > an action.  I also think it's probably time to get rid of the old
> > Eeschema/Pcbnew application names.  Since KiCad normally runs in
> a
> > single process, better menu entries might be "Edit Schematic"
> > and "Edit
> > Board (or PCB)".  New users aren't going to know what Eeschema
> and
> > Pcbnew are.
> >
> > I would also would not refer to the footprint library "table"
> > either.
> > The word table seems to confuse users.  I know we refer to it as
> > a table
> > on the developers mailing list but I think users are more
> > comfortable
> > with "Manage Footprint Libraries".  I am aware that I used table
> > for the
> > symbol library table dialog menus entry but this is temporary.
> > Once I
> > finish the symbol library table remapping code, this dialog will
> > go away
> > and "Manage Symbol Libraries" will open the symbol library table
> > edit
> > dialog.
> >
> > The use of symbol was intentional so I would prefer that it not
> be
> > changed.  There was a discussion about this not too long ago and
> the
> > consensus was that symbol made the most sense versus component
> > or part.
> > I realize that component (and part) are used in the source code
> > and most
> >     of the UI strings but I would prefer that we change the UI
> > strings to
> > symbol for the stable 5 release rather than continue to use
> > component
> > and/or part.  I will change the source when I get a chance so
> > that the
> > terminology is coherent between the source and the UI strings.
> > I know
> > we still have the module/footprint distinction in the Pcbnew
> > source but
> > at least all of the UI strings are "footprint".
> >
> > Cheers,
> >
> > Wayne
> >
> > On 8/22/2017 5:47 PM, Fabrizio Tappero wrote:
> &g

Re: [Kicad-developers] disable icons in menus by default on osx

[Fabrizio Tappero]

Hi Diogo,
thanks for point it our. This has been fixed in a patch that is currently
in the pipeline.

Cheers
Fabrizio


On Mon, Sep 11, 2017 at 7:51 PM, Diogo Condeço 
wrote:

> While personally I won't use icons in the menus if that option is
> available to me, I can see why someone would like to use them.
>
> I can see it being useful to identify actions visually, but with that in
> mind, I can't understand why having icons and reusing them on different
> functions would help anyone. I've attached a screenshot where the same icon
> is used for 3 different actions
>
> BR,
> Diogo
>
> On Thu, Sep 7, 2017 at 3:59 PM, Miguel Angel Ajo Pelayo <
> majop...@redhat.com> wrote:
>
>> I personally (as a user) find the icons visually more intuitive.
>> Specially for newcomers and better adoption of KiCad.
>>
>> I know it's out of some guidelines, but this is a very complex software.
>>
>> My feeling is that it's better with a "on" by default setting, as long as
>> people already used to the software, or not liking icons could disable them.
>>
>> On Thu, Sep 7, 2017 at 4:34 PM, Michael Kavanagh <
>> mich...@michaelkavanagh.me> wrote:
>>
>>> Hi,
>>>
>>> Sorry to bring this up again, but for me icons are still enabled by
>>> default on macOS (and Windows unsurprisingly). I deleted
>>> /Library/Application Support/kicad, ~/Library/Preferences/kicad and
>>> /Applications/Kicad, reinstalled from most recent nightly (07-Sep-2017)
>>> and the icons were there upon startup.
>>>
>>> I think the problem was the default value was true when the key wasn't
>>> found (ie for new install), see http://docs.wxwidgets.org/
>>> trunk/classwx_config_base.html#a93b700301e0b73f1b42f14497f2e6bc7
>>>
>>> I have attached a patch to turn icons off by default on all platforms
>>> (doing away with "ugly" #if defined()/#endif). I think this would be
>>> preferable as per both the macOS and Windows guidelines. I am
>>> unfamiliar with Linux UI's but if Linux users want the icons enabled by
>>> default the #if will have to be added again.
>>>
>>> Cheers,
>>> Michael
>>>
>>>
>>> On 13 April 2017 at 18:51, Wayne Stambaugh  wrote:
>>>
 Simon,

 I committed your patch since osx expects the icons to be disabled by
 default.

 Thanks,

 Wayne

 On 4/8/2017 6:42 AM, Simon Wells wrote:
 > Please see attached patch to disable icons in the menus by default on
 osx
 >
 >
 >
 > ___
 > 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
>>
>>
>
>
> --
> Diogo Condeço
>
> ___
> 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] minor icon improvements

[Fabrizio Tappero]

Hi Wayne,
it sound good.
I think "Run" should go and I think "Edit Schematic" in place of "Run
Eeschema" is a great step up.

The considerations about the use of the words "Symbol" and "Table" sound
good too.

I changed the patch accordingly and resubmitted here. Just as reference,
this is what I came up with:

-Run Eeschema
+   Edit Schematic

-Run Library Editor
+   Edit Schematic Symbol

-Run Pcbnew
+   Edit PCB

-Run Footprint Editor
+   Edit PCB Footprint

-Run Gerbview
+   View GERBER

-Run Bitmap2Component
+   Convert Bitmap to Footprint

-Run Pcb Calculator
+   Run PCB Calculator

-Run Page Layout Editor
+   Edit Sheet Layout

Wayne, please feel free to change the content of this patch as you think it
is best.

cheers
Fabrizio





On Mon, Aug 28, 2017 at 9:00 PM, Wayne Stambaugh <stambau...@gmail.com>
wrote:

> Fabrizio,
>
> I'm fine with the icon changes.  The menu entry changes could use some
> improvement.  I'm not sure removing "Run" from the KiCad launcher menu
> entries is a good idea.  Generally (at least in most of the applications
> that I've looked at), actions are used in menu string when the entry is
> an action.  I also think it's probably time to get rid of the old
> Eeschema/Pcbnew application names.  Since KiCad normally runs in a
> single process, better menu entries might be "Edit Schematic" and "Edit
> Board (or PCB)".  New users aren't going to know what Eeschema and
> Pcbnew are.
>
> I would also would not refer to the footprint library "table" either.
> The word table seems to confuse users.  I know we refer to it as a table
> on the developers mailing list but I think users are more comfortable
> with "Manage Footprint Libraries".  I am aware that I used table for the
> symbol library table dialog menus entry but this is temporary.  Once I
> finish the symbol library table remapping code, this dialog will go away
> and "Manage Symbol Libraries" will open the symbol library table edit
> dialog.
>
> The use of symbol was intentional so I would prefer that it not be
> changed.  There was a discussion about this not too long ago and the
> consensus was that symbol made the most sense versus component or part.
> I realize that component (and part) are used in the source code and most
> of the UI strings but I would prefer that we change the UI strings to
> symbol for the stable 5 release rather than continue to use component
> and/or part.  I will change the source when I get a chance so that the
> terminology is coherent between the source and the UI strings.  I know
> we still have the module/footprint distinction in the Pcbnew source but
> at least all of the UI strings are "footprint".
>
> Cheers,
>
> Wayne
>
> On 8/22/2017 5:47 PM, Fabrizio Tappero wrote:
> > Reminder.
> >
> > Regards
> > Fabrizio
> >
> >
> > On Aug 17, 2017 4:42 PM, "Fabrizio Tappero" <fabrizio.tapp...@gmail.com
> > <mailto:fabrizio.tapp...@gmail.com>> wrote:
> >
> > Hello,
> > the following patch does the following:
> > 1) correct few pcbnew and eeschema menu text entries
> > 2) add the library table icon (minor look change)
> > 3) delete the redundant word "Run" into the KiCad - Tools menu entry
> >
> > cheers
> > Fabrzio
> >
> >
> >
> > ___
> > 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
>
From b977fa7899d3aac0ac925aa57b31edf4d79b510c Mon Sep 17 00:00:00 2001
From: Fabrizio Tappero <fabrizio.tapp...@gmail.com>
Date: Thu, 17 Aug 2017 16:39:11 +0200
Subject: [PATCH] library option reviewed and renamed, minor menu text changes

---
 bitmaps_png/CMakeLists.txt|   1 -
 bitmaps_png/cpp_26/library_option.cpp | 117 +++
 bitmaps_png/cpp_26/library_table.cpp  | 170 ++
 bitmaps_png/cpp_26/move_zone.cpp  |  67 --
 bitmaps_png/sources/library_table.svg | 137 ++-
 bitmaps_png/sources/move_zone.svg | 169 -
 cvpcb/menubar.cpp |   2 +-
 eeschema/menubar.cpp 

Re: [Kicad-developers] Routing algorithm used in PCB

[Fabrizio Tappero]

Hi Arun,
if yu like you can contribute with the documentation.

Regards
Fabrizio


On Mon, Aug 28, 2017 at 10:47 AM, Arun Kumar  wrote:

> I don't know C++ so unable  to contribute and I want to build my own FOSS
> app with the languages I know. I always wanted to contribute to an existing
> project there  isn't a proper documentation about the source code. Have to
> go through hundreds and thousands of lines of code to understand where they
> have implemented a specific functionality.
>
> I browsed the folders of the source code of Kicad but unable to understand
> what routing techniques are used and the code associated with it. I  found
>  a folder with name algorithm but couldn't understand how they're working
> with the parts.
>
> Thanks,
> Arun
>
> On Mon, Aug 28, 2017 at 12:04 PM, José Ignacio 
> wrote:
>
>> You already established that you want to extract techniques from kicad
>> for your own project instead of contributing. The code is all there in the
>> repo, free to use under the GPL.
>>
>> On Mon, Aug 28, 2017 at 12:41 AM, Arun Kumar 
>> wrote:
>>
>>> Hi Team,
>>>
>>> Which PCB routing algorithm are used in PCB designing in Kicad?
>>>
>>> Thanks
>>> Arun
>>>
>>> ___
>>> 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] minor icon improvements

[Fabrizio Tappero]

Reminder.

Regards
Fabrizio


On Aug 17, 2017 4:42 PM, "Fabrizio Tappero" <fabrizio.tapp...@gmail.com>
wrote:

> Hello,
> the following patch does the following:
> 1) correct few pcbnew and eeschema menu text entries
> 2) add the library table icon (minor look change)
> 3) delete the redundant word "Run" into the KiCad - Tools menu entry
>
> cheers
> Fabrzio
>
>
___
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] Introducing myself

[Fabrizio Tappero]

Hi Tarjei,
welcome to the community.

cheers
Fabrizio


On Wed, Aug 16, 2017 at 11:47 PM, Tarjei Knapstad  wrote:

> Hi all,
>
> In my recent endeavours to teach myself to create hobbyist PCB's, I've
> landed on KiCAD as my weapon of choice (open source, mature, actively
> developed). I found the learning curve quite steep though (the
> Contextual Electronics youtube tutorial as well as the recent Hackaday
> tutorial were indispensable aides *), and I keep coming across things
> that could be improved.
>
> I'm hoping to be able to contribute to the development of KiCAD with
> an initial interest in improving the usability and make it easier for
> new users to get started. I'll try to fix a few of the starter bugs
> while getting to know the code base and we'll see how it goes :)
>
> *)
> https://www.youtube.com/watch?v=JN_Y93RTdSo=
> PLy2022BX6Eso532xqrUxDT1u2p4VVsg-q
> https://hackaday.com/2016/11/17/creating-a-pcb-in-everything-kicad-part-1/
>
> Regards,
> --
> Tarjei Knapstad
> Norway
>
> ___
> 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] [PATCH] minor icon improvements

[Fabrizio Tappero]

Hello,
the following patch does the following:
1) correct few pcbnew and eeschema menu text entries
2) add the library table icon (minor look change)
3) delete the redundant word "Run" into the KiCad - Tools menu entry

cheers
Fabrzio
From b977fa7899d3aac0ac925aa57b31edf4d79b510c Mon Sep 17 00:00:00 2001
From: Fabrizio Tappero <fabrizio.tapp...@gmail.com>
Date: Thu, 17 Aug 2017 16:39:11 +0200
Subject: [PATCH] library option reviewed and renamed, minor menu text changes

---
 bitmaps_png/CMakeLists.txt|   1 -
 bitmaps_png/cpp_26/library_option.cpp | 117 +++
 bitmaps_png/cpp_26/library_table.cpp  | 170 ++
 bitmaps_png/cpp_26/move_zone.cpp  |  67 --
 bitmaps_png/sources/library_table.svg | 137 ++-
 bitmaps_png/sources/move_zone.svg | 169 -
 cvpcb/menubar.cpp |   2 +-
 eeschema/menubar.cpp  |   8 +-
 eeschema/menubar_libedit.cpp  |   6 +-
 include/bitmaps.h |   1 -
 kicad/menubar.cpp |  16 ++--
 pcbnew/help_common_strings.h  |   4 +-
 pcbnew/menubar_modedit.cpp|   4 +-
 pcbnew/menubar_pcbframe.cpp   |   4 +-
 pcbnew/onrightclick.cpp   |   2 +-
 15 files changed, 258 insertions(+), 450 deletions(-)
 create mode 100644 bitmaps_png/cpp_26/library_option.cpp
 delete mode 100644 bitmaps_png/cpp_26/move_zone.cpp
 delete mode 100644 bitmaps_png/sources/move_zone.svg

diff --git a/bitmaps_png/CMakeLists.txt b/bitmaps_png/CMakeLists.txt
index 40003dc..33bcdbc 100644
--- a/bitmaps_png/CMakeLists.txt
+++ b/bitmaps_png/CMakeLists.txt
@@ -345,7 +345,6 @@ set( BMAPS_MID
 move_rectangle
 move_sheet
 move_target
-move_zone
 move
 move_relative
 mw_add_gap
diff --git a/bitmaps_png/cpp_26/library_option.cpp b/bitmaps_png/cpp_26/library_option.cpp
new file mode 100644
index 000..8e90fbf
--- /dev/null
+++ b/bitmaps_png/cpp_26/library_option.cpp
@@ -0,0 +1,117 @@
+
+/* Do not modify this file, it was automatically generated by the
+ * PNG2cpp CMake script, using a *.png file as input.
+ */
+
+#include 
+
+static const unsigned char png[] = {
+ 0x89, 0x50, 0x4e, 0x47, 0x0d, 0x0a, 0x1a, 0x0a, 0x00, 0x00, 0x00, 0x0d, 0x49, 0x48, 0x44, 0x52,
+ 0x00, 0x00, 0x00, 0x1a, 0x00, 0x00, 0x00, 0x1a, 0x08, 0x06, 0x00, 0x00, 0x00, 0xa9, 0x4a, 0x4c,
+ 0xce, 0x00, 0x00, 0x06, 0x41, 0x49, 0x44, 0x41, 0x54, 0x48, 0xc7, 0xad, 0x96, 0x6b, 0x4c, 0x93,
+ 0x57, 0x18, 0xc7, 0x0b, 0x7e, 0xd8, 0x96, 0x7d, 0xdc, 0xfc, 0xb2, 0x2d, 0x93, 0xf7, 0x2d, 0x83,
+ 0x4d, 0x65, 0x43, 0x05, 0x26, 0x8a, 0x02, 0x6d, 0xb9, 0x33, 0x83, 0x2e, 0x5e, 0xe2, 0x15, 0x50,
+ 0xc8, 0x20, 0x92, 0xa9, 0x44, 0x68, 0x01, 0x95, 0xcc, 0x88, 0x20, 0x0e, 0x04, 0x26, 0xcc, 0x11,
+ 0x05, 0x17, 0x30, 0xd0, 0x22, 0xe3, 0x32, 0x19, 0xb0, 0x04, 0x27, 0x2a, 0xde, 0xca, 0x45, 0xee,
+ 0x20, 0x13, 0x14, 0x08, 0xa0, 0x68, 0xb9, 0x94, 0x16, 0x69, 0xcb, 0x7f, 0xe7, 0x9c, 0x42, 0x27,
+ 0x48, 0xa6, 0x26, 0x7b, 0x93, 0x27, 0x39, 0x79, 0xfb, 0xe6, 0xfc, 0xce, 0xf3, 0xfc, 0xff, 0xe7,
+ 0x79, 0x2a, 0x10, 0xcc, 0x7b, 0xc4, 0xd1, 0xc2, 0x08, 0x71, 0x34, 0x97, 0x2d, 0x91, 0x72, 0xc1,
+ 0xa2, 0x08, 0xce, 0xc1, 0xf1, 0xe0, 0x27, 0xef, 0x09, 0xde, 0xf0, 0x69, 0x56, 0x98, 0xa9, 0x5a,
+ 0x14, 0x66, 0x93, 0xf3, 0x83, 0xbc, 0x9f, 0x78, 0xe5, 0x63, 0xd7, 0x68, 0xae, 0xe9, 0xeb, 0x64,
+ 0x1e, 0x8e, 0xa7, 0x79, 0xb5, 0x73, 0x2c, 0x37, 0x2a, 0x91, 0xf1, 0x3a, 0x71, 0x0c, 0xf7, 0xc8,
+ 0xe5, 0x88, 0x45, 0xa1, 0x9b, 0x4c, 0xb8, 0xf6, 0xbf, 0x40, 0x2d, 0x72, 0x81, 0x7e, 0xb2, 0xce,
+ 0x12, 0xba, 0x06, 0xab, 0x39, 0xd1, 0xaa, 0x30, 0x7b, 0x31, 0xe7, 0xc3, 0xd8, 0x58, 0x81, 0xb9,
+ 0x44, 0xc6, 0x4d, 0x5a, 0x29, 0x2c, 0x61, 0x59, 0x64, 0x8c, 0xcf, 0x0a, 0x2d, 0xb1, 0x2c, 0xc7,
+ 0x12, 0x04, 0xaa, 0x91, 0x48, 0xf9, 0x6f, 0x5f, 0x07, 0xd2, 0xdf, 0xb7, 0x06, 0x9a, 0x97, 0xce,
+ 0x89, 0xd6, 0x02, 0xf3, 0xc9, 0xb9, 0x65, 0x93, 0xf1, 0x56, 0xa2, 0x18, 0x4e, 0x4d, 0x01, 0xd6,
+ 0xc5, 0xd6, 0x70, 0xf8, 0xc3, 0xc1, 0x04, 0x24, 0xef, 0x27, 0x24, 0xd2, 0x4f, 0xf9, 0x37, 0x06,
+ 0xa9, 0x4a, 0x80, 0x16, 0xdb, 0x85, 0x41, 0x92, 0x48, 0x6e, 0xcb, 0xda, 0x38, 0x7e, 0x94, 0x6e,
+ 0xec, 0x5d, 0xe5, 0x8d, 0x46, 0x55, 0x23, 0x83, 0x58, 0x93, 0x0c, 0xc5, 0x32, 0x4e, 0x6b, 0xe6,
+ 0x26, 0x1f, 0x11, 0xb8, 0xc9, 0x0d, 0xaf, 0x84, 0x84, 0xc4, 0x7c, 0x90, 0x6e, 0x08, 0x68, 0x5d,
+ 0xb9, 0x30, 0x48, 0x14, 0x65, 0x11, 0x6f, 0x9f, 0xc6, 0xeb, 0xe9, 0xe6, 0xe1, 0xca, 0x70, 0xe4,
+ 0xf7, 0xe4, 0x33, 0x90, 0x4d, 0xb6, 0x10, 0xae, 0x31, 0x5c, 0x83, 0xb9, 0x7b, 0x81, 0xc6, 0xf3,
+ 0xf4, 0x18, 0xfc, 0xce, 0x4e, 0x99, 0xe2, 0x9b, 0x14, 0x2d, 0x08, 0x08, 0x6f, 0x05, 0x22, 0x9b,
+ 0xdd, 0xf8, 0xf2, 0x82, 0x90, 0x6d, 0x9e, 0xf9, 0x20, 0x13, 0xb1, 0xf7, 0x63, 0xd9, 0x7a, 0x55,
+ 0x3a, 0x3f, 0x2d, 0x89, 0xe2, 0x33, 0x28, 0xc8, 0xf7, 0x8c, 0x06, 0x9b, 0xcf, 0xc1, 0x14, 0x9b,
+ 0xd2, 0xf5, 0x6f, 0x0f, 0x12, 0x45, 0x73, 0xaa, 0xcf, 0xf3, 0x8c, 0x9a, 0xdc, 0x7c, 0x

[Kicad-developers] Fwd: [PATCH] minor icons and text improvement in Archive Footprint Menu bar.

[Fabrizio Tappero]

Reminder


-- Forwarded message --
From: "Fabrizio Tappero" <fabrizio.tapp...@gmail.com>
Date: Aug 11, 2017 11:03 AM
Subject: [PATCH] minor icons and text improvement in Archive Footprint Menu
bar.
To: "KiCad Developers" <kicad-developers@lists.launchpad.net>
Cc:

Hello,
> the following patches add two new improved icons (and delete the old one)
> for the "archive footprint" menu in pcbnew as in the pic:
>
>
> [image: Inline image 1]
>
> Cheers
> Fabrizio
>
>
From 47dc9d216721baf44bc0822c096adf91132ddc9a Mon Sep 17 00:00:00 2001
From: Fabrizio Tappero <fabrizio.tapp...@gmail.com>
Date: Fri, 11 Aug 2017 11:01:28 +0200
Subject: [PATCH] delete library upgrade icon and make two new icons for the
 archive footprint menu in pcbnew

---
 bitmaps_png/CMakeLists.txt |   3 +-
 bitmaps_png/cpp_26/library_archive.cpp |  92 +++
 bitmaps_png/cpp_26/library_archive_as.cpp  | 101 
 bitmaps_png/cpp_26/library_update.cpp  | 104 
 bitmaps_png/sources/library_archive.svg| 175 +++
 bitmaps_png/sources/library_archive_as.svg | 184 +
 bitmaps_png/sources/library_update.svg | 138 --
 include/bitmaps.h  |   3 +-
 pcbnew/menubar_pcbframe.cpp|  12 +-
 9 files changed, 562 insertions(+), 250 deletions(-)
 create mode 100644 bitmaps_png/cpp_26/library_archive.cpp
 create mode 100644 bitmaps_png/cpp_26/library_archive_as.cpp
 delete mode 100644 bitmaps_png/cpp_26/library_update.cpp
 create mode 100644 bitmaps_png/sources/library_archive.svg
 create mode 100644 bitmaps_png/sources/library_archive_as.svg
 delete mode 100644 bitmaps_png/sources/library_update.svg

diff --git a/bitmaps_png/CMakeLists.txt b/bitmaps_png/CMakeLists.txt
index 7e4c65f..40003dc 100644
--- a/bitmaps_png/CMakeLists.txt
+++ b/bitmaps_png/CMakeLists.txt
@@ -307,7 +307,8 @@ set( BMAPS_MID
 lib_next
 lib_previous
 library_browse
-library_update
+library_archive
+library_archive_as
 library
 library_table
 lines90
diff --git a/bitmaps_png/cpp_26/library_archive.cpp b/bitmaps_png/cpp_26/library_archive.cpp
new file mode 100644
index 000..c47b35d
--- /dev/null
+++ b/bitmaps_png/cpp_26/library_archive.cpp
@@ -0,0 +1,92 @@
+
+/* Do not modify this file, it was automatically generated by the
+ * PNG2cpp CMake script, using a *.png file as input.
+ */
+
+#include 
+
+static const unsigned char png[] = {
+ 0x89, 0x50, 0x4e, 0x47, 0x0d, 0x0a, 0x1a, 0x0a, 0x00, 0x00, 0x00, 0x0d, 0x49, 0x48, 0x44, 0x52,
+ 0x00, 0x00, 0x00, 0x1a, 0x00, 0x00, 0x00, 0x1a, 0x08, 0x06, 0x00, 0x00, 0x00, 0xa9, 0x4a, 0x4c,
+ 0xce, 0x00, 0x00, 0x04, 0xb2, 0x49, 0x44, 0x41, 0x54, 0x48, 0xc7, 0xad, 0x96, 0x6f, 0x4c, 0x13,
+ 0x67, 0x1c, 0xc7, 0xab, 0x6f, 0x16, 0x5f, 0x2d, 0x4b, 0xb6, 0xbd, 0x5a, 0x66, 0x7b, 0x85, 0x21,
+ 0x10, 0xa7, 0x73, 0x31, 0xc0, 0x16, 0xf9, 0xd3, 0x76, 0xc5, 0x0d, 0x45, 0xdd, 0x14, 0x90, 0xe9,
+ 0x8b, 0x4d, 0xa2, 0xc9, 0xb2, 0x64, 0xa0, 0x06, 0x5b, 0xc0, 0x49, 0x70, 0x73, 0x23, 0x28, 0xce,
+ 0xa1, 0x5b, 0x60, 0x62, 0x30, 0x71, 0x32, 0x61, 0x28, 0x14, 0xe4, 0xef, 0x10, 0x27, 0xa0, 0x0c,
+ 0x68, 0x29, 0xb5, 0x20, 0x83, 0xf2, 0x57, 0xa4, 0x50, 0x2c, 0xad, 0x50, 0xa0, 0xa5, 0x94, 0xef,
+ 0x9e, 0xbb, 0x5b, 0x85, 0xb6, 0x9c, 0xb0, 0x64, 0x4d, 0x3e, 0xb9, 0x4b, 0xef, 0x7a, 0x9f, 0x7b,
+ 0x9e, 0xdf, 0xf7, 0xf9, 0x3d, 0xe5, 0xf1, 0xdc, 0x3e, 0xe2, 0x24, 0xc1, 0xd9, 0xd0, 0x93, 0xfc,
+ 0x9b, 0x62, 0x39, 0x75, 0x54, 0x2a, 0x13, 0x8a, 0xda, 0xfb, 0xfe, 0xda, 0x66, 0xb5, 0x5a, 0x0f,
+ 0xaf, 0xc8, 0xf4, 0xc4, 0x17, 0x83, 0xf7, 0x63, 0xa1, 0x2d, 0xe0, 0x2d, 0x0b, 0xcf, 0x43, 0x94,
+ 0x4c, 0x0d, 0x6d, 0xcd, 0x12, 0x22, 0xf0, 0x3c, 0x65, 0x0d, 0x39, 0x4d, 0x99, 0x73, 0xca, 0xbf,
+ 0x9f, 0x27, 0x0f, 0x42, 0x69, 0x84, 0x12, 0x95, 0x31, 0xed, 0x9c, 0x94, 0x7e, 0xa8, 0x84, 0x79,
+ 0x64, 0x10, 0x0e, 0xcd, 0x06, 0x38, 0x1e, 0xba, 0xa2, 0x2d, 0xe4, 0x2d, 0xb8, 0x48, 0x82, 0x12,
+ 0xde, 0x58, 0x27, 0x91, 0x53, 0x76, 0xef, 0x9b, 0x5e, 0xf0, 0x2a, 0x66, 0x49, 0xd7, 0xa4, 0x83,
+ 0x16, 0x55, 0xc6, 0xa8, 0xd1, 0x9c, 0xaa, 0xe3, 0xa4, 0xe6, 0xa0, 0x06, 0xa6, 0xa1, 0x01, 0x2c,
+ 0x68, 0xfd, 0x00, 0x37, 0x3c, 0x44, 0x52, 0x39, 0x3f, 0x20, 0xec, 0x14, 0xf5, 0x8c, 0x16, 0xf8,
+ 0x29, 0xfc, 0x10, 0x5c, 0x15, 0x8c, 0x8c, 0x87, 0x19, 0xac, 0x28, 0x5a, 0x8d, 0xa6, 0xe4, 0x1e,
+ 0x4e, 0x6a, 0x0e, 0x68, 0x30, 0x31, 0x38, 0xb8, 0x28, 0x9a, 0x6a, 0xe0, 0x16, 0x89, 0x4f, 0xf0,
+ 0x8f, 0x04, 0x65, 0x50, 0x16, 0x5a, 0xb4, 0xbf, 0x7e, 0x3f, 0xea, 0xc7, 0xea, 0x5d, 0x44, 0xf7,
+ 0x13, 0xff, 0xe6, 0xa4, 0xfa, 0xd3, 0x76, 0x4c, 0x0c, 0x2c, 0x11, 0xcd, 0x4f, 0xbe, 0x40, 0x94,
+ 0xcc, 0xcf, 0xdd, 0xf2, 0xb3, 0x90, 0x99, 0xb2, 0x34, 0x4d, 0x1a, 0x72, 0xba, 0x73, 0x70, 0x4e,
+ 0x7b, 0x8e, 0x15, 0x45, 0xa9, 0xd1, 0x90, 0xd0, 0xc5, 0x49, 0x55, 0xac, 0x1a, 0x13, 0xfd, 0xab,
+ 0x14, 0x1d, 0xfa, 0x71, 0x7b, 0xcf, 0xa1, 

[Kicad-developers] [PATCH] minor icons and text improvement in Archive Footprint Menu bar.

[Fabrizio Tappero]

Hello,
the following patches add two new improved icons (and delete the old one)
for the "archive footprint" menu in pcbnew as in the pic:


[image: Inline image 1]

Cheers
Fabrizio
From 47dc9d216721baf44bc0822c096adf91132ddc9a Mon Sep 17 00:00:00 2001
From: Fabrizio Tappero <fabrizio.tapp...@gmail.com>
Date: Fri, 11 Aug 2017 11:01:28 +0200
Subject: [PATCH] delete library upgrade icon and make two new icons for the
 archive footprint menu in pcbnew

---
 bitmaps_png/CMakeLists.txt |   3 +-
 bitmaps_png/cpp_26/library_archive.cpp |  92 +++
 bitmaps_png/cpp_26/library_archive_as.cpp  | 101 
 bitmaps_png/cpp_26/library_update.cpp  | 104 
 bitmaps_png/sources/library_archive.svg| 175 +++
 bitmaps_png/sources/library_archive_as.svg | 184 +
 bitmaps_png/sources/library_update.svg | 138 --
 include/bitmaps.h  |   3 +-
 pcbnew/menubar_pcbframe.cpp|  12 +-
 9 files changed, 562 insertions(+), 250 deletions(-)
 create mode 100644 bitmaps_png/cpp_26/library_archive.cpp
 create mode 100644 bitmaps_png/cpp_26/library_archive_as.cpp
 delete mode 100644 bitmaps_png/cpp_26/library_update.cpp
 create mode 100644 bitmaps_png/sources/library_archive.svg
 create mode 100644 bitmaps_png/sources/library_archive_as.svg
 delete mode 100644 bitmaps_png/sources/library_update.svg

diff --git a/bitmaps_png/CMakeLists.txt b/bitmaps_png/CMakeLists.txt
index 7e4c65f..40003dc 100644
--- a/bitmaps_png/CMakeLists.txt
+++ b/bitmaps_png/CMakeLists.txt
@@ -307,7 +307,8 @@ set( BMAPS_MID
 lib_next
 lib_previous
 library_browse
-library_update
+library_archive
+library_archive_as
 library
 library_table
 lines90
diff --git a/bitmaps_png/cpp_26/library_archive.cpp b/bitmaps_png/cpp_26/library_archive.cpp
new file mode 100644
index 000..c47b35d
--- /dev/null
+++ b/bitmaps_png/cpp_26/library_archive.cpp
@@ -0,0 +1,92 @@
+
+/* Do not modify this file, it was automatically generated by the
+ * PNG2cpp CMake script, using a *.png file as input.
+ */
+
+#include 
+
+static const unsigned char png[] = {
+ 0x89, 0x50, 0x4e, 0x47, 0x0d, 0x0a, 0x1a, 0x0a, 0x00, 0x00, 0x00, 0x0d, 0x49, 0x48, 0x44, 0x52,
+ 0x00, 0x00, 0x00, 0x1a, 0x00, 0x00, 0x00, 0x1a, 0x08, 0x06, 0x00, 0x00, 0x00, 0xa9, 0x4a, 0x4c,
+ 0xce, 0x00, 0x00, 0x04, 0xb2, 0x49, 0x44, 0x41, 0x54, 0x48, 0xc7, 0xad, 0x96, 0x6f, 0x4c, 0x13,
+ 0x67, 0x1c, 0xc7, 0xab, 0x6f, 0x16, 0x5f, 0x2d, 0x4b, 0xb6, 0xbd, 0x5a, 0x66, 0x7b, 0x85, 0x21,
+ 0x10, 0xa7, 0x73, 0x31, 0xc0, 0x16, 0xf9, 0xd3, 0x76, 0xc5, 0x0d, 0x45, 0xdd, 0x14, 0x90, 0xe9,
+ 0x8b, 0x4d, 0xa2, 0xc9, 0xb2, 0x64, 0xa0, 0x06, 0x5b, 0xc0, 0x49, 0x70, 0x73, 0x23, 0x28, 0xce,
+ 0xa1, 0x5b, 0x60, 0x62, 0x30, 0x71, 0x32, 0x61, 0x28, 0x14, 0xe4, 0xef, 0x10, 0x27, 0xa0, 0x0c,
+ 0x68, 0x29, 0xb5, 0x20, 0x83, 0xf2, 0x57, 0xa4, 0x50, 0x2c, 0xad, 0x50, 0xa0, 0xa5, 0x94, 0xef,
+ 0x9e, 0xbb, 0x5b, 0x85, 0xb6, 0x9c, 0xb0, 0x64, 0x4d, 0x3e, 0xb9, 0x4b, 0xef, 0x7a, 0x9f, 0x7b,
+ 0x9e, 0xdf, 0xf7, 0xf9, 0x3d, 0xe5, 0xf1, 0xdc, 0x3e, 0xe2, 0x24, 0xc1, 0xd9, 0xd0, 0x93, 0xfc,
+ 0x9b, 0x62, 0x39, 0x75, 0x54, 0x2a, 0x13, 0x8a, 0xda, 0xfb, 0xfe, 0xda, 0x66, 0xb5, 0x5a, 0x0f,
+ 0xaf, 0xc8, 0xf4, 0xc4, 0x17, 0x83, 0xf7, 0x63, 0xa1, 0x2d, 0xe0, 0x2d, 0x0b, 0xcf, 0x43, 0x94,
+ 0x4c, 0x0d, 0x6d, 0xcd, 0x12, 0x22, 0xf0, 0x3c, 0x65, 0x0d, 0x39, 0x4d, 0x99, 0x73, 0xca, 0xbf,
+ 0x9f, 0x27, 0x0f, 0x42, 0x69, 0x84, 0x12, 0x95, 0x31, 0xed, 0x9c, 0x94, 0x7e, 0xa8, 0x84, 0x79,
+ 0x64, 0x10, 0x0e, 0xcd, 0x06, 0x38, 0x1e, 0xba, 0xa2, 0x2d, 0xe4, 0x2d, 0xb8, 0x48, 0x82, 0x12,
+ 0xde, 0x58, 0x27, 0x91, 0x53, 0x76, 0xef, 0x9b, 0x5e, 0xf0, 0x2a, 0x66, 0x49, 0xd7, 0xa4, 0x83,
+ 0x16, 0x55, 0xc6, 0xa8, 0xd1, 0x9c, 0xaa, 0xe3, 0xa4, 0xe6, 0xa0, 0x06, 0xa6, 0xa1, 0x01, 0x2c,
+ 0x68, 0xfd, 0x00, 0x37, 0x3c, 0x44, 0x52, 0x39, 0x3f, 0x20, 0xec, 0x14, 0xf5, 0x8c, 0x16, 0xf8,
+ 0x29, 0xfc, 0x10, 0x5c, 0x15, 0x8c, 0x8c, 0x87, 0x19, 0xac, 0x28, 0x5a, 0x8d, 0xa6, 0xe4, 0x1e,
+ 0x4e, 0x6a, 0x0e, 0x68, 0x30, 0x31, 0x38, 0xb8, 0x28, 0x9a, 0x6a, 0xe0, 0x16, 0x89, 0x4f, 0xf0,
+ 0x8f, 0x04, 0x65, 0x50, 0x16, 0x5a, 0xb4, 0xbf, 0x7e, 0x3f, 0xea, 0xc7, 0xea, 0x5d, 0x44, 0xf7,
+ 0x13, 0xff, 0xe6, 0xa4, 0xfa, 0xd3, 0x76, 0x4c, 0x0c, 0x2c, 0x11, 0xcd, 0x4f, 0xbe, 0x40, 0x94,
+ 0xcc, 0xcf, 0xdd, 0xf2, 0xb3, 0x90, 0x99, 0xb2, 0x34, 0x4d, 0x1a, 0x72, 0xba, 0x73, 0x70, 0x4e,
+ 0x7b, 0x8e, 0x15, 0x45, 0xa9, 0xd1, 0x90, 0xd0, 0xc5, 0x49, 0x55, 0xac, 0x1a, 0x13, 0xfd, 0xab,
+ 0x14, 0x1d, 0xfa, 0x71, 0x7b, 0xcf, 0xa1, 0xca, 0x03, 0x88, 0xbb, 0x1f, 0x87, 0xc6, 0xb1, 0x46,
+ 0xe4, 0xe9, 0xf2, 0x50, 0x39, 0x54, 0xc9, 0x88, 0x2a, 0xf6, 0xa9, 0xf1, 0xe7, 0x97, 0x9d, 0x9c,
+ 0x54, 0x91, 0x40, 0x18, 0x07, 0x9e, 0x60, 0xbe, 0xf7, 0x33, 0x38, 0x68, 0xec, 0x16, 0x38, 0x06,
+ 0xbe, 0x82, 0x63, 0xf0, 0x28, 0x1e, 0x95, 0xbc, 0xb6, 0x28, 0x4a, 0x4d, 0xe5, 0xad, 0x8d, 0xfe,
+ 0x2e, 0xd0, 

Re: [Kicad-developers] PCBNew, Archive Footprint Menu - suggest better text

[Fabrizio Tappero]

Hi Wayne,
I understand. I am considering all your comments and I propose few minor
improvements.

I will submitting a patch shortly with minor text and icon modifications.

Cheers
Fabrizio


On Thu, Aug 10, 2017 at 7:16 PM, Wayne Stambaugh <stambau...@gmail.com>
wrote:

> On 8/10/2017 12:56 PM, Fabrizio Tappero wrote:
> > Hi Wayne,
> > I understand. Maybe somebody else can clear up this issue.
> >
> > Regarding the "Archive Footprints in Footprint Library Table Entry", I
> > am not sure people would actually know what a "library table entry",
> > wouldn they? maybe "Archive Footprints in New Library"?
>
> It's hard to say but "Archive Footprints in New Library" is misleading.
> If you are choosing a library from the library table, then it already
> exists.  Perhaps "Archive Footprints in Existing Library" would be less
> confusing but the user will still be limited to fp lib table entries
> rather than any path of the user's choosing.  I also noticed that the
> dialog showing the list of fp lib table entries for the user to select
> showed all of the entries rather than only the entries that the user has
> write permission so there is that issue as well.
>
> >
> > cheers
> > Fabrizio
> >
> >
> > On Thu, Aug 10, 2017 at 6:33 PM, Wayne Stambaugh <stambau...@gmail.com
> > <mailto:stambau...@gmail.com>> wrote:
> >
> > I'm not sure about this myself.  I took a look at the code and I
> still
> > don't fully understand why there are multiple options.
> >
> > The ID_MENU_ARCHIVE_MODULES_IN_LIBRARY command appears to only
> allow you
> > to save the footprints in the current board to a library already
> listed
> > in the footprint library table.  I'm not sure this is necessary since
> > you could easily select an existing pretty footprint library (in the
> > footprint library table or otherwise) and overwrite it without
> limiting
> > the choices to the footprint library table.  The best description I
> can
> > think of for this is "Archive Footprints in Footprint Library Table
> > Entry".  This would a least be accurate.
> >
> > The ID_MENU_CREATE_LIBRARY_AND_ARCHIVE_MODULES command appears to
> allow
> > you to save the footprints in the current board to either a new
> library
> > path chosen by the user or overwrite an existing pretty footprint
> > library.  I would think that this option alone would be sufficient
> but
> > maybe I'm not seeing why the command above needed.  The best
> description
> > I can think of for this is "Archive Footprints in Library".  You
> could
> > use this option to perform the same operation above.
> >
> > It seems to med a better approach would be to just have a single
> archive
> > command and prompt the user for either a library table entry or
> library
> > path.  At least this would be easier to understand for the user.  I
> > didn't write this code so maybe I am missing something.
> >
> > On 8/9/2017 6:24 AM, Fabrizio Tappero wrote:
> > > Hello,
> > > I am tinkering the appearance of some icons and I would like to
> > improve
> > > the following menu by adding specific archive icons and make some
> > of the
> > > text a little clearer.
> > >
> > > This is the current code:
> > >
> > > //- archive submenu
> > > -
> > > wxMenu* submenuarchive = new wxMenu();
> > >
> > > AddMenuItem( submenuarchive, ID_MENU_ARCHIVE_MODULES_IN_
> LIBRARY,
> > >  _( " Footprints in Project Library." ),
> > >  _( "Archive footprints in existing library in
> > footprint
> > > Lib table"
> > > "(does not remove other footprints in this
> > library)" ),
> > >  KiBitmap( library_update_xpm ) );
> > >
> > > AddMenuItem( submenuarchive,
> > ID_MENU_CREATE_LIBRARY_AND_ARCHIVE_MODULES,
> > >  _( " Library and Archive Footprints." ),
> > >  _( "Archive all footprints in new library\n"
> > > "(if the library already exists it will be
> > deleted)" ),
> > >  KiBitmap( library_xpm ) );
> > >
&g

Re: [Kicad-developers] PCBNew, Archive Footprint Menu - suggest better text

[Fabrizio Tappero]

Hi Wayne,
I understand. Maybe somebody else can clear up this issue.

Regarding the "Archive Footprints in Footprint Library Table Entry", I am
not sure people would actually know what a "library table entry", wouldn
they? maybe "Archive Footprints in New Library"?

cheers
Fabrizio


On Thu, Aug 10, 2017 at 6:33 PM, Wayne Stambaugh <stambau...@gmail.com>
wrote:

> I'm not sure about this myself.  I took a look at the code and I still
> don't fully understand why there are multiple options.
>
> The ID_MENU_ARCHIVE_MODULES_IN_LIBRARY command appears to only allow you
> to save the footprints in the current board to a library already listed
> in the footprint library table.  I'm not sure this is necessary since
> you could easily select an existing pretty footprint library (in the
> footprint library table or otherwise) and overwrite it without limiting
> the choices to the footprint library table.  The best description I can
> think of for this is "Archive Footprints in Footprint Library Table
> Entry".  This would a least be accurate.
>
> The ID_MENU_CREATE_LIBRARY_AND_ARCHIVE_MODULES command appears to allow
> you to save the footprints in the current board to either a new library
> path chosen by the user or overwrite an existing pretty footprint
> library.  I would think that this option alone would be sufficient but
> maybe I'm not seeing why the command above needed.  The best description
> I can think of for this is "Archive Footprints in Library".  You could
> use this option to perform the same operation above.
>
> It seems to med a better approach would be to just have a single archive
> command and prompt the user for either a library table entry or library
> path.  At least this would be easier to understand for the user.  I
> didn't write this code so maybe I am missing something.
>
> On 8/9/2017 6:24 AM, Fabrizio Tappero wrote:
> > Hello,
> > I am tinkering the appearance of some icons and I would like to improve
> > the following menu by adding specific archive icons and make some of the
> > text a little clearer.
> >
> > This is the current code:
> >
> > //- archive submenu
> > -
> > wxMenu* submenuarchive = new wxMenu();
> >
> > AddMenuItem( submenuarchive, ID_MENU_ARCHIVE_MODULES_IN_LIBRARY,
> >  _( " Footprints in Project Library." ),
> >  _( "Archive footprints in existing library in footprint
> > Lib table"
> > "(does not remove other footprints in this library)"
> ),
> >  KiBitmap( library_update_xpm ) );
> >
> > AddMenuItem( submenuarchive, ID_MENU_CREATE_LIBRARY_AND_
> ARCHIVE_MODULES,
> >  _( " Library and Archive Footprints." ),
> >  _( "Archive all footprints in new library\n"
> > "(if the library already exists it will be deleted)"
> ),
> >  KiBitmap( library_xpm ) );
> >
> > AddMenuItem( aParentMenu, submenuarchive,
> >  ID_MENU_ARCHIVE_MODULES,
> >  _( "Arc Footprints" ),
> >  _( "Archive or add footprints in library file" ),
> >  KiBitmap( library_xpm ) );
> >
> > I would propose these changes:
> >
> > _( " Footprints in Default Project Library" ),
> > _( "Archive all footprints in existing default project library file"
> > "(does not remove other footprints in this library)" ),
> > "(the content of default library is maintained)" ),
> >
> >  _( " New Library and Archive Footprints" ),
> > _( "Archive all footprints in new library file\n"
> > "(if library file already exists its content is rewritten)" ),
> >
> >  _( "Arc Footprints" ),
> > _( "Archive or add footprints in library file" ), >> _( "Archive all
> > footprints in library file" ),
> >
> > For the option "Create New Library and Archive Footprints" I think it is
> > not clear what library file will be used. Default Project Library sounds
> > good to me but I dont think there is a default project library.
> >
> > Any feedback is welcome
> > cheers
> > Fabrizio
> >
> >
> >
> > ___
> > 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] minor icon fix

[Fabrizio Tappero]

​no worries

cheers
Fabrizio
​

On Wed, Aug 9, 2017 at 9:59 PM, Wayne Stambaugh <stambau...@gmail.com>
wrote:

> Fabrizio,
>
> Much better!  I committed your patch.  Thank you for your contribution
> to KiCad.
>
> Cheers,
>
> Wayne
>
> On 8/9/2017 9:31 AM, Fabrizio Tappero wrote:
> > Hi Wayne,
> > as discussed a while back, here you have the patch that eliminated the
> > white background behind all library icons. This will make all these
> > icons more appropriate for distro with dark background bar.
> >
> > This can be considered a very minor icon modification.
> >
> > Cheers
> > Fabrizio
> >
> >
> >
> > ___
> > 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] PCBNew, Archive Footprint Menu - suggest better text

[Fabrizio Tappero]

Hello,
I am tinkering the appearance of some icons and I would like to improve the
following menu by adding specific archive icons and make some of the text a
little clearer.

This is the current code:

//- archive submenu
-
wxMenu* submenuarchive = new wxMenu();

AddMenuItem( submenuarchive, ID_MENU_ARCHIVE_MODULES_IN_LIBRARY,
 _( " Footprints in Project Library." ),
 _( "Archive footprints in existing library in footprint
Lib table"
"(does not remove other footprints in this library)" ),
 KiBitmap( library_update_xpm ) );

AddMenuItem( submenuarchive, ID_MENU_CREATE_LIBRARY_AND_ARCHIVE_MODULES,
 _( " Library and Archive Footprints." ),
 _( "Archive all footprints in new library\n"
"(if the library already exists it will be deleted)" ),
 KiBitmap( library_xpm ) );

AddMenuItem( aParentMenu, submenuarchive,
 ID_MENU_ARCHIVE_MODULES,
 _( "Arc Footprints" ),
 _( "Archive or add footprints in library file" ),
 KiBitmap( library_xpm ) );

I would propose these changes:

_( " Footprints in Default Project Library" ),
_( "Archive all footprints in existing default project library file"
"(does not remove other footprints in this library)" ),
"(the content of default library is maintained)" ),

 _( " New Library and Archive Footprints" ),
_( "Archive all footprints in new library file\n"
"(if library file already exists its content is rewritten)" ),

 _( "Arc Footprints" ),
_( "Archive or add footprints in library file" ), >> _( "Archive all
footprints in library file" ),

For the option "Create New Library and Archive Footprints" I think it is
not clear what library file will be used. Default Project Library sounds
good to me but I dont think there is a default project library.

Any feedback is welcome
cheers
Fabrizio
___
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] Generating the _xpm files uside by icons in eeschema.

[Fabrizio Tappero]

that is true.

SVG to PNG to CPP requires a linux software called PNGCRUSH
https://pmt.sourceforge.io/pngcrush/

cheers
Fabrizio



On Tue, Jul 25, 2017 at 9:02 AM, Oliver Walters <
oliver.henry.walt...@gmail.com> wrote:

> Kristoffer,
>
> I believe you also have to be compiling under Linux, for this to work.
>
> On Tue, Jul 25, 2017 at 4:35 PM, Maciej Sumiński 
> wrote:
>
>> Hi Kristoffer,
>>
>> You need to add entries to bitmaps_png/CMakeLists.txt and
>> include/bitmaps.h. After that you need to build KiCad with a Cmake
>> option -DMAINTAIN_PNGS=ON. You will need Inkscape for file format
>> conversion.
>>
>> Regards,
>> Orson
>>
>> On 07/24/2017 09:40 PM, Kristoffer Ödmark wrote:
>> > Hello!
>> >
>> > I am working on some patches currently that adds a few menu entries in
>> > eeschema. Since they seem to require me to add icons to all of the
>> > entries, I am now stuck on trying to generate the .cpp files. Could
>> > someone point me in the correct way on how to do this.
>> >
>> > I currently have added 2 svg files in bitmaps_png/sources/ after that I
>> > am unsure of what to do. Tried running a script i found in there, which
>> > ran "rm -r *", causing me to have to remake svgs.
>> >
>> > - Kristoffer
>> >
>> > ___
>> > 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] correct text inside two importantplot windows

[Fabrizio Tappero]

Hi guys,
thanks for the explanation.

cheers
Fabrizio

On Fri, Jul 21, 2017 at 11:06 PM, Wayne Stambaugh <stambau...@gmail.com>
wrote:

> This is correct.  I just remember if the string in a group box
> (wxStaticBoxSizer) than it doesn't get a colon.  If the string is static
> text (wxStaticText) that describes a text control, then it should end in
> a colon.
>
> On 7/21/2017 2:31 PM, Chris Pavlina wrote:
> > Generally single entry controls will contain a colon in the label but
> > entire sections will not - thus "Output directory" and "Default line
> > thickness (mm)" should have colons, but "Messages" and "Page Size"
> > should not. This is because the single entry controls read as a single
> > line of text, where it's correct to separate a label with a colon,
> > whereas the section headings read as standalone labels that sit apart
> > from the thing they label.
> >
> > On Fri, Jul 21, 2017 at 05:41:59PM +0200, Fabrizio Tappero wrote:
> >> Hi Wayne,
> >>
> >> this is an exmaple of the current plot schematic window.
> >>
> >> [image: Inline image 1]
> >>
> >>
> >> I think it is expected that "Output directory:" and "Default line
> thickness
> >> (mm):" and "Messages:" have a colon.
> >>
> >> Am I correct?
> >>
> >> cheers
> >> Fabrizio
> >>
> >>
> >>
> >> On Fri, Jul 21, 2017 at 4:23 PM, Wayne Stambaugh <stambau...@gmail.com>
> >> wrote:
> >>
> >>> Fabrizio,
> >>>
> >>> I pushed your patch to the master branch.  Thank you for your
> >>> contribution to KiCad.
> >>>
> >>> This is not aimed at your patch but one thing I notice is that there is
> >>> and inconsistency in some of our wxStaticBoxSizer() strings.  There are
> >>> a few cases where the string ends with a colon (:) but it's rare.  For
> >>> the sake of consistency, if you find any cases in the future where this
> >>> is true, please remove the trailing colon.
> >>>
> >>> Cheers,
> >>>
> >>> Wayne
> >>>
> >>>
> >>> On 7/20/2017 5:59 AM, Fabrizio Tappero wrote:
> >>>> Hi Wayne,
> >>>> you are right. Sorry about that. I have reviewed and changed all
> >>> instances.
> >>>>
> >>>> In attachment the new patch.
> >>>>
> >>>> cheers
> >>>> Fabrizio
> >>>>
> >>>>
> >>>> On Wed, Jul 19, 2017 at 3:59 PM, Wayne Stambaugh <
> stambau...@gmail.com
> >>>> <mailto:stambau...@gmail.com>> wrote:
> >>>>
> >>>> Fabrizio,
> >>>>
> >>>> You are still using header instead of sentence capitalization of
> text
> >>>> box labels.  For example, in pcbnew/dialogs/dialog_plot_base.cpp
> you
> >>>> changed:
> >>>>
> >>>> "Plot format:"
> >>>>
> >>>> to
> >>>>
> >>>> "Plot Format:"
> >>>>
> >>>> The original capitalization is correct.  I see a lot of this in
> this
> >>>> patch.
> >>>>
> >>>> Please correct the text box label capitalization and resubmit your
> >>>> patch.  Also, please give your patches a unique name so I don't
> have
> >>> to.
> >>>>  Even easier, just use the name generated by `git format-patch`.
> >>>>
> >>>> Wayne
> >>>>
> >>>> On 7/19/2017 6:55 AM, Fabrizio Tappero wrote:
> >>>> > Hi Wayne,
> >>>> > really tedious work to spot these kind of mistakes... I hope I
> >>> fixed all
> >>>> > mistakes.
> >>>> >
> >>>> > In attachment the new patch.
> >>>> >
> >>>> > cheers
> >>>> > Fabrizio
> >>>> >
> >>>> >
> >>>> > On Wed, Jul 19, 2017 at 12:19 PM, Fabrizio Tappero
> >>>> > <fabrizio.tapp...@gmail.com <mailto:fabrizio.tapp...@gmail.com>
> >>>> <mailto:fabrizio.tapp...@gmail.com
> >>>> <mailto:fabrizio.tapp...@gmail.com>>> wrote:
> >>>> >

Re: [Kicad-developers] [PATCH] correct text inside two importantplot windows

[Fabrizio Tappero]

Hi Wayne,

this is an exmaple of the current plot schematic window.

[image: Inline image 1]


I think it is expected that "Output directory:" and "Default line thickness
(mm):" and "Messages:" have a colon.

Am I correct?

cheers
Fabrizio



On Fri, Jul 21, 2017 at 4:23 PM, Wayne Stambaugh <stambau...@gmail.com>
wrote:

> Fabrizio,
>
> I pushed your patch to the master branch.  Thank you for your
> contribution to KiCad.
>
> This is not aimed at your patch but one thing I notice is that there is
> and inconsistency in some of our wxStaticBoxSizer() strings.  There are
> a few cases where the string ends with a colon (:) but it's rare.  For
> the sake of consistency, if you find any cases in the future where this
> is true, please remove the trailing colon.
>
> Cheers,
>
> Wayne
>
>
> On 7/20/2017 5:59 AM, Fabrizio Tappero wrote:
> > Hi Wayne,
> > you are right. Sorry about that. I have reviewed and changed all
> instances.
> >
> > In attachment the new patch.
> >
> > cheers
> > Fabrizio
> >
> >
> > On Wed, Jul 19, 2017 at 3:59 PM, Wayne Stambaugh <stambau...@gmail.com
> > <mailto:stambau...@gmail.com>> wrote:
> >
> > Fabrizio,
> >
> > You are still using header instead of sentence capitalization of text
> > box labels.  For example, in pcbnew/dialogs/dialog_plot_base.cpp you
> > changed:
> >
> > "Plot format:"
> >
> > to
> >
> > "Plot Format:"
> >
> > The original capitalization is correct.  I see a lot of this in this
> > patch.
> >
> > Please correct the text box label capitalization and resubmit your
> > patch.  Also, please give your patches a unique name so I don't have
> to.
> >  Even easier, just use the name generated by `git format-patch`.
> >
> > Wayne
> >
> > On 7/19/2017 6:55 AM, Fabrizio Tappero wrote:
> > > Hi Wayne,
> > > really tedious work to spot these kind of mistakes... I hope I
> fixed all
> > > mistakes.
> > >
> > > In attachment the new patch.
> > >
> > > cheers
> > > Fabrizio
> > >
> > >
> > > On Wed, Jul 19, 2017 at 12:19 PM, Fabrizio Tappero
> > > <fabrizio.tapp...@gmail.com <mailto:fabrizio.tapp...@gmail.com>
> > <mailto:fabrizio.tapp...@gmail.com
> > <mailto:fabrizio.tapp...@gmail.com>>> wrote:
> > >
> > > Hi Wayne,
> > > apologies for that. I sometimes think that a unique patch is
> more
> > > friendly than several ones.
> > >
> > > Will fix and resubmit.
> > >
> > > cheers
> > > Fabrizio
> > >
> > >
> > > On Tue, Jul 18, 2017 at 3:35 PM, Wayne Stambaugh
> > > <stambau...@gmail.com <mailto:stambau...@gmail.com>
> > <mailto:stambau...@gmail.com <mailto:stambau...@gmail.com>>> wrote:
> > >
> > > Fabrizio,
> > >
> > > This patch has far more changes than the plot dialogs
> > mentioned
> > > in your
> > > commit message.  In the future, please either make your
> commit
> > > message
> > > describe all of the changes related to the patch.  I would
> > > prefer that
> > > you only make one wxFormbuilder dialog change per patch.
> > > wxFormbuilder
> > > changes tend to be noisy so it takes longer to review them.
> > >
> > > You are using the incorrect capitalization in text box
> labels.
> >     >     Text box
> > > labels use sentence capitalization not header
> > capitalization per
> > > the UI
> > > guidelines[1].
> > >
> > > Please fix your patch accordingly so I can commit it.
> > >
> > > Cheers,
> > >
> > > Wayne
> > >
> > >
> >  [1]:http://docs.kicad-pcb.org/doxygen/md_Documentation_
> development_ui-policy.html
> > <http://docs.kicad-pcb.org/doxygen/md_Documentation_
> development_ui-policy.html>
> >     >
> >  <http://docs.kicad-pcb.org/doxygen/md_Documentation_
> development_ui-policy.html
> 

Re: [Kicad-developers] [PATCH] simplied right click menu icons

[Fabrizio Tappero]

cheers and sorry for the back and forth.

Fabrizio


On Thu, Jul 20, 2017 at 5:33 PM, Wayne Stambaugh <stambau...@gmail.com>
wrote:

> This look good to me.  I'm fine with the unified menu icons.  If no one
> has any objections, I will commit it.
>
> On 7/20/2017 8:45 AM, Fabrizio Tappero wrote:
> > Hi Wayne,
> > how are you?
> >
> > very cool. I have changed this patch so that everywhere:
> >
> > "Rotate 90 deg CW" -> "Rotate Clockwise"
> > "Rotate 90 deg CCW" -> "Rotate Counterclockwise"
> >
> > thanks a lot
> > Fabrizio
> >
> >
> >
> >
> >
> >
> >
> > On Wed, Jul 19, 2017 at 3:35 PM, Wayne Stambaugh <stambau...@gmail.com
> > <mailto:stambau...@gmail.com>> wrote:
> >
> > On 7/19/2017 6:17 AM, Fabrizio Tappero wrote:
> > > Hi Wayne,
> > > Thanks for the many messages. I did not know that devs were so into
> > > translation...
> > >
> > > My overall effort is to uniformise the Kicad UI and make it
> consistent
> > > and as correct as possible.
> > >
> > > Currently in Kicad we are using "Rotate 90 deg CW" and "Rotate 90
> deg
> > > CCW" in many many menus (see below). This expression is also used
> in
> > > Inkscape, a pretty high standard software for vector image
> manipulation.
> > > I personally think that consistency is the most important aspect
> of my
> > > contributions and, despite loving internal conversations about
> > > translations, etc I think we need to pick what is considered the
> best
> > > expression and use it coherently in all kicad menus. I have the
> feeling
> > > that if I submit a similar patch in few months, this kind of
> discussion
> > > will come up again. In a way this is typical of open-source
> software, so
> > > maybe it is not a bad thing.
> >
> > I'm fine with consistent but consistently incorrect or confusing is
> no
> > better than inconsistent.
> >
> > >
> > > In my opinion I think it would be good not to reinvent
> expressions. I
> > > think "CW" and "CCW" is a perfectly understandable and usable
> expression.
> >
> > CW and CCW are not expressions.  They are abbreviations which may
> not be
> > understood outside of English.  I would prefer not to use
> abbreviations
> > except for units unless space is at a premium.  In this case, I don't
> > think there is a space issue.  Please use terms clockwise and
> > counterclockwise.  These are the correct English terms for rotation
> > direction.
> >
> > >
> > > The custom-defined rotation value is a new piece of info, thanks
> Wayne
> > > for that! does it apply to all rotations?
> >
> > This only applies when the user changes the default rotation angle
> from
> > 90 to something else.  The rotation angle is fixed to 90 in the
> > schematic, symbol library, and footprint library editors and is user
> > configurable in the board editor.
> >
> > >
> > > Please advise how to modify this patch to make it submittable.
> >
> > Use clockwise and counter clockwise instead of CW and CCW.  Either
> > remove the 90 deg rotation angle or use the user rotation angle in
> the
> > board editor menu string.  I don't have a preference.
> >
> > >
> > > Cheers
> > > Fabrizio
> > >
> > >
> > >
> > > Inline image 1
> > >
> > >
> > >
> > > On Wed, Jul 19, 2017 at 2:47 AM, Wayne Stambaugh <
> stambau...@gmail.com <mailto:stambau...@gmail.com>
> > > <mailto:stambau...@gmail.com <mailto:stambau...@gmail.com>>>
> wrote:
> > >
> > > On 7/18/2017 8:24 PM, Chris Pavlina wrote:
> > > >> (remember, this is localization, not literal translation)
> > > >
> > > > Thank you! en_US should be "counterclockwise" and
> "clockwise" (or
> > > > even CCW/CW would be easily understood), and different
> phrasings
> > > > should be used in different languages. Don't avoid
> "clockwise" in
> > > > English because the French don't use it. It's up to the
> translators
> >

Re: [Kicad-developers] [PATCH] correct text inside two importantplot windows

[Fabrizio Tappero]

Hi Wayne,
apologies for that. I sometimes think that a unique patch is more friendly
than several ones.

Will fix and resubmit.

cheers
Fabrizio


On Tue, Jul 18, 2017 at 3:35 PM, Wayne Stambaugh <stambau...@gmail.com>
wrote:

> Fabrizio,
>
> This patch has far more changes than the plot dialogs mentioned in your
> commit message.  In the future, please either make your commit message
> describe all of the changes related to the patch.  I would prefer that
> you only make one wxFormbuilder dialog change per patch.  wxFormbuilder
> changes tend to be noisy so it takes longer to review them.
>
> You are using the incorrect capitalization in text box labels.  Text box
> labels use sentence capitalization not header capitalization per the UI
> guidelines[1].
>
> Please fix your patch accordingly so I can commit it.
>
> Cheers,
>
> Wayne
>
> [1]:http://docs.kicad-pcb.org/doxygen/md_Documentation_
> development_ui-policy.html
>
> On 7/3/2017 4:45 AM, Fabrizio Tappero wrote:
> > Hi JP,
> > thanks for it. I updated my wxformbuilder to the latest (3.6v)
> > version. And I fixed the (mm) issue you mentioned.
> >
> > In attachment the patch.
> >
> > thank you
> > Fabrizio
> >
> >
> > On Sat, Jul 1, 2017 at 8:40 PM, jp charras <jp.char...@wanadoo.fr>
> wrote:
> >> Le 30/06/2017 à 15:34, Fabrizio Tappero a écrit :
> >>> Hello,
> >>> in attachment the patch reviewed after Wayne comments.
> >>>
> >>> Best regards
> >>> Fabrizio
> >>>
> >>
> >> Hi Fabrizio,
> >>
> >> I had a look at your last patch, and found a few issues:
> >> for instance the change:
> >>
> >> -   m_defaultLineWidthTitle = new wxStaticText( 
> >> sbSizerPlotFormat->GetStaticBox(),
> wxID_ANY,
> >> _("Default line thickness"), wxDefaultPosition, wxDefaultSize, 0 );
> >> +   m_defaultLineWidthTitle = new wxStaticText( 
> >> sbSizerPlotFormat->GetStaticBox(),
> wxID_ANY, _("Line
> >> Thickness (mm):"), wxDefaultPosition, wxDefaultSize, 0 );
> >>
> >>
> >> is not good for 2 reasons:
> >> - "Default line thickness" is the right title (see a previous Wayne's
> answer)
> >> - "Line Thickness (mm):" is incorrect:
> >> the units symbol " (mm):" is added a run time, because units can be mm
> or inches.
> >> so never change titles like "Value" to "Value (mm):".
> >> It creates a wrong title.
> >>
> >> Besides your wxFormBuilder version is rather old and creates incorrect
> C++ sources: please update it.
> >>
> >> Thanks.
> >>
> >> --
> >> Jean-Pierre CHARRAS
> >>
> >>
> >> ___
> >> Mailing list: https://launchpad.net/~kicad-developers
> >> Post to : kicad-developers@lists.launchpad.net
> >> Unsubscribe : https://launchpad.net/~kicad-developers
> >> More help   : https://help.launchpad.net/ListHelp
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
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] simplied right click menu icons

[Fabrizio Tappero]

Hi Wayne,
Thanks for the many messages. I did not know that devs were so into
translation...

My overall effort is to uniformise the Kicad UI and make it consistent and
as correct as possible.

Currently in Kicad we are using "Rotate 90 deg CW" and "Rotate 90 deg CCW"
in many many menus (see below). This expression is also used in Inkscape, a
pretty high standard software for vector image manipulation. I personally
think that consistency is the most important aspect of my contributions
and, despite loving internal conversations about translations, etc I think
we need to pick what is considered the best expression and use it
coherently in all kicad menus. I have the feeling that if I submit a
similar patch in few months, this kind of discussion will come up again. In
a way this is typical of open-source software, so maybe it is not a bad
thing.

In my opinion I think it would be good not to reinvent expressions. I think
"CW" and "CCW" is a perfectly understandable and usable expression.

The custom-defined rotation value is a new piece of info, thanks Wayne for
that! does it apply to all rotations?

Please advise how to modify this patch to make it submittable.

Cheers
Fabrizio



[image: Inline image 1]



On Wed, Jul 19, 2017 at 2:47 AM, Wayne Stambaugh 
wrote:

> On 7/18/2017 8:24 PM, Chris Pavlina wrote:
> >> (remember, this is localization, not literal translation)
> >
> > Thank you! en_US should be "counterclockwise" and "clockwise" (or
> > even CCW/CW would be easily understood), and different phrasings
> > should be used in different languages. Don't avoid "clockwise" in
> > English because the French don't use it. It's up to the translators
> > to decide how things should be phrased in their locale.
>
> Yes!  This is how it should be done.
>
> >
> > On Tue, Jul 18, 2017 at 07:19:35PM -0500, José Ignacio wrote:
> >> Clockwise and counter-clockwise are the most usual term in American
> >> Engish, other localizations should use the most usual term in their
> >> respective locales (remember, this is localization, not literal
> >> translation). For example in Argentinian Spanish it should be
> >> "Horario" and "Antihorario". Encoding information in the icons only
> >> is not a good idea, as users can disable them (or the system can
> >> disable them by default) also screen readers can't read icons
> >> (though i doubt many blind people would be using kicad to lay out
> >> circuits).
> >>
> >> On Tue, Jul 18, 2017 at 4:00 PM, Clemens Koller 
> >> wrote:
> >>
> >>> Hi!
> >>>
> >>> If we want to avoid clockwise (CW) and counterclockwise (CCW) I
> >>> suggest to add a sign to the rotation, which should be trivial to
> >>> translate:
> >>>
> >>> Mathematics/complex plane stuff tells that: CCW = positive
> >>> rotation =  rotate + = rot+ CW = negative rotation = rotate - =
> >>> rot-
> >>>
> >>> In german we can use "rotieren +" und "rotieren -".
> >>>
> >>> Regards,
> >>>
> >>> Clemens
> >>>
> >>>
> >>> On 2017-07-18 19:34, jp charras wrote:
>  Le 18/07/2017 à 19:14, "Jörg Hermann" a écrit :
> > Translation of Clockwise and Counterclockwise are long texts
> > in many
> >>> languages:
> > Uhrzeigersinn and Gegenuhrzeigersinn in german for example.
> >
> > If the icon depicts (dynamically) the sense of rotation, the
> > text can
> >>> be short as "Rotate" - which
> > is short in many languages. Just an idea?
> >
> > Jörg Hermann
> >
> 
>  I agree icons should show the rotation.
> 
>  However Rotate Clockwise (or Counter Clockwise ) is still
>  needed (just
> >>> "Rotate" is not acceptable)
>  because icons are not always displayed: - On OSX by default
>  (although they can be shown, this is an option in
> >>> Kicad, now)
>  - On Linux, some WM do not display icons in menus.
> 
>  Besides, English language is know for its short words and
>  sentences. Translations are using most of time longer words and
>  sentences, and this
> >>> is sometimes an issue in menus.
>  We (translators) have to live with that.
> 
> >>>
> >>> ___ 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] correct text inside two importantplot windows

[Fabrizio Tappero]

gentle reminder.

cheers
Fabrizio


On Mon, Jul 3, 2017 at 10:45 AM, Fabrizio Tappero <
fabrizio.tapp...@gmail.com> wrote:

> Hi JP,
> thanks for it. I updated my wxformbuilder to the latest (3.6v)
> version. And I fixed the (mm) issue you mentioned.
>
> In attachment the patch.
>
> thank you
> Fabrizio
>
>
> On Sat, Jul 1, 2017 at 8:40 PM, jp charras <jp.char...@wanadoo.fr> wrote:
> > Le 30/06/2017 à 15:34, Fabrizio Tappero a écrit :
> >> Hello,
> >> in attachment the patch reviewed after Wayne comments.
> >>
> >> Best regards
> >> Fabrizio
> >>
> >
> > Hi Fabrizio,
> >
> > I had a look at your last patch, and found a few issues:
> > for instance the change:
> >
> > -   m_defaultLineWidthTitle = new wxStaticText( 
> > sbSizerPlotFormat->GetStaticBox(),
> wxID_ANY,
> > _("Default line thickness"), wxDefaultPosition, wxDefaultSize, 0 );
> > +   m_defaultLineWidthTitle = new wxStaticText( 
> > sbSizerPlotFormat->GetStaticBox(),
> wxID_ANY, _("Line
> > Thickness (mm):"), wxDefaultPosition, wxDefaultSize, 0 );
> >
> >
> > is not good for 2 reasons:
> > - "Default line thickness" is the right title (see a previous Wayne's
> answer)
> > - "Line Thickness (mm):" is incorrect:
> > the units symbol " (mm):" is added a run time, because units can be mm
> or inches.
> > so never change titles like "Value" to "Value (mm):".
> > It creates a wrong title.
> >
> > Besides your wxFormBuilder version is rather old and creates incorrect
> C++ sources: please update it.
> >
> > Thanks.
> >
> > --
> > Jean-Pierre CHARRAS
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] simplied right click menu icons

[Fabrizio Tappero]

gentle reminder.

cheers
Fabrizio


On Tue, Jul 4, 2017 at 6:03 PM, Fabrizio Tappero <fabrizio.tapp...@gmail.com
> wrote:

> Hello,
> following up on the ongoing effort of reducing kicad icons and making
> kicad UI more usable I am sending this patch.
>
> Essentially this patch simplify several icons of the right click menu
> of both eeschema, pcbnew and lib component SW.
>
> Few minor icon look improvements  are also present.
>
> Cheers
> Fabrizio
>
___
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] renamed eeschema right click menu "copy" into "duplicate" and some more

[Fabrizio Tappero]

Hi Guys,
I agree with making the CTRL+D the key for duplicated in eeschema so
that it is coherent with the same duplicated key in pcbnew. I did not
insist with Wayne on this because I felt he knew why it was a good
idea not to do it.

But if I can insist I insist ;-)

Cheers
Fabrizio




On Mon, Jul 3, 2017 at 6:10 PM, Maciej Sumiński <maciej.sumin...@cern.ch> wrote:
> For the record, the patch is merged. I kept the old hot key for
> duplication (as requested), but if I were to decide - I would go for
> CTRL+D. Alternatively, I would change pcbnew to use C for duplicate,
> just make the hot keys coherent.
>
> Cheers,
> Orson
>
> On 06/23/2017 08:00 PM, Wayne Stambaugh wrote:
>> Fabrizio,
>>
>> I took a look at this patch and have a few comments.
>>
>> It will need to be rebased since I've already removed the hierarchy tool
>> and all related code.
>>
>> The ctrl-d hotkey is already used in pcbnew so I don't think changing it
>> in eeschema makes sense.  I would keep 'C' in eeschema for consistency.
>>
>> I'm OK with the icon changes and the terminology change form "Copy" to
>> "Duplicate".
>>
>> Thanks,
>>
>> Wayne
>>
>> On 6/20/2017 6:02 AM, Fabrizio Tappero wrote:
>>> Hello,
>>> following up on the recent proposal to rename the eeschema "copy"
>>> command into "duplicate" and its shortcut I am sending this patch.
>>>
>>> Specifically this patch does the following:
>>>
>>> 1) rename eeschema right click menu item "Copy" into "Duplicate"
>>> 2) rename eeschema right click menu item "Save block" into "Copy block"
>>> 3) change "Duplicate" shortcut from "C" to "Ctrl-D"
>>> 4) change eeschema right click menu item "Duplicate" icon from a copy
>>> icon into a duplicate
>>> 5) deletes right vertical toolbar "ascend/descend hierarchy" icon and
>>> its unnecessary code. Please make sure I deleted all of it.
>>> 6) replace few redundant icons in the eeschema right click menu into
>>> more global icon (now global move icon)
>>> 7) replace the "mirror_footprint_axisX.svg" for a more standard
>>> "mirror" global icon.
>>> 8) replaced eeschema right click menu "delete_text" icon with more
>>> global "delete" icon
>>>
>>>
>>> Cheers
>>> Fabrizio
>>>
>>>
>>>
>>> ___
>>> 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] Copy/Paste/Cut defaults to ctrl + c, v, x as most other software.

[Fabrizio Tappero]

great !

thanks a lot

Fabrizio


On Mon, Jul 3, 2017 at 6:07 PM, Maciej Sumiński <maciej.sumin...@cern.ch> wrote:
> Hi Fabrizio,
>
> No problem, it is already pushed (split into two commits). Thank you for
> the patch!
>
> Cheers,
> Orson
>
> On 07/03/2017 05:41 PM, Fabrizio Tappero wrote:
>> Hi Maciej,
>> yes please!
>>
>> I have been busy with some other patch and I could not find the time
>> to get back to this one. I would it really appreciate if you could
>> apply my patch including Weyne comments. Please mind that the same
>> patch includes some copy icon fixes too.
>>
>> Cheers
>> Fabrizio
>>
>>
>> On Mon, Jul 3, 2017 at 4:51 PM, Maciej Sumiński <maciej.sumin...@cern.ch> 
>> wrote:
>>> Hi Kristoffer,
>>>
>>> Thank you very much, I have just pushed your patch. I was really close
>>> to implementing it myself, so I am glad you have done it.
>>>
>>> Other related changes I would like to introduce (open for discussion):
>>>
>>> - Proper naming for copy/duplicate operation (addressed by Fabrizio's
>>> patch, I will simply rebase it and apply Wayne's remarks as it has been
>>> reviewed already)
>>>
>>> - Rename constants to match the actions (BLOCK_COPY->BLOCK_DUPLICATE,
>>> BLOCK_SAVE->BLOCK_COPY)
>>>
>>> - Remove the toolbar icons for cut/copy/paste. I am not sure if they are
>>> even usable (with exception of Paste button). One cannot select a block
>>> and move the mouse cursor out of the schematic frame to click the
>>> toolbar buttons.
>>>
>>> - Add Paste operation in the right-click context menu when clipboard is
>>> not empty.
>>>
>>> Regards,
>>> Orson
>>>
>>> On 07/03/2017 01:51 PM, Kristoffer Ödmark wrote:
>>>> Hey!
>>>>
>>>> I made the copy/paste/cut functionality work as someone new to the
>>>> software might expect. That is, the cut command now actually puts the
>>>> block in clipboard and then deletes the block, compared to just deleting
>>>> it (wtf)?
>>>>
>>>> They are also bound to the almost universal defaults of ctrl+c/v/x.
>>>>
>>>> - Kristoffer
>>>>
>>>>
>>>> ___
>>>> 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] Copy/Paste/Cut defaults to ctrl + c, v, x as most other software.

[Fabrizio Tappero]

Hi Maciej,
yes please!

I have been busy with some other patch and I could not find the time
to get back to this one. I would it really appreciate if you could
apply my patch including Weyne comments. Please mind that the same
patch includes some copy icon fixes too.

Cheers
Fabrizio


On Mon, Jul 3, 2017 at 4:51 PM, Maciej Sumiński  wrote:
> Hi Kristoffer,
>
> Thank you very much, I have just pushed your patch. I was really close
> to implementing it myself, so I am glad you have done it.
>
> Other related changes I would like to introduce (open for discussion):
>
> - Proper naming for copy/duplicate operation (addressed by Fabrizio's
> patch, I will simply rebase it and apply Wayne's remarks as it has been
> reviewed already)
>
> - Rename constants to match the actions (BLOCK_COPY->BLOCK_DUPLICATE,
> BLOCK_SAVE->BLOCK_COPY)
>
> - Remove the toolbar icons for cut/copy/paste. I am not sure if they are
> even usable (with exception of Paste button). One cannot select a block
> and move the mouse cursor out of the schematic frame to click the
> toolbar buttons.
>
> - Add Paste operation in the right-click context menu when clipboard is
> not empty.
>
> Regards,
> Orson
>
> On 07/03/2017 01:51 PM, Kristoffer Ödmark wrote:
>> Hey!
>>
>> I made the copy/paste/cut functionality work as someone new to the
>> software might expect. That is, the cut command now actually puts the
>> block in clipboard and then deletes the block, compared to just deleting
>> it (wtf)?
>>
>> They are also bound to the almost universal defaults of ctrl+c/v/x.
>>
>> - Kristoffer
>>
>>
>> ___
>> 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] correct text inside two importantplot windows

[Fabrizio Tappero]

Hi JP,
thanks for it. I updated my wxformbuilder to the latest (3.6v)
version. And I fixed the (mm) issue you mentioned.

In attachment the patch.

thank you
Fabrizio


On Sat, Jul 1, 2017 at 8:40 PM, jp charras <jp.char...@wanadoo.fr> wrote:
> Le 30/06/2017 à 15:34, Fabrizio Tappero a écrit :
>> Hello,
>> in attachment the patch reviewed after Wayne comments.
>>
>> Best regards
>> Fabrizio
>>
>
> Hi Fabrizio,
>
> I had a look at your last patch, and found a few issues:
> for instance the change:
>
> -   m_defaultLineWidthTitle = new wxStaticText( 
> sbSizerPlotFormat->GetStaticBox(), wxID_ANY,
> _("Default line thickness"), wxDefaultPosition, wxDefaultSize, 0 );
> +   m_defaultLineWidthTitle = new wxStaticText( 
> sbSizerPlotFormat->GetStaticBox(), wxID_ANY, _("Line
> Thickness (mm):"), wxDefaultPosition, wxDefaultSize, 0 );
>
>
> is not good for 2 reasons:
> - "Default line thickness" is the right title (see a previous Wayne's answer)
> - "Line Thickness (mm):" is incorrect:
> the units symbol " (mm):" is added a run time, because units can be mm or 
> inches.
> so never change titles like "Value" to "Value (mm):".
> It creates a wrong title.
>
> Besides your wxFormBuilder version is rather old and creates incorrect C++ 
> sources: please update it.
>
> Thanks.
>
> --
> Jean-Pierre CHARRAS
From dd379374dfddb262552a928df7f0412309ceaaa9 Mon Sep 17 00:00:00 2001
From: Fabrizio Tappero <fabrizio.tapp...@gmail.com>
Date: Mon, 3 Jul 2017 10:38:01 +0200
Subject: [PATCH] fixed plot menu labels

---
 common/dialogs/wx_html_report_panel_base.cpp   |  8 +++---
 common/dialogs/wx_html_report_panel_base.fbp   | 14 -
 common/dialogs/wx_html_report_panel_base.h |  2 +-
 eeschema/dialogs/dialog_plot_schematic_base.cpp| 33 ++
 eeschema/dialogs/dialog_plot_schematic_base.fbp| 33 --
 eeschema/dialogs/dialog_plot_schematic_base.h  |  4 +--
 .../dialog_non_copper_zones_properties_base.cpp| 11 
 .../dialog_non_copper_zones_properties_base.fbp|  5 ++--
 .../dialog_non_copper_zones_properties_base.h  |  2 +-
 pcbnew/dialogs/dialog_plot_base.cpp| 30 ++--
 pcbnew/dialogs/dialog_plot_base.fbp| 30 ++--
 pcbnew/dialogs/dialog_print_for_modedit_base.cpp   | 10 +++
 pcbnew/dialogs/dialog_print_for_modedit_base.fbp   |  8 +++---
 pcbnew/dialogs/dialog_print_for_modedit_base.h |  2 +-
 pcbnew/dialogs/dialog_print_using_printer_base.cpp | 24 
 pcbnew/dialogs/dialog_print_using_printer_base.fbp | 22 +++
 pcbnew/dialogs/dialog_print_using_printer_base.h   |  2 +-
 pcbnew/dialogs/dialog_target_properties_base.cpp   |  8 +++---
 pcbnew/dialogs/dialog_target_properties_base.fbp   |  6 ++--
 pcbnew/dialogs/dialog_target_properties_base.h |  2 +-
 pcbnew/dialogs/dialog_update_pcb.fbp   |  2 +-
 pcbnew/dialogs/dialog_update_pcb_base.cpp  |  4 +--
 pcbnew/dialogs/dialog_update_pcb_base.h| 14 -
 23 files changed, 138 insertions(+), 138 deletions(-)

diff --git a/common/dialogs/wx_html_report_panel_base.cpp b/common/dialogs/wx_html_report_panel_base.cpp
index b297a5a..66b2b76 100644
--- a/common/dialogs/wx_html_report_panel_base.cpp
+++ b/common/dialogs/wx_html_report_panel_base.cpp
@@ -1,5 +1,5 @@
 ///
-// C++ code generated with wxFormBuilder (version May  6 2016)
+// C++ code generated with wxFormBuilder (version Dec 21 2016)
 // http://www.wxformbuilder.org/
 //
 // PLEASE DO "NOT" EDIT THIS FILE!
@@ -11,7 +11,7 @@
 
 WX_HTML_REPORT_PANEL_BASE::WX_HTML_REPORT_PANEL_BASE( wxWindow* parent, wxWindowID id, const wxPoint& pos, const wxSize& size, long style ) : wxPanel( parent, id, pos, size, style )
 {
-	m_box = new wxStaticBoxSizer( new wxStaticBox( this, wxID_ANY, _("Messages:") ), wxVERTICAL );
+	m_box = new wxStaticBoxSizer( new wxStaticBox( this, wxID_ANY, _("Output Messages:") ), wxVERTICAL );
 	
 	wxFlexGridSizer* fgSizer4;
 	fgSizer4 = new wxFlexGridSizer( 2, 1, 0, 0 );
@@ -31,7 +31,7 @@ WX_HTML_REPORT_PANEL_BASE::WX_HTML_REPORT_PANEL_BASE( wxWindow* parent, wxWindow
 	fgSizer3->SetFlexibleDirection( wxBOTH );
 	fgSizer3->SetNonFlexibleGrowMode( wxFLEX_GROWMODE_SPECIFIED );
 	
-	m_staticText3 = new wxStaticText( m_box->GetStaticBox(), wxID_ANY, _("Filter:"), wxDefaultPosition, wxDefaultSize, 0 );
+	m_staticText3 = new wxStaticText( m_box->GetStaticBox(), wxID_ANY, _("Show:"), wxDefaultPosition, wxDefaultSize, 0 );
 	m_staticText3->Wrap( -1 );
 	fgSizer3->Add( m_staticText3, 0, wxALIGN_CENTER_VERTICAL|wxTOP|wxRIGHT, 5 );
 	
@@ -

Re: [Kicad-developers] [PATCH] renamed eeschema right click menu "copy" into "duplicate" and some more

[Fabrizio Tappero]

hi Wayne,
ctrld-d was chosen for UI consistancy as discussed previously. "Control D"
is aready "Duplicate" in PCB new and it seems a good thing to me.

I will try to resubmit this patch with the changes you propose.

cheers
Fabrizio




On Fri, Jun 23, 2017 at 8:00 PM, Wayne Stambaugh <stambau...@gmail.com>
wrote:

> Fabrizio,
>
> I took a look at this patch and have a few comments.
>
> It will need to be rebased since I've already removed the hierarchy tool
> and all related code.
>
> The ctrl-d hotkey is already used in pcbnew so I don't think changing it
> in eeschema makes sense.  I would keep 'C' in eeschema for consistency.
>
> I'm OK with the icon changes and the terminology change form "Copy" to
> "Duplicate".
>
> Thanks,
>
> Wayne
>
> On 6/20/2017 6:02 AM, Fabrizio Tappero wrote:
> > Hello,
> > following up on the recent proposal to rename the eeschema "copy"
> > command into "duplicate" and its shortcut I am sending this patch.
> >
> > Specifically this patch does the following:
> >
> > 1) rename eeschema right click menu item "Copy" into "Duplicate"
> > 2) rename eeschema right click menu item "Save block" into "Copy block"
> > 3) change "Duplicate" shortcut from "C" to "Ctrl-D"
> > 4) change eeschema right click menu item "Duplicate" icon from a copy
> > icon into a duplicate
> > 5) deletes right vertical toolbar "ascend/descend hierarchy" icon and
> > its unnecessary code. Please make sure I deleted all of it.
> > 6) replace few redundant icons in the eeschema right click menu into
> > more global icon (now global move icon)
> > 7) replace the "mirror_footprint_axisX.svg" for a more standard
> > "mirror" global icon.
> > 8) replaced eeschema right click menu "delete_text" icon with more
> > global "delete" icon
> >
> >
> > Cheers
> > Fabrizio
> >
> >
> >
> > ___
> > 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] correct text inside two importantplot windows

[Fabrizio Tappero]

hi Wayne,
sure, no problem. I will fix this patch and send it back to you.

cheers
Fabrizio


On Fri, Jun 23, 2017 at 6:45 PM, Wayne Stambaugh <stambau...@gmail.com>
wrote:

> On 6/22/2017 3:48 AM, Fabrizio Tappero wrote:
> > Hi Wayne,
> > thanks for taking the time to review this.
> > ​I'll certainly review the changes you proposel​.
> > I am
> > ​ just​
> > a little unsure abut the use of colon. This is the present version of
> > the plot window
> > ​:​
> >
> > ​Inline image 1​
> >
> > Are you suggesting that "Plot format:" should get a colon but "Options"
> > or "Gerber Options" should not?
>
> That is correct.  Labels is a group box (wxStaticBoxSizer) should not
> end with a colon.  Labels (wxStaticText) that precede another control
> such as a text edit control should end with a colong.
>
> >
> > thanks
> > Fabrizio
> >
> >
> >
> >
> >
> >
> >
> >
> > On Wed, Jun 21, 2017 at 8:04 PM, Diego Herranz
> > <diegoherr...@diegoherranz.com <mailto:diegoherr...@diegoherranz.com>>
> > wrote:
> >
> > Hi,
> >
> > Random comments for a few of the topics discussed or proposed:
> >
> > - "Format" -> "Coordinate Format": The Gerber standard
> > <https://www.ucamco.com/files/downloads/file/81/the_gerber_
> file_format_specification.pdf> uses
> > Coordinate format for this, so I think this change is OK.
> >
> > - "solder mask" vs "solder stop mask": I'm European and I've never
> > used (or heard used) "solder stop mask". Always solder mask or I've
> > also used resist or solder resist. But I think solder mask is the
> > most common.
> >
> > - "Save Messages to File": +1
> >
> > - "Default line width" -> "Line width": please don't. The former is
> > more descriptive and correct in my opinion.
> >
> > Thanks,
> >
> > Diego
> >
> > On Wed, Jun 21, 2017 at 5:59 PM, Wayne Stambaugh
> > <stambau...@gmail.com <mailto:stambau...@gmail.com>> wrote:
> >
> > Fabrizio,
> >
> > I finally had a chance to look at this.  Here are my comments.
> >
> > You fixed the capitalization for some labels but broke it for
> > others.
> > Please take a look at the "Capitalization Table" section in the
> > KiCad
> > "User Interface Guidelines" [1] and make the appropriate changes.
> >
> > For the most part we do not use colons (:) at the end of group
> box
> > label.  I know we are not as consistent with this as we should
> > be but
> > most of the dialogs do not use them.  We should probably make
> > this a UI
> > policy.  Text labels for other controls should have a colon at
> > the end.
> >
> > I don't think the wording change from "Current solder mask
> > settings" to
> > "Solder Stop Mask Options" is very good.  Here in the states, I
> > cannot
> > ever remember some referring to solder mask as solder stop
> > mask.  Maybe
> > this is a European thing.
> >
> > The "Save Output" button could be more descriptive.  The
> > previous label
> > was better (although capitalized incorrectly).  Perhaps "Save
> > Messages
> > to File" would be better.
> >
> > Everything else seems fine to me.
> >
> > Cheers,
> >
> > Wayne
> >
> >
> > [1]:
> > http://docs.kicad-pcb.org/doxygen/md_Documentation_
> development_ui-policy.html
> > <http://docs.kicad-pcb.org/doxygen/md_Documentation_
> development_ui-policy.html>
> >
> > On 6/9/2017 6:43 AM, Fabrizio Tappero wrote:
> > > things like
> > >
> > > Options => Options:
> >     > 4.5 (unit mm) => 4.5, unit mm
> > > Messages => Output Mesages:
> > > Save report to file... => Save Output
> > > Capital letters, shorten sentences, etc
> > >
> > > Please refer to the patch for a detailed
> > >
> > > cheers
> > > Fabrizio
> > >
> > >
> &

[Kicad-developers] [PATCH] renamed eeschema right click menu "copy" into "duplicate" and some more

[Fabrizio Tappero]

Hello,
following up on the recent proposal to rename the eeschema "copy"
command into "duplicate" and its shortcut I am sending this patch.

Specifically this patch does the following:

1) rename eeschema right click menu item "Copy" into "Duplicate"
2) rename eeschema right click menu item "Save block" into "Copy block"
3) change "Duplicate" shortcut from "C" to "Ctrl-D"
4) change eeschema right click menu item "Duplicate" icon from a copy
icon into a duplicate
5) deletes right vertical toolbar "ascend/descend hierarchy" icon and
its unnecessary code. Please make sure I deleted all of it.
6) replace few redundant icons in the eeschema right click menu into
more global icon (now global move icon)
7) replace the "mirror_footprint_axisX.svg" for a more standard
"mirror" global icon.
8) replaced eeschema right click menu "delete_text" icon with more
global "delete" icon


Cheers
Fabrizio
From 20101438915447ca543a7e7eadedfb3d91e25227 Mon Sep 17 00:00:00 2001
From: Fabrizio Tappero <fabrizio.tapp...@gmail.com>
Date: Tue, 20 Jun 2017 09:41:32 +0200
Subject: [PATCH 1/2] deleted hierarchy_cursor icon and its code

---
 bitmaps_png/CMakeLists.txt   |   1 -
 bitmaps_png/cpp_26/hierarchy_cursor.cpp  |  60 -
 bitmaps_png/sources/hierarchy_cursor.svg | 143 ---
 eeschema/eeschema_id.h   |   1 -
 eeschema/onleftclick.cpp |  18 
 eeschema/schedit.cpp |   4 -
 eeschema/tool_sch.cpp|   4 -
 include/bitmaps.h|   1 -
 8 files changed, 232 deletions(-)
 delete mode 100644 bitmaps_png/cpp_26/hierarchy_cursor.cpp
 delete mode 100644 bitmaps_png/sources/hierarchy_cursor.svg

diff --git a/bitmaps_png/CMakeLists.txt b/bitmaps_png/CMakeLists.txt
index 8584eaa..62b81ed 100644
--- a/bitmaps_png/CMakeLists.txt
+++ b/bitmaps_png/CMakeLists.txt
@@ -269,7 +269,6 @@ set( BMAPS_MID
 hammer
 help
 hidden_pin
-hierarchy_cursor
 hierarchy_nav
 hotkeys
 hotkeys_import
diff --git a/bitmaps_png/cpp_26/hierarchy_cursor.cpp b/bitmaps_png/cpp_26/hierarchy_cursor.cpp
deleted file mode 100644
index 5a5d6fb..000
--- a/bitmaps_png/cpp_26/hierarchy_cursor.cpp
+++ /dev/null
@@ -1,60 +0,0 @@
-
-/* Do not modify this file, it was automatically generated by the
- * PNG2cpp CMake script, using a *.png file as input.
- */
-
-#include 
-
-static const unsigned char png[] = {
- 0x89, 0x50, 0x4e, 0x47, 0x0d, 0x0a, 0x1a, 0x0a, 0x00, 0x00, 0x00, 0x0d, 0x49, 0x48, 0x44, 0x52,
- 0x00, 0x00, 0x00, 0x1a, 0x00, 0x00, 0x00, 0x1a, 0x08, 0x06, 0x00, 0x00, 0x00, 0xa9, 0x4a, 0x4c,
- 0xce, 0x00, 0x00, 0x02, 0xb5, 0x49, 0x44, 0x41, 0x54, 0x48, 0xc7, 0xb5, 0x96, 0xcb, 0x6b, 0x1a,
- 0x51, 0x14, 0xc6, 0x5d, 0xd8, 0xd0, 0x55, 0x4b, 0xb6, 0xa1, 0xab, 0x50, 0x28, 0x59, 0x76, 0xd3,
- 0x07, 0x64, 0xa1, 0xd6, 0xb7, 0x42, 0x33, 0x3a, 0x6a, 0x4c, 0x82, 0x69, 0x12, 0x75, 0xa8, 0x90,
- 0x92, 0x94, 0xa4, 0x10, 0xdf, 0x4a, 0xd1, 0x4d, 0x63, 0x1f, 0xa4, 0x50, 0xff, 0x86, 0xd8, 0x5d,
- 0xba, 0x88, 0x5d, 0xa6, 0x0b, 0x37, 0xe9, 0x2a, 0xb1, 0x6d, 0x48, 0x45, 0x41, 0xd0, 0xfa, 0x56,
- 0x4a, 0x2d, 0x16, 0x7b, 0x7a, 0xef, 0xc0, 0x88, 0x5a, 0xc7, 0xb7, 0x17, 0x3e, 0x66, 0xe6, 0x72,
- 0x39, 0x3f, 0xce, 0xbd, 0xe7, 0xbb, 0x67, 0x38, 0x1c, 0x34, 0xdc, 0x6e, 0x37, 0x17, 0x69, 0x76,
- 0x42, 0xe2, 0x62, 0x06, 0x27, 0x18, 0x0c, 0x5e, 0xf1, 0xf9, 0x7c, 0x09, 0xaf, 0xd7, 0x0b, 0x93,
- 0x10, 0x8a, 0x1d, 0xc7, 0x0c, 0x9c, 0xcd, 0x0c, 0x9e, 0x48, 0xa5, 0x52, 0x50, 0xa9, 0x54, 0xc6,
- 0x2a, 0x1c, 0x13, 0xc7, 0xc6, 0x8c, 0x06, 0xa8, 0x50, 0x28, 0x40, 0xad, 0x56, 0x6b, 0xa8, 0x5a,
- 0xad, 0xc2, 0xe5, 0xf7, 0xcb, 0x96, 0xb9, 0x41, 0x85, 0x63, 0xf6, 0x04, 0x45, 0xbf, 0x44, 0x41,
- 0x2a, 0x97, 0xc0, 0xd1, 0x87, 0xa3, 0x09, 0x83, 0xa2, 0xe7, 0x60, 0xb3, 0x5b, 0x61, 0xcf, 0xb6,
- 0x07, 0xfb, 0x81, 0x17, 0x74, 0x86, 0x63, 0x01, 0xc5, 0xe3, 0x71, 0xc8, 0x64, 0x32, 0x0d, 0x45,
- 0x22, 0x11, 0xf0, 0x3e, 0xf7, 0x42, 0xa9, 0x54, 0x82, 0x83, 0xb7, 0x07, 0xf0, 0x74, 0x67, 0x1b,
- 0x12, 0x89, 0x44, 0xcb, 0x9a, 0x5e, 0xc2, 0x31, 0x9b, 0x41, 0x53, 0x9d, 0xaa, 0x6e, 0xf7, 0xd9,
- 0x2e, 0xca, 0xc8, 0xd6, 0x38, 0xd8, 0xc3, 0xd0, 0x21, 0xe8, 0x16, 0xb5, 0x60, 0xb5, 0x59, 0x07,
- 0xae, 0x3a, 0xcc, 0xe0, 0x30, 0x3e, 0x32, 0x1a, 0x8d, 0x73, 0x72, 0xb9, 0x1c, 0xf0, 0xd3, 0xef,
- 0xf7, 0x4f, 0x2f, 0x90, 0x0b, 0x0f, 0xd0, 0xd6, 0xe5, 0x9b, 0xab, 0xe8, 0xe4, 0xd3, 0xc9, 0x5f,
- 0xb5, 0x46, 0x95, 0x23, 0x34, 0x84, 0x00, 0xaf, 0xe9, 0x47, 0x0d, 0x1f, 0x31, 0x43, 0x24, 0x12,
- 0xcd, 0x88, 0xc5, 0x62, 0xc0, 0x4f, 0xfc, 0x2d, 0x90, 0x08, 0xee, 0xd8, 0x1d, 0xb6, 0x6c, 0x7b,
- 0xc9, 0x9e, 0x9d, 0x9f, 0x81, 0x46, 0x47, 0x16, 0x65, 0x4a, 0xd9, 0x32, 0x67, 0x98, 0xd1, 0x0e,
- 0x12, 0x8b, 0xf9, 0x77, 0x11, 0x28, 0xd7, 0xc9, 0x1f, 0xc9, 0x64, 0x12, 0x4c, 0x94, 0xa9, 0xac,
- 0x22, 0x55, 0xef, 0xfa, 0xbe, 0x19, 0xd8, 0x

Re: [Kicad-developers] [PATCH] hierarchy navigator icon moved where it belongs

[Fabrizio Tappero]

Hi guys,
no worries. To my eyes this change was similar to move the zoom icon. I
learn only now that right hand side icons change the status of the mouse
and horizontal icons cannot have this functionality. My knowledge of KiCad
is definitely limited.


+1 for removing it. I find its use already fulfilled by the hierarchical
nav dialog.

cheers
Fabrizio



On Sat, Jun 17, 2017 at 2:41 PM, Wayne Stambaugh <stambau...@gmail.com>
wrote:

> On 6/17/2017 8:11 AM, jp charras wrote:
> > Le 17/06/2017 à 13:38, Fabrizio Tappero a écrit :
> >> Hi guys,
> >> I'd like to reminder that this patch is still pending. I would love it
> to be applied.
> >>
> >> cheers
> >> Fabrizio
> >
> > Hi Fabrizio,
> >
> > Sorry to say that, but you cannot move this icon without changing the
> associated code.
> > Unlike icons in vertical toolbar, this icon, like all icons of the
> vertical right toolbar, is a
> > wxITEM_CHECK tool (and unlike tools of the main upper toolbar).
> >
> > To tell the truth, I am not especially thrilled by your proposal,
> because this icon does not act as
> > the hierarchy navigator icon in main toolbar, but like any other tool
> icon of the vertical right
> > toolbar (It changes the properties of the left click mouse button and
> the shape of the mouse cursor).
> >
> > For instance, after moving the Zoom on selection tool from vertical
> toolbar to main toolbar, I spent
> > 2 days to fix UI issues created by this change.
> > Just because the associated code was designed to manage tools of the
> vertical toolbar, not for any
> > tool in any toolbar, both in legacy canvas and gal canvas, and was not
> fixed by the initial patch.
> >
>
> I'm going to side with JP on this.  While I applaud all efforts to
> improve our UI consistency, breaking things is not the way to go about it.
>
> I wonder if the navigation tool is really necessary.  Does any one use
> it?  I can't recall ever using it.  We already have the hierarchy
> navigator dialog, leave sheet command, double click to enter a sheet,
> and alt-bkspc to leave sheet.  Interestingly, the hierarchy navigation
> tool always enabled even on schematics with no sheets.  Perhaps this is
> a tool that we can remove in the name of simplification.
>
> ___
> 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] hierarchy navigator icon moved where it belongs

[Fabrizio Tappero]

Hi guys,
I'd like to reminder that this patch is still pending. I would love it to
be applied.

cheers
Fabrizio



On Thu, Jun 8, 2017 at 10:03 AM, Fabrizio Tappero <
fabrizio.tapp...@gmail.com> wrote:

> Hello,
> I moved the hierarchy navigator icon next to the other two hierarchy icons
> to make the toolbar more coherent.
>
> [image: Inline image 1]
>
> I think the hierarchy navigator window, activated by the first hierarchy
> icon, has a bigger margin so that scrollbar is not show (see below) but I
> could not find a way to do that. Maybe some wxwidget person can advise.
>
> [image: Inline image 2]
>
> cheers
> Fabrizio
>
>
>
>
>
>
>
> From 6ffa93414e2076dc048769eee48581abcb2f1634 Mon Sep 17 00:00:00 2001
> From: Fabrizio Tappero <fabrizio.tapp...@gmail.com>
> Date: Thu, 8 Jun 2017 09:56:25 +0200
> Subject: [PATCH] hierarchy navigator icon moved where it belongs
>
> ---
>  eeschema/tool_sch.cpp | 11 +--
>  1 file changed, 5 insertions(+), 6 deletions(-)
>
> diff --git a/eeschema/tool_sch.cpp b/eeschema/tool_sch.cpp
> index 78e0179..f872592 100644
> --- a/eeschema/tool_sch.cpp
> +++ b/eeschema/tool_sch.cpp
> @@ -130,11 +130,14 @@ void SCH_EDIT_FRAME::ReCreateHToolbar()
>  m_mainToolBar->AddSeparator();
>
>  m_mainToolBar->AddTool( ID_HIERARCHY, wxEmptyString, KiBitmap(
> hierarchy
> _nav_xpm ),
> -_( "Navigate schematic hierarchy" ) );
> +_( "Show sheet hierarchy window" ) );
>
>
>  m_mainToolBar->AddTool( ID_POPUP_SCH_LEAVE_SHEET, wxEmptyString,
> KiBitma
> p( leave_sheet_xpm ),
> -_( "Leave sheet" ) );
> +_( "Jump to master sheet" ) );
> +
> +m_mainToolBar->AddTool( ID_HIERARCHY_PUSH_POP_BUTT, wxEmptyString,
> KiBit
> map( hierarchy_cursor_xpm ),
> +_( "Navigate sheet hierarchy" ), wxITEM_CHECK
> );
>
>  m_mainToolBar->AddSeparator();
>
> @@ -201,10 +204,6 @@ void SCH_EDIT_FRAME::ReCreateVToolbar()
>  m_drawToolBar->AddTool( ID_HIGHLIGHT, wxEmptyString, KiBitmap(
> net_highl
> ight_schematic_xpm ),
>  _( "Highlight net" ), wxITEM_CHECK );
>
> -m_drawToolBar->AddTool( ID_HIERARCHY_PUSH_POP_BUTT, wxEmptyString,
> -KiBitmap( hierarchy_cursor_xpm ),
> -_( "Ascend/descend hierarchy" ), wxITEM_CHECK
> );
> -
>  m_drawToolBar->AddTool( ID_SCH_PLACE_COMPONENT, wxEmptyString,
> KiBitmap(
>  add_component_xpm ),
>  HELP_PLACE_COMPONENTS, wxITEM_CHECK );
>
> --
> 2.7.4
>
>
___
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] Proposal to change "Copy" to "Duplicate"

[Fabrizio Tappero]

;Library Browser -
> Browse Components" while the equivalent for Footprint uses the (clearer, In
> My Opinion) "Open footprint viewer".
>
> 2. The tooltips for selecting the current library have "Select active
> library" or "Select working library". I would prefer "working" but would
> prefer consistency more!
>
> 3. The Save option uses tooltips "Save footprint in active library" and
> "Save current library to disk", which confuses me. It may be that different
> things are happening underneath, but the user doesn't (shouldn't need to...
> ) know.
>
> 4. "Delete component from current library" -- neither "active" nor
> "working"...
>
>
> ...
>
> I think that's enough for the moment (?!!), and I hope this is useful.
>
> Regards,
> Ruth
>
>
> On 16/06/2017 16:51, Fabrizio Tappero wrote:
>
> Hi Ruth,
> thanks for your feedack. I put quite some energy in trying to fix UI
> problems. I just need a little bit more time... ;-)
>
> It would be great if your could provide clear suggestions about those
> hidden functionalities.
>
> cheers
> Fabrizio
>
> On Fri, Jun 16, 2017 at 4:27 PM, <r...@ivimey.org> wrote:
>
>>
>> One of my earliest impressions of KiCad as a new user was confusion over
>> UI inconsistency: terminology, menu layouts, and shortcuts in particular.
>> For common actions there should be a common trigger (key, click) with a
>> common indication (icon, tooltip words etc). As an example I noticed again
>> yesterday in pcbnew, mostly you 'delete' an element, except when you
>> 'remove' it!
>>
>> Personally, I find Command-D very handy as a duplicate action; I would be
>> happy to see that used whenever it made sense. However, the best option
>> would be to build in a keymap editor (surely there are components for
>> this!) so we don't need a one-size-fits-all solution.
>>
>> While on the topic, it would be really good to include more actions on
>> the main menu: there are many things hidden in context menus that don't
>> need to be.
>>
>
>
___
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] Proposal to change "Copy" to "Duplicate"

[Fabrizio Tappero]

Hi Ruth,
thanks for your feedack. I put quite some energy in trying to fix UI
problems. I just need a little bit more time... ;-)

It would be great if your could provide clear suggestions about those
hidden functionalities.

cheers
Fabrizio

On Fri, Jun 16, 2017 at 4:27 PM,  wrote:

>
> One of my earliest impressions of KiCad as a new user was confusion over
> UI inconsistency: terminology, menu layouts, and shortcuts in particular.
> For common actions there should be a common trigger (key, click) with a
> common indication (icon, tooltip words etc). As an example I noticed again
> yesterday in pcbnew, mostly you 'delete' an element, except when you
> 'remove' it!
>
> Personally, I find Command-D very handy as a duplicate action; I would be
> happy to see that used whenever it made sense. However, the best option
> would be to build in a keymap editor (surely there are components for
> this!) so we don't need a one-size-fits-all solution.
>
> While on the topic, it would be really good to include more actions on the
> main menu: there are many things hidden in context menus that don't need to
> be.
>
> Ruth
>
>
> On 2017-06-16 14:54, Wayne Stambaugh wrote:
>
>> Please do not use 'D'.  Use Ctrl+D for duplicate.  You should check the
>> Eeschema and Pcbnew hot key lists to make sure Ctrl+D is not already in
>> use.
>>
>>
>
___
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] Proposal to change "Copy" to "Duplicate"

[Fabrizio Tappero]

Hi Nick,
how about we actually make "D" the shortcut for duplicate in both eescheama
and pcbnew. I notice that in pcbnew the "D" shortcut is taken by "Drag
Track Keep Slope" which I do not know what it means.

does anybody has anything against it?

JP, you are the one who knows more about shortcuts

Cheers
Fabrizio


On Thu, Jun 15, 2017 at 9:29 PM, Nick Østergaard <oe.n...@gmail.com> wrote:

> I think the duplicate hotkey should be ctrl+d, as it is in pcbnew.
>
> 2017-06-15 14:33 GMT+02:00 Wayne Stambaugh <stambau...@gmail.com>:
> > On 6/15/2017 6:02 AM, Simon Richter wrote:
> >> Hi,
> >>
> >> On 15.06.2017 10:17, Fabrizio Tappero wrote:
> >>
> >>> Inline image 1
> >>> I would like to propose to rename the "Copy Block" into "Duplicate
> >>> Block" and add to it the shortcut D. Possible? does it make sense? the
> >>> shortcut D seems available but better ask first?
> >>
> >> Yes please.
> >>
> >> Also, "Save Block" should be named "Copy", because it is the action that
> >> stores the block in the clipboard so it can be pasted using the Paste
> >> tool. It already has the correct shortcut.
> >>
> >>Simon
> >>
> >
> > This all makes sense to me.
> >
> > 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

[Kicad-developers] Proposal to change "Copy" to "Duplicate"

[Fabrizio Tappero]

hello,
inside the schematic editor, this is the right click menu when a group of
component is selected

[image: Inline image 1]
I would like to propose to rename the "Copy Block" into "Duplicate Block"
and add to it the shortcut D. Possible? does it make sense? the shortcut D
seems available but better ask first?

Also, again in the schematic editor, this is the right click menu when
hovering on one component.

[image: Inline image 2]

here again I'd like to propose to rename "Copy" with "Duplicate" and change
its shortcut to D.


As many, I constantly use these right click menus and I am trying to make
them better.

cheers
Fabrizio
___
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] [PATCH] hierarchy navigator icon moved where it belongs

[Fabrizio Tappero]

Hello,
I moved the hierarchy navigator icon next to the other two hierarchy icons
to make the toolbar more coherent.

[image: Inline image 1]

I think the hierarchy navigator window, activated by the first hierarchy
icon, has a bigger margin so that scrollbar is not show (see below) but I
could not find a way to do that. Maybe some wxwidget person can advise.

[image: Inline image 2]

cheers
Fabrizio







>From 6ffa93414e2076dc048769eee48581abcb2f1634 Mon Sep 17 00:00:00 2001
From: Fabrizio Tappero <fabrizio.tapp...@gmail.com>
Date: Thu, 8 Jun 2017 09:56:25 +0200
Subject: [PATCH] hierarchy navigator icon moved where it belongs

---
 eeschema/tool_sch.cpp | 11 +--
 1 file changed, 5 insertions(+), 6 deletions(-)

diff --git a/eeschema/tool_sch.cpp b/eeschema/tool_sch.cpp
index 78e0179..f872592 100644
--- a/eeschema/tool_sch.cpp
+++ b/eeschema/tool_sch.cpp
@@ -130,11 +130,14 @@ void SCH_EDIT_FRAME::ReCreateHToolbar()
 m_mainToolBar->AddSeparator();

 m_mainToolBar->AddTool( ID_HIERARCHY, wxEmptyString, KiBitmap(
hierarchy
_nav_xpm ),
-_( "Navigate schematic hierarchy" ) );
+_( "Show sheet hierarchy window" ) );


 m_mainToolBar->AddTool( ID_POPUP_SCH_LEAVE_SHEET, wxEmptyString,
KiBitma
p( leave_sheet_xpm ),
-_( "Leave sheet" ) );
+_( "Jump to master sheet" ) );
+
+m_mainToolBar->AddTool( ID_HIERARCHY_PUSH_POP_BUTT, wxEmptyString,
KiBit
map( hierarchy_cursor_xpm ),
+_( "Navigate sheet hierarchy" ), wxITEM_CHECK
);

 m_mainToolBar->AddSeparator();

@@ -201,10 +204,6 @@ void SCH_EDIT_FRAME::ReCreateVToolbar()
 m_drawToolBar->AddTool( ID_HIGHLIGHT, wxEmptyString, KiBitmap(
net_highl
ight_schematic_xpm ),
 _( "Highlight net" ), wxITEM_CHECK );

-m_drawToolBar->AddTool( ID_HIERARCHY_PUSH_POP_BUTT, wxEmptyString,
-KiBitmap( hierarchy_cursor_xpm ),
-_( "Ascend/descend hierarchy" ), wxITEM_CHECK
);
-
 m_drawToolBar->AddTool( ID_SCH_PLACE_COMPONENT, wxEmptyString,
KiBitmap(
 add_component_xpm ),
 HELP_PLACE_COMPONENTS, wxITEM_CHECK );

-- 
2.7.4
___
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] Reunion of zoom toolbar buttons

[Fabrizio Tappero]

hum.. hierarchy navigation is good but isn't great I think.

The use of the hierarchy nav icon on the right toolbar is a unknown  to me.
I would not mind to delete it but I feel maybe somebody knows how to use it.

cheers
Fabrizio


On Wed, Jun 7, 2017 at 5:16 PM, Marco Ciampa <ciam...@libero.it> wrote:

> On Tue, Jun 06, 2017 at 04:07:09PM +0200, Fabrizio Tappero wrote:
> > Hi Wayne,
> > there are some little tiny quirks like this in kicad. It is just
> > matter of time and we will fix them all !
>
> Perhaps also the two very similar hirarchy buttons could be grouped
> together on the main bar?
>
> TIA
>
> --
>
>
> 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] properly read default PDF viewer and use (under Linux Debian)

[Fabrizio Tappero]

Hi Wayne,
I guess this is what you want
cheers
Fabrizio


pdf-vieweer-inside-main-k.patch
>From 544416795fed2492b3ffa96b4b2c92285ce5071e Mon Sep 17 00:00:00 2001
From: Fabrizio Tappero <fabrizio.tapp...@gmail.com>
Date: Wed, 7 Jun 2017 17:35:37 +0200
Subject: [PATCH] read and use default linux pdf viewer inside main kicad
 windows when pdf is double-clicked

---
 common/gestfich.cpp | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/common/gestfich.cpp b/common/gestfich.cpp
index b68ec68..b54003f 100644
--- a/common/gestfich.cpp
+++ b/common/gestfich.cpp
@@ -352,7 +352,10 @@ bool OpenPDF( const wxString& file )
 if( !Pgm().UseSystemPdfBrowser() )//  Run the preferred PDF Browser
 {
 AddDelimiterString( filename );
-command = Pgm().GetPdfBrowserName() + wxT( " " ) + filename;
+if (wxLaunchDefaultApplication( filename ))
+{
+return true;
+}
 }
 else
 {
-- 
2.7.4




On Wed, Jun 7, 2017 at 5:11 PM, Wayne Stambaugh <stambau...@gmail.com>
wrote:

> Oops!  I didn't see this post before I sent my last post.  Please ignore
> it.  There is a slight problem with your patch.  You should check the
> return value of wxLaunchDefaultApplication and take the appropriate
> action.  In your patch, if wxLaunchDefaultApplication cannot launch the
> pdf viewer, it fails silently.  A better solution would be:
>
> if( wxLaunchDefaultApplication( file ) )
> return true;
>
> This would leave the command string empty and display the error message
> if wxLaunchDefaultApplication fails.
>
> Please make this change and I will commit your patch.
>
> Thanks,
>
> Wayne
>
> On 6/7/2017 10:50 AM, Fabrizio Tappero wrote:
> > Hi guys
> >
> > the following patch fix the problem of detecting the default PDF viewer
> > and use it to open PDF files (under Linux Debian) in the kicad main
> > window when you double click on a PDF doc.
> >
> > It would be great to test it under windows and OSX.
> >
> > cheers
> > Fabrizio
> >
> >
> >
> >
> >
> > From b3aa02b874476ae9f25311b4525e03b635091ed1 Mon Sep 17 00:00:00 2001
> > From: Fabrizio Tappero <fabrizio.tapp...@gmail.com
> > <mailto:fabrizio.tapp...@gmail.com>>
> > Date: Wed, 7 Jun 2017 16:43:16 +0200
> > Subject: [PATCH] default pdf reader is now properly detected unider Linux
> >
> > ---
> >  common/gestfich.cpp | 11 ---
> >  1 file changed, 4 insertions(+), 7 deletions(-)
> >
> > diff --git a/common/gestfich.cpp b/common/gestfich.cpp
> > index 3a09576..b68ec68 100644
> > --- a/common/gestfich.cpp
> > +++ b/common/gestfich.cpp
> > @@ -344,7 +344,7 @@ wxString KicadDatasPath()
> >
> >  bool OpenPDF( const wxString& file )
> >  {
> > -wxString command;
> > +wxString command = "";
> >  wxString filename = file;
> >
> >  Pgm().ReadPdfBrowserInfos();
> > @@ -356,12 +356,9 @@ bool OpenPDF( const wxString& file )
> >  }
> >  else
> >  {
> > -wxFileType* filetype =
> > wxTheMimeTypesManager->GetFileTypeFromExtension( wxT( "pdf" ) );
> > -
> > -if( filetype )
> > -command = filetype->GetOpenCommand( filename );
> > -
> > -delete filetype;
> > +AddDelimiterString( filename );
> > +wxLaunchDefaultApplication( filename );
> > +return true;
> >  }
> >
> >  if( !command.IsEmpty() )
> > --
> > 2.7.4
> >
> >
> >
> > ___
> > 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] pull default PDF viewer

[Fabrizio Tappero]

I noticed this problem in the past. also never really unrstood how to
handle that often two PDF documentation files are often defined (one in the
lib component properties) and one in the schematic comp properties. I am
really not sure how the two are defined. I assume you are talking about the
schedit.cpp portion

case ID_POPUP_SCH_DISPLAYDOC_CMP:

// Ensure the struct is a component (could be a piece of a
component, like Field, text..)
if( item && item->Type() == SCH_COMPONENT_T )
{
if( PART_LIBS* libs = Prj().SchLibs() )
{
LIB_ALIAS* entry = libs->FindLibraryAlias( (
(SCH_COMPONENT*) item )->GetLibId() );

if( entry && !!entry->GetDocFileName() )
{
SEARCH_STACK* lib_search = Prj().SchSearchS();

GetAssociatedDocument( this, entry->GetDocFileName(),
lib_search );
}
}
}
break;


cheers
Fabrizio



On Wed, Jun 7, 2017 at 5:05 PM, Wayne Stambaugh <stambau...@gmail.com>
wrote:

> Fabrizio,
>
> Thanks for testing this on Linux.  There is no need to send me a patch.
> I verified that this did not break the windows system default pdf viewer
> so I already have the change made.  I'm hoping it doesn't break anything
> on osx.  I will give you credit for the commit.
>
> In a related note, I found that the symbol context menu entry "Open
> Documentation" in Eeschema opens the documentation file defined by the
> symbol library (LIB_PART) rather than the documentation file defined by
> the schematic symbol (SCH_COMPONENT).  This needs to be fixed as well.
>
> Cheers,
>
> Wayne
>
> On 6/7/2017 10:45 AM, Fabrizio Tappero wrote:
> > ​works great! I'll submit a patch in a sec.
> >
> > cheers
> > Fabrizio
> > ​
> >
> > On Wed, Jun 7, 2017 at 2:03 PM, Wayne Stambaugh <stambau...@gmail.com
> > <mailto:stambau...@gmail.com>> wrote:
> >
> > Fabrizio,
> >
> > Try replacing wxMimeTypeManager with wxLaunchDefaultApplication[1].
> It
> > looks like this might be a better solution.  I would try it myself
> but
> > I'm at work and don't have access to a linux system.
> >
> > Cheers,
> >
> > Wayne
> >
> > [1]:
> > http://docs.wxwidgets.org/trunk/group__group__funcmacro__misc.html#
> ga04038d4c78e4c111d018b8f82b2d66c3
> > <http://docs.wxwidgets.org/trunk/group__group__funcmacro__misc.html#
> ga04038d4c78e4c111d018b8f82b2d66c3>
> >
> > On 6/7/2017 3:37 AM, Fabrizio Tappero wrote:
> > > Hi Wayne,
> > > it is indeed checked and it appears to be a 2 year old bug.
> > >
> > > http://thread.gmane.org/gmane.comp.lib.wxwidgets.devel/162783
> > <http://thread.gmane.org/gmane.comp.lib.wxwidgets.devel/162783>
> > >
> > > Any idea of how to properly fix this problem?
> > >
> > > cheers
> > > Fabrizio
> > >
> > >
> > >
> > > On Tue, Jun 6, 2017 at 7:58 PM, Wayne Stambaugh <
> stambau...@gmail.com <mailto:stambau...@gmail.com>
> > > <mailto:stambau...@gmail.com <mailto:stambau...@gmail.com>>>
> wrote:
> > >
> > > On 6/6/2017 4:17 AM, Fabrizio Tappero wrote:
> > > > ​Apologies for presenting this problem again and again
> > > >
> > > >  I think this topic came up too many times but (on my linux
> > system) the
> > > > default PDF viewer is not pulled correctly by kiCad. From
> > the terminal:
> > > >
> > > > $ cat /usr/share/applications/defaults.list  | grep pdf
> > > > application/pdf=xreader.desktop;evince.desktop;atril.desktop
> > >
> > > Is this the same as the mime type?  Look at another app such as
> > > Thunderbird and see what app it uses to open PDF files.
> > >
> > > >
> > > > but KiCad insist using Gimp.
> > >
> > > Is Preferences->PDF Viewer->System Default PDF Viewer in the
> KiCad
> > > launcher checked?  If not, KiCad will attempt to fall back on
> some
> > > reasonable default.  If it is checked, then there is most
> > likely a bug
> > > in wxMimeTypeManager which is used to determine the system
> > command to
> > > open a PDF file.
> > >
> > > >
> >  

[Kicad-developers] [PATCH] properly read default PDF viewer and use (under Linux Debian)

[Fabrizio Tappero]

Hi guys

the following patch fix the problem of detecting the default PDF viewer and
use it to open PDF files (under Linux Debian) in the kicad main window when
you double click on a PDF doc.

It would be great to test it under windows and OSX.

cheers
Fabrizio





>From b3aa02b874476ae9f25311b4525e03b635091ed1 Mon Sep 17 00:00:00 2001
From: Fabrizio Tappero <fabrizio.tapp...@gmail.com>
Date: Wed, 7 Jun 2017 16:43:16 +0200
Subject: [PATCH] default pdf reader is now properly detected unider Linux

---
 common/gestfich.cpp | 11 ---
 1 file changed, 4 insertions(+), 7 deletions(-)

diff --git a/common/gestfich.cpp b/common/gestfich.cpp
index 3a09576..b68ec68 100644
--- a/common/gestfich.cpp
+++ b/common/gestfich.cpp
@@ -344,7 +344,7 @@ wxString KicadDatasPath()

 bool OpenPDF( const wxString& file )
 {
-wxString command;
+wxString command = "";
 wxString filename = file;

 Pgm().ReadPdfBrowserInfos();
@@ -356,12 +356,9 @@ bool OpenPDF( const wxString& file )
 }
 else
 {
-wxFileType* filetype =
wxTheMimeTypesManager->GetFileTypeFromExtension( wxT( "pdf" ) );
-
-if( filetype )
-command = filetype->GetOpenCommand( filename );
-
-delete filetype;
+AddDelimiterString( filename );
+wxLaunchDefaultApplication( filename );
+return true;
 }

 if( !command.IsEmpty() )
-- 
2.7.4
___
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] pull default PDF viewer

[Fabrizio Tappero]

​works great! I'll submit a patch in a sec.

cheers
Fabrizio
​

On Wed, Jun 7, 2017 at 2:03 PM, Wayne Stambaugh <stambau...@gmail.com>
wrote:

> Fabrizio,
>
> Try replacing wxMimeTypeManager with wxLaunchDefaultApplication[1].  It
> looks like this might be a better solution.  I would try it myself but
> I'm at work and don't have access to a linux system.
>
> Cheers,
>
> Wayne
>
> [1]:
> http://docs.wxwidgets.org/trunk/group__group__funcmacro__misc.html#
> ga04038d4c78e4c111d018b8f82b2d66c3
>
> On 6/7/2017 3:37 AM, Fabrizio Tappero wrote:
> > Hi Wayne,
> > it is indeed checked and it appears to be a 2 year old bug.
> >
> > http://thread.gmane.org/gmane.comp.lib.wxwidgets.devel/162783
> >
> > Any idea of how to properly fix this problem?
> >
> > cheers
> > Fabrizio
> >
> >
> >
> > On Tue, Jun 6, 2017 at 7:58 PM, Wayne Stambaugh <stambau...@gmail.com
> > <mailto:stambau...@gmail.com>> wrote:
> >
> > On 6/6/2017 4:17 AM, Fabrizio Tappero wrote:
> > > ​Apologies for presenting this problem again and again
> > >
> > >  I think this topic came up too many times but (on my linux
> system) the
> > > default PDF viewer is not pulled correctly by kiCad. From the
> terminal:
> > >
> > > $ cat /usr/share/applications/defaults.list  | grep pdf
> > > application/pdf=xreader.desktop;evince.desktop;atril.desktop
> >
> > Is this the same as the mime type?  Look at another app such as
> > Thunderbird and see what app it uses to open PDF files.
> >
> > >
> > > but KiCad insist using Gimp.
> >
> > Is Preferences->PDF Viewer->System Default PDF Viewer in the KiCad
> > launcher checked?  If not, KiCad will attempt to fall back on some
> > reasonable default.  If it is checked, then there is most likely a
> bug
> > in wxMimeTypeManager which is used to determine the system command to
> > open a PDF file.
> >
> > >
> > > can anybody point me to the right direction? I am looking at
> preferences.cpp
> >
> > The source file you are looking for is common/gestfich.cpp.  The
> > function is OpenPDF().
> >
> > >
> > > Cheers
> > > Fabrizio​
> > >
> > >
> > > ___
> > > Mailing list: https://launchpad.net/~kicad-developers
> > <https://launchpad.net/~kicad-developers>
> > > Post to : kicad-developers@lists.launchpad.net
> > <mailto:kicad-developers@lists.launchpad.net>
> > > Unsubscribe : https://launchpad.net/~kicad-developers
> > <https://launchpad.net/~kicad-developers>
> > > More help   : https://help.launchpad.net/ListHelp
> > <https://help.launchpad.net/ListHelp>
> > >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > <https://launchpad.net/~kicad-developers>
> > Post to : kicad-developers@lists.launchpad.net
> > <mailto:kicad-developers@lists.launchpad.net>
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > <https://launchpad.net/~kicad-developers>
> > More help   : https://help.launchpad.net/ListHelp
> > <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] pull default PDF viewer

[Fabrizio Tappero]

Hi Wayne,
it is indeed checked and it appears to be a 2 year old bug.

http://thread.gmane.org/gmane.comp.lib.wxwidgets.devel/162783

Any idea of how to properly fix this problem?

cheers
Fabrizio



On Tue, Jun 6, 2017 at 7:58 PM, Wayne Stambaugh <stambau...@gmail.com>
wrote:

> On 6/6/2017 4:17 AM, Fabrizio Tappero wrote:
> > ​Apologies for presenting this problem again and again
> >
> >  I think this topic came up too many times but (on my linux system) the
> > default PDF viewer is not pulled correctly by kiCad. From the terminal:
> >
> > $ cat /usr/share/applications/defaults.list  | grep pdf
> > application/pdf=xreader.desktop;evince.desktop;atril.desktop
>
> Is this the same as the mime type?  Look at another app such as
> Thunderbird and see what app it uses to open PDF files.
>
> >
> > but KiCad insist using Gimp.
>
> Is Preferences->PDF Viewer->System Default PDF Viewer in the KiCad
> launcher checked?  If not, KiCad will attempt to fall back on some
> reasonable default.  If it is checked, then there is most likely a bug
> in wxMimeTypeManager which is used to determine the system command to
> open a PDF file.
>
> >
> > can anybody point me to the right direction? I am looking at
> preferences.cpp
>
> The source file you are looking for is common/gestfich.cpp.  The
> function is OpenPDF().
>
> >
> > Cheers
> > Fabrizio​
> >
> >
> > ___
> > 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] [RFC] Standard field for manufacturer part number in schematic symbols

[Fabrizio Tappero]

​Hi there,​

Just in case somebody does not know what JP means here, I share my personal
​ preference setting​
:

 KiCad - Schematic - Preferences - Schematic Editor Options - Default Fields

​[image: Inline image 1]​

I personally think that JP suggestion is the solution to the basic problem
that Kaspar is talking about. I have to agree however with Kaspar when
 he says that a "MPN" is more meaningful than the
"datasheet" default field.

At the end of the day a schematic is made of components that deserve an
ID or a MPN.

my 2c
Fabrizio





On Wed, Dec 21, 2016 at 6:01 PM, jp charras  wrote:

> Le 21/12/2016 à 17:19, Kaspar Emanuel a écrit :
> > Thank you Clemens and Kevin for your responses.
> >
> > Clemens, you raise that you are not happy with hard-coding fields at all
> because there is no
> > standard way to do it. But KiCad’s symbols already come with a datasheet
> field for instance. To me,
> > the datasheet field is way less useful than an MPN field. In any case we
> are trying to come up with
> > a better, standard way to do it, what's the problem with that?
> >
> > You then go on to describe your method and say you have no use case for
> it. That’s fair enough but I
> > think its clean that I and a few other people /do/ have a use case.
> Furthermore, the proposal, if
> > implemented, shouldn’t affect your way of working at all.
> >
> > Kevin, you say that this would not work for generic components like
> resistors and capacitors. I
> > don’t think I was clear enough: the proposal is to add a standard MPN
> field to schematic symbols to
> > be populated /when they are part of a schematic/, i.e. their values (and
> tolerances etc) have been
> > assigned. Really we are talking about the schematic format.
>
> Kaspar,
>
> Adding a new field does not imply a schematic format change.
> You can already add any field to a schematic component or a library
> component (library part)
>
> I don't really understand why you are thinking the schematic file format
> should be modified.
>
> If you want to see a user field always existing in your component editor,
> just add this field name
> and a default value in the schematic editor options (Default fields).
>
> The feature you want is already available since many years in Eeschema.
>
> The spice simulator also uses predefined fields to store simulator
> parameters in lib or in schematic.
> AFAIK, it works without issues, and without any change in schematic file
> format.
>
> For me, the main question is:
> From the point of view of the *schematic editor*, what is the purpose of
> this field?
> (I am not talking about the user point of view)
>
> >
> > Your alternative system is interesting but/is/ a bit more complicated.
> Standardizing on an MPN field
> > is something existing tooling could make use of very quickly but with
> yours they would have to
> > change their way of working quite substantively. I think further
> discussion of your proposal is a
> > separate point and should continue in another thread.
> >
> > All the best,
> >
> > Kaspar
> >
>
> --
> Jean-Pierre CHARRAS
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Reunion of zoom toolbar buttons

[Fabrizio Tappero]

Hi Wayne,
there are some little tiny quirks like this in kicad. It is just
matter of time and we will fix them all !

cheers
Fabrizio


On Tue, Jun 6, 2017 at 3:41 PM, Wayne Stambaugh  wrote:
> Bernhard,
>
> I committed your patch.  Good catch.  I never even noticed this before
> but it definitely makes more sense to group all of the zoom buttons
> together.
>
> Thanks,
>
> Wayne
>
> On 6/5/2017 2:17 PM, Bernhard Stegmaier wrote:
>> Hi,
>>
>> I use KiCad for some while now, but I only recently noticed that there is a 
>> “zoom to selection” function/button in the right toolbox.
>> Don’t know why, maybe because of an icon change.
>>
>> I guess the main reason that I didn’t notice it before was that I just 
>> didn’t expect it to be in the right toolbar with all the schema, PCB, etc. 
>> related (drawing) stuff. And, in contrast having all the other zoom buttons 
>> in the top toolbar.
>>
>> Attached a patch that moves “zoom selection” into top toolbar next to the 
>> other zoom buttons.
>> It further slightly switches buttons so that all zoom buttons are next to 
>> each other:
>>
>>
>>
>>
>>
>> For my taste it makes much more sense like this.
>> However, if there are good reasons against it or many don’t like it, then 
>> just ignore it… :)
>>
>>
>> Regards,
>> Bernhard
>>
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>
> ___
> 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] pull default PDF viewer

[Fabrizio Tappero]

​Apologies for presenting this problem again and again

 I think this topic came up too many times but (on my linux system) the
default PDF viewer is not pulled correctly by kiCad. From the terminal:

$ cat /usr/share/applications/defaults.list  | grep pdf
application/pdf=xreader.desktop;evince.desktop;atril.desktop

but KiCad insist using Gimp.

can anybody point me to the right direction? I am looking at preferences.cpp

Cheers
Fabrizio​
___
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] Reunion of zoom toolbar buttons

[Fabrizio Tappero]

totally needed patch!

cheers
Fabrizio


On Mon, Jun 5, 2017 at 8:17 PM, Bernhard Stegmaier 
wrote:

> Hi,
>
> I use KiCad for some while now, but I only recently noticed that there is
> a “zoom to selection” function/button in the right toolbox.
> Don’t know why, maybe because of an icon change.
>
> I guess the main reason that I didn’t notice it before was that I just
> didn’t expect it to be in the right toolbar with all the schema, PCB, etc.
> related (drawing) stuff. And, in contrast having all the other zoom buttons
> in the top toolbar.
>
> Attached a patch that moves “zoom selection” into top toolbar next to the
> other zoom buttons.
> It further slightly switches buttons so that all zoom buttons are next to
> each other:
>
>
>
> For my taste it makes much more sense like this.
> However, if there are good reasons against it or many don’t like it, then
> just ignore it… :)
>
>
> Regards,
> Bernhard
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
___
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] kicad right click menu corrections and few icons corrections

[Fabrizio Tappero]

Thank you for point it out.

I am on it.

cheers
Fabrizio


On Mon, Jun 5, 2017 at 6:40 PM, Wayne Stambaugh <stambau...@gmail.com>
wrote:

> I second this.  The biggest offender that I can see is the new library
> viewer icon.  There are also a few images with a while border around
> them as well and the don't look very good with your typical grey toolbar
> color.
>
> On 6/5/2017 8:09 AM, Nick Østergaard wrote:
> > I see some buggy icons, they contain a white background which makes
> > them look funky. Could you please fix those?  See attached.
> >
> > 2017-05-30 17:17 GMT+02:00 Fabrizio Tappero <fabrizio.tapp...@gmail.com
> >:
> >> here you go.
> >>
> >> Fabrizio
> >>
> >> On Tue, May 30, 2017 at 4:05 PM, Nick Østergaard <oe.n...@gmail.com>
> wrote:
> >>>
> >>> I don't see any patches attached.
> >>>
> >>> 2017-05-30 14:54 GMT+02:00 Fabrizio Tappero <
> fabrizio.tapp...@gmail.com>:
> >>>> Hello Wayne,
> >>>> In attachment you can find a good review of approx 30 icons and a
> global
> >>>> simplification of approx 30 icons.
> >>>> I have also corrected some menu labels.
> >>>>
> >>>> Since there is a lot of corrected text that is very much related to
> >>>> English, it would be great if you could review it before submitting
> it.
> >>>> A
> >>>> not so fun work but I think it will make kicad a much better tool.
> >>>>
> >>>> I think it would be recommendable to avoid "a" and "the" in button and
> >>>> menu
> >>>> tooltips. So that it way easier to understand what the button or
> tooltip
> >>>> is
> >>>> about. The use of singular plural is also inconsistent and I tried to
> >>>> fix
> >>>> it. Please Wayne feel free to make any changes you think is important.
> >>>>
> >>>> I have also notices that several menus are a little inconstant. I will
> >>>> try
> >>>> work on it since I think the current kicad UI is very usable but it
> >>>> needs
> >>>> to be more consistent.
> >>>>
> >>>> I have tried to fixed a lot of icons so that their meaning is more
> >>>> immediate to understand. I have as well started a process of
> >>>> simplification
> >>>> of many redundant icons. I think it is important that we begin
> >>>> simplifing
> >>>> the kicad icon set because at the moment is really too large.
> >>>>
> >>>> Here below a detailed description of the changes.
> >>>>
> >>>> Cheers
> >>>> Fabrizio
> >>>>
> >>>>
> >>>> ### Deleted the following icons(deleted: svg, cpp and png):
> >>>> edit_component
> >>>> edit_part
> >>>> move_text
> >>>> rotate_field
> >>>> rotate_glabel
> >>>> rotate_module_cw
> >>>> rotate_module_ccw
> >>>> rotate_pin
> >>>> rotatehlabel
> >>>> many_good_icons
> >>>> dismiss
> >>>> move_track
> >>>> move_track_segment
> >>>> library2
> >>>> copy_button
> >>>> copyblock
> >>>> edit_sheet
> >>>> icon_text
> >>>> pagelayout_new
> >>>> sch_new
> >>>> rescue_pcbnew
> >>>> schematic
> >>>> pagelayout_load_default
> >>>> gerbview_open_recent_ziparchive_files
> >>>> gerbview_open_recent_drill_files
> >>>> gerber_recent_files
> >>>> pagelayout_recent
> >>>> revert_pcbnew
> >>>>
> >>>> ### Lightly modified icons:
> >>>> bom
> >>>> autoplace_fields
> >>>> flip_board
> >>>> duplicate_module
> >>>> delete
> >>>> new_sch
> >>>> new_pcb
> >>>> new_component
> >>>> general_deletions
> >>>> reload
> >>>> pagelayout_load
> >>>> add_line
> >>>> add_entry
> >>>> add_tracks
> >>>> add_tracks_and_vias
> >>>> about
> >>>> array_module
> >>>> image
> >>>> noconn
> >>>> add_dashed_line.svg
> >>>> add_bus.svg
>

Re: [Kicad-developers] menu icons

[Fabrizio Tappero]

hi,
on (probably last) linux mint, menu icons work well and are 100% controlled
t the preference option.

cheers
Fabrizio


On Tue, Jun 6, 2017 at 9:14 AM, Marco Ciampa  wrote:

> On Mon, Jun 05, 2017 at 05:37:32PM -0500, José Ignacio wrote:
> > Menu icons are disabled by default in gnome 3 in an effort to make it
> look
> > more like an Apple product. You can enable them (on gtk 3.10+) with:
> >
> > gsettings set org.gnome.settings-daemon.plugins.xsettings overrides
> > "{'Gtk/ButtonImages': <1>, 'Gtk/MenuImages': <1>}"
>
> So the
>
> Preference->Icon options->Icons in menu
>
> is there for what?
>
> TIA
>
> Regards,
>
> --
>
>
> Marco Ciampa
>
> I know a joke about UDP, but you might not get it.
>
> 
>
>  GNU/Linux User #78271
>  FSFE fellow #364
>
> 
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
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] kicad right click menu corrections and few icons corrections

[Fabrizio Tappero]

cheers Jose,
I will look into it and submit all necessary fix next week.

cheers
Fabrizio


On Fri, Jun 2, 2017 at 5:05 PM, José Ignacio <jose.cyb...@gmail.com> wrote:

> The use of "..." for menu items that show a dialog with extra options
> necessary to perform the operation has been in Microsoft's UX guidelines
> and apple's HIG since time immemorial:
>
> https://msdn.microsoft.com/en-us/library/dn742392.aspx#usingellipses
>
> https://developer.apple.com/library/content/documentation/
> UserExperience/Conceptual/OSXHIGuidelines/TerminologyWording.html#//
> apple_ref/doc/uid/2957-CH15-SW3
>
> https://developer.gnome.org/hig/stable/writing-style.html.en#ellipses
>
> It is a very well known and traditional convention and Kicad shouldn't
> break it. As the guidelines say, the ellipsis (...) is reserved for
> commands that need further input from the user to proceed, showing a modal
> dialog shouldn't be enough to warrant adding the ellipsis (though I've seen
> several programs be ellipsis-happy and put it on everything that calls a
> dialog...)
>
> On Fri, Jun 2, 2017 at 8:20 AM, Fabrizio Tappero <
> fabrizio.tapp...@gmail.com> wrote:
>
>> Hi JP,
>>
>> thanks a lot!!
>>
>> I am a little unsure about this "Save as..." three dots thing used every
>> time the menu item takes you to a second window. but I will investigate
>> about UI stuff a little.
>>
>> cheers
>> Fabrizio
>>
>>
>>
>>
>> On Fri, Jun 2, 2017 at 12:44 PM, jp charras <jp.char...@wanadoo.fr>
>> wrote:
>>
>>> Le 30/05/2017 à 14:54, Fabrizio Tappero a écrit :
>>> > Hello Wayne,
>>> > In attachment you can find a good review of approx 30 icons and a
>>> global
>>> > simplification of approx 30 icons.
>>> > I have also corrected some menu labels.
>>> >
>>> > Since there is a lot of corrected text that is very much related to
>>> > English, it would be great if you could review it before submitting
>>> it. A
>>> > not so fun work but I think it will make kicad a much better tool.
>>> >
>>> > I think it would be recommendable to avoid "a" and "the" in button and
>>> menu
>>> > tooltips. So that it way easier to understand what the button or
>>> tooltip is
>>> > about. The use of singular plural is also inconsistent and I tried to
>>> fix
>>> > it. Please Wayne feel free to make any changes you think is important.
>>> >
>>> > I have also notices that several menus are a little inconstant. I will
>>> try
>>> > work on it since I think the current kicad UI is very usable but it
>>> needs
>>> > to be more consistent.
>>> >
>>> > I have tried to fixed a lot of icons so that their meaning is more
>>> > immediate to understand. I have as well started a process of
>>> simplification
>>> > of many redundant icons. I think it is important that we begin
>>> simplifing
>>> > the kicad icon set because at the moment is really too large.
>>> >
>>> > Here below a detailed description of the changes.
>>> >
>>> > Cheers
>>> > Fabrizio
>>>
>>>
>>> Hi Fabrizio,
>>>
>>> I committed your icons.
>>> Thanks.
>>>
>>>
>>> --
>>> Jean-Pierre CHARRAS
>>>
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] kicad right click menu corrections and few icons corrections

[Fabrizio Tappero]

Hi JP,

thanks a lot!!

I am a little unsure about this "Save as..." three dots thing used every
time the menu item takes you to a second window. but I will investigate
about UI stuff a little.

cheers
Fabrizio




On Fri, Jun 2, 2017 at 12:44 PM, jp charras <jp.char...@wanadoo.fr> wrote:

> Le 30/05/2017 à 14:54, Fabrizio Tappero a écrit :
> > Hello Wayne,
> > In attachment you can find a good review of approx 30 icons and a global
> > simplification of approx 30 icons.
> > I have also corrected some menu labels.
> >
> > Since there is a lot of corrected text that is very much related to
> > English, it would be great if you could review it before submitting it. A
> > not so fun work but I think it will make kicad a much better tool.
> >
> > I think it would be recommendable to avoid "a" and "the" in button and
> menu
> > tooltips. So that it way easier to understand what the button or tooltip
> is
> > about. The use of singular plural is also inconsistent and I tried to fix
> > it. Please Wayne feel free to make any changes you think is important.
> >
> > I have also notices that several menus are a little inconstant. I will
> try
> > work on it since I think the current kicad UI is very usable but it needs
> > to be more consistent.
> >
> > I have tried to fixed a lot of icons so that their meaning is more
> > immediate to understand. I have as well started a process of
> simplification
> > of many redundant icons. I think it is important that we begin simplifing
> > the kicad icon set because at the moment is really too large.
> >
> > Here below a detailed description of the changes.
> >
> > Cheers
> > Fabrizio
>
>
> Hi Fabrizio,
>
> I committed your icons.
> Thanks.
>
>
> --
> Jean-Pierre CHARRAS
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Hello & Questions to future Administration of Python Plugins

[Fabrizio Tappero]

Hi Simon,
footprint library components are not very problematic for me because there
are already
so many in the standard kicad lib. In that department I feel it would be
great to just add
aliases so that when some manufacturer decides that a diode SOD123 should
be called
XYZ I can just look for XYZ (in an hypotetical search window that does not
yet exist) and
I find the SOD123 which has XYZ as alias.

Nevertheless I love Altium footprint wizard even thogh I almost never
used it.

What takes some of my time is the schematic lib component generation that
cannot really
be automated. So Once I have created a new component I guess I could just
submit it to
some github repo to be vetted by kicad librarians.

The problem of the existance of a librarian is also a hard issue to
solve... maybe guys at
Nvidia will fix that problem with some AI stuff.

When I mentioned the F1, F2, F3 buttons liked to python script I meant
sometihng like this:
[image: Inline image 1]

An other really time consuming process is the filling up of the schematic
library component
parameters from the mouser webpage. god that is tedious.

cheers
Fabrizio



On Fri, Jun 2, 2017 at 12:36 PM, Simon Küppers <
simon.kuepp...@ruhr-uni-bochum.de> wrote:

> Hi Fabrizio,
>
> I spend long hours doing schematics at work and I love the idea of
>> implementing python stuff that could make my life easier. Specifically
>> I spend a long time in library component generation and I would love
>> to do something about it. This could be done by creating new python
>> (or non python) tools to import component info or to created tools to
>> facilitate the contribution to the quality (and size) of the kicad
>> lib. Not really sure what is best.
>>
>
> With regard to library generation I think the footprint generator is a
> good example
> of what even a "standard" user can achieve with available python scripting
> support.
> Imagine one wants to quickly add pin headers with N pins where N ranges
> from 4 to 64.
>
> Python scripts could be attached to F1, F2 and F3 general-purpose
>> buttons.
>>
>
> I did not check specifically, but I read somewhere that KiCad has
> something like a
> central point where shortcuts are set up right? In this case, executing a
> python script
> with a given name could be just another entry in this central
> configuration. This would
> allow maximum flexibility.
>
> However, you remind me of another thing and that is something like
> function call hooks.
> It would be really cool to have something like a python script that
> registers callback
> functions that are hooked to "pick up trace" and "drop trace" for example.
> Now with
> respect to the Via Fence generator and some clever coding, this could
> allow moving
> a trace with online rebuilding of the Via Fence when the trace is released
> again
> after moving. Just an idea!
>
> This people
>> would probably make kicad better. This would be classified as "kicad
>> user harvesting via python scripting for library component creation "
>> ;-) a topic I always wanted to talk about on this mailing list.
>>
>
> I second that. Could be really powerful to the overall development of the
> KiCad Software
>
> Best Regards
> Simon
>
___
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] Hello & Questions to future Administration of Python Plugins

[Fabrizio Tappero]

Hi Simon,
welcome to the group!

Reading your interesting email I decided to write to you. I am interested
as well in the python functionality for the purpose of implementing killing
functionalities. via-fence generator is certainly an interesting thing.

I spend long hours doing schematics at work and I love the idea of
implementing python stuff that could make my life easier. Specifically I
spend a long time in library component generation and I would love to do
something about it. This could be done by creating new python (or non
python) tools to import component info or to created tools to facilitate
the contribution to the quality (and size) of the kicad lib. Not really
sure what is best.

Python scripts could be attached to F1, F2 and F3 general-purpose buttons.
So that others can easily use these scripts. This people would probably
make kicad better. This would be classified as "kicad user harvesting via
python scripting for library component creation " ;-) a topic I always
wanted to talk about on this mailing list.

Regarding your scripting database idea. Kicad comes with some script for
BOM generation and I guess lead developers would certainly consider adding
more scripts into the main kicad repo.

Cheers
Fabrizio




On Thu, Jun 1, 2017 at 8:01 PM, Simon Küppers <
simon.kuepp...@ruhr-uni-bochum.de> wrote:

> Hi everyone,
> Thanks Wayne for approving me to the developers mailing list.
> I am very new to KiCAD (only heard of it some time ago) and just stumbled
> upon a
> Youtube Video of 2017 FOSDEM (I believe?) where Wayne presented the
> current state of KiCAD.
> As a result I had to see for myself and I am quite impressed of the
> development of KiCAD in the
> last years! Very impressive.
>
> I am a Researcher working in the areas of IC Design, (RF-) PCB Design and
> I am also a quite
> realiable programmer (thats what I think anyway :-)). I am used to EAGLE
> CAD (from the oldern days)
> and Altium Designer (ugh..). For IC Design we use Cadence Virtuoso.
>
> Now, what really kicks me off with KiCAD is the (still very early) Python
> support. In my opinion, it is definitely
> the right choice to pull some non-major functionality from the main KiCAD
> core and implement it into Python.
> Why? Simply because that way it is much easier for people to modify,
> tweak, extend and bugfix the KiCAD software,
> without having to study the KiCAD core. I want to be the living proof for
> this fact ;-)
>
> I already have some ideas for pcbnew plugins. E.g. a Via-Fence Generator
> (select a line-segment in pcbnew, start
> generator and enjoy the vias to the left and right of the line). There is
> similar functionality in Altium, but it
> is very rudimentory and cannot be adjusted or tweaked very much. Also it
> is sometimes quite buggy resulting in non-ideal via
> placement and due to this we usually place those vias (with GCPW
> transmission lines for example) by hand...
> I think this would be a nice example of what non-proficient users could
> add to KiCAD without ever touching anything belonging
> to the KiCAD C++ core application (where the latter would not fit into my
> available spare time due to its complexity, sorry!)
>
> Anyway, what I wanted to ask before even starting with the development is
> the following. I know the current status of the
> Python interface in pcbnew is very limited and "only" an interface
> generated by SWIG. So I guess there will be some
> heavy adjustments in the API in the future (which is fine with me).
>
> Is it planned in the future to make plugins part of the KiCAD distribution
> (i.e. ship them within the distro packages?)?
> (Or do KiCAD users have to find a way for organizing a repository of KiCAD
> plugins?)
> If yes, is the correct place to discuss their development (and request
> features) in this mailing list? Or should the forums
> be used instead/at first?
>
> I guess that is it for now. A big thanks to all the developers and
> especially the CERN folks. I put in a donation a few days ago :-)
>
> Best 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

[Kicad-developers] did something happened?

[Fabrizio Tappero]

hi guys,
I am experiencing a very low email traffic in this mailing list. Did
something happened?

cheers
Fabrizio
___
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: Open Datasheet in Project Dir

[Fabrizio Tappero]

Hi Cheng,

Don't worry you are doing just fine.

Whenever somebody submits a patch, he does exactly what you did. Normally
it takes some days for the patch to get submitted because in these days
several people express opinions and feedback, as in your case.

If nobody is against it and if the patch is useful for KiCad, the patch is
applied to the main repo in few days. A gentle reminder is a good way to
communicate with people with kicad repo writing rights.

I hope you will submit more stuff. Contributing can be quite a rewarding
experience, I think. Just remember that the dev. community decides what
goes in and what stays out. And normally common good is paramount.

cheers
Fabrizio







On Wed, May 31, 2017 at 11:49 AM, Cheng Sheng  wrote:

> okay, thanks for the info, Sergey.
>
> Don't find any explicit rule on how to select reviewers on the how to
> contribute  page. So
> cc Jean-Pierre because you did a lot of commits recently. Let me know or
> reassign if there's some duty partitioning. Thanks.
>
> Regards,
> Cheng
>
> On 31 May 2017 at 11:01, Sergey A. Borshch 
> wrote:
>
>> On 31.05.2017 10:57, Cheng Sheng wrote:
>>
>>> So is there any conclusion on this patch like it will be accepted or
>>> rejected or needs some improvement?
>>>
>>> Sergey, are you a patch reviewer who can commit to the repo, or I need
>>> to add someone explicitly? Thanks.
>>>
>> No, I'm just a user who wanted to share it's point of view.
>>
>> Regards,
>>> Cheng
>>>
>>> On May 29, 2017 12:33 PM, "Cheng Sheng" > jeru.sh...@gmail.com>> wrote:
>>>
>>>
>>>
>>> On 29 May 2017 at 09:40, Sergey A. Borshch <
>>> sb...@users.sourceforge.net
>>> > wrote:
>>>
>>> On 28.05.2017 23:49, Cheng Sheng wrote:
>>>
>>> I myself prefer storing all files specific to the project
>>> within the
>>> project directory, including datasheets, components, adjusted
>>> footprints and scripts. This way makes things easier when I
>>> copy the
>>> project around. After all, I don't mind disk space waste on
>>> a few
>>> duplicated datasheets; they don't take much space.
>>>
>>> Ok, what is your workflow? You choose component, pick it from
>>> library
>>> into schematics and then manually copy it's datasheet (from
>>> where?) into
>>> the project folder to make it available from schematics?
>>>
>>> I'm not a professional on electronics so I don't (want/bother to)
>>> maintain a
>>> centralized collection of datasheets. Instead, when I select
>>> components, I
>>> do parametric search on digikey/mouser/whatever, then check
>>> datasheets on
>>> the website, download to project dir if chosen.
>>>
>>>
>>> I have my library and my project both under version control
>>> system, so I
>>> use latest, exactly the same (with all latest error fixes)
>>> library and
>>> latest, most actual datasheets in every project. But I always
>>> can easily
>>> revert library repository to state it was when project was
>>> finished.
>>>
>>> I admire your patience and professionalism. I see your spirit to
>>> reuse as
>>> many things as possible. Shared library has its reuse benefit. Of
>>> course,
>>> also has its downsides. Eg., I don't necessarily remember how the
>>> shared
>>> libraries are setup one year after I finish a project or after I
>>> move to a
>>> new machine. So I prefer each project to be as self-containing as
>>> possible.
>>>
>>> Of course, putting everything inside the project also has its
>>> downsides,
>>> maybe even more than your proposed shared library approach. But I
>>> suppose
>>> this is just personal preferences. Unless there's a strong reason
>>> why my
>>> personal preference is terrible (that it is worse than a "standard
>>> approach"
>>> in ALL aspects) or by following this preference my patch makes the
>>> software
>>> terrible, it shouldn't be forbidden, right?
>>>
>>>
>>> There is "Archive library" option in eeschema File menu, which
>>> extract
>>> from library all components used in project. It can be extended
>>> to
>>> extract datasheets as well if it doesn't do it right now.
>>>
>>> hm... Am I missing some compile options? I don't see such an option
>>> in
>>> eevschema. Instead, only an "Archive Current Project" item in the
>>> project
>>> window.
>>>
>>> Anyway, even if datasheet extraction is added to "Archive library",
>>> you'll
>>> still need a way to open a relative datasheet unless the archiving
>>> leaves an
>>> absolute path (which seems unlikely the case, by guessing).
>>>
>>>
>>>
>>> If the direction of move by the patch makes some other
>>> workflow
>>> styles harder to optimize in the future, please let me know.

[Kicad-developers] [PATCH] kicad right click menu corrections and few icons corrections

[Fabrizio Tappero]

Hello Wayne,
In attachment you can find a good review of approx 30 icons and a global
simplification of approx 30 icons.
I have also corrected some menu labels.

Since there is a lot of corrected text that is very much related to
English, it would be great if you could review it before submitting it. A
not so fun work but I think it will make kicad a much better tool.

I think it would be recommendable to avoid "a" and "the" in button and menu
tooltips. So that it way easier to understand what the button or tooltip is
about. The use of singular plural is also inconsistent and I tried to fix
it. Please Wayne feel free to make any changes you think is important.

I have also notices that several menus are a little inconstant. I will try
work on it since I think the current kicad UI is very usable but it needs
to be more consistent.

I have tried to fixed a lot of icons so that their meaning is more
immediate to understand. I have as well started a process of simplification
of many redundant icons. I think it is important that we begin simplifing
the kicad icon set because at the moment is really too large.

Here below a detailed description of the changes.

Cheers
Fabrizio


### Deleted the following icons(deleted: svg, cpp and png):
edit_component
edit_part
move_text
rotate_field
rotate_glabel
rotate_module_cw
rotate_module_ccw
rotate_pin
rotatehlabel
many_good_icons
dismiss
move_track
move_track_segment
library2
copy_button
copyblock
edit_sheet
icon_text
pagelayout_new
sch_new
rescue_pcbnew
schematic
pagelayout_load_default
gerbview_open_recent_ziparchive_files
gerbview_open_recent_drill_files
gerber_recent_files
pagelayout_recent
revert_pcbnew

### Lightly modified icons:
bom
autoplace_fields
flip_board
duplicate_module
delete
new_sch
new_pcb
new_component
general_deletions
reload
pagelayout_load
add_line
add_entry
add_tracks
add_tracks_and_vias
about
array_module
image
noconn
add_dashed_line.svg
add_bus.svg
scheamatic
resize_sheet
eeschema
netlist
pagelayout_load_default
datasheet
svg_file
pagelayout_normal_view_mode
pagelayout_special_view_mode
unknow
export
import
pcb_update
pcbnew
editor
edit
directory
browse_files
icon_gerbview_small
post_drill



### created few new icons that replace few icons used inproperly (created
svg, cpp, png):
exchange
icon
drag
rescue
path
copy
new_generic
recent
pcbcalculator

### Corrected some label content. It is important here to be rigorus about
it. Inkscape could
be a good tool that can be used as reference:
eescheam rightclick menu
cvpcb rightclick menu
pcbnew rightclick menu
libedit rightclick menu
icon tooltips
gerber and drill file menu
main kicad hotkey icon menu
fixes several tooltip phrases like "Opens a new schematic" into "Open new
schematic sheet"
few more menues and sub menus here and there (see git log for details).

Beside makes many icons more effective, this massive patch is trying to
rise the quality of the kicad UI. Few examples are:
write all words in a menu  with capital letter. Tooltip sentence should
start with capital letter.
do not end a menu item is with a dot "."
do not use "the" or "a" when possible for both tooltip and menu item
use consistent and meaninguful text. "Set Language" is better than
"Language".
"Set grid origin" is better than "Set origin point for the grid"
limit use of "..." (this is a debatable issue)
etc.
___
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] Bugfix for component table

[Fabrizio Tappero]

Hi Oliver,

How would I realize that? "Description" field does not appear in the
schematic component properties window. Maximum freedom to add all fields
the user wants should, I think, be imperative. btw, all description field
content coming from .dcm is actually empty in all my schematics.

cheers
Fabrizio


On Wed, May 24, 2017 at 12:51 AM, Oliver Walters <
oliver.henry.walt...@gmail.com> wrote:

> Cirilo,
>
> I think the major issue here is that I introduced a previously
> invisible-to-the-user field called "Description" which is lifted from the
> .dcm file. Fabrizio had a custom field called "Description" as he did not
> know that this other field existed.
>
> Just as people would not have a custom field called "Footprint", I think
> that once people realize that the "Description" field is inherent to the
> symbol itself, they will rename such custom fields to something else.
>
>
>
> Also, I note that there seems to be a duplication of fields already -
> there's a "Datasheet" field and a "Documentation" field, one lives in the
> .dcm file and one in the .lib file. This seems to be much more of a source
> of confusion to me.
>
> On Wed, May 24, 2017 at 8:20 AM, Cirilo Bernardo <
> cirilo.berna...@gmail.com> wrote:
>
>> On Tue, May 23, 2017 at 1:10 PM, Wayne Stambaugh <stambau...@gmail.com>
>> wrote:
>> > On 5/23/2017 4:17 AM, Fabrizio Tappero wrote:
>> >> cheers Oliver,
>> >> I do not know what a .dcm file is.
>> >>
>> >> I am not sure it is a good idea to have a in-built field called
>> >> Description in the table viewer. But I can easily see how that is
>> >> useful. I guess you would like to use this table to add info. This
>> makes
>> >> it non a table viewer. The current icon label says "Component table
>> >> view" which I find ambiguous. Maybe Wayne can jump in with a proper
>> name
>> >> for it.
>> >
>> > The component information strings are not fields.  They are part of the
>> > component definition and are not user definable.  There are four
>> > component information definitions: name, description, key words (tags),
>> > and documentation file name.  You could create fields with the same
>> > names so I can understand how this could be confusing.
>> >
>> > Toolbar button tooltips should be a verb followed by a short
>> > description.  In this case "Edit component properties" would work.
>> >
>>
>> Perhaps the software should (re)assign the names of the first 4 fields and
>> use a 2-part name to distinguish them from anything else? Maybe a special
>> character at the front of the name would be enough - let's say '@'.  That
>> shouldn't look too ugly and it's unlikely someone would begin a field name
>> with '@' (or some other suitable character). At any rate, if the user can
>> give an arbitrary field > 4 a name which happens to match a name of one
>> of the first 4 fields, we need some scheme so that users (and machines!)
>> can distinguish the special fields.
>>
>> - Cirilo
>>
>> >>
>> >> I am having the feeling the development of this table did not come from
>> >> a clean plan of having an XYZ tool. Or maybe is just me. Please dont
>> get
>> >> me wrong, I love this table (and the soon to come new icon) but it
>> might
>> >> be a good idea to drop the word viewer for it if we want the (great)
>> >> ability to edit stuff.
>> >>
>> >> I hope this helps.
>> >>
>> >> Fabrizio
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> On Tue, May 23, 2017 at 10:00 AM, Oliver Walters
>> >> <oliver.henry.walt...@gmail.com <mailto:oliver.henry.walt...@gmail.com
>> >>
>> >> wrote:
>> >>
>> >> Fabrizio,
>> >>
>> >> 1. You have added a custom field called "Description".
>> >> 2. The table viewer has an "inbuild" field called "Description". It
>> >> populates this field with the component description which is found
>> >> in the .dcm files
>> >>
>> >> Here's what I see.
>> >>
>> >> Inline image 1
>> >>
>> >> Here I have added the custom "description" field with dummy data to
>> >> only one comp

Re: [Kicad-developers] {PATCH] Icon tweaks

[Fabrizio Tappero]

cheers, I will have a look.

Fabrizio


On Thu, May 4, 2017 at 5:12 AM, Константин Барановский <
baranovskiykonstan...@gmail.com> wrote:

> Hi Fabrizio,
> you can find all the icons in my branch:
> https://code.launchpad.net/~baranovskiykonstantin/kicad/+
> git/kicad/+ref/new_icons_rebased
>
> This branch was reworked and now it looks like patch sets over master
> branch. I'm periodically apply the rebasing, so be careful if you planing
> to use it.
>
> 2017-05-03 11:59 GMT+03:00 Fabrizio Tappero <fabrizio.tapp...@gmail.com>:
>
>> Hi konstantin.
>> how are you? could you please direct me to these icons please?
>>
>> cheers
>> Fabrizio
>>
>>
>> On Sat, Feb 11, 2017 at 8:05 AM, Константин Барановский <
>> baranovskiykonstan...@gmail.com> wrote:
>>
>>> I'm also working on new icons for a long time. You can find them in my
>>> branch:
>>> https://code.launchpad.net/~baranovskiykonstantin/kicad/+git/kicad
>>>
>>>
>>> 2017-02-11 1:10 GMT+02:00 Ben Hest <bombledm...@gmail.com>:
>>>
>>>> Not entirely sure which OS you are using, but LightShot [1] is
>>>> fantastic at being able take pictures of menus on Windows. (It works on Mac
>>>> also)
>>>>
>>>> [1] https://app.prntscr.com/en/index.html
>>>>
>>>> On Fri, Feb 10, 2017 at 3:55 PM, John Beard <john.j.be...@gmail.com>
>>>> wrote:
>>>>
>>>>> And here are the same images with the changed icons highlighted, maybe
>>>>> not everyone loves spot-the-difference puzzles that much!
>>>>>
>>>>> Some icons are hidden in menus which I don't seem to be able to
>>>>> screenshot.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> John
>>>>>
>>>>> On Sat, Feb 11, 2017 at 5:37 AM, John Beard <john.j.be...@gmail.com>
>>>>> wrote:
>>>>> > Hi,
>>>>> >
>>>>> > I have a few tweaks to some icons in Pcbnew and Eeschema. These are
>>>>> > mostly minor tweaks that are intended to make the icons match a
>>>>> little
>>>>> > better and give a more uniform look and feel:
>>>>> >
>>>>> > https://code.launchpad.net/~john-j-beard/kicad/+git/kicad/+ref/icons
>>>>> >
>>>>> > * Pixel align a few icons to make then crisper when displayed
>>>>> > * Redraw all the zoom icons to be crisper and flatter. The zoom to
>>>>> fit
>>>>> > (Home) icon is now a sort of reticle rather than a pair of square
>>>>> > brackets as text.
>>>>> > * Redraw console icon to be flat to match other existing icons.
>>>>> > * Mute some very bright colours, especially the green-legged module
>>>>> > icons - use the zone icons as a guide for the colour brightness.
>>>>> >
>>>>> > Attached are screen shots of pcbnew and eeschema, where you can see
>>>>> > some of the icons.
>>>>> >
>>>>> > I know icons and UI subjects in general are very subjective and
>>>>> > personal, so I'd welcome input!
>>>>> >
>>>>> > Cheers,
>>>>> >
>>>>> > John
>>>>>
>>>>> ___
>>>>> 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
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> -Ben
>>>>
>>>> ___
>>>> 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] [RFC] Application naming

[Fabrizio Tappero]

Hi Guys,
I actually did propose to change the names of the kicad tools few years
ago.

I personally think:

- all kicad tools should be renamed with 100% priority to users. Hence, for
example, the schematic editor should be called "schematic editor".
- rename kicad itself would also be a good idea but as JP says, kicad is
actually good enough for me. Google will eventually find it out.
- please let's stop using capital letters in all his possible combinations,
I am pretty sure no kicad user knows if it is KiCad, Kicad or kicad.
- I strongly think "ki-something" or "kicad-something" should be avoided.
- I am actually not surprised that some brand name sells more than others.
Very few people would like his girlfriend to be called "Rotox"

cheers
Fabrizio




On Mon, Apr 10, 2017 at 11:51 AM, Marco Ciampa  wrote:

> On Thu, Feb 02, 2017 at 05:59:00PM -0500, Chris Pavlina wrote:
> > On Thu, Feb 02, 2017 at 11:54:09PM +0100, Kristoffer Ödmark wrote:
> > > Why dont keep it dead simple, but still keeping the KiCAD brand?
> > >
> > > I suggest prefix every subprogram with kicad- and then use a either
> > > extremely well known abbreviation (PCB) or a descriptive english word.
> > >
> > > Examples:
> > >
> > > eeschema-> kicad-schematics
> > > pcbnew  -> kicad-layouts
> > > 3d-viewer   -> kicad-3d
> > > gerb-viewer -> kicad-gerbers
> > > whatever-> kicad-whatever
> > > 
> > >
> > > Self explaining names that are easy to use standalone as well as names
> that
> > > will not make a new users scoff and works well as binary filenames.
> >
> > Yes, I like this. I was talking about the names in the UI, mostly - this
> > is a good companion to that.
> >
> > >
> > > I really dislike having entirely different names for the binary and the
> > > shortcut-key/desktop-shortcut like ubuntu and their decision to have
> > > "Document Viewer" as the name for evince etc.
> >
> > Agreed.
> >
>
> Sorry for being so late...
>
> For what is worth my opinion, I strongly agree to both.
>
> BTW: apart from screenshots texts, search & replace can do miracles on
> all documentation in every language...
>
> --
>
>
> 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] Fwd: [PATCH] 3 better icons

[Fabrizio Tappero]

Hi Wayne,
I actually agree. I am looking at improving the current icons without
really going for big changes because of the usual documentation problem.

thanks for merging this patch.

cheers
Fabrizio


On Tue, Apr 4, 2017 at 3:18 PM, Wayne Stambaugh <stambau...@gmail.com>
wrote:

> Hey Fabrizio,
>
> I merged your patch.  I was wondering if a ruler would be a more
> universally recognizable metaphor for measurement rather than calipers.
> Calipers are a pretty specialized measurement tool that not everyone who
> used KiCad may recognize.  I'm not saying it needs to be changed but
> just something to think about.
>
> Thanks,
>
> Wayne
>
> On 4/3/2017 8:53 AM, Fabrizio Tappero wrote:
> > Dear Wayne,
> > apologize for generating these kind of problems. I have rebased it and
> > generated a new patch of all 4 new icons.
> >
> > Regards
> > Fabrizio
> >
> >
> >
> >
> >
> >
> > On Fri, Mar 31, 2017 at 10:32 PM, Wayne Stambaugh <stambau...@gmail.com
> > <mailto:stambau...@gmail.com>> wrote:
> >
> > Fabrizio,
> >
> > This patch did not apply cleanly.  Please rebase and repost it.
> >
> > Thanks,
> >
> > Wayne
> >
> > On 3/28/2017 12:37 PM, Fabrizio Tappero wrote:
> > > gentle reminder
> > >
> > > regards
> > > Fabrizio
> > >
> > >
> > >
> > > -- Forwarded message --
> > > From: *Fabrizio Tappero* <fabrizio.tapp...@gmail.com  fabrizio.tapp...@gmail.com>
> > > <mailto:fabrizio.tapp...@gmail.com <mailto:fabrizio.tappero@
> gmail.com>>>
> > > Date: Wed, Mar 22, 2017 at 4:25 PM
> > > Subject: [PATCH] 3 better icons
> > > To: KiCad Developers <kicad-developers@lists.launchpad.net
> > <mailto:kicad-developers@lists.launchpad.net>
> > > <mailto:kicad-developers@lists.launchpad.net
> > <mailto:kicad-developers@lists.launchpad.net>>>
> > >
> > >
> > > Hello,
> > > like in the picture below the following patch is an improvement of
> the
> > > following icons:
> > >
> > > highlight nets
> > > display local ratsnest
> > > click to highlight net
> > >
> > > nowadays having the mouse pointer in the icon is really not needed.
> > >
> > > Regards
> > > Fabrizio
> > >
> > > Inline image 1
> > >
> > > Inline image 2
> > >
> > >
> > >
> > > ___
> > > Mailing list: https://launchpad.net/~kicad-developers
> > <https://launchpad.net/~kicad-developers>
> > > Post to : kicad-developers@lists.launchpad.net
> > <mailto:kicad-developers@lists.launchpad.net>
> > > Unsubscribe : https://launchpad.net/~kicad-developers
> > <https://launchpad.net/~kicad-developers>
> > > More help   : https://help.launchpad.net/ListHelp
> > <https://help.launchpad.net/ListHelp>
> > >
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > <https://launchpad.net/~kicad-developers>
> > Post to : kicad-developers@lists.launchpad.net
> > <mailto:kicad-developers@lists.launchpad.net>
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > <https://launchpad.net/~kicad-developers>
> > More help   : https://help.launchpad.net/ListHelp
> > <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] Fwd: [PATCH] 3 better icons

[Fabrizio Tappero]

Dear Wayne,
apologize for generating these kind of problems. I have rebased it and
generated a new patch of all 4 new icons.

Regards
Fabrizio






On Fri, Mar 31, 2017 at 10:32 PM, Wayne Stambaugh <stambau...@gmail.com>
wrote:

> Fabrizio,
>
> This patch did not apply cleanly.  Please rebase and repost it.
>
> Thanks,
>
> Wayne
>
> On 3/28/2017 12:37 PM, Fabrizio Tappero wrote:
> > gentle reminder
> >
> > regards
> > Fabrizio
> >
> >
> >
> > -- Forwarded message --
> > From: *Fabrizio Tappero* <fabrizio.tapp...@gmail.com
> > <mailto:fabrizio.tapp...@gmail.com>>
> > Date: Wed, Mar 22, 2017 at 4:25 PM
> > Subject: [PATCH] 3 better icons
> > To: KiCad Developers <kicad-developers@lists.launchpad.net
> > <mailto:kicad-developers@lists.launchpad.net>>
> >
> >
> > Hello,
> > like in the picture below the following patch is an improvement of the
> > following icons:
> >
> > highlight nets
> > display local ratsnest
> > click to highlight net
> >
> > nowadays having the mouse pointer in the icon is really not needed.
> >
> > Regards
> > Fabrizio
> >
> > Inline image 1
> >
> > Inline image 2
> >
> >
> >
> > ___
> > 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
>
From 9183824ddfea31109153b2852fcb8a021d557b97 Mon Sep 17 00:00:00 2001
From: Fabrizio Tappero <fabrizio.tapp...@gmail.com>
Date: Mon, 3 Apr 2017 14:44:27 +0200
Subject: [PATCH] 4 better icons

---
 bitmaps_png/cpp_26/measurement.cpp  |  35 --
 bitmaps_png/cpp_26/net_highlight.cpp|  65 +--
 bitmaps_png/cpp_26/net_highlight_schematic.cpp  |  70 +++-
 bitmaps_png/cpp_26/tool_ratsnest.cpp|  90 +++
 bitmaps_png/sources/measurement.svg | 136 ---
 bitmaps_png/sources/net_highlight.svg   |  51 -
 bitmaps_png/sources/net_highlight_schematic.svg |  88 +++
 bitmaps_png/sources/tool_ratsnest.svg   | 140 +++-
 8 files changed, 274 insertions(+), 401 deletions(-)

diff --git a/bitmaps_png/cpp_26/measurement.cpp b/bitmaps_png/cpp_26/measurement.cpp
index 8031f1f..023e0a0 100644
--- a/bitmaps_png/cpp_26/measurement.cpp
+++ b/bitmaps_png/cpp_26/measurement.cpp
@@ -7,16 +7,31 @@
 
 static const unsigned char png[] = {
  0x89, 0x50, 0x4e, 0x47, 0x0d, 0x0a, 0x1a, 0x0a, 0x00, 0x00, 0x00, 0x0d, 0x49, 0x48, 0x44, 0x52,
- 0x00, 0x00, 0x00, 0x1a, 0x00, 0x00, 0x00, 0x1a, 0x08, 0x04, 0x00, 0x00, 0x00, 0x03, 0x43, 0x84,
- 0x45, 0x00, 0x00, 0x00, 0x76, 0x49, 0x44, 0x41, 0x54, 0x38, 0xcb, 0x63, 0x60, 0x18, 0x2a, 0x20,
- 0x35, 0x01, 0x3b, 0x1b, 0x2f, 0x48, 0xfb, 0x92, 0xaa, 0x0d, 0xd5, 0xa2, 0x9d, 0xf6, 0x85, 0x58,
- 0x4d, 0xff, 0xd3, 0xae, 0xc6, 0x72, 0x33, 0x30, 0xc4, 0x72, 0xa7, 0x5d, 0x4d, 0xfb, 0x4f, 0xbc,
- 0xa6, 0xff, 0xe9, 0xf3, 0x19, 0x18, 0xd2, 0xe7, 0x83, 0x58, 0x24, 0x68, 0x02, 0x29, 0x86, 0xd1,
- 0x78, 0x81, 0xdd, 0x25, 0xe3, 0xff, 0xa4, 0x41, 0xa0, 0x26, 0xe3, 0xff, 0x17, 0x49, 0x84, 0x50,
- 0x4d, 0xc8, 0x1a, 0x09, 0xb3, 0x51, 0x34, 0x11, 0x4b, 0x92, 0xab, 0xc9, 0xf6, 0x1a, 0x19, 0x01,
- 0x81, 0x3d, 0x90, 0x09, 0x06, 0xfc, 0x70, 0xd4, 0x94, 0x5e, 0x8e, 0x43, 0x53, 0x3d, 0xde, 0xf4,
- 0x07, 0xd2, 0x86, 0xa1, 0xa9, 0x9e, 0x61, 0x14, 0xe0, 0x07, 0x00, 0x55, 0x88, 0x33, 0x29, 0x9a,
- 0xe8, 0x0b, 0x9c, 0x00, 0x00, 0x00, 0x00, 0x49, 0x45, 0x4e, 0x44, 0xae, 0x42, 0x60, 0x82,
+ 0x00, 0x00, 0x00, 0x1a, 0x00, 0x00, 0x00, 0x1a, 0x08, 0x06, 0x00, 0x00, 0x00, 0xa9, 0x4a, 0x4c,
+ 0xce, 0x00, 0x00, 0x01, 0x65, 0x49, 0x44, 0x41, 0x54, 0x48, 0xc7, 0x63, 0x60, 0x18, 0x05, 0x54,
+ 0x05, 0x8b, 0x3e, 0x6b, 0x32, 0xac, 0xfa, 0xcf, 0x06, 0x62, 0x1a, 0x1a, 0x1a, 0xea, 0xd3, 0xd0,
+ 0xa2, 0x8f, 0x7d, 0x30, 0x8b, 0x8c, 0x8c, 0x8c, 0x66, 0xd0, 0xc6, 0x92, 0x49, 0xff, 0xd9, 0x19,
+ 0x16, 0x7e, 0x7c, 0x03, 0xa6, 0x81, 0xc0, 0xd8, 0xd8, 0xf8, 0xb3, 0xb9, 0xb9, 0x39, 0x1f, 0x86,
+ 0xba, 0xfd, 0xff, 0x59, 0x80, 0xea, 0xfe, 0x83, 0xf1, 0xff, 0xff, 0x8c, 0xa4, 0x5b, 0xb4, 0xf0,
+ 0x43, 0x08, 0x58, 0x33, 0xc2, 0xa2, 0xff, 0x40, 0x5f, 0xa5, 0xe1, 0xb1, 0xe8, 0x1f, 0x79, 0x3e,
+ 0x5a, 0xf8, 0x71, 0x1b, 0xd8, 0x80, 0xf9, 0xff, 0x39, 0x60, 0x16, 0x01, 0xf1, 0x19, 0xea, 0x04,
+ 0xd7, 0xfc, 0x8f, 0xa6, 0x70, 0x0b, 0x60, 0x78, 0

Re: [Kicad-developers] [PATCH] better UI experience (properties window)

[Fabrizio Tappero]

thanks a lot Wayne,
cheers
Fabrizio


On Fri, Mar 31, 2017 at 10:27 PM, Wayne Stambaugh <stambau...@gmail.com>
wrote:

> Fabrizio,
>
> I pushed your patch to the master branch.  Thank you for your contribution.
>
> Cheers,
>
> Wayne
>
> On 3/30/2017 7:28 AM, Fabrizio Tappero wrote:
> > Hi Wayne,
> > OK, I fixed the problem. Please refer to the patch in attachment, it
> > will produce this:
> >
> > ​Inline image 1​
> >
> > ​I tried to use the extra ASCII degree simbol but I could ​not compile
> it.
> >
> > PLEASE pay attention to the fact that the vertical position part is now
> > "top center bottom"
> >
> > Cheers
> > Fabrizio
> >
> > On Tue, Mar 28, 2017 at 7:38 PM, Wayne Stambaugh <stambau...@gmail.com
> > <mailto:stambau...@gmail.com>> wrote:
> >
> > Hey Fabrizio,
> >
> > No problem.  Thank you for the update.
> >
> > Cheers,
> >
> > Wayne
> >
> > On 3/28/2017 1:41 PM, Fabrizio Tappero wrote:
> > > Hi Wayne,
> > > yeah I have wrongly inserted the patch file into it. I can fix it
> but I
> > > need two days to get back to my PC.
> > >
> > > I will get back to you on Thursday
> > >
> > > cheers
> > > Fabrizio
> > >
> > >
> > > On Tue, Mar 28, 2017 at 6:43 PM, Wayne Stambaugh <
> stambau...@gmail.com <mailto:stambau...@gmail.com>
> > > <mailto:stambau...@gmail.com <mailto:stambau...@gmail.com>>>
> wrote:
> > >
> > > Hey Fabrizio,
> > >
> > > Still no luck.  Here is the `git am` output:
> > >
> > > $ git am <
> > > /c/Users/Wayne/Archive/temp/kicad/patches/better-
> properties-wind.patch
> > > Applying: commit 49df104f1b7c7e7ac4a1087a7dc3bfef053fcc33
> > > error: better-properties-wind.patch: does not exist in index
> > > error: patch failed:
> > > eeschema/dialogs/dialog_edit_component_in_schematic_fbp.cpp:45
> > > error: eeschema/dialogs/dialog_edit_
> component_in_schematic_fbp.cpp:
> > > patch does not apply
> > > error: patch failed:
> > > eeschema/dialogs/dialog_edit_component_in_schematic_fbp.
> fbp:480
> > > error: eeschema/dialogs/dialog_edit_
> component_in_schematic_fbp.fbp:
> > > patch does not apply
> > > Patch failed at 0001 commit 49df104f1b7c7e7ac4a1087a7dc3bf
> ef053fcc33
> > > The copy of the patch that failed is found in:
> .git/rebase-apply/patch
> > > When you have resolved this problem, run "git am --continue".
> > > If you prefer to skip this patch, run "git am --skip" instead.
> > > To restore the original branch and stop patching, run "git am
> --abort".
> > >
> > >
> > > On 3/28/2017 12:37 PM, Fabrizio Tappero wrote:
> > > > Hi Wayne,
> > > > here you go. I am having some problems with this PC.
> > > >
> > > > cheers
> > > > Fabrizio
> > > >
> > > >
> > > >
> > > >
> > > > On Tue, Mar 28, 2017 at 4:40 PM, Wayne Stambaugh <
> stambau...@gmail.com <mailto:stambau...@gmail.com>
> > <mailto:stambau...@gmail.com <mailto:stambau...@gmail.com>>
> > > > <mailto:stambau...@gmail.com <mailto:stambau...@gmail.com>
> > <mailto:stambau...@gmail.com <mailto:stambau...@gmail.com>>>> wrote:
> > > >
> > > > Fabrizio,
> > > >
> > > > I just attempt to apply this patch and both `git am` and
> `patch` are
> > > > failing to apply the patch.  Please rebase and resend it.
> > > >
> > > > Thanks,
> > > >
> > > > Wayne
> > > >
> > > > On 3/28/2017 4:06 AM, Fabrizio Tappero wrote:
> > > > > Hi guys,
> > > > > OK, fixed all problems ;-)
> > > > >
> > > > > Inline image 1
> > > > >
> > > > > Please note that, as rightly suggested, the vertical
> po

Re: [Kicad-developers] [PATCH] Measurement tool for GAL

[Fabrizio Tappero]

I second this

Regards
Fabrizio


On Wed, Mar 29, 2017 at 2:23 AM, Andrey Kuznetsov <kandre...@gmail.com>
wrote:

> Good point Kevin.
>
> Can we have "hold down CTRL" to disable snap to grip feature? That would
> cover the caliper and other myriad of uses when snap to grid is unwanted.
>
> On Tue, Mar 28, 2017 at 7:07 AM, Kevin Cozens <ke...@ve3syb.ca> wrote:
>
>> On 2017-03-28 03:25 AM, Fabrizio Tappero wrote:
>>
>>> this ruler (caliper icon) does look really good.
>>>
>> [snip]
>>
>>> It is often a good idea to have a way to measure footprint size.
>>>
>>
>> The caliper tool is a useful addition to Kicad. The only one thing I've
>> noticed about it is it only lets you measure distances from one grid point
>> to another. If you need to measure starting from the edge of a pad (for
>> example) to some other point you can't unless you change the grid spacing.
>>
>> If there is a way to tell the caliper to not snap to grid points when you
>> are using it to make a measurement I haven't figured out how to do that.
>>
>> --
>> Cheers!
>>
>> Kevin.
>>
>> http://www.ve3syb.ca/   |"Nerds make the shiny things that
>> distract
>> Owner of Elecraft K2 #2172  | the mouth-breathers, and that's why
>> we're
>> | powerful!"
>> #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
>>
>
>
>
> --
> Remember The Past, Live The Present, Change The Future
> Those who look only to the past or the present are certain to miss the
> future [JFK]
>
> kandre...@gmail.com
> Live Long and Prosper,
> Andrey
>
> ___
> 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] Fwd: [PATCH] new measurement (caliper) icon

[Fabrizio Tappero]

gentle reminder.

Sorry I do not want to be insistent at all it is just that I will loose
track of these patches.

Regards
Fabrizio

-- Forwarded message --
From: Fabrizio Tappero <fabrizio.tapp...@gmail.com>
Date: Wed, Mar 22, 2017 at 4:47 PM
Subject: [PATCH] new measurement (caliper) icon
To: KiCad Developers <kicad-developers@lists.launchpad.net>


This patch is an importuned version of the measurement icon (caliper)

thanks

Fabrzio
diff --git a/bitmaps_png/cpp_26/measurement.cpp b/bitmaps_png/cpp_26/measurement.cpp
index 8031f1f..023e0a0 100644
--- a/bitmaps_png/cpp_26/measurement.cpp
+++ b/bitmaps_png/cpp_26/measurement.cpp
@@ -7,16 +7,31 @@
 
 static const unsigned char png[] = {
  0x89, 0x50, 0x4e, 0x47, 0x0d, 0x0a, 0x1a, 0x0a, 0x00, 0x00, 0x00, 0x0d, 0x49, 0x48, 0x44, 0x52,
- 0x00, 0x00, 0x00, 0x1a, 0x00, 0x00, 0x00, 0x1a, 0x08, 0x04, 0x00, 0x00, 0x00, 0x03, 0x43, 0x84,
- 0x45, 0x00, 0x00, 0x00, 0x76, 0x49, 0x44, 0x41, 0x54, 0x38, 0xcb, 0x63, 0x60, 0x18, 0x2a, 0x20,
- 0x35, 0x01, 0x3b, 0x1b, 0x2f, 0x48, 0xfb, 0x92, 0xaa, 0x0d, 0xd5, 0xa2, 0x9d, 0xf6, 0x85, 0x58,
- 0x4d, 0xff, 0xd3, 0xae, 0xc6, 0x72, 0x33, 0x30, 0xc4, 0x72, 0xa7, 0x5d, 0x4d, 0xfb, 0x4f, 0xbc,
- 0xa6, 0xff, 0xe9, 0xf3, 0x19, 0x18, 0xd2, 0xe7, 0x83, 0x58, 0x24, 0x68, 0x02, 0x29, 0x86, 0xd1,
- 0x78, 0x81, 0xdd, 0x25, 0xe3, 0xff, 0xa4, 0x41, 0xa0, 0x26, 0xe3, 0xff, 0x17, 0x49, 0x84, 0x50,
- 0x4d, 0xc8, 0x1a, 0x09, 0xb3, 0x51, 0x34, 0x11, 0x4b, 0x92, 0xab, 0xc9, 0xf6, 0x1a, 0x19, 0x01,
- 0x81, 0x3d, 0x90, 0x09, 0x06, 0xfc, 0x70, 0xd4, 0x94, 0x5e, 0x8e, 0x43, 0x53, 0x3d, 0xde, 0xf4,
- 0x07, 0xd2, 0x86, 0xa1, 0xa9, 0x9e, 0x61, 0x14, 0xe0, 0x07, 0x00, 0x55, 0x88, 0x33, 0x29, 0x9a,
- 0xe8, 0x0b, 0x9c, 0x00, 0x00, 0x00, 0x00, 0x49, 0x45, 0x4e, 0x44, 0xae, 0x42, 0x60, 0x82,
+ 0x00, 0x00, 0x00, 0x1a, 0x00, 0x00, 0x00, 0x1a, 0x08, 0x06, 0x00, 0x00, 0x00, 0xa9, 0x4a, 0x4c,
+ 0xce, 0x00, 0x00, 0x01, 0x65, 0x49, 0x44, 0x41, 0x54, 0x48, 0xc7, 0x63, 0x60, 0x18, 0x05, 0x54,
+ 0x05, 0x8b, 0x3e, 0x6b, 0x32, 0xac, 0xfa, 0xcf, 0x06, 0x62, 0x1a, 0x1a, 0x1a, 0xea, 0xd3, 0xd0,
+ 0xa2, 0x8f, 0x7d, 0x30, 0x8b, 0x8c, 0x8c, 0x8c, 0x66, 0xd0, 0xc6, 0x92, 0x49, 0xff, 0xd9, 0x19,
+ 0x16, 0x7e, 0x7c, 0x03, 0xa6, 0x81, 0xc0, 0xd8, 0xd8, 0xf8, 0xb3, 0xb9, 0xb9, 0x39, 0x1f, 0x86,
+ 0xba, 0xfd, 0xff, 0x59, 0x80, 0xea, 0xfe, 0x83, 0xf1, 0xff, 0xff, 0x8c, 0xa4, 0x5b, 0xb4, 0xf0,
+ 0x43, 0x08, 0x58, 0x33, 0xc2, 0xa2, 0xff, 0x40, 0x5f, 0xa5, 0xe1, 0xb1, 0xe8, 0x1f, 0x79, 0x3e,
+ 0x5a, 0xf8, 0x71, 0x1b, 0xd8, 0x80, 0xf9, 0xff, 0x39, 0x60, 0x16, 0x01, 0xf1, 0x19, 0xea, 0x04,
+ 0xd7, 0xfc, 0x8f, 0xa6, 0x70, 0x0b, 0x60, 0x78, 0xd5, 0x7f, 0x4e, 0x24, 0x8b, 0xc8, 0xc1, 0xe5,
+ 0xd8, 0x7c, 0xf1, 0x1d, 0xc5, 0x12, 0x10, 0x9e, 0xf9, 0x8c, 0x8b, 0x42, 0x8b, 0xfe, 0x63, 0x8b,
+ 0x97, 0x6f, 0x18, 0x16, 0x2d, 0xfc, 0x18, 0xc3, 0xb0, 0xe8, 0x43, 0x28, 0xd5, 0x30, 0xd4, 0x47,
+ 0x5f, 0xb1, 0x58, 0x44, 0x5d, 0x0c, 0xb5, 0xe8, 0x0b, 0xbd, 0x2c, 0xfa, 0x4c, 0x2f, 0x8b, 0x3e,
+ 0xa2, 0x08, 0x52, 0x33, 0x6e, 0x50, 0xe2, 0x68, 0xd1, 0xc7, 0x0f, 0x98, 0xb6, 0x43, 0x80, 0x8a,
+ 0x8a, 0x0a, 0x3b, 0x15, 0x53, 0xdd, 0xc7, 0x13, 0x28, 0x16, 0x21, 0x15, 0x29, 0x14, 0x58, 0xd4,
+ 0x81, 0xc5, 0xa2, 0x4f, 0x45, 0x54, 0xb6, 0xa8, 0x03, 0x7b, 0xc9, 0x30, 0xef, 0xad, 0x2c, 0xb8,
+ 0xcc, 0x82, 0x59, 0xd4, 0xf0, 0x9f, 0x09, 0x87, 0x45, 0xd7, 0x28, 0x2f, 0x86, 0x16, 0x7e, 0x3c,
+ 0x89, 0x54, 0xfc, 0x30, 0xe3, 0xb0, 0x68, 0x16, 0xe5, 0x16, 0x2d, 0xf8, 0x54, 0x06, 0xb3, 0xe8,
+ 0xcf, 0xbf, 0xff, 0xaf, 0xfe, 0xff, 0xff, 0xff, 0x09, 0x84, 0x7f, 0xfc, 0xf8, 0xf1, 0x1a, 0x66,
+ 0x91, 0x89, 0x89, 0x49, 0x1c, 0x15, 0x2a, 0xbb, 0x0f, 0x8a, 0xb0, 0xe0, 0xfb, 0xfd, 0xef, 0xff,
+ 0x8f, 0xff, 0x50, 0xf0, 0xf3, 0xe7, 0xcf, 0x1f, 0x30, 0x8b, 0x4c, 0x4d, 0x4d, 0x95, 0xa8, 0x53,
+ 0x8a, 0x2f, 0xf8, 0xb8, 0x1c, 0x64, 0xd1, 0xaf, 0xbf, 0x98, 0x16, 0x01, 0xeb, 0xa4, 0x8d, 0xd4,
+ 0xab, 0x5d, 0x67, 0xbe, 0xe3, 0x07, 0x5a, 0xf4, 0x10, 0x8b, 0x45, 0xcf, 0x81, 0x58, 0x84, 0xba,
+ 0x55, 0xf9, 0x82, 0x8f, 0xde, 0x3f, 0xff, 0xfe, 0x7f, 0x0f, 0xb4, 0xe3, 0x3b, 0x08, 0x03, 0x2d,
+ 0x7a, 0x0f, 0x8c, 0x1b, 0xbf, 0x21, 0xd3, 0xb0, 0x02, 0x00, 0x19, 0xe9, 0x9a, 0x8a, 0x19, 0x88,
+ 0x19, 0xc3, 0x00, 0x00, 0x00, 0x00, 0x49, 0x45, 0x4e, 0x44, 0xae, 0x42, 0x60, 0x82,
 };
 
 const BITMAP_OPAQUE measurement_xpm[1] = {{ png, sizeof( png ), "measurement_xpm" }};

diff --git a/bitmaps_png/sources/measurement.svg b/bitmaps_png/sources/measurement.svg
index f821f10..1627adb 100644
--- a/bitmaps_png/sources/measurement.svg
+++ b/bitmaps_png/sources/measurement.svg
@@ -11,7 +11,7 @@
width="26"
version="1.1"
id="svg2"
-   inkscape:version="0.92.1 r"
+   inkscape:version="0.91 r"
sodipodi:docname="measurement.svg">
   
@@ -21,7 +21,7 @@
 image/svg+xml
 http://purl.org/dc/dcmitype/StillImage; />
-
+
   
 
   
@@ -34,15 +34,15 @@
  guidetolerance="10"
  inkscape:pageopacity=&quo

[Kicad-developers] Fwd: [PATCH] 3 better icons

[Fabrizio Tappero]

gentle reminder

regards
Fabrizio



-- Forwarded message --
From: Fabrizio Tappero <fabrizio.tapp...@gmail.com>
Date: Wed, Mar 22, 2017 at 4:25 PM
Subject: [PATCH] 3 better icons
To: KiCad Developers <kicad-developers@lists.launchpad.net>


Hello,
like in the picture below the following patch is an improvement of the
following icons:

highlight nets
display local ratsnest
click to highlight net

nowadays having the mouse pointer in the icon is really not needed.

Regards
Fabrizio

[image: Inline image 1]

[image: Inline image 2]
diff --git a/bitmaps_png/cpp_26/net_highlight.cpp b/bitmaps_png/cpp_26/net_highlight.cpp
index d3e941d..ecb1808 100644
--- a/bitmaps_png/cpp_26/net_highlight.cpp
+++ b/bitmaps_png/cpp_26/net_highlight.cpp
@@ -8,46 +8,31 @@
 static const unsigned char png[] = {
  0x89, 0x50, 0x4e, 0x47, 0x0d, 0x0a, 0x1a, 0x0a, 0x00, 0x00, 0x00, 0x0d, 0x49, 0x48, 0x44, 0x52,
  0x00, 0x00, 0x00, 0x1a, 0x00, 0x00, 0x00, 0x1a, 0x08, 0x06, 0x00, 0x00, 0x00, 0xa9, 0x4a, 0x4c,
- 0xce, 0x00, 0x00, 0x02, 0x62, 0x49, 0x44, 0x41, 0x54, 0x48, 0xc7, 0xbd, 0x96, 0xcd, 0x6f, 0x12,
- 0x41, 0x18, 0x87, 0xd7, 0xd8, 0x26, 0x3d, 0xf6, 0xe4, 0x49, 0xff, 0x00, 0xff, 0x02, 0xce, 0x06,
- 0xb2, 0x59, 0x41, 0x3e, 0xba, 0x85, 0x96, 0x82, 0x80, 0x29, 0x2d, 0x35, 0xdb, 0xb2, 0x7e, 0x9b,
- 0x40, 0x8d, 0xd2, 0x43, 0xa9, 0x91, 0x86, 0xa4, 0x1c, 0x40, 0x30, 0x31, 0xc6, 0x46, 0x4d, 0x3c,
- 0x78, 0x6d, 0x6f, 0x36, 0x31, 0x69, 0xf5, 0xd4, 0x36, 0xe1, 0x6a, 0xf6, 0x40, 0x24, 0x6d, 0x0c,
- 0xb0, 0x72, 0x50, 0x2e, 0xfa, 0xeb, 0xcc, 0xca, 0xd2, 0xa5, 0x45, 0x61, 0x71, 0xf1, 0xf0, 0x64,
- 0xf3, 0xce, 0x6c, 0xde, 0x27, 0x33, 0xfb, 0xce, 0xbc, 0xcb, 0x00, 0x60, 0xfe, 0x07, 0x7f, 0x9e,
- 0x1c, 0x1e, 0x16, 0x09, 0x12, 0x41, 0xe8, 0x96, 0x24, 0x9f, 0xcf, 0x8b, 0x04, 0xa9, 0x50, 0x28,
- 0x08, 0xfd, 0x88, 0x1a, 0x04, 0x10, 0xe4, 0x1e, 0x44, 0x0d, 0x02, 0x08, 0x72, 0x3f, 0x22, 0xb4,
- 0xe8, 0x2e, 0x82, 0x4a, 0x5f, 0xa2, 0xcf, 0x23, 0x23, 0x83, 0x15, 0x99, 0xcd, 0xe6, 0xd0, 0x03,
- 0x87, 0x03, 0xcf, 0xd3, 0x69, 0xd0, 0x27, 0x8d, 0x0d, 0x11, 0x31, 0x1f, 0x19, 0x81, 0x20, 0x13,
- 0x40, 0xb1, 0xdf, 0xb6, 0xa3, 0x5c, 0x2e, 0xb7, 0xa0, 0xb1, 0x3a, 0xa7, 0x8b, 0x4f, 0x4c, 0x83,
- 0xd9, 0x61, 0x44, 0xad, 0x48, 0x52, 0x27, 0x87, 0xde, 0x0d, 0x21, 0xfd, 0x2c, 0xdd, 0x26, 0xa2,
- 0x31, 0x1d, 0xa7, 0xf3, 0xa6, 0x98, 0x09, 0xa3, 0x6f, 0x47, 0xf5, 0x08, 0xa5, 0x63, 0x11, 0xb1,
- 0x2a, 0xf6, 0x1e, 0x56, 0x74, 0xd9, 0xcd, 0x61, 0x22, 0xe2, 0xc1, 0x85, 0xc2, 0xf9, 0x5e, 0x24,
- 0x74, 0x97, 0x84, 0xbe, 0xbe, 0x91, 0x8b, 0x77, 0xd6, 0x0e, 0x0e, 0x0f, 0x10, 0xbd, 0x11, 0xad,
- 0xb9, 0x78, 0xd7, 0x2a, 0xc3, 0x30, 0x67, 0x06, 0x52, 0x75, 0x54, 0x54, 0xaf, 0xd7, 0x21, 0xcb,
- 0x32, 0x1e, 0x3f, 0x59, 0xf9, 0xc6, 0xbb, 0xc7, 0x36, 0xb2, 0xd9, 0xec, 0xbf, 0x89, 0x3a, 0x9d,
- 0x23, 0x55, 0xa4, 0xf2, 0xfa, 0xcd, 0xab, 0x1f, 0xc1, 0x50, 0x00, 0x99, 0x4c, 0xc6, 0x60, 0xd1,
- 0xb8, 0xb3, 0xaa, 0x15, 0x51, 0xb6, 0xb6, 0xde, 0xc3, 0xe7, 0x9f, 0x42, 0x2a, 0x95, 0x32, 0x4e,
- 0x34, 0x36, 0xee, 0x3a, 0x25, 0xa2, 0x14, 0x8b, 0x45, 0xf8, 0x03, 0x7e, 0x70, 0x57, 0x38, 0xab,
- 0x31, 0x22, 0x77, 0x67, 0x11, 0xa5, 0x54, 0x2a, 0x21, 0x3c, 0x1b, 0xae, 0xba, 0x78, 0xc7, 0x9d,
- 0x81, 0x8a, 0x28, 0x95, 0x4a, 0x05, 0xb1, 0xc5, 0x58, 0x8d, 0xac, 0xfc, 0x85, 0xc7, 0xe3, 0x39,
- 0xdb, 0xb7, 0x88, 0x77, 0xf3, 0x95, 0x4e, 0x82, 0xdc, 0xd3, 0x1c, 0x1e, 0x25, 0x1e, 0x22, 0x7a,
- 0x33, 0x7a, 0x18, 0x9a, 0x0e, 0x7e, 0xb5, 0xb0, 0xe6, 0x5f, 0x9c, 0x8d, 0x73, 0xb4, 0x89, 0x68,
- 0x1f, 0xa1, 0x57, 0x7c, 0xdb, 0x79, 0xd0, 0x88, 0xb4, 0xe3, 0xde, 0xa9, 0xc9, 0x53, 0x12, 0x5a,
- 0xea, 0x5e, 0xdf, 0x24, 0xe2, 0x8b, 0x71, 0xa4, 0x56, 0x53, 0x58, 0xcb, 0xac, 0x21, 0x97, 0xcb,
- 0xa1, 0xd9, 0x3e, 0x8e, 0xaf, 0x20, 0xda, 0xb4, 0xb4, 0xc9, 0xfe, 0x2a, 0xf2, 0xfd, 0x16, 0x49,
- 0x92, 0x84, 0xf0, 0xcc, 0x34, 0xd6, 0xd7, 0x5f, 0x2a, 0xf1, 0xe6, 0xe6, 0x06, 0xe6, 0x17, 0x04,
- 0x9c, 0xcc, 0x43, 0x73, 0x6b, 0x45, 0xa2, 0xa6, 0x79, 0x75, 0x15, 0xed, 0xee, 0xed, 0x2a, 0xe5,
- 0x9c, 0x58, 0x4a, 0x90, 0xd8, 0xab, 0x14, 0x01, 0x95, 0xcd, 0x46, 0x66, 0x94, 0x15, 0x69, 0xde,
- 0x97, 0xd5, 0xae, 0xab, 0xfb, 0x1b, 0xd9, 0xec, 0xd6, 0xef, 0xa4, 0x20, 0xbe, 0x58, 0x2c, 0x96,
- 0x8b, 0x4a, 0x6c, 0xe3, 0x42, 0xcb, 0xc9, 0x65, 0x45, 0xb4, 0xbd, 0xb3, 0x0d, 0xcf, 0x84, 0xfb,
- 0x83, 0x21, 0xe5, 0x6d, 0xb3, 0xdb, 0xe2, 0x2c, 0xcb, 0x9e, 0x6b, 0x25, 0x20, 0x77, 0x5d, 0x20,
- 0x78, 0x55, 0x39, 0x47, 0x54, 0x26, 0xde, 0x12, 0xab, 0x2c, 0x7b, 0xc9, 0x34, 0x90, 0x56, 0x9e,
- 0x5c, 0x49, 0x62, 0x41, 0x9c, 0xc7, 0xfe, 0xfe, 0x1e, 0x42, 0xd7, 0x82, 0x35, 0xd6, 0xca, 0xea,
- 0x12, 0xc9, 0x4d, 0x51, 0xa3, 0x87, 0x56, 0x2e, 0xdf, 0xbb, 0x7f, 0x17, 0x73, 0xd7, 0x23, 0x3f,
- 0x9d, 0xbc, 0x7d, 0x4e, 0xef, 0xd6, 0x09, 0xcd, 0xdf, 0x2d, 0xb1, 0x9b, 0xa8, 0x79, 0x3c, 0x24,
- 0xb5, 0x94, 0xf5, 0x89, 0x0c, 0xe6, 0x08, 0xeb, 0x8b, 0x2d, 0x65, 0x32, 0xd4, 0x80, 0x37, 0x00,
- 0x00, 0x00, 0x00, 0x49, 0x45, 0x4e, 0x44, 0xae, 0x42, 0x60, 0x82,
+ 0xce, 0x00, 0x00, 0x01, 0x6b, 0x49, 0x44, 0x41, 0x54, 0x48, 0xc7, 0x63, 0x60, 0x18

Re: [Kicad-developers] [PATCH] Measurement tool for GAL

[Fabrizio Tappero]

Hi guys,
this ruler (caliper icon) does look really good. Is there anyway to have it
available in the 2D/3D viewer when a footprint is chosen (inside the
library browser)?

It is often a good idea to have a way to measure footprint size.

cheers
Fabrizio



On Fri, Mar 10, 2017 at 5:07 PM, Maciej Sumiński 
wrote:

> Perfect, the measurement tool is already included in the master branch.
> Thanks!
>
> Cheers,
> Orson
>
> On 03/10/2017 03:07 PM, John Beard wrote:
> > Hi Orson,
> >
> > That patch looks fine. Sorry about the formatting/copyright header.
> > You are right for the by-ref and the const.
> >
> > "Measure distance" sounds fine to me.
> >
> > Cheers,
> >
> > John
> >
> > On Fri, Mar 10, 2017 at 9:59 PM, Maciej Sumiński
> >  wrote:
> >> Hi John,
> >>
> >> All I can say is: it looks really cool! I would like to merge, but
> >> before I do so, would you consider the attached fixup patch? If so, I
> >> simply update the existing set of patches and merge everything.
> >>
> >> Changes:
> >> - Changed std::vector<> to const std::vector<>& in
> >> PREVIEW::SetConstantGlyphHeight()
> >>
> >> - One of the new files had Tom as the copyright holder and incorrect
> >> date, changed to "(c) 2017 KiCad Developers"
> >>
> >> - Changed "Measure between two points" to "Measure distance between two
> >> points". I am not a native English speaker, so I need your advice here.
> >>
> >> - A few code formatting fixes.
> >>
> >> Cheers,
> >> Orson
> >>
> >> On 03/10/2017 12:18 PM, John Beard wrote:
> >>> Hi Nick,
> >>>
> >>> That's because the label formatting just uses a fixed 2 DP display for
> >>> mm (it uses 4 for inches, and 1 for degrees). It's not a perfect
> >>> solution, but it does line up nicely when the labels are on the left
> >>> of the line. Stripping trailing zeroes would make it ragged when you
> >>> zoom in a bit and get "1, 1.25, 1.5, 1.75, 2".
> >>>
> >>> Cheers,
> >>>
> >>> John
> >>>
> >>> On Fri, Mar 10, 2017 at 4:34 PM, Nick Østergaard 
> wrote:
>  It certainly looks quite nice. I have not yet tested the patch, but I
>  wonder why it shall show the integer labels here with decimals behind
>  it when they are all zero?
> 
>  2017-03-09 18:18 GMT+01:00 John Beard :
> > By the way, here's a screenshot of the ruler tool:
> >
> > Cheers,
> >
> > John
> >
> > On Fri, Mar 10, 2017 at 1:11 AM, John Beard 
> wrote:
> >> Hi,
> >>
> >> Here's a tool I'm had on my list for a while - a ruler tool.
> >>
> >> This patch set introduces a new directory, for "preview items" which
> >> are EDA_ITEMS that are only used for transient previews, such as
> >> drawing aids and selection boxes. These are located in common, so
> that
> >> they can (in theory) be used in any GAL canvas, not just
> >> Pcbnew/Modedit.
> >>
> >> There are also some functions that hopefully will be useful for
> other
> >> preview items in future in the utils file.
> >>
> >> There's an oustanding bug with the OpenGL GAL in that it cannot draw
> >> spaces in text, so there are a couple of places where it
> pre-emptively
> >> strips spaces that should be removed when that bug is fixed.
> >> (https://bugs.launchpad.net/kicad/+bug/1668455).
> >>
> >> Cheers,
> >>
> >> John
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
> >>>
> >>> ___
> >>> Mailing list: https://launchpad.net/~kicad-developers
> >>> Post to : kicad-developers@lists.launchpad.net
> >>> Unsubscribe : https://launchpad.net/~kicad-developers
> >>> More help   : https://help.launchpad.net/ListHelp
> >>>
> >>
> >>
> >> ___
> >> Mailing list: https://launchpad.net/~kicad-developers
> >> Post to : kicad-developers@lists.launchpad.net
> >> Unsubscribe : https://launchpad.net/~kicad-developers
> >> More help   : https://help.launchpad.net/ListHelp
> >>
>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] better UI experience (properties window)

[Fabrizio Tappero]

here the current look

[image: Inline image 1]

On Mon, Mar 27, 2017 at 6:17 PM, Fabrizio Tappero <
fabrizio.tapp...@gmail.com> wrote:

> Hi Wayne,
> sure no problem. Here you go.
>
> Let me know if you want something else to be changed.
>
> cheers
> Fabrizio
> PS I do not seem to understand how to change the spacing of the font size
> and X pos elements...
>
>
>
>
> On Mon, Mar 27, 2017 at 4:12 PM, Wayne Stambaugh <stambau...@gmail.com>
> wrote:
>
>> Hey Fabrizio,
>>
>> Sorry I didn't comment on this sooner but I've been busy.  I have a few
>> comments:
>>
>> "Custom Fields" should just read "Fields".  The first four fields are
>> mandatory so the word custom is misleading.
>>
>> The "Assert" button is confusing.  This button tests the component name
>> but does not updated the component.  "Verify", "Validate", or "Test"
>> would be more descriptive.
>>
>> Please change "deg" to "degrees" in the orientation control.  I'm not
>> sure "deg" is a standard abbreviation for degrees in the same way the
>> "mm" is the standard abbreviation for millimeters.
>>
>> I know this isn't specific to your changes but I would appreciate if you
>> would fix the spacing between the "Font Size", "X Position", and "Y
>> Position" controls.  It's been on my todo list for a long time so it
>> would be helpful if you could fix this.
>>
>> Thanks,
>>
>> Wayne
>>
>> On 3/27/2017 9:48 AM, Fabrizio Tappero wrote:
>> > ​Hello,
>> > This patch fixes several labeling errors with the "edit properties"
>> window.
>> > Preview of the windows that you get after the patch is this:
>> >
>> > ​Inline image 1​
>> >
>> > ​Cheers
>> > Fabrizio
>> > ​
>> >
>> >
>> >
>> >
>> >
>> > ___
>> > 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