Options disappear on custom Keymaps #68820
Labels
No Label
Priority
High
Priority
Low
Priority
Normal
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Content
Type
Design
Type
Report
Type
To Do
Type
Web Development
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: studio/blender-studio#68820
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Windows-10-10.0.17134 64 Bits
Graphics card: GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86
Blender Version
Broken: version: 2.81 (sub 2), branch: master, commit date: 2019-08-17 21:40, hash:
blender/blender@e69fb44027Short description of error
When creating or switching to a custom keymap instead of the default "Blender" keymap, the options at the top of the tab completely disappear.
This is a bug that existed for a long time since the alpha of Blender 2.80.
Added subscriber: @JulienKaspar
Added subscriber: @WilliamReynish
Changed status from 'Open' to: 'Archived'
This is not a bug and those options don't disappear.
These are merely keymap preferences that change the default keymaps. If you create a custom keymap, you are on your own.
@WilliamReynish Ok this surprised me. I don't think this is very user friendly. I do get the justification on a surface level but then why wouldn't the options also disappear the moment you create custom shortcuts or change some shortcuts manually. You could change the Blender keymap completely and still have these options available but once you create a new keymap to export it or create a backup, it will deny you these basic options?
To everyone here at the studio this looked like a bug because it seems nonsensical to just remove the settings after a new keymap is created.
Even in 2.79 you still had these options on the side after creating a custom keymap.
Let's say I change a shortcut completely that relates to these options like: Change the mode switching pie menu from Ctrl + Tab to Ctrl + Spacebar. When I toggle the "Tab for Pie Menu" option and "Spacebar Action" it will override any of those changes anyway. Why should that only be an option in the Blender keymap but not a custom one???
If the user doesn't want to use these settings there is an option to close the dropdown of them. Out of sight, out of mind.
@JulienKaspar We didn't have this concept at all in 2.79 and earlier.
I'm merely pointing out that it's not a bug and that it works as designed. I won't argue with you that it couldn't perhaps work differently or more nicely in some ways, but that's a separate thing.
Added subscriber: @nokipaike
@JulienKaspar a trick..
if you want the settings to work also on the custom keymaps, first set the options from blender keymap, then set the customized keymap .. it works ;)
Added subscriber: @ThatAsherGuy
@WilliamReynish
As long as developers are aware of the issue and it's documented somewhere as a to do I'm ok with that ;)
That deserves it's own bug report :D
Added subscriber: @Likkez-2
I thought you guys said 2.7 keymap will be still supported.... Why do I have to be punished for not wanting to use the 2.8 keymap that is missing quite a bit of keys from the 2.7 one. I dont get why advanced users became second class citizens all over a sudden because u guys decided to make blender more friendly for beginners. I want to have Pie menus in 2.7 keymap too but the only option is the Pie addon which isn't quite like it.
@Likkez-2 the 2.7x keymap is still available. In 2.7x, the pie menus were only available via addons.