Re: [Kicad-developers] PATCH pcbnew half-rotate actions and shortcuts

[Andrew Lutsenko]

In Pcbnew that is already the case, shift+R rotates the other way around.
Eeschema doesn't have that shortcut.

On Mon, Jun 10, 2019 at 4:15 PM Kevin Cozens  wrote:

> On 2019-06-10 6:35 p.m., Andrew Lutsenko wrote:
> > I like to keep rotation angle set to 90 because that covers 98% of cases
> and
> > is it's faster to press R two or three times instead of 4 or 6 times (I
> > frequently go the wrong way around since unfortunately R in pcbnew
> rotates
> > ccw and R in eeschema rotates cw, that is something that should be made
> > consistent).
>
> Hm... I can't say I had really noticed that the rotation directions are
> opposite between the two. After a quick test I noticed that you can rotate
> something in the default direction but if you go too far you have to hit R
> more times to "back up".
>
> It would be useful to have R to do rotations in one direction and either
> Ctrl+R or Shift+R to do rotations in the other.
>
> --
> Cheers!
>
> Kevin.
>
> http://www.ve3syb.ca/   | "Nerds make the shiny things that
> https://www.patreon.com/KevinCozens | distract the mouth-breathers, and
>  | that's why we're powerful"
> Owner of Elecraft K2 #2172  |
> #include  | --Chris Hardwick
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://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 pcbnew half-rotate actions and shortcuts

[Kevin Cozens]

On 2019-06-10 6:35 p.m., Andrew Lutsenko wrote:
I like to keep rotation angle set to 90 because that covers 98% of cases and 
is it's faster to press R two or three times instead of 4 or 6 times (I 
frequently go the wrong way around since unfortunately R in pcbnew rotates 
ccw and R in eeschema rotates cw, that is something that should be made 
consistent).


Hm... I can't say I had really noticed that the rotation directions are 
opposite between the two. After a quick test I noticed that you can rotate 
something in the default direction but if you go too far you have to hit R 
more times to "back up".


It would be useful to have R to do rotations in one direction and either 
Ctrl+R or Shift+R to do rotations in the other.


--
Cheers!

Kevin.

http://www.ve3syb.ca/   | "Nerds make the shiny things that
https://www.patreon.com/KevinCozens | distract the mouth-breathers, and
| that's why we're powerful"
Owner of Elecraft K2 #2172  |
#include  | --Chris Hardwick

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

Re: [Kicad-developers] [PATCH] Crash Reporter

[Wayne Stambaugh]

Did you test the latest commit 2745a95b6b02c3864d6594503cc21619691cdd94?

On 6/10/19 6:02 PM, Nick Østergaard wrote:
> It didn't seem to work for the use case I described on windows last week.
> 
> On Mon, 10 Jun 2019 at 23:51, Wayne Stambaugh  wrote:
>>
>> Hey Tom,
>>
>> On 6/4/2019 12:31 PM, Tomasz Wlostowski wrote:
>>> On 04/06/2019 17:11, Tomasz Wlostowski wrote:
>>>
 Hi Wayne,

 It looks like I screwed up the exception handler under KiCad windows
 shell. Will fix soon.
>>>
>>> Fixed in my github branch.
>>>
>>> T.
>>>
>>
>> I just finished testing this on windows (32 and 64 bit) and it appears
>> to work fine when launched from KiCad and stand alone mode.  I only
>> tested it using your provided force crash menu entry so I don't know if
>> it will work with a crash other than that.  Too bad the gcc windows
>> build crash report doesn't have a stack trace.  Maybe MSVC builds would
>> have more debug info.  It looks like it's ready to be merged for further
>> testing.
>>
>> Cheers,
>>
>> Wayne

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

Re: [Kicad-developers] PATCH pcbnew half-rotate actions and shortcuts

[Andrew Lutsenko]

Wayne,

I like to keep rotation angle set to 90 because that covers 98% of cases
and is it's faster to press R two or three times instead of 4 or 6 times (I
frequently go the wrong way around since unfortunately R in pcbnew rotates
ccw and R in eeschema rotates cw, that is something that should be made
consistent). But for the remaining 2% of cases when 45 degree angle is
preferable achieving that angle involves multiple clicks. Layout process
(at least for me) is very iterative and I often need to try multiple
positions of footprints to get best results. Going back and forth between
45 and 90 angle setting gets old fast.

If adding 2 new default shortcuts is not ideal maybe there is a way to have
these as actions with no shortcuts and let the user choose if they want to
use them and assign any shortcut they want. Is that technically supported
with current hotkey framework?

On Mon, Jun 10, 2019 at 1:15 PM Wayne Stambaugh 
wrote:

> Andrew,
>
> I'm not sure why you need a half step rotation when you can just change
> the rotation angle to 45°.  I'm not opposed to this change but given
> that we are running out of hotkeys, I don't know if this is the best use
> of them.
>
> Cheers,
>
> Wayne
>
> On 6/9/2019 8:40 PM, Andrew Lutsenko wrote:
> > I could replace diff pair dimensions shortcut with something else if
> > that is fine by devs, Ctrl+Shift+I is available.
> >
> > On Sat, Jun 8, 2019 at 3:49 AM Ian McInerney  > > wrote:
> >
> > Just a note, the hotkey ctrl+shift+R is already assigned to
> > "Differential Pair Dimensions" by default so this would introduce a
> > duplicate hotkey conflict. It probably makes sense for this action
> > to be ctrl+shift+R, but that means that the other needs to be
> changed.
> >
> > Also, as a side note to the lead devs, is it still necessary to have
> > the hotkeys say (Modern Toolset only) in the master branch?
> >
> > -Ian
> >
> > On Sat, Jun 8, 2019 at 8:22 AM Andrew Lutsenko  > > wrote:
> >
> > Hi all,
> >
> > I frequently find that I need to rotate a footprint or a few by
> > 45 degrees. To do that I either have to edit it's properties
> > (works if it's just one but slow) or change pcbnew preferences
> > (very slow).
> > I thought I'd add a quick shortcut to rotate selected items by
> > half of the configured rotation angle and learn a bit of tool
> > related code in the process. Please see attached patch for that.
> >
> > I suspect the way I handled passing double parameter to the
> > action is not ideal but it's impossible to have a pointer to
> > constant literal without storing it in a variable (to my
> > knowledge). I'm open to suggestions on how to clean up that
> > part, maybe move the constants somewhere?
> >
> > Regards,
> > Andrew
> > ___
> > Mailing list: https://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] Crash Reporter

[Nick Østergaard]

It didn't seem to work for the use case I described on windows last week.

On Mon, 10 Jun 2019 at 23:51, Wayne Stambaugh  wrote:
>
> Hey Tom,
>
> On 6/4/2019 12:31 PM, Tomasz Wlostowski wrote:
> > On 04/06/2019 17:11, Tomasz Wlostowski wrote:
> >
> >> Hi Wayne,
> >>
> >> It looks like I screwed up the exception handler under KiCad windows
> >> shell. Will fix soon.
> >
> > Fixed in my github branch.
> >
> > T.
> >
>
> I just finished testing this on windows (32 and 64 bit) and it appears
> to work fine when launched from KiCad and stand alone mode.  I only
> tested it using your provided force crash menu entry so I don't know if
> it will work with a crash other than that.  Too bad the gcc windows
> build crash report doesn't have a stack trace.  Maybe MSVC builds would
> have more debug info.  It looks like it's ready to be merged for further
> testing.
>
> Cheers,
>
> Wayne

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

Re: [Kicad-developers] [PATCH] Crash Reporter

[Wayne Stambaugh]

Hey Tom,

On 6/4/2019 12:31 PM, Tomasz Wlostowski wrote:
> On 04/06/2019 17:11, Tomasz Wlostowski wrote:
> 
>> Hi Wayne,
>>
>> It looks like I screwed up the exception handler under KiCad windows
>> shell. Will fix soon.
> 
> Fixed in my github branch.
> 
> T.
> 

I just finished testing this on windows (32 and 64 bit) and it appears
to work fine when launched from KiCad and stand alone mode.  I only
tested it using your provided force crash menu entry so I don't know if
it will work with a crash other than that.  Too bad the gcc windows
build crash report doesn't have a stack trace.  Maybe MSVC builds would
have more debug info.  It looks like it's ready to be merged for further
testing.

Cheers,

Wayne

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

Re: [Kicad-developers] PATCH pcbnew half-rotate actions and shortcuts

[Wayne Stambaugh]

Andrew,

I'm not sure why you need a half step rotation when you can just change
the rotation angle to 45°.  I'm not opposed to this change but given
that we are running out of hotkeys, I don't know if this is the best use
of them.

Cheers,

Wayne

On 6/9/2019 8:40 PM, Andrew Lutsenko wrote:
> I could replace diff pair dimensions shortcut with something else if
> that is fine by devs, Ctrl+Shift+I is available.
> 
> On Sat, Jun 8, 2019 at 3:49 AM Ian McInerney  > wrote:
> 
> Just a note, the hotkey ctrl+shift+R is already assigned to
> "Differential Pair Dimensions" by default so this would introduce a
> duplicate hotkey conflict. It probably makes sense for this action
> to be ctrl+shift+R, but that means that the other needs to be changed.
> 
> Also, as a side note to the lead devs, is it still necessary to have
> the hotkeys say (Modern Toolset only) in the master branch?
> 
> -Ian
> 
> On Sat, Jun 8, 2019 at 8:22 AM Andrew Lutsenko  > wrote:
> 
> Hi all,
> 
> I frequently find that I need to rotate a footprint or a few by
> 45 degrees. To do that I either have to edit it's properties
> (works if it's just one but slow) or change pcbnew preferences
> (very slow).
> I thought I'd add a quick shortcut to rotate selected items by
> half of the configured rotation angle and learn a bit of tool
> related code in the process. Please see attached patch for that.
> 
> I suspect the way I handled passing double parameter to the
> action is not ideal but it's impossible to have a pointer to
> constant literal without storing it in a variable (to my
> knowledge). I'm open to suggestions on how to clean up that
> part, maybe move the constants somewhere?
> 
> Regards,
> Andrew
> ___
> Mailing list: https://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] New package for macOS 5.1.2 stable including ngspice-30 ?

[Carsten Schoenert]

Hello Wayne,

Am 10.06.19 um 20:15 schrieb Wayne Stambaugh:
> We cannot make ngspice 30 the minimum version.  There are far too many
> linux distros where 30 is not available yet.  Please keep in mind,
> Debian stable and the latest Ubuntu LTS version are the benchmarks for
> dependency package versions.  I'm fine with packaging macos and windows
> with 30.

current Debian stable (Stretch) has KiCad version 4.0.5+dfsg1-4 in the
archive and no package libngspice0 at all (not even in non-free) so
there is nothing to take care on here.

The current Ubuntu LTS release 18.04 (Bionic Beaver) has KiCad version
4.0.7+dfsg1-1ubuntu2 and libngspice0 version 27-1.
At least the KiCad version is long long outdated. So also not really
relevant too.

But all relevant current Debian releases are providing a recent KiCad
version and also libngspice0 in version 30.2-1 (from unstable to
stretch-backports). This is also available in all Downstream of Debian
means also in Ubuntu >= 'Cosmic Cuttlefish' are providing KiCad
5.0.0+dfsg1-2, but also libngspice0 in version 27. Updates wont happen.

But Jean-Samuel Reynaud is providing actual versions of KiCad and also
the depending libngspice0 package and they even work in the always
outdated Linux Mint distro. So for me your requirements you like to set
are fulfilled.

And normally the application is defining the requirements. Simulations
seems to be for some users an critical option. So if the maintainers of
ngspice hardly suggesting to use the most recent version of ngspice in
recent KiCad version I would strongly consider to increase this build
dependency.

In the end it's up to the KiCad maintainers to define the requirements
for KiCad. It was a long road to get ngspice into Debian main but in the
end it happened, big thanks to Holger again btw! So Debian has no
problem to provide KiCad with a depending libngspice0 library >= 30.2.

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

Re: [Kicad-developers] 5.1.3 stable release

[Wayne Stambaugh]

Ian,

If you can get it done by the freeze, then I don't have any issue with
this.  Otherwise, it will have to wait until 5.1.4.

Cheers,

Wayne

On 6/9/2019 7:39 PM, Ian McInerney wrote:
> To add on to this, the hotkey validation architecture that I have been
> building up to take care of the many issues surrounding the
> duplicate/invalid hotkeys (and also the fact that they can exist due to
> a user's hotkey settings from prior versions) will require new strings
> since I have error prompts. If this is something that should go in
> 5.1.3, then string changes will need to be allowed.
> 
> I hope to have a patch set based on master put together in the next few
> days for people to test, and if you want to include it in 5.1.3 I can
> trim down the patch set to work on the 5.1 (I believe that some changes
> may not cherrypick easily from master to 5.1).
> 
> -Ian
> 
> On Sun, Jun 9, 2019 at 3:27 PM Seth Hillbrand  > wrote:
> 
> On 2019-05-22 16:37, Wayne Stambaugh wrote:
> > We are getting a decent set of bug fixes in the 5.1 branch so we
> should
> > seriously start thinking about a 5.1.3 stable release by the end of
> > June.  What I would like to see is push to fix some of the outstanding
> > 5.1 bugs[1] and then do a string freeze in the middle of June.  If you
> > see a bug that is code that you are familiar with, please consider
> > fixing it.  There will be plenty of time to work on v6.  Thanks again
> > everyone for your continued efforts.
> 
> Hi Wayne-
> 
> Are we considering string changes for 5.1.3?  I had thought our policy
> was no string changes for the minor bug fix releases.  If we do have
> string changes, I'll push a couple additional mods to the 5.1.3 branch
> that clarify actions.
> 
> Could we also get a 5.1.4 tag for bugs that are lower priority/harder
> implementations?
> 
> -Seth
> 
> ___
> Mailing list: https://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] Latest info on copper zones using solid polygons without outline thickness.

[jp charras]

Le 10/06/2019 à 03:40, lê văn lập a écrit :
> Dear all DEV !
> I am currently designing pcb using zuken's cr5000 software, I would like
> to contribute to kicad's development, this is gerber when exported from
> cr5000, they use line and arc to create copper zones, hopefully this
> will is a good idea for us
> 

Alas! If your are talking about painting zones by segments, like the
filled (painted) zones shown by your images, this is a very bad idea:

* This is inefficient because it can create *a lot* of segments when the
minimal thickness is low (solid polygons are much more efficient).

* This is prohibited by Gerber file format: see chapter 7.7 of the
current gerber file format specifications (freely available from Ucamco):
Here is what this doc say:

"Painted areas and pads are not suited for PCB fabrication. Sending
files with painted to a PCB fabricator is quite disrespectful."

* For these reasons, this feature was removed from Kicad code some time ago.

If cr5000 software uses only painted zones, this is really a bad idea.

Now adding thick arcs in zone outlines to replace rough arc
approximation for a better shape is an other problem:
It could be a really good idea.
However I am guessing this is not so easy to code.

-- 
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] New package for macOS 5.1.2 stable including ngspice-30 ?

[Wayne Stambaugh]

On 6/9/2019 12:28 PM, Carsten Schoenert wrote:
> Hi
> 
> Am 09.06.19 um 09:03 schrieb Holger Vogt:
>> Hi Adam,
>>
>> would you mind creating a new package for macOS 5.1.2 stable replacing 
>> the outdated libngspice 26 by the recent libngspice version 30?
>>
>> And then use libngspice 30 also for the nightlies?
>>
>> Nick has done this successfully for Windows. All tests have been o.k..
>>
>> The users may benefit from the ngspice patches since version 26 (see 
>> https://bugs.launchpad.net/kicad/+bug/1821520) towards better usage 
>> during pcb design.
> 
> it should be possible to check the version of the ngspice library while
> the cmake configure run and error out if the version is lower than 30.
> I'm not an CMake expert but some version check should be possible here too.
> 

We cannot make ngspice 30 the minimum version.  There are far too many
linux distros where 30 is not available yet.  Please keep in mind,
Debian stable and the latest Ubuntu LTS version are the benchmarks for
dependency package versions.  I'm fine with packaging macos and windows
with 30.

Cheers,

Wayne

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

Re: [Kicad-developers] 5.1.3 stable release

[Wayne Stambaugh]

On 6/9/2019 10:27 AM, Seth Hillbrand wrote:
> On 2019-05-22 16:37, Wayne Stambaugh wrote:
>> We are getting a decent set of bug fixes in the 5.1 branch so we should
>> seriously start thinking about a 5.1.3 stable release by the end of
>> June.  What I would like to see is push to fix some of the outstanding
>> 5.1 bugs[1] and then do a string freeze in the middle of June.  If you
>> see a bug that is code that you are familiar with, please consider
>> fixing it.  There will be plenty of time to work on v6.  Thanks again
>> everyone for your continued efforts.
> 
> Hi Wayne-
> 
> Are we considering string changes for 5.1.3?  I had thought our policy
> was no string changes for the minor bug fix releases.  If we do have
> string changes, I'll push a couple additional mods to the 5.1.3 branch
> that clarify actions.
> 
> Could we also get a 5.1.4 tag for bugs that are lower priority/harder
> implementations?
> 
> -Seth

Seth,

We can always commit string changes to any branch until a string freeze
is implemented.  I'm going to add a new message dialog string to bug fix
I'm working on to the 5.1 branch in the next day or so.  I will probably
implement the string freeze either 6/14 or 6/16 so you still have time
to get string changes into the 5.1 branch.

Wayne

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

Re: [Kicad-developers] [PATCH] Show the current grid setting.

[Steven A. Falco]

I've rebased my patch to show the current grid setting, and I've generated it 
both for the master branch and the 5.1 branch.  The attached patches were 
generated via git format-patch.

Please consider these patches for inclusion into KiCad, and please let me know 
if there is anything that I should change to make them acceptable.

Thanks,
Steve
>From 86c241349bfabfd4ff20ba4064ef0870243e1471 Mon Sep 17 00:00:00 2001
From: "Steven A. Falco" 
Date: Mon, 10 Jun 2019 10:16:14 -0400
Subject: [PATCH] Show the current grid setting.

---
 common/legacy_gal/eda_draw_frame.cpp  | 38 --
 common/legacy_wx/eda_draw_frame.cpp   | 38 --
 eeschema/sch_base_frame.cpp   |  3 ++
 gerbview/gerbview_frame.cpp   | 38 ++
 gerbview/gerbview_frame.h |  7 
 include/draw_frame.h  |  5 +++
 include/pcb_base_frame.h  |  7 
 pagelayout_editor/pl_editor_frame.cpp | 46 ---
 pagelayout_editor/pl_editor_frame.h   |  2 ++
 pcbnew/pcb_base_frame.cpp | 38 ++
 10 files changed, 213 insertions(+), 9 deletions(-)

diff --git a/common/legacy_gal/eda_draw_frame.cpp b/common/legacy_gal/eda_draw_frame.cpp
index 058df54f8..877d16e10 100644
--- a/common/legacy_gal/eda_draw_frame.cpp
+++ b/common/legacy_gal/eda_draw_frame.cpp
@@ -169,7 +169,7 @@ EDA_DRAW_FRAME::EDA_DRAW_FRAME( KIWAY* aKiway, wxWindow* aParent,
 
 m_auimgr.SetFlags(wxAUI_MGR_DEFAULT);
 
-CreateStatusBar( 6 );
+CreateStatusBar( 7 );
 
 // set the size of the status bar subwindows:
 
@@ -192,6 +192,9 @@ EDA_DRAW_FRAME::EDA_DRAW_FRAME( KIWAY* aKiway, wxWindow* aParent,
 // delta distances
 GetTextSize( wxT( "dx 0234.567890  dx 0234.567890  d 0234.567890" ), stsbar ).x + 10,
 
+// grid size
+GetTextSize( wxT( "grid X 0234.567890  Y 0234.567890" ), stsbar ).x + 10,
+
 // units display, Inches is bigger than mm
 GetTextSize( _( "Inches" ), stsbar ).x + 10,
 
@@ -614,6 +617,37 @@ void EDA_DRAW_FRAME::DisplayToolMsg( const wxString& msg )
 }
 
 
+/*
+ * Display the grid status.
+ */
+void EDA_DRAW_FRAME::DisplayGridMsg()
+{
+wxString line;
+wxString gridformatter;
+
+switch( m_UserUnits )
+{
+case INCHES:
+gridformatter = "grid %.3f";
+break;
+
+case MILLIMETRES:
+gridformatter = "grid %.4f";
+break;
+
+default:
+gridformatter = "grid %f";
+break;
+}
+
+wxRealPoint curr_grid_size = GetScreen()->GetGridSize();
+double grid = To_User_Unit( m_UserUnits, curr_grid_size.x );
+line.Printf( gridformatter, grid );
+
+SetStatusText( line, 4 );
+}
+
+
 void EDA_DRAW_FRAME::DisplayUnitsMsg()
 {
 wxString msg;
@@ -625,7 +659,7 @@ void EDA_DRAW_FRAME::DisplayUnitsMsg()
 default:  msg = _( "Units" );  break;
 }
 
-SetStatusText( msg, 4 );
+SetStatusText( msg, 5 );
 }
 
 
diff --git a/common/legacy_wx/eda_draw_frame.cpp b/common/legacy_wx/eda_draw_frame.cpp
index 3871cfb26..e54861459 100644
--- a/common/legacy_wx/eda_draw_frame.cpp
+++ b/common/legacy_wx/eda_draw_frame.cpp
@@ -172,7 +172,7 @@ EDA_DRAW_FRAME::EDA_DRAW_FRAME( KIWAY* aKiway, wxWindow* aParent,
 
 m_auimgr.SetFlags(wxAUI_MGR_DEFAULT);
 
-CreateStatusBar( 6 );
+CreateStatusBar( 7 );
 
 // set the size of the status bar subwindows:
 
@@ -195,6 +195,9 @@ EDA_DRAW_FRAME::EDA_DRAW_FRAME( KIWAY* aKiway, wxWindow* aParent,
 // delta distances
 GetTextSize( wxT( "dx 0234.567890  dx 0234.567890  d 0234.567890" ), stsbar ).x + 10,
 
+// grid size
+GetTextSize( wxT( "grid X 0234.567890  Y 0234.567890" ), stsbar ).x + 10,
+
 // units display, Inches is bigger than mm
 GetTextSize( _( "Inches" ), stsbar ).x + 10,
 
@@ -622,6 +625,37 @@ void EDA_DRAW_FRAME::DisplayToolMsg( const wxString& msg )
 }
 
 
+/*
+ * Display the grid status.
+ */
+void EDA_DRAW_FRAME::DisplayGridMsg()
+{
+wxString line;
+wxString gridformatter;
+
+switch( m_UserUnits )
+{
+case INCHES:
+gridformatter = "grid %.3f";
+break;
+
+case MILLIMETRES:
+gridformatter = "grid %.4f";
+break;
+
+default:
+gridformatter = "grid %f";
+break;
+}
+
+wxRealPoint curr_grid_size = GetScreen()->GetGridSize();
+double grid = To_User_Unit( m_UserUnits, curr_grid_size.x );
+line.Printf( gridformatter, grid );
+
+SetStatusText( line, 4 );
+}
+
+
 void EDA_DRAW_FRAME::DisplayUnitsMsg()
 {
 wxString msg;
@@ -641,7 +675,7 @@ void EDA_DRAW_FRAME::DisplayUnitsMsg()
 break;
 }
 
-SetStatusText( msg, 4 );
+SetStatusText( msg, 5 );
 }
 
 
diff --git a/eeschema/sch_base_frame.cpp b/eeschema/sch_base_frame.cpp
index 741ccaa59..923d4046d 100644
--- a/eeschema/sch_base_frame.cpp
+++ b/eeschema/sch_base_frame.cpp
@@ -284,6 +284,9 @@ void SCH_BASE_FRAME::UpdateSta

Re: [Kicad-developers] New package for macOS 5.1.2 stable including ngspice-30 ?

[Nick Østergaard]

I made it a dash 2 pkgrel for windows, I suggest doing the same for the
macos package.

man. 10. jun. 2019 10.51 skrev Carsten Schoenert :

> Hi,
>
> Am 10.06.19 um 01:46 schrieb Ian McInerney:
> > Is there a reason that pushing a change like this can't wait until the
> > 5.1.3 release?
>
> that's up to the packagers in my eyes and the severity of the issue. As
> far I read the reason behind the request from Holger it's an important
> enough update to provide an updated version 5.1.2 for macOS.
>
> > Wayne had mentioned wanting to try to get it out the door in
> > early July, which wouldn't be that far off. That would also give more
> > uniformity in its roll out across the various platforms, and allow for
> > easier identification of if a user is using the ngsice-30 version when
> bug
> > reports are filed (since apparently the version information doesn't seem
> to
> > contain that).
>
> There will be always differences between Windows, Linux and macOS that
> can't be completely wiped out. And the required and uniformed versions
> of the build dependencies are only solvable by the configure settings.
>
> > On Sun, Jun 9, 2019 at 10:01 PM Adam Wolf  >
> > wrote:
> >
> >> How about making 5.1.2-1 or -2 or whatever.  I don't like replacing
> >> packages that have been released.
>
> Yes of course, only increase the packaging version.
>
> --
> 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

Re: [Kicad-developers] New package for macOS 5.1.2 stable including ngspice-30 ?

[Carsten Schoenert]

Hi,

Am 10.06.19 um 01:46 schrieb Ian McInerney:
> Is there a reason that pushing a change like this can't wait until the
> 5.1.3 release?

that's up to the packagers in my eyes and the severity of the issue. As
far I read the reason behind the request from Holger it's an important
enough update to provide an updated version 5.1.2 for macOS.

> Wayne had mentioned wanting to try to get it out the door in
> early July, which wouldn't be that far off. That would also give more
> uniformity in its roll out across the various platforms, and allow for
> easier identification of if a user is using the ngsice-30 version when bug
> reports are filed (since apparently the version information doesn't seem to
> contain that).

There will be always differences between Windows, Linux and macOS that
can't be completely wiped out. And the required and uniformed versions
of the build dependencies are only solvable by the configure settings.

> On Sun, Jun 9, 2019 at 10:01 PM Adam Wolf 
> wrote:
> 
>> How about making 5.1.2-1 or -2 or whatever.  I don't like replacing
>> packages that have been released.

Yes of course, only increase the packaging version.

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