Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Keyboard shortcuts need to consider UserForm and Properties windows #1413

Closed
ThunderFrame opened this issue Apr 30, 2016 · 4 comments
Closed

Keyboard shortcuts need to consider UserForm and Properties windows #1413

ThunderFrame opened this issue Apr 30, 2016 · 4 comments

Comments

@ThunderFrame
Copy link
Member

@ThunderFrame ThunderFrame commented Apr 30, 2016

TIL - When in User Form design mode, or when the Properties Window is active, Ctrl+Shift+X will select the first/next Property name (in the Properties window) that starts with "X", even if the Properties window is not visible.

Rubberduck may need to consider whether to honor this behavior or apply a shortcut, based on the active window. It might need to be a user setting?

@retailcoder
Copy link
Member

@retailcoder retailcoder commented May 9, 2016

Not sure what this is about. How does it affect Rubberduck? Or rather, how does Rubberduck affect this shortcut?

@Vogel612
Copy link
Member

@Vogel612 Vogel612 commented Dec 7, 2017

IIUC what this issue suggests is that Rubberduck Hotkeys with Ctrl + Shift should not trigger in User Form design mode, since the designer already uses that key-combination to select Properties based on their name.

The alternative would be to ignore this behaviour.

@Vogel612 Vogel612 removed the stale label Dec 7, 2017
@ThunderFrame
Copy link
Member Author

@ThunderFrame ThunderFrame commented Dec 7, 2017

Maybe an option in RD settings, to determine the priority of shortcuts when a designer is active?

@bclothier
Copy link
Contributor

@bclothier bclothier commented Jan 17, 2019

The hotkeys are now configurable so this shouldn't be a problem anymore. At minimum open a new issue for where the default for a particular hotkey isn't that great.

@bclothier bclothier closed this Jan 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants