Maniphest T93481

Workspaces don't have a shortcut, workaround has an issue
Closed, Resolved
Actions

Assigned To
None
Authored By
Dan McLaughlin (DrM)
Nov 29 2021, 4:30 PM
Tags
  • BF Blender
Subscribers
Dan McLaughlin (DrM)
Philipp Oeser (lichtwerk)

Description

System Information
Operating system: Win10
Graphics card: N/A

Blender Version
Broken: All

Short description of error
Workspaces don't have a shortcut. There is a workaround however

Preferences > Keymap > Screen (Global)

Add a new keymap (e.g.)

However there is an issue with this. When switching workspaces this way the new workspace isn't preserved as it is when you click the header. For example, go from Layout to Sculpting, and Sculpting will end up in Object mode. I suspect that clicking the tab performs other operations such as restoring state. Just calling "wm.context_set_id" appears not to do this. A proper shortcut would fix.

Exact steps for others to reproduce the error

  1. Add shortcuts like this
  2. Switch between the two tabs and see that state for the workspace isn't preserved.

Event Timeline

Dan McLaughlin (DrM) created this task.Nov 29 2021, 4:30 PM
Philipp Oeser (lichtwerk) changed the task status from Needs Triage to Needs Information from User.Jan 19 2022, 10:35 AM
Philipp Oeser (lichtwerk) added a subscriber: Philipp Oeser (lichtwerk).

Switching workspaces like you suggested using shortcuts seems to be working fine here (mode is properly set)

Tested 3.0, master, 2.93.7 and 2.83.18.

This is either Windows specific or the is something else interfering?
Please try with File → Defaults → Load Factory Settings to see if you still can reproduce this issue.
Have you tried other shortcuts?

Pratik Borhade (PratikPB2123) added a subscriber: Pratik Borhade (PratikPB2123).Jan 19 2022, 10:37 AM
Dan McLaughlin (DrM) added a comment.Jan 26 2022, 3:40 PM

I've done some debugging, I think it may be due to the fact that I'm using a 3DConnexion keyboard. The NDOF code for 3Dc isn't aware of some of their newer products such as the mouse and keyboard, and I'm seeing extraneous things going on because it thinks its NDOF input. Let me do some more checking, and I may submit a patch to have it ignore the 3Dc keyboard mouse (via USB VID/PID) because the handling for that should be pure keyboard and mouse, not NDOF.

Philipp Oeser (lichtwerk) added a comment.Feb 7 2022, 10:16 AM
In T93481#1295348, @Dan McLaughlin (DrM) wrote:

I've done some debugging, I think it may be due to the fact that I'm using a 3DConnexion keyboard. The NDOF code for 3Dc isn't aware of some of their newer products such as the mouse and keyboard, and I'm seeing extraneous things going on because it thinks its NDOF input. Let me do some more checking, and I may submit a patch to have it ignore the 3Dc keyboard mouse (via USB VID/PID) because the handling for that should be pure keyboard and mouse, not NDOF.

How did it go?
If you have a patch, please link it to this report.

Pratik Borhade (PratikPB2123) removed a subscriber: Pratik Borhade (PratikPB2123).Feb 15 2022, 8:03 AM
Dan McLaughlin (DrM) added a comment.Mar 11 2022, 1:34 PM

This issue resolved otherwise, but will submit a patch so Blender can recognize new 3Dconn devices separately.

Dan McLaughlin (DrM) closed this task as Resolved.Mar 11 2022, 1:35 PM