A teaser of what might come in @kicad v10, which is the release after the upcoming v9. #KiCon
@kicad Continued
@kicad @kicad future feedback for Wayne, would love it if those items had GitLab issue number added next to them where applicable :)
@arturo182 @kicad in still on V6 because it still works fine for me but I’ll be updating eventually I’m sure. A better library experience would be very welcome.
@arturo182 @kicad what's 'Automatic neck down"? Ta for these toots!

@concretedog @kicad Might be this and/or the reverse of this (automatically make the trace smaller so that it can reach the pad with no DRC issues):

https://gitlab.com/kicad/code/kicad/-/issues/8766

wishlist router: Automatically select maximum width available when starting violating track (#8766) · Issues · KiCad / KiCad Source Code / kicad · GitLab

Description Routing would be much easier if router automatically select highest possible trackwidth here, because user intends to route track wider...

GitLab
@arturo182 @kicad wdym remove standalone editors?
Does that mean
a) no schematic or board editor without the project environment and subsequent trouble, or
b) no more ability to use schematic and board views across multiple monitors?
@arturo182 @kicad Saw the talk and it looks EXACTLY like the plan to nuke support for multiple monitors.
Can't KiCad just take care of the technical debt instead of constantly throwing stuff under the bus...
@MisterHW @arturo182 that means that the schematic and board editor executable files will go away. You will launch the KiCad executable to access the editor windows. It has no impact on multiple monitors