Re: [Kicad-developers] [RFC] Change to object visibility system for usability/clarity

2018-02-22 Thread Maciej Sumiński
Good catch, thank you Andrzej. I have just committed your patch to the master branch. Cheers, Orson On 02/22/2018 02:43 PM, Andrzej Wolski wrote: > Wayne, > > thanks for merging. I have a complementary patch that fixes problem with > selecting hidden tracks. > > Cheers, > Andrzej > > > On

Re: [Kicad-developers] [RFC] Change to object visibility system for usability/clarity

2018-02-22 Thread Andrzej Wolski
Hi Jeff, I mean tracks hidden with "Tracks" checkbox in Render tab. Cheers, Andrzej W dniu 2018-02-22 o 16:39, Jeff Young pisze: Hi Andrzej, If you mean tracks under footprints, I think that’s already been fixed. See https://bugs.launchpad.net/kicad/+bug/1646339. Cheers, Jeff. On 22

Re: [Kicad-developers] [RFC] Change to object visibility system for usability/clarity

2018-02-22 Thread Jeff Young
Hi Andrzej, If you mean tracks under footprints, I think that’s already been fixed. See https://bugs.launchpad.net/kicad/+bug/1646339. Cheers, Jeff. > On 22 Feb 2018, at 13:43, Andrzej Wolski wrote: > > Wayne, > > thanks for merging. I have a complementary patch

Re: [Kicad-developers] [RFC] Change to object visibility system for usability/clarity

2018-02-22 Thread Andrzej Wolski
Wayne, thanks for merging. I have a complementary patch that fixes problem with selecting hidden tracks. Cheers, Andrzej On 02/21/2018 08:40 PM, Wayne Stambaugh wrote: Andrzej, I merged your patches. Hopefully this will tamp down some of the layer visibility complaints. Thank you for

Re: [Kicad-developers] [RFC] Change to object visibility system for usability/clarity

2018-02-21 Thread Wayne Stambaugh
Andrzej, I merged your patches. Hopefully this will tamp down some of the layer visibility complaints. Thank you for your contribution to KiCad. Cheers, Wayne On 2/21/2018 12:44 PM, Andrzej Wolski wrote: > Wayne, > > in attachment all 3 patches I have, rebased. > > Cheers, > Andrzej > >

Re: [Kicad-developers] [RFC] Change to object visibility system for usability/clarity

2018-02-21 Thread Andrzej Wolski
Wayne, in attachment all 3 patches I have, rebased. Cheers, Andrzej On 02/21/2018 05:45 PM, Wayne Stambaugh wrote: Andrzej, This patch does not apply cleanly. Please rebase and resubmit it when you get a chance. Thanks, Wayne On 2/21/2018 11:27 AM, Andrzej Wolski wrote: Wayne, I have

Re: [Kicad-developers] [RFC] Change to object visibility system for usability/clarity

2018-02-21 Thread Wayne Stambaugh
Andrzej, You have not replied to my last message about your original patch that you sent to the developers mailing list[1]. I need that one so I can apply and test the rest of your layer visibility patches. If you want these to make it into rc1, please send me this patch as an attachment soon.

Re: [Kicad-developers] [RFC] Change to object visibility system for usability/clarity

2018-02-20 Thread Vesa Solonen
Andrey Kuznetsov kirjoitti 19/02/18 klo 03:59: > Front Pads > Bottom Pads > - > Front Text > Bottom Text > - > etc Please also keep track on consistent naming... Top-Bottom or Front-Back. There used to be a convention which pair to use. -Vesa

Re: [Kicad-developers] [RFC] Change to object visibility system for usability/clarity

2018-02-19 Thread Eeli Kaikkonen
Pretty much, looks great :) BTW, I remembered still one little thing: Through Hole Pads and Non Plated Holes tooltips aren't in line with what they actually do; it's like someone who wrote the texts had a different kind of action in mind. Now it looks like that if it's checked, the rendering

Re: [Kicad-developers] [RFC] Change to object visibility system for usability/clarity

2018-02-19 Thread Andrzej Wolski
It would also be great to see all the holes like in a drill file Something like this? :) http://bit.ly/2ojZEq7 Cheers, ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe :

Re: [Kicad-developers] [RFC] Change to object visibility system for usability/clarity

2018-02-19 Thread Jon Evans
1. Agree, I will try to do this 2. I will see if there is an easy grouping. I don't want to make sweeping UI changes this close to the release. I also think it would be good to be able to show plated holes in the copper layer color somehow. I will think about easy ways to do this. On Mon, Feb

Re: [Kicad-developers] [RFC] Change to object visibility system for usability/clarity

2018-02-19 Thread Eeli Kaikkonen
It's been difficult to follow the discussion, and the subject matter and problems related to it are complex. If only minimal changes are done now I want to propose two easy things (which may have been mentioned before, but I didn't find them): 1. The Render items seem to be in a random order, at

Re: [Kicad-developers] [RFC] Change to object visibility system for usability/clarity

2018-02-19 Thread Wayne Stambaugh
I have wanted user definable layer visibility settings since we implemented the layer manager. I would be nice if the user definable layer visibility settings could be named and added to the layer manager for easy access. On 2/19/2018 12:16 PM, Jon Evans wrote: > Lots of good feedback here and

Re: [Kicad-developers] [RFC] Change to object visibility system for usability/clarity

2018-02-19 Thread Jon Evans
Lots of good feedback here and on the forums. For a long time it has been on my to-do list to add "saved view schemes" like Altium and Xpedition support, which would allow you to quickly pull up sets of shown/hidden layers/objects. I still plan on working on that for 6.0. In the short term it

Re: [Kicad-developers] [RFC] Change to object visibility system for usability/clarity

2018-02-19 Thread Andrzej Wolski
Patch (in attachment) for "Tracks" turned out to be very simple. If it gets accepted, I could make more of these. Andrzej On 02/19/2018 02:12 PM, Andrzej Wolski wrote: It would be also nice to have separate controls for: 1. Tracks 2. Drawing primitives (graphic lines, arcs, and circles) 3.

Re: [Kicad-developers] [RFC] Change to object visibility system for usability/clarity

2018-02-19 Thread Nick Østergaard
2018-02-19 1:37 GMT+01:00 Jon Evans : > I'm going to go to the user forum with these questions too, but curious > what the devs think about this: > > In my original RFC, I proposed eliminating the different between "front" > and "back" in the Render checkboxes. > I still think

Re: [Kicad-developers] [RFC] Change to object visibility system for usability/clarity

2018-02-19 Thread Andrzej Wolski
It would be also nice to have separate controls for: 1. Tracks 2. Drawing primitives (graphic lines, arcs, and circles) 3. Zones 4. Polygons 5. Text (now there is control only for footprint text) 6. Dimensions 7. Plated holes That would make Render tab (almost) complete. Andrzej W dniu

Re: [Kicad-developers] [RFC] Change to object visibility system for usability/clarity

2018-02-18 Thread hauptmech
I know the use case is implied in this thread, and the only real need before 5 is to fix the blatant bugs, but I thought it might be helpful to explicitly state the use case. A PCB layout has too much information for it to be displayed all together on the screen at once. The user (or the

Re: [Kicad-developers] [RFC] Change to object visibility system for usability/clarity

2018-02-18 Thread Andrey Kuznetsov
Jon, thanks for clarifying the cases. I hadn't thought about Wayne's suggestion that way, and it does seem to make sense to me more than mine, however I don't think the Render tab's items should be checked/modified when Visibility is checked/modified. For example, if I want to turn off Front Cu

Re: [Kicad-developers] [RFC] Change to object visibility system for usability/clarity

2018-02-18 Thread Wayne Stambaugh
That's how I see it. If I turn off the top copper layer and the footprints are linked to the layer then I want to turn off the footprint pads on that layer. The remaining footprint layers would still be visible (silk screen, solder, mask, etc.). Through hole layers may be tricking. I don't

Re: [Kicad-developers] [RFC] Change to object visibility system for usability/clarity

2018-02-18 Thread Jon Evans
Those are interesting ideas. My reading is that Andrey and Wayne are actually proposing two different "linking" modes: Andrey: linking Front and Back (i.e. checking Front pads also checks Back pads) Wayne: linking copper and render (i.e. checking F.Cu also checks Front pads) Am I right about

Re: [Kicad-developers] [RFC] Change to object visibility system for usability/clarity

2018-02-18 Thread Andrey Kuznetsov
Wayne, Yep, that's what I meant, kind of like the Photoshop linked layers. I should have added that the link is only between two of the same checkboxes that are front and bottom. Ie Front/Bottom Pads would have linkage, a different linkage would be between F/B Text, and another for etc... Please

Re: [Kicad-developers] [RFC] Change to object visibility system for usability/clarity

2018-02-18 Thread Greg Smith
When considering the ease of use of the dialog, remember LayerViewSet (python) adds some functionality and will be upgraded to work with v5. I hope similar functionality is built in to v6. Greg S. > On Feb 18, 2018, at 7:07 PM, Michael Kavanagh > wrote: > > Hi

Re: [Kicad-developers] [RFC] Change to object visibility system for usability/clarity

2018-02-18 Thread Wayne Stambaugh
I was thinking the same thing but rather than locked, I was thinking linked to the layer but the concept is the same. If they are linked, when the layer is turned off, so are the footprints on that layer. When they are unlinked, they are independent similar to the current behavior. I would

Re: [Kicad-developers] [RFC] Change to object visibility system for usability/clarity

2018-02-18 Thread Andrey Kuznetsov
Hi Jon, Make sure Andrews' patches are consistent with your commits, essentially don't commit if it'll end up as a hodge podge of code that even though it works is not coherent. I can see benefits to having control over showing front copper pads but hiding bottom copper pads, so I would keep

Re: [Kicad-developers] [RFC] Change to object visibility system for usability/clarity

2018-02-18 Thread Michael Kavanagh
Hi Jon, I like your suggestion. If you're worried about backlash, how about using a wxTreeCtrl to list the copper layers and respective names, and nested under each layer is traces/zones and pads, eg for a 2 layer board: 1. F.Cu Traces/Zones Pads 2. B.Cu Traces/Zones Pads Each item could

Re: [Kicad-developers] [RFC] Change to object visibility system for usability/clarity

2018-02-18 Thread Jon Evans
I'm going to go to the user forum with these questions too, but curious what the devs think about this: In my original RFC, I proposed eliminating the different between "front" and "back" in the Render checkboxes. I still think this makes sense for things like text and footprints, but I'm having

Re: [Kicad-developers] [RFC] Change to object visibility system for usability/clarity

2018-02-18 Thread Jon Evans
Thanks Wayne and Jeff (and yes there are a lot of edge cases here to sort out) Note that Andrzej Wolski already did propose some changes related to this that might be good to merge as a first step. I have only done limited testing on them so far but they do work and resolve some of the problems:

Re: [Kicad-developers] [RFC] Change to object visibility system for usability/clarity

2018-02-18 Thread Jeff Young
Hi Jon, Sounds good to me too. A few edge-cases you might want to watch out for: https://bugs.launchpad.net/kicad/+bug/1733894 https://bugs.launchpad.net/kicad/+bug/1744521

Re: [Kicad-developers] [RFC] Change to object visibility system for usability/clarity

2018-02-18 Thread Wayne Stambaugh
Hey Jon, I'm good with all of this. I would like to get this cleaned up before the stable release if possible since there are so many complaints and bug reports about it. Thanks, Wayne On 02/18/2018 03:00 PM, Jon Evans wrote: Hi all, Right now the behavior of the "Layer" and "Render"

[Kicad-developers] [RFC] Change to object visibility system for usability/clarity

2018-02-18 Thread Jon Evans
Hi all, Right now the behavior of the "Layer" and "Render" tabs of the layers widget are confusing to users, resulting in complaints on the forum and some bug reports: https://bugs.launchpad.net/kicad/+bug/1748181 https://bugs.launchpad.net/kicad/+bug/1743890 I could take a crack at fixing this