[Kicad-developers] r6791 also to stable with versioning patch

Simon Wells found a build error that happens with the versioning patch on some compiler/platform/wx combinations - rev 6791 needs to be applied to stable along with the original 6788 when we merge that. -- Chris ___ Mailing list:

Re: [Kicad-developers] What are dx and dy?

Perfect, this would have helped my past self immensely :) Thanks. On Tue, May 10, 2016 at 4:16 PM, Martin d'Allens wrote: > I think that the current ruler feature works great. Unfortunately > people don't discover it easily. > There are frequent questions on the user

Re: [Kicad-developers] What are dx and dy?

Ooh, I like! I'll test and merge this tonight if nobody else complains. I have no problem with showing a hint when no origin has been set. Note for the future, use _() instead of wxT() to make a string that can be translated - and a couple bits don't follow the defined coding style. I'll just fix

Re: [Kicad-developers] What are dx and dy?

I think that the current ruler feature works great. Unfortunately people don't discover it easily. There are frequent questions on the user forum that we just answer by mentioning the space hotkey and how it works. Here is a patch that could solve this problem:

[Kicad-developers] Dump zone geometry to files when filling

In 6790 I removed the user option to "Dump zone geometry to files when filling"; Tom indicated that this was no longer necessary and could be removed. I left the *code*, however. I took the global flag out of pcbnew.h and replaced it with a static const bool in the file where the actual dumping

Re: [Kicad-developers] [PATCH] pcbnew legacy: remove option to hide via drill

Pushed in 6789. On Tue, May 10, 2016 at 02:19:11PM -0400, Wayne Stambaugh wrote: > I agree. If there is a hole, then it should be displayed. The only > reason not to display it may be for rendering speed issues but I would > think that would not be a significant issue these days. Even my slow

Re: [Kicad-developers] mode openGL issues after latest updates

There was another fix for pcbnew crashing with OpenGL GAL applied in revision 6781, so there is a chance that your problem is already resolved. I will be grateful for feedback. Regards, Orson On 05/10/2016 09:07 PM, easyw wrote: > Hi, >> Are there any particular steps I need to perform? Open

Re: [Kicad-developers] Maximum undo items

Actually, you might be onto something. Of course you can FRO with the environment vars ;D but perhaps we could leave it an option to be set in the configuration manually for the one time in 2018 JP wants to restrict this for debugging... On Wed, May 11, 2016 at 06:58:58AM +1200, Simon Wells

Re: [Kicad-developers] Maximum undo items

The trolling is funnier in IRC ;) On Wed, May 11, 2016 at 06:58:58AM +1200, Simon Wells wrote: > or just make it so it always works but is either a command line > option/env variable or manually editing the configuration file > > On Wed, May 11, 2016 at 6:56 AM, Chris Pavlina

Re: [Kicad-developers] mode openGL issues after latest updates

Hi, Are there any particular steps I need to perform? Open pcbnew empty? Load a specific board? Use the launcher? I tried just opening pcbnew empty or with a board but when I switch from legacy to OpenGl it crashes...The same from the kicad launcher... I tested till rev 6776 ... I'm going to

Re: [Kicad-developers] Maximum undo items

or just make it so it always works but is either a command line option/env variable or manually editing the configuration file On Wed, May 11, 2016 at 6:56 AM, Chris Pavlina wrote: > Urgh, do we really need to keep features that a developer may need at some > point in

Re: [Kicad-developers] Maximum undo items

Urgh, do we really need to keep features that a developer may need at some point in the future in the UI? This is something that one person may need once sometime next year. Can't we make this a #define or something instead? We really shouldn't be cluttering everyone's UI with developer-only

Re: [Kicad-developers] Maximum undo items

Le 10/05/2016 à 20:41, Chris Pavlina a écrit : > Back in August (git:aaadb40), I made the undo history infinite in pcbnew, > eeschema, modedit, and libedit. Wayne wanted this to remain an option, in case > of issues with the memory consumption of the undo stack. Currently, if you set > "Maximum

[Kicad-developers] Maximum undo items

Back in August (git:aaadb40), I made the undo history infinite in pcbnew, eeschema, modedit, and libedit. Wayne wanted this to remain an option, in case of issues with the memory consumption of the undo stack. Currently, if you set "Maximum undo items" to zero, you get infinite history. I also

[Kicad-developers] wxwidgets regex library type dependency - Remove it?

Hi, I'm packaging KiCad for GNU Guix. In the course of doing that I found that KiCad depends on specific wxwidget flags, i.e. on how exactly wxwidgets was built. (I mean that I get a KiCad compilation error complaining about "wxRE_ADVANCED" - reason see below). We can work around that in GNU

Re: [Kicad-developers] New pcbnew features and versioning

On 5/10/2016 2:17 PM, Chris Pavlina wrote: > I don't think there is anything that can be done about that. If the file was > made by a later version, there's no way I can think of to distinguish a true > error from a new feature. Personally, I think the combination of (later > version > + new

Re: [Kicad-developers] [PATCH] pcbnew legacy: remove option to hide via drill

I agree. If there is a hole, then it should be displayed. The only reason not to display it may be for rendering speed issues but I would think that would not be a significant issue these days. Even my slow laptop renders the video demo comfortably in the legacy canvas. On 5/10/2016 2:15 PM,

Re: [Kicad-developers] New pcbnew features and versioning

I don't think there is anything that can be done about that. If the file was made by a later version, there's no way I can think of to distinguish a true error from a new feature. Personally, I think the combination of (later version + new feature) is much more likely than (later version + file

Re: [Kicad-developers] [PATCH] pcbnew legacy: remove option to hide via drill

We do always show either the correct diameter or nothing at all. Thankfully never a *different* diameter, or else I'd have raised a stink long ago! ;) What I'd like to change is that it's even an option to show nothing at all. If there's a hole through the board, it should be shown, period. On

Re: [Kicad-developers] [PATCH] pcbnew legacy: remove option to hide via drill

On Tue, May 10, 2016 at 08:02:35PM +0200, jp charras wrote: > Le 10/05/2016 à 18:28, Chris Pavlina a écrit : > > [snip] > > This is an opinion, which can be discussed. > > AFAIK, since a long time the default via hole diameter does not exist. You > can change the netclass > drill diameter

Re: [Kicad-developers] [PATCH] pcbnew legacy: remove option to hide via drill

On 5/10/2016 2:02 PM, jp charras wrote: > Le 10/05/2016 à 18:28, Chris Pavlina a écrit : >> Part one of many to clean up pcbnew preferences and unify legacy vs GAL >> options. >> >> This patch removes the option in legacy to hide via drills. As Tom >> indicated[1], the layout should as much as

Re: [Kicad-developers] New pcbnew features and versioning

Chris, I finally got a chance to test this patch. I couldn't find any issues with it. The only thing that could be confusing to the user is if the board parser fails for a legitimate error, recommending an upgrade may be misleading. I'm not sure there is much you can do about that. If it's

Re: [Kicad-developers] [PATCH] pcbnew legacy: remove option to hide via drill

Le 10/05/2016 à 18:28, Chris Pavlina a écrit : > Part one of many to clean up pcbnew preferences and unify legacy vs GAL > options. > > This patch removes the option in legacy to hide via drills. As Tom > indicated[1], the layout should as much as possible be WYSIWYG, and if a via > has a drill

[Kicad-developers] [PATCH] pcbnew legacy: remove option to hide via drill

Part one of many to clean up pcbnew preferences and unify legacy vs GAL options. This patch removes the option in legacy to hide via drills. As Tom indicated[1], the layout should as much as possible be WYSIWYG, and if a via has a drill it should show it. Therefore we chose to remove this option

Re: [Kicad-developers] What are dx and dy?

Hello. I think he want to see additional fields with delta_x and delta_y (and maybe distance) relative of latest start point of drawing graphic primitive (like line) but he doesn't want to reset the user origin. >Вторник, 10 мая 2016, 17:25 +03:00 от Wayne Stambaugh : >

Re: [Kicad-developers] mode openGL issues after latest updates

Do you get any error message? I am trying hard to reproduce the problem, but none of the available PCs expose the bug. I have tried Win7 & Win10 64-bit. Both build with msys2/gcc 5.3, but I still cannot crash pcbnew. Are there any particular steps I need to perform? Open pcbnew empty? Load a

Re: [Kicad-developers] What are dx and dy?

Well, I've stared at that dx and dy for countless sessions of pcbnew, trying to figure out how to make it useful based on looking at the UI. I couldn't. What if we replace the (IMO useless) mimicking of X and Y with a message to press 'space' to measure? Otherwise, there is no UI hint as to how

Re: [Kicad-developers] What are dx and dy?

I don't like the idea of a "smart" origin either. When I set the user origin, it's typically to place multiple objects on a given x or y coordinate. I don't want kicad thinking it's smarter than I am and reset the user origin relative to where I started drawing some object. To me that would be

Re: [Kicad-developers] What are dx and dy?

I can see how this is useful once you know to press space bar. But what if it assumes an implicit origin in the following case: - no explicit origin has been set - the user is drawing a shape On May 10, 2016 12:39 AM, "Nick Østergaard" wrote: >

Re: [Kicad-developers] What are dx and dy?

Because that's only useful once in the entire session using pcbnew. Once you've set an origin once you can't use that anymore. What's the point? I quite like the simplicity of the tool as it is. It's a ruler that you can move around. Why do you need a ruler that's smart and picks itself up once

[Kicad-developers] crash on kicad latest dev version, what can I do now?

I just recompiled the sources like "The same thing we do every night, Pinky " Application: kicad Version: (2016-05-09 BZR 6783)-product, release build Libraries: wxWidgets 3.0.2 libcurl/7.35.0 OpenSSL/1.0.1f zlib/1.2.8 libidn/1.28 librtmp/2.3 Platform: Linux 3.13.0-85-generic x86_64,