On 01/04/2018 11:39 AM, André S. wrote: > Am 2018-01-04 um 17:27 schrieb Wayne Stambaugh: >> This behavior was considered a bug not to mention confusing. If a layer >> is turned off, turning on objects in that layer doesn't make any sense. >> The new (corrected) behavior is far more logical. > This is how I interpreted it after some time. :) > However, historically I did not even know that Values are tied to the > Fab layer and References to SilkS because they could be enabled/disabled > independently. > > Thanks for the information. Sorry for the confusion. > > Sadly I now have to live with the Fab symbols always visible when I want > to see the Values of the footprint. Same with Reference and SilkS. > I like to see only that information that I currently really need. Helps > to spot errors more easily when less "noise" is on the screen. > Will it be possible to solve this via Python shell/scripting? Then this > would be one path for me so solve this. Did not need it until now.
It should be possible to turn any thing on/off using Python. > > Thanks again for your patience. :) > > André > >> On 01/04/2018 10:55 AM, Nick Østergaard wrote: >>> OK, but the legacy behavior in 4.0.7 was considered a bug. I think there >>> is a launchpad bug for that. The current behavior is how it is intended >>> to work as I understand it :) >>> >>> 2018-01-04 15:16 GMT+01:00 André S. <[email protected] >>> <mailto:[email protected]>>: >>> >>> Hi Nick, >>> >>> I try to detail it again and hope I can make clear what I mean: >>> - currently you can in 4.0.7 Legacy canvas >>> * toggle the Value and Reference option in Visibility:Elements. >>> When you do that: >>> * Value/Reference are displayed or hidden according to the status >>> of the Element control. >>> The state of the _Layer option_ F.SilkS/B.SilkS and F.Fab/B.Fab >>> have _no influence_ on the visibility of Value/Reference. >>> >>> - when you switch to OpenGL or Cairo Value/Reference _disappear_ on >>> the PCB when F.SilkS/B.SilkS and F.Fab/B.Fab are _unset_ in the >>> Layer options regardless that Value/Reference option are set in >>> Elements. >>> Value/Reference are in OpenGL/Cairo only _displayed_ when >>> *.SilkS/*.Fab are _set_ *and* the Element control for >>> Value/Reference are set. >>> >>> This is independent from the actual PCB project. (I tried it on >>> three different projects) >>> In the current Nightly all canvases act the same as OpenGL/Cairo in >>> 4.0.7. (Legacy in 4.0.7 behaves differently as Legacy in Nightly.) >>> >>> I hope this made it clearer. >>> >>> André >>> >>> >>> >>> Am 2018-01-04 <tel:20%2018%2001%2004> um 14:18 schrieb Nick >>> Østergaard: >>>> 2018-01-04 <tel:20%2018%2001%2004> 9:55 GMT+01:00 André S. >>>> <[email protected] >>>> <mailto:[email protected]>>: >>>> >>>> Hi everyone, >>>> >>>> I discovered some not consistent behaviour in the current >>>> stable release: >>>> On the Legacy canvas you can display Value of the footprint by >>>> enabling Value option under Elements in the Visibility menu. >>>> This is not true for OpenGL and Cairo canvas. >>>> In the Nightly from 2018-01-02 <tel:2018-01-02> Legacy shows >>>> the same behaviour as OpenGL and Cairo. There Value is only >>>> visible when F.Fab is visible. >>>> This means 5.0 will show consistent behaviour over all >>>> canvases. Fine. >>>> The same is true with References and F.SilkS layer. >>>> >>>> What is missing with this solution is the possibility to be >>>> able to only display Value/Reference of a footprint as the >>>> current stable release Legacy canvas allows. (I really like >>>> this feature because it removes a lot of visual noise on the >>>> PCB during layout design). >>>> >>>> >>>> I don't understand you. There is still the toggle for references >>>> and values in the render (elemente) tab. I don't understand why >>>> you exemplify it with 4.0.7 when you say there is no regression. >>>> Please illustrate what you would like to have and attach an >>>> example kicad_pcb file, it is easier to comment on that. >>>> >>>> https://bugs.launchpad.net/bugs/1741015 >>>> <https://bugs.launchpad.net/bugs/1741015> >>>> >>>> I do think the behaviour of Legacy was always there, therefore >>>> my confusion with the Values and References not visible when >>>> switching canvases. >>>> Is there any chance that in future there will be an option >>>> (again) to toggle Value and Reference visibility independently >>>> from F.Fab and F.Silks? >>>> >>>> Best Regards, >>>> André >>>> >>>> PS: xkcd reference: https://xkcd.com/1172/ ;) >>>> >>>> _______________________________________________ >>>> Mailing list: https://launchpad.net/~kicad-developers >>>> <https://launchpad.net/%7Ekicad-developers> >>>> Post to : [email protected] >>>> <mailto:[email protected]> >>>> 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 : [email protected] >>> Unsubscribe : https://launchpad.net/~kicad-developers >>> More help : https://help.launchpad.net/ListHelp >>> >> _______________________________________________ >> Mailing list: https://launchpad.net/~kicad-developers >> Post to : [email protected] >> Unsubscribe : https://launchpad.net/~kicad-developers >> More help : https://help.launchpad.net/ListHelp > _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
