Hi there,
quick question, is it also the case with you that if “Do not display free space” is activated, it is still displayed when new traces are drawn?
Current version, same for Win and Linux. Or is there another deactivation?
Hi there,
quick question, is it also the case with you that if “Do not display free space” is activated, it is still displayed when new traces are drawn?
Current version, same for Win and Linux. Or is there another deactivation?
You write wire and show track?
What KiCad version are you using - I can’t find “Do not display free space” flag.
He probably means: PCB Editor / Preferences / Preferences / PCB Editor / Display Options / Clearance Outlines / Tracks: … which has a list with 5 options. (And a checkbox for the pads) And as far as I know, this only works for the thin lines, not the full “shadow” when drawing a track.
Yes, you are right. The translation was bad
“Tracks: Do not show clearances”
I was able to deactivate it in earlier versions of KiCad.
Because of ‘activate’ I was searching only check boxes and didn’t looked into Selection boxes.
I would just like to know if it’s a bug or if there are other ways to disable it.
If remember well I noticed it when KiCad was V5 and didn’t found the way to switch it off. But then I just forgot of it as a problem and I got used to it.
I was not experimenting with these settings since V5 so just don’t know the answer.
But if it can’t be switched off I would rather suppose that it is intended behavior and not a bug. The decision could be that even you don’t see clearances for all others you should see here were you are routing.
What I was trying to switch off and failed is reference and value texts when moving footprint. With small footprint like 0402 these texts make me not see the footprint rectange and I have to position it several times to get the place I want. May be it is because I have reference and value at Courtyard layer and I can’t switch that layer off. I have them there because there are no user layer pair that would be flipped together with footprint so according to my investigation it was the better layer for reference and value. I hope such pair will be in V9.
“What I was trying to switch off and failed is reference and value texts when moving footprint.”
Yes, I would also like to switch that off.
I think it’s a mistake. Let’s wait and see.
May be my memory lies me but I vaguely remember that someone wrote to me that it was intentional.
For a lot of things I have stopped tweaking small personal things about user interfaces. The defaults are normally quite usable It’s always a compromise between different ways of using a GUI and there are often good reasons why they are the defaults. When starting to learn and get comfortable with a new program such compromises are not always obvious, and this misunderstanding can easily lead to twiddling with trivial settings, and this can silently absorb hours of your time (spread over weeks, months or years)
I am guessing you also turned off Preferences / Mouse and Touchpad / Pand and Zoom / Center and warp cursor on zoom I needed a few days to get used to it, and am now longing for all other programs to implement panning and zooming in this way.
I’m totally happy with Kicad, the only thing that bothers me is that I can’t switch off this free space.
I hardly notice these “clearance shadows”, It’s mostly when some event such as this post jogs my memory that I start noticing them again for a while. It also was very helpful for making screenshots for the issue below, in which clearances were modified by custom rules. Without the clearance outline you would not be able to see where it goes wrong.
And best I know, it is not possible to turn them off, and I do regard this as a (small) UI inconsistency, and therefore it would be valid to make a feature request for it on gitlab. Maybe someone agrees and fixes it for you. Small things like this are often just overlooked and I guess that several hundred of similar small things get fixed each year. KiCad development is very active.
If it is possible to switch it off, it should also work. Let’s wait and see, maybe someone will fix it at some point…hopefully.
To improve the changes a bug should be reported in Gitlab, otherwise the developer may never see that there is a problem, this is a user forum after all.
If someone could do this please
Go find a mirror, point at it and then say that again loudly three times.
Most people here do not find it important enough to make an issue out of it.
ok ok
I will try it, hopefully there is one guy who will have a mercy on me
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.