Page MenuHome

Display Keyboard Shortcuts for X-Ray (and Other On-Screen Buttons)
Closed, ResolvedPublic


System Information
Operating system: Windows-10-10.0.18362 64 Bits
Graphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.30

Blender Version
Broken: version: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: rBf6cb5f54494e
Worked: (optional)

Short description of error

This is a repost from devtalk->paper_cuts of this post where I was directed to report it as a bug. The text is identical with the exception of one corrected image.

I’m a new Blender user (less than 10 hours under my belt), and I realized I was toggling X-Ray frequently. So I need a shortcut. Upon hovering my mouse over the icon, a tooltip popup appears with no mention of a shortcut. So my assumption was that there wasn’t one but can probably set my own. So I got around to Googling it and discovered there is, in fact, a shortcut (Alt-Z). But what if I haven’t Googled it? I might be using my mouse to switch for months! Based on my experiences (and the 637 peoples who viewed this forum) I believe this issue to be a problem that deserves a fix.

Also, X-Ray isn’t the only one that doesn’t have the shortcuts in the tooltips. Selection modes, as well as shading modes it’s likewise missing (but snapping does have them).

Because the template insists on a solution I declare that the selection modes buttons: Vertex Select, Edge Select, Face Select; the Show Overlays button (if indeed there is a shortcut Googling required); the X-Ray button; and the Viewport Shading Modes: Wireframe, Solid, Look Dev, Rendered should have their respective keyboard shortcuts displayed in the tooltips.


Event Timeline

William Reynish (billreynish) lowered the priority of this task from 90 to 50.

I can confirm this issue.

@Campbell Barton (campbellbarton) Is this a bug, or is there some technical limitation why this doesn't work in these examples?

Fixed the X-ray case, other cases aren't so straightforward since buttons don't always use the same functionality as shortcut keys.

To make every case work we would have to have some way to tell the button an alternate access method it could use to access the shortcut. Or hard code this in somewhere - neither are nice options.