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

Use additional mouse buttons to go back/forward in inspector history #19772

Closed
BeayemX opened this issue Jun 25, 2018 · 3 comments
Closed

Use additional mouse buttons to go back/forward in inspector history #19772

BeayemX opened this issue Jun 25, 2018 · 3 comments

Comments

@BeayemX
Copy link
Contributor

BeayemX commented Jun 25, 2018

Godot version:

All versions

Issue description:

Some mice have additional buttons that usually are mapped to go back or forwad in a web browser. Would it be possible to use those buttons to go to previous edited / next edited object in history in the inspector when navigating through subresources?

@Zylann
Copy link
Contributor

Zylann commented Jun 26, 2018

If that's possible, I'd like this to be an option, since I use those buttons for other purposes.

@vnen
Copy link
Member

vnen commented Jun 27, 2018

The problem is that it's not possible to set mouse buttons as shortcuts, only keys.

@akien-mga
Copy link
Member

Feature and improvement proposals for the Godot Engine are now being discussed and reviewed in a dedicated Godot Improvement Proposals (GIP) (godotengine/godot-proposals) issue tracker. The GIP tracker has a detailed issue template designed so that proposals include all the relevant information to start a productive discussion and help the community assess the validity of the proposal for the engine.

The main (godotengine/godot) tracker is now solely dedicated to bug reports and Pull Requests, enabling contributors to have a better focus on bug fixing work. Therefore, we are now closing all older feature proposals on the main issue tracker.

If you are interested in this feature proposal, please open a new proposal on the GIP tracker following the given issue template (after checking that it doesn't exist already). Be sure to reference this closed issue if it includes any relevant discussion (which you are also encouraged to summarize in the new proposal). Thanks in advance!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants