please open an issue at the gh repo… I don’t have any report ATM
StepUp works for me in FC 1.0, but there’s an issue in FC 1.0 that makes unions loses colors, so I’m still mostly using an older version of FC for KiCad related stuff.
3 Likes
…which is exactly? from the image is not clear.
It is actually an important thing for the T-Model. In summary, you can look at this picture and the link for detailed information.
1 Like
…Altium? no, thanks not interested.
1 Like
This is not about Altium. It is about the way memory blocks communicate.
I will fight with all my heart to bring all the features related to High Speed Design and Custom Design Rule that are in Altium to Kicad. 
4 Likes
a dubious proposal. in Altium everything is very cut down. like for example the power analyzer. what is missing is a full panalization and the Gerber editor
1 Like
One of the features of Cadstar that I really miss in KiCad is trace backtracking, where you can partially erase a track while routing by simply going back over the already routed part. In KiCad, I’m often left with stubs that I have to delete afterwards.
2 Likes
Are you aware that you can already (v9) define connection topologies for length matching using the fromTo function in the DRC rule language? We don’t have a GUI/wizard for this, but all the core stuff is already there.
I need first class variants so badly. There are workarounds, but they all usually rely on abusing fields and don’t play nicely with a fully specified atomic database library. Same goes for sheet reuse and variants. The current work around is to make field variables at the sheet level, and place these in the ‘value’ field of components.
5 Likes
Very substantive answer 
Variants is also the most requested feature on GitLab: Create a PCB assembly variant system (lp:#1767218) (#2131) · Issues · KiCad / KiCad Source Code / kicad · GitLab
I wonder if we could have a crowdfunding campaign to pay one of the devs or KiPro to implement it. Not sure how much we would need to raise.
8 Likes
You can already fund the development of KiCad. While it is not focused on a specific task, the general development budget influences the amount of dev-time
One of the features of Cadstar that I really miss in KiCad is trace backtracking, where you can partially erase a track while routing by simply going back over the already routed part. In KiCad, I’m often left with stubs that I have to delete afterwards.
Can you elaborate? I’m unable to work out the user interaction aspect. Thanks.
Is it possible to adding to Custom design rule as “Rule Builder” ?
Altium solves this with Query Builder and you can add many rules in many tables like in Kicad’s netclass rules based.
I guess it can be easy to add this feature.
We’d like to do something better for rules configuration, but haven’t settled on an approach yet. And I’m afraid that these things are never easy!
(Also, the logic conditions in that screenshot make me shudder a bit - there’s a whole load of implicit operator precedence going on there which makes it impossible for a human to parse easily).
1 Like
I actually prefer to have each of these rules structured in a separate window. These windows can also be collected in a place like a netclass table. We can adjust each rule we create without mixing them together.
This will make it easier for us in complex projects.
And these can also be shown in the Rule table like the netclass table.
2 Likes
It’s a bit like this:
“Oops, I overshot my mark!”
I’ll track back and LMB.
And I’m off again from the correct point.
1 Like
Can’t you just got the delete or backspace key and undo the last click? I might be thinking of Protel.