Re: [Kicad-developers] UI improvements

We really need an official repository of "Wayne puts his foot down" decisions for looking up ;) On Thu, Mar 23, 2017 at 10:03:37PM -0400, Tiger12506 wrote: > I swear the dev the list has completely and utterly hashed this out before. > Maybe about when the footprint table came into effect. I

Re: [Kicad-developers] UI improvements

I swear the dev the list has completely and utterly hashed this out before. Maybe about when the footprint table came into effect. I mean, I know you can decide to change things now, but it was long and bitter and there was a decision made, I'm sure of it. On 3/23/2017 8:34 AM, Wayne

Re: [Kicad-developers] OpenGL fallback and video compat test

Should. I'm not sure how exactly it behaves, so it may be necessary to add a specific check for them in the test binary. But I can't see why it wouldn't work. Does anyone here have this chipset to test? On Fri, Mar 24, 2017 at 01:55:25PM +1300, Simon Wells wrote: > would this work on the useless

Re: [Kicad-developers] OpenGL fallback and video compat test

would this work on the useless 945 chipset or whichever one it is that reports having hte right opengl features but does not? On 24 March 2017 at 13:39, Chris Pavlina wrote: > Yeah, good autosave helps. > > To be fair this is a bit offtopic - what I want really is a

Re: [Kicad-developers] OpenGL fallback and video compat test

Yeah, good autosave helps. To be fair this is a bit offtopic - what I want really is a properly functioning way to check if OpenGL works, not a way to clean up if it doesn't. The fact that that involves containing an unavoidable crash in a child process is a bit of an implementation detail IMO ;)

Re: [Kicad-developers] OpenGL fallback and video compat test

On Thu, Mar 23, 2017 at 8:30 PM, Chris Pavlina wrote: > Remember, once a crash has actually > occurred in the main program you're already past the point of no return > for possible data loss. > > One alternative approach which can work quite well (Mentor Graphics does

Re: [Kicad-developers] OpenGL fallback and video compat test

On Thu, Mar 23, 2017 at 08:25:27PM -0400, Jon Evans wrote: > That sounds like a reasonable approach if the lag time of running the test > is low enough to not be a nuisance. Are these crashes you speak of ones > that appear when the user first tries to switch to OpenGL, or later? Ideally, I'd

Re: [Kicad-developers] OpenGL fallback and video compat test

That sounds like a reasonable approach if the lag time of running the test is low enough to not be a nuisance. Are these crashes you speak of ones that appear when the user first tries to switch to OpenGL, or later? One alternative approach (that might actually work well alongside yours) is a

[Kicad-developers] OpenGL fallback and video compat test

Hi, I've been thinking about my intent to make KiCad fall back cleanly to Cairo when OpenGL isn't available. From what I can see, there are certain situations where trying to use OpenGL causes crashes that appear very hard to prevent. I really want to do something about this - they're hard to

Re: [Kicad-developers] [PATCH] Add footprint select dropdown to component chooser, serious refactoring

Oops, I guess I didn't pay enough attention updating the patch. :\ On Thu, Mar 23, 2017 at 07:02:59PM -0400, Wayne Stambaugh wrote: > Chris, > > I got the following build error with the latest patch on windows > (msys2/mingw32): > >

Re: [Kicad-developers] [PATCH] Add footprint select dropdown to component chooser, serious refactoring

Chris, I got the following build error with the latest patch on windows (msys2/mingw32): E:/msys64/home/Wayne/src/kicad-lp-clone/eeschema/dialogs/dialog_choose_component.h:104:5: error: 'DIALOG_CHOOSE_COMPONENT::~DIALOG_CHOOSE_COMPONENT()' cannot be overloaded ~DIALOG_CHOOSE_COMPONENT();

Re: [Kicad-developers] [Patch] Add an option to select a reference point and an anchor in pcbnew move exactly dialog

Wayne, I'll create a follow up patch to address the issues you mentioned in the next few days. Thank you for the excellent suggestion of adding the the aux origin. Robbert From: Wayne Stambaugh Sent: Wednesday, March 22, 2017 4:59 PM To: Robbert Lagerweij; KiCad

Re: [Kicad-developers] UI improvements

This is a good point, and I totally agree. KiCad libraries isn't optimal like they are now with new feautures like simulation added. But that belongs in another thread, this was to discuss naming in the UI. Perhaps a discussion on v6 roadmap would be a better place as this will probably be a

Re: [Kicad-developers] UI improvements

Long before computer CAD software, we used Symbol for the schematic, and footprint or package for the physical device. What is a good reason to go away from that? Just my $0.02 Jean-Paul N1JPL > On Mar 23, 2017, at 2:02 PM, Heiko Rosemann wrote: > > I strongly believe

Re: [Kicad-developers] [PATCH] common.h tidyups

John, I committed up to patch 9. Patch 6 did not apply cleanly. Apparently it needs the broken patch 5 so it will need to be rebased once you fix patch 5. I have a question about patch 10. Did you test InitAboutKicad from the python scripting. It was originally ignored because there were

Re: [Kicad-developers] UI improvements

I strongly believe that's because many people come from Eagle originally (even via a different professional tool) and Eagle has this distinction. A symbol is what you place in the schematic, a footprint is what you place on the PCB and a component is what defines their relationship (and links to a

Re: [Kicad-developers] KiCad patch: Use XDG_CONFIG_HOME on Windows

Will my patch be considered to be implemented? In the meantime I've released a KiCad Portable here: http://portableapps.com/node/55837 ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net

Re: [Kicad-developers] WxFormBuilder - is it used?

On Thu, Mar 23, 2017 at 03:16:34PM +0100, Fabrizio Tappero wrote: > If I should not edit directly the mentioned file, I like to know how to > trigger the Builder from cmake. I simply do a generate from within the builder before exiting :D -- Lorenzo Marcantonio signature.asc Description: PGP

[Kicad-developers] WxFormBuilder - is it used?

Hello, in reference to this recent email about using and not using the wxFormBuilder: https://lists.launchpad.net/kicad-developers/msg27613.html I like to know how I am supposed to modify a gui element like: eeschema/dialogs/dialog_edit_component_in_schematic_fbp.cpp If I should not edit

Re: [Kicad-developers] WxFormBuilder - is it used?

For dialogs already using wxFormBuilder, you should continue to do so. Any patches editing the generated files by hand will be rejected. On Thu, Mar 23, 2017 at 03:16:34PM +0100, Fabrizio Tappero wrote: > Hello, > in reference to this recent email about using and not using the > wxFormBuilder: >

Re: [Kicad-developers] UI improvements

I agree with Simon. I have plans to propose something like this in the future (i.e. an integrated part library that manages symbols/footprints/etc together) and it would be best to reserve the term "component" for this future use, since in my experience that's what "component" means in the big

Re: [Kicad-developers] UI improvements

one of the things that irks me about component is even though its meant to only be schematic being component libs a lot of the questions asked in irc will state component when they use that as either a generic term for symbols AND footprints or sometimes footprints only, as to some i guess thats

Re: [Kicad-developers] UI improvements

Ah, interesting. This is a ... fiddly distinction, I don't like it. This is one case where I think we really should _not_ follow. I'm still not flipping from component back to symbol myself though - this is just Altium. The rest of them still mostly use "component", right? On Thu, Mar 23, 2017

Re: [Kicad-developers] [PATCH] common.h tidyups

So far, I've tested patches 1-4 and they seem fine. Patch 5 fails to compile on windows with the following compiler output: C:/msys64/home/wstambaugh/src/kicad-trunk/common/directory_utils.cpp: In function 'wxConfigBase* GetNewConfig(const wxString&)':

Re: [Kicad-developers] UI improvements

Here is the Altium library documentation: http://www.altium.com/documentation/17.0/display/ADES/((More+about+Components+and+Libraries))_AD Interestingly the terms component, part, symbol, model, and footprint are all mentioned. It appears that the folks at Altium have answered the is it a

Re: [Kicad-developers] [PATCH] common.h tidyups

Hi John, Thank you for the patches. I have committed: 0001 OPENGL_GAL: Init currentTarget 0003 Rework zone creation in GAL (committed yesterday) I had a look at other changes, and they appear to be a sensible common.h clean-up. All patches received the Orson Approves™ badge, but I leave the

Re: [Kicad-developers] UI improvements

Many of them actually don't have that notion. Surprisingly enough, Altium of all things has a system that is remarkably similar to our own, just with a different library management discipline applied in their standard library. On Fri, Mar 24, 2017 at 01:50:08AM +1300, Simon Wells wrote: > Do most

Re: [Kicad-developers] UI improvements

I think doing something just because everyone else is can be a very good thing sometimes. When you borrow someone else's car, you don't accidentally drive through a storefront because they swapped the accelerator and brake pedal. When people want to communicate on this mailing list, they speak

Re: [Kicad-developers] UI improvements

Do most of the other EDA packages not refer to a component as something that combines a symbol AND a footprint though? On 24 March 2017 at 01:34, Wayne Stambaugh wrote: > I'm going to weigh in on this because this has been on my radar with the > symbol library table work

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

Hi Kevin, The patch addresses just the appearance of the icons, the position was decided by the person who introduced the new feature of he latest. The presence of a mouse arrow is not needed in the ratsnest icon. Please have a look at inkscape icons (a reference tool) for similar icons. I know

Re: [Kicad-developers] UI improvements

I'm going to weigh in on this because this has been on my radar with the symbol library table work I've been doing. I do agree that we need to pick one term and use it consistently. My preference is the term symbol because in my mind this is a component[1] and this is symbolic representation[2]

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

On 2017-03-22 11:25 AM, Fabrizio Tappero wrote: like in the picture below the following patch is an improvement of the following icons:Â highlight nets display local ratsnest click to highlight net [snip] Inline image 1 Inline image 2 In the sample images you swapped the positions of the

Re: [Kicad-developers] UI improvements

On 3/22/2017 7:12 PM, Chris Pavlina wrote: > On Wed, Mar 22, 2017 at 11:53:40PM +0100, Clemens Koller wrote: >> Hello, Fabrizio! >> >> The horizontal + vertical justify radio buttons could possibly be improved >> by showing the alignment visually as it's done in [1] by using a 3 x 3 radio >>

Re: [Kicad-developers] UI improvements

Symbol has been used as long as I can remember. The proper names should probably be defined to avoid confusion. In my book: A "symbol" is a generic repesentation for drawing a schematic, and that is whats used in eeschema right now. A "footprint" is the pads and silkscreen ++ used in pcbnew.

Re: [Kicad-developers] UI improvements

Hi, Chris! On 2017-03-23 11:24, Chris Pavlina wrote: > On Thu, Mar 23, 2017 at 10:27:55AM +0100, Clemens Koller wrote: >> Hello, Chris! >> >> On 2017-03-23 00:12, Chris Pavlina wrote: >>> On Wed, Mar 22, 2017 at 11:53:40PM +0100, Clemens Koller wrote: The timestamp is not human readable. It

[Kicad-developers] GAL tools needed for via stitching & co.

Hi all, I'm finishing the new connectivity algorithm (I'm going to send a patch soon), which will allow stuff like overlapping zones and free-placed vias, without any additional constraints. A nice addition to that would be to: - Add new DRC markers showing clearly unconnected items (instead of

Re: [Kicad-developers] UI improvements

On Thu, Mar 23, 2017 at 10:27:55AM +0100, Clemens Koller wrote: > Hello, Chris! > > On 2017-03-23 00:12, Chris Pavlina wrote: > > On Wed, Mar 22, 2017 at 11:53:40PM +0100, Clemens Koller wrote: > >> The timestamp is not human readable. It seems strange to me to dump it as > >> hex-number on the

Re: [Kicad-developers] UI improvements

Hello, Fabrizio! On 2017-03-23 10:03, Fabrizio Tappero wrote: > Hi Clemens, > what do you exactly mean by a 3x3 radio button matrix? > The thing is bugging me the most is the ambiguity of button that says "Test" > and the one that says "Select" which by the way I use very often. > In the 3 x 3

Re: [Kicad-developers] UI improvements

Hello, Chris! On 2017-03-23 00:12, Chris Pavlina wrote: > On Wed, Mar 22, 2017 at 11:53:40PM +0100, Clemens Koller wrote: >> The timestamp is not human readable. It seems strange to me to dump it as >> hex-number on the UI. (WTF!?) > > I'm struggling to think of a use for this. Maybe for power

Re: [Kicad-developers] UI improvements

editable timestamp could be good if it has some sort of "power user" usage. Does it? On Thu, Mar 23, 2017 at 12:12 AM, Chris Pavlina wrote: > On Wed, Mar 22, 2017 at 11:53:40PM +0100, Clemens Koller wrote: > > Hello, Fabrizio! > > > > The horizontal + vertical justify

Re: [Kicad-developers] UI improvements

Hi Clemens, what do you exactly mean by a 3x3 radio button matrix? The thing is bugging me the most is the ambiguity of button that says "Test" and the one that says "Select" which by the way I use very often. On Wed, Mar 22, 2017 at 11:53 PM, Clemens Koller wrote: > Hello,

Re: [Kicad-developers] Icon policy

Hi David, thanks for the feedback. The patch, in particular, submitted does not change the look of the icon, instead makes it more pleasing to the eye and improves the chance that a new user will understand its use. I am aware of the problem of heavy changes. That is why I try to do it with great

Re: [Kicad-developers] [PATCH] CPolyLine -> SHAPE_POLY_SET refactor

Oh, cool, then there are no objections from me. Thank you! Best, Alejandro 2017-03-23 9:28 GMT+01:00 Maciej Sumiński : > I have done this already, no worries. > > Regards, > Orson > > On 03/23/2017 09:26 AM, Alejandro Garcia Montoro wrote: > > Do the patches apply

Re: [Kicad-developers] [PATCH] CPolyLine -> SHAPE_POLY_SET refactor

I have done this already, no worries. Regards, Orson On 03/23/2017 09:26 AM, Alejandro Garcia Montoro wrote: > Do the patches apply cleanly? It is possible that they need a slight rebase > since the latest changes on the GAL zone. > > Let me check it. > > 2017-03-23 9:19 GMT+01:00 Maciej

Re: [Kicad-developers] [PATCH] CPolyLine -> SHAPE_POLY_SET refactor

Do the patches apply cleanly? It is possible that they need a slight rebase since the latest changes on the GAL zone. Let me check it. 2017-03-23 9:19 GMT+01:00 Maciej Sumiński : > Finally I had some time to test the branch and I could not find any > problems, hence I

Re: [Kicad-developers] [PATCH] CPolyLine -> SHAPE_POLY_SET refactor

Finally I had some time to test the branch and I could not find any problems, hence I would like to merge it. Let me know if there are any objections. @Nick: Could you give more details? I placed keepout zones and refilled zones for all demo boards, and every time I get exactly the same zones

Re: [Kicad-developers] UI improvements

On Thu, Mar 23, 2017 at 01:41:05PM +1100, Oliver Walters wrote: > No matter what they are called, it should be *one* thing. Currently there > seems to be a few options. > > Schematic items - symbol / chip / component > PCB item - footprint / module / package > >From the documentation point of