change U and D shortcuts

[yorik]

Currently U and D shortcut keys are hard-coded to Dock and Undock (Gui/CommandView.cpp line 1354).
I don’t think these multi-actions commands can have their shortcut easily changed… But I don’t think many people use these shortcuts so I propose to set them to Shift+D and Shift+U, so U and D become free for multi-keys shortcuts… Anyone is against that? Speak now or stay quiet for ever!

[microelly2]

Changing from hard coded to another hard coded only moves the problem a bit.
The better way in my eyes is to make the shortcuts configurable and have some configurations available like the style sheets.
So FreeCAD beginners start with the documented an well known shortkeys and Blenders can use Blender like keys.

[DeepSOIC]

I use D/U keys sometimes. But I don’t mind if you change them.

[triplus]

Working on this area for a while:

http://forum.freecadweb.org/viewtopic.php?f=22&t=15638

I can say whatever you do likely it won’t be the solution that wouldn’t count as a compromise. A compromise that doesn’t solve all that much. Example from @sgrogan test:

http://forum.freecadweb.org/viewtopic.php?f=22&t=15638&start=10#p136920

This just isn’t sustainable in FreeCAD.

@microelly2

The better way in my eyes is to make the shortcuts configurable and have some configurations available like the style sheets.
So FreeCAD beginners start with the documented an well known shortkeys and Blenders can use Blender like keys.

Now the problem with configurable shortcuts is it can be done:

http://forum.freecadweb.org/viewtopic.php?f=22&t=15638#p124700

But FreeCAD is a bit different compared to Blender. It has workbenches and therefore changing workbench should change default set of shortcuts or it just can’t work. This currently does not happen. In ShortCuts i moved away from resolving this on such low level as workbench specific shortcuts could be implemented but it is just to easy for users to produce results like setting shortcut to for example Ctrl + N or Ctrl + Q … Although experienced user might want to do just that i do feel regular user would by overriding such standard/basic shortcut combination introduce usability issues. And from regular user point of view (not some shortcut guru) setting shortcuts directly can easily turn into complex and not that simple task.

Therefore different approach will be used and hopefully it will solve some of the issues i mentioned and it will fit in the FreeCAD way of doing things. As in this regard we can’t compare to for example Blender. As we do things differently and therefore likely need different solutions for this area.

[wmayer]

At the moment StdViewDockUndockFullscreen is a group command where its sub-actions have short cuts assigned. To make them customizable the command should be split into separate dummy commands.

[pablogil]

@microelly2

Changing from hard coded to another hard coded only moves the problem a bit.
The better way in my eyes is to make the shortcuts configurable and have some configurations available like the style sheets.
So FreeCAD beginners start with the documented an well known shortkeys and Blenders can use Blender like keys.

+1

[triplus]

@pablogil

@microelly2

Changing from hard coded to another hard coded only moves the problem a bit.
The better way in my eyes is to make the shortcuts configurable and have some configurations available like the style sheets.
So FreeCAD beginners start with the documented an well known shortkeys and Blenders can use Blender like keys.

+1

But that already is possible in FreeCAD:

In Keyboard, you can see the keyboard shortcuts associated with every FreeCAD command, and if you want, modify or assign new shortcut to any command. This is where to come if you use a particular workbench often, and would like to speed up its use by using the keyboard.

http://www.freecadweb.org/wiki/index.php?title=Interface_Customization

[yorik]

I was trying to be lazy, but I see you guys wont let me
Okay I’ll try to do it Werners way

[wmayer]

@yorik

I was trying to be lazy, but I see you guys wont let me

I do: ef363f9

[yorik]

Now I’m ashamed Thanks Werner!

[pablogil]

@triplus

@pablogil

@microelly2

Changing from hard coded to another hard coded only moves the problem a bit.
The better way in my eyes is to make the shortcuts configurable and have some configurations available like the style sheets.
So FreeCAD beginners start with the documented an well known shortkeys and Blenders can use Blender like keys.

+1

But that already is possible in FreeCAD:

In Keyboard, you can see the keyboard shortcuts associated with every FreeCAD command, and if you want, modify or assign new shortcut to any command. This is where to come if you use a particular workbench often, and would like to speed up its use by using the keyboard.

http://www.freecadweb.org/wiki/index.php?title=Interface_Customization

Of course is possible, but I think @microelly2 added the option to have different configurations preloaded so that the user can choose between them. It would be necessary to add some options to the actual Keyboard preferences panel:

• drop-down menu with selectable keyboard schemes
• create/modify/delete name for the actual keyboard scheme
• import/export button

Blender does this way and it’s very handy and very flexible for users:

[triplus]

There is import/export capability built in Parameter editor and there is possibility to configure keyboard shortcut for commands in FreeCAD. Therefore although is not as fancy as it could be it does allow you to do exactly that.

Therefore when asking to have such capability in FreeCAD. The answer is that is already available.

But if you are a regular FreeCAD user and not some shortcut guru with in-depth understanding of FreeCAD and Qt shortcut management you will easily produce results that don’t work good. And from the perspective of having 100+ available modules/workbenches for FreeCAD. Keyboard is just to small to support all that. And here FreeCAD is different compared to Blender and therefore needs different solutions. Shortcuts need to be managed on individual workbench level or they are not managed at all. And if they are not managed good luck with making all that work.

Therefore what i am trying to say is creating and exporting/importing shortcut scheme is “the easy” part and it is already possible. Relying on it to work good in 100+ module/workbench scenario in the way things currently work isn’t realistic.