All 5.x versions of KiCad do this. Hide all layers in pcbnew. Now start drag-selecting. You’ll get footprints, silkscreen text, edges, traces, the works.
Ever heard the saying - “Wie man in den Wald rein ruft, so schallt es heraus”?
(lose: What goes around, comes around).
People who rant, especially without specifics, shall not be surprised if the audience returns in kind.
And don’t get me started on Autodesk stuff that is not working, or stops working from one version to the next. At least I’m on a university license, so have no skin in the game and if I find some bug I report it.
Did you or the OP did that in the case of KiCAD and the bugs you encounter (if yes, fine, my hat is off to you sir, if not, you really have nothing to complain about).
KiCAD thrives the more people use it and help to make it better.
Complaining is easy. Anyone can do that. But that’s not helping. That’s just complaining.
1 Like
This might be a bug connected to the “can select invisible things” problem you have: https://bugs.launchpad.net/kicad/+bug/1789122
I am sure there are other similar bug reports out there. If enough people talk to the devs about something like this then it will be fixed in time. If nobody cares to report it how should the devs know about the problem?
Yeah, sounds a bit like it, but without proper follow up and more details from users the devs naturally do not get the feedback that would be needed to get this solved and working more consistently.
Who can blame them, it takes time and effort to produce a proper bug report.
Not everybody is carved out for that.
/s
So far I’ve filed one bug report. It remains in limbo.
The OP @Zom-B has made two posts. The first one (about background colours) Filled rectangle? has been picked up and filed in the bugtracker. https://bugs.launchpad.net/kicad I would think that since eeschema is in the current work plan it stands a good chance of making the cut for version 6.
The second post is pure rant but has generated a lot of comments. Which strategy is likely to be more fruitful in getting a developer to spend their time solving your problem?
We all get cross with software - sometimes because of a bug, sometimes because a workflow or function is unsupported. This is not going to get better without a bug report. Sometimes the workflow is unclear - the forum users are always keen to help with clarification and work arounds. Sure there are people coming from other software who bring a different perspective and we should always be open minded enough to listen to see if there might be a better way to achieve a solution
Most of us have managed to use KiCad to produce some pcb designs which meet professional standards. It is not perfect and has a learning curve like all other software. It is $7500 less than Altium and has been largely the result of volunteer effort (putting aside the recent CERN funding). You don’t get much buy in from volunteers when you tell them their work is rubbish. Patience and a bit of psychology is likely to be more effective than ranting.
4 Likes
I have disabled the “Center and warp cursor on zoom” and the cursor doesn’t warp in the cases you mentioned. The cases I noticed that the cursor still warps is when using the right click menu while routing and when importing a netlist.
I think the warping when using the right click menu is necessary for now, the result without warping is more annoying, try KiCad on Linux with Wayland, it doesn’t support mouse warping.
I don’t know what would be the real fix for this, but just disabling mouse warping is not.
Has anyone reported this?
That’s a known problem.
If you meant 5.0.x you may be correct, otherwise you’re wrong. Doesn’t happen in 5.1dev (aka 6.0-rc1-dev-etc. aka current nightly builds).
If this is true then the bug report i linked above can be marked as fixed.
I’m curious about that. Do you have a link? I have reported quite many and I must say most of the real bugs (clearly unexpected behavior) have been fixed quickly. Feature request and opinions of course not. Sometimes I have felt that the response haven’t been what I wanted but I can live with that.
That’s great news if hiding Layers prevents the selection of Items on those layers in nightlies. The problem persists in 5.0.2. I’ve spent a lot of time going to the Items tab and unchecking everything but Footprints and Tracks just to wrangle things. Sometimes I remember to use High Contrast Mode to work around.
My bug was about using Ctrl-# as hotkeys with 5.0 Release. This (likely) Windows-specific bug still exists in 5.0.2. I have not tried nightlies yet. For now I am able to Export Hotkeys, edit the file, and then Import Hotkeys to get the desired behavior.
I guest you mean me who post had been remove by some one in here. 
your post is still here 
(at least for me)
Recommending installing (unsupported) 4.0.7 for a group of serious new users is not advice I want to see on this forum now.
Let’s concentrate on getting 5.0.2 used correctly and on reporting its bugs accurately on Launchpad to get squished in 5.1
1 Like
@davidsrsb: I do not disagree with you. But when I read @Zom-B frustration - I can see it happen to me, and I can see 4.0.7 would ease a lot of his problems especially collaborating. But I do encourage him to keep trying and check on new versions on his own until he see it can fit his team work flow… In professional work, it not necessary best to keep update the tools, but it usually introducing unnecessary cost for the team without a “soft” introduction (like test/trial by individual…)
I don’t quite see how 4.x is better for collaborating. A lot of features added to v5 make this sort of thing a lot easier (especially the introduction of the symbol library table which makes setting up a proper environment a lot easier)
The only reason i would understand for not going with the current version is if you have an extensive number of projects already done in v4. But even there i would suggest a dual setup. New projects only in v5 and v4 only used to manage old projects. (If one does not do it that way then one will still be stuck at v4 when v6 comes out. The longer one sticks with legacy systems the more work an eventual switch over will be.)
2 Likes
The reason are base on teams, and environment - there is no logical explain about it. It just what the team comfortable with, and work with. As individual in the team, I do look forward to update the tool when it fit. I also do understand, and agree with @Rene_Poschl for hard to migrate if we hold it back too long…
For my case: I found I cannot effectively do component placement manually as 4.0.7 just because of the ratsnet highlight feature been changed to the way it do not help me. So I did request the feature, but no idea when, and how would that like yet. Also, crashing are seem to not be avoidable - much like a part of working mode! So it for me is not mature enough to introduce into the team.
I don’t have any complain about UX, it just not important for me, as long I can work with them effectively when I got use to it. I like the fact the a lot of hot key reduce my hand movements. But the mouse way do make my hand move so much, and tired (but it is what it is). The less hand movement, the more effective … like “VIM” editor…