You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently it seems, that a chosen non-default tool is switched back to the default tool immediately after one use of the non-default tool. This is quite inconvenient.
The text was updated successfully, but these errors were encountered:
@dumblob This is a little bit more of a subtle issue. For the schematic tools, if you double click on the "trace" or "no-connect" tools, then they persist. The trace tool can be double clicked to "tie-off" and ESC can be hit to stop the "no-connect" tool. The board "track" tool persists until it is "tied-off" by a double click. In the board portion, the "edge" tool also persists until a double click. Both the "delete" tool in the schematic and board can only be used once before reverting back to the default tool.
It's come up before that the delete tool might want to persist, maybe via a 'double-click' selection from the tool bar. My worry is that this might cause confusion in how to get out of it (either by hitting ESC or explicitly switching tools).
There is also a hot key for most tools. Hitting the 'help' (the question mark on the toolbar) will give you a list.
Can you be more specific about which tool you'd like to see persist?
I've tried several double clicks (at different places and at different stages of the following sequence). While drawing schemes immediately after clicking on "place wire" and drawing the desired path and connecting to some pin, the tool (what's the proper name of this tool?) switches to the default arrow (is this one called a manupulation tool?). The same holds also for "no-connection".
I doubt it's because of my web browser (Safari on OS X).
Currently it seems, that a chosen non-default tool is switched back to the default tool immediately after one use of the non-default tool. This is quite inconvenient.
The text was updated successfully, but these errors were encountered: