Customizable shortcuts

Forum|Forum|5 years ago
January 26, 2021
203 replies
51005 views

The main source of inspiration for this idea was to match the keyboard shortcuts themselves to different keyboard layouts. Right now, users who don’t use US keyboards have to memorize the location of the keys, rather than to use the actual character location to be able to use the shortcuts. Those involving this region are primarily the case:

ABNT2 layout (Brazil).

And here’s an example of confusing shortcuts:

Although this problem could be solved by just rebinding the shortcuts to the actual character and not the location on the keyboard, I’ve noticed there are some other issues concerning key bindings.

On this forum post, a member of the community asked for help on backing one layer level with a different shortcut from what Figma has right now. This makes the user adapt their workflow to the tool, and not the other way around — and that hinders efficiency. It would be nice if the tool itself provided some sort of customization on this regard.

Although being a workaround, Mac users can customize keyboard shortcuts by application, but it is a bit limited. It’s also not a possibility for Windows users.

I think this could be a game-changer, as i’ve seen people who refused to migrate from other tools to Figma because they couldn’t customize shortcuts. It would also give the user more control over the tool and their workflow.

What do you guys think about it?

Share an idea

Show previous replies

Rubem_Pechansky

Active Member

Now the Windows workaround with PowerToys does not work anymore. PowerToys does work for other apps, though. Any answers from the Figma team would be very welcome.

Rotem_Elimelech

Can you please recommend a 3rd party app that does that? I couldn’t find any

RubyComp

Why Figma doesn’t support hotkeys customization? It’s really strange. How I can press “Alt+H” shortcut in ~0.3 sec, if my fingers at ASDF+space position? Maybe, Figma-developers make some video?)

Lukas_Oppermann1

Even though on mac some things can be customised using mac system keyboard commands, things like cursor chat are currently not accessible as they are no menu items and thus can not be called via a mac settings keyboard shortcut.

PLEASE figma, finally work on the keyboard issue, this is really not acceptable for a company this large with so many users world wide.

Gloria_Lin

I too would like to request that F1-F12 be customizable as Figma shortcuts. In order to make the F keys work as a shortcut right now, I have to make the key combination “Command + F* key”. Like why?? I just want to press a single key for my shortcut, not multiple. It’s not like my F keys are even being used for anything else.

Chris_Glick

This is a huge problem for me because I have nerve damage in my hands from keyboard use which means I often miss the key I was trying to hit, or hit the wrong shortcut by mistake.

This becomes a big problem when there are shortcuts that move the viewport to a different location from where I was working without a way to get back. If I could un-bind these “non-undoable” viewport movement hotkeys I wouldn’t have to worry about Figma suddenly teleporting my view to a different file or page or area in my viewport.

I encounter this issue multiple times a day.

Ariel_Cavalcante

@figma @anon21722796 @support Any news on this topic? I’ve been having issues with this for the past year and I can either ask windows to read my keyboard as american and write without acentuations my language has or copy properties and run the last plugin by clicking the right button and selecting the option. Like a savage.

Kai_Magnus

That sounds really bad, I wish they would provide more accessibility features since they’re really lacking in that area.

Also just this week: Figma Releases: ⬌ FigJam usability updates

Jam now uses the same broken shortcuts? Come on…

Tomagochic

Still hoping for an official comment here @anon21722796 how do we fix this? What’s your plan?

This friction I have to endure EVERY SINGLE DAY is driving me mad, and I don’t have the impression that you guys take the issue seriously.

What are you doing to fix this core issue plaguing the product for a very hefty chunk of your user base?

I am seriously tired of being left in the dark by @anon21722796 Just tell us what you’re doing to address this or that you’re not going to fix it, just say something.