pablogil wrote:Really cool update @triplus!!
I like it a lot, it works perfect and it allows super fast launch of commands (even without the need to open an specific workbench and then run the command)
Good to hear that.
I have tested it for a while and, by the time being, I find myself very comfortable with just Global commands and 200ms for "key delay"...
Such things are left to the end user to figure them out.
For future updates I still miss:
- "clear workbench binds" button
- "reset all binds" button
- (I know you are going to tell me that it's already possible through "Edit parameters..." panel but:) import/export buttons for newbies and people that don't know how to do it through "Edit parameters" panel
This will happen and in addition developers should be able to define and provide default set of shortcuts for their workbench in the future. As for export/import capability. Such functionality will likely be explored as one of the last features added.
And above all those: I wish this become FreeCAD default because of its features and because that way it wouldn't be necessary to have an "invoke key" and it would turn into an even faster and perfect workflow...
Invoke key is needed as this is just the way how ShortCuts work. I was thinking about what is simple and what is complex. What can work reliably and what can't... From shortcuts perspective FreeCAD is more than a single application as each workbench is basically a whole new application. There can be 100 or more of them in the future. Then there is Qt and the default set of shortcuts it provide. The list of shortcuts is actually substantial (standard shortcuts like Ctrl + N). After that there are different operating systems heavily relying on modifier keys (and additional key combinations). Then there are macros that can at any time introduce new shortcut anywhere. And finally there is the end user that has built in ability to define custom shortcuts. Well as i said in the past good luck with that.
If i would try really hard i probably could introduce a way on how to manage this slightly better. That is improve things like local workbench shortcut behaviour. Slightly better duplicate condition management... But due to complexity and different needs and expectations from all the mentioned parties involved this can always work only up to a point.
Therefore in my opinion better to leave standard Qt an operating system related shortcuts as they are. Provide as much workbench specific shortcuts as possible behind invoke key. By providing sensible combinations by default. User can always manage them after. And leave the keyboard itself for macro writers and end users to actually have a chance to use currently built in shortcut system to define some custom shortcuts.
This is what ShortCuts is all about. This is how i made it and i provided the reasoning why. On how the result (once finished) will be used in the future i can't say.
Any official developer reading this thread? what do you think about it?
I wouldn't count on that too much.