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

Usability improvement: Editor hotkeys #3925

Closed
polezhaevdmi opened this issue Jun 14, 2017 · 1 comment
Closed

Usability improvement: Editor hotkeys #3925

polezhaevdmi opened this issue Jun 14, 2017 · 1 comment
Labels
type: enhancement Something could be better than it currently is

Comments

@polezhaevdmi
Copy link

Target: RT 5 and above.
Goal: increase GUI usability for photographers.
Suggestions:

  • Make the RT keyboard shortcuts editable and document the way to edit them. Or, at least, add in SETM the synonims for "Shift+F3"/"Shift+F4" keys as "RightArrow"/"LeftArrow". Just because the frequent use of F-keys in a multiimage workflow is extremely boring. The Shift/Alt/Ctrl+"RightArrow"/"LeftArrow" combinations also acceptable.
  • The "Delete" key in Editor should put the active file into Trash AND automatically open NEXT available file, which is NOT marked as Trash. Now the Trash morking looses the focus in Filmstrip and makes the further movement impossible (seems, coupled with issue RT 5.1 on Windows 7 x64: can't delete raw file while in editor tab #3904 ). The Filmstrip "activity" mark should reflect the file, which is loaded in Editor.
  • The Filmstrip should "predict" the Editor file opening sequence by giving more stip space to "movement" direction. For example, when the "RightArrow" is pressed, the current opened file should be placed at about 1/3th distance from left to right. Otherwise, when the "LeftArrow" is pressed, the "active" file should be at 1/3th from right to left. This will give much information about image sequence to operator.

Thank You!

@Beep6581 Beep6581 added the type: enhancement Something could be better than it currently is label Jun 18, 2017
@Beep6581
Copy link
Owner

Beep6581 commented Sep 6, 2019

Duplicate of #1472, and point 3 was done in 5.6 or so. In the future, open 1 issue per issue.

@Beep6581 Beep6581 closed this as completed Sep 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement Something could be better than it currently is
Projects
None yet
Development

No branches or pull requests

2 participants