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

Focus change when moving keyword up or down #2844

Open
JFoederer opened this issue Aug 7, 2024 · 2 comments
Open

Focus change when moving keyword up or down #2844

JFoederer opened this issue Aug 7, 2024 · 2 comments
Labels
bug Malfunctions that should be fixed to comply with the expected behavior help_wanted If you have suggestions on how to fix, they are welcome prio-low Nice to haves, if we have time and aren't working on something else wontfix Feature requests that don’t align with desired design or no solution is available.
Milestone

Comments

@JFoederer
Copy link
Collaborator

Consider a resource file with multiple keywords. You want to move one of the keywords to a new location using the shortcut keys CTRL+UP or CTRL+DOWN from the tree view.

When moving up a keyword in the resource file, while the grid editor is open, everything works as expected. You can move the keyword up multiple positions until it arrives at the preferred spot.

When moving down a keyword in the resource file, while the grid editor is open, you will see that the editor view gets a refresh every time you move the keyword down one step. In this case you can continue to move the keyword down.

When moving a keyword up or down in the resource file, while the text editor is open, the focus shifts to the text editor and your next key press will move the cursor in the text editor, instead of moving the keyword down the second step.

RIDE v2.1dev64 on Windows and Linux

@HelioGuilherme66 HelioGuilherme66 added the bug Malfunctions that should be fixed to comply with the expected behavior label Aug 7, 2024
@HelioGuilherme66
Copy link
Member

@JFoederer I tried my best to find a fix for this issue, but did not. However, I found that this exists, since at least v2.0.8.1.

Because these are actions that the user can understand how to repeat by clicking the keyword to move, and I did not found a solution to fix, I will mark this as won't fix.

By the way, the Move Up can be done by using Ctrl-Up repeatedly in a short time interval, but not the Ctrl-Down.

@HelioGuilherme66 HelioGuilherme66 added prio-low Nice to haves, if we have time and aren't working on something else wontfix Feature requests that don’t align with desired design or no solution is available. help_wanted If you have suggestions on how to fix, they are welcome labels Aug 12, 2024
@HelioGuilherme66 HelioGuilherme66 added this to the Future milestone Aug 12, 2024
@JFoederer
Copy link
Collaborator Author

Thanks for the effort Helio. I see you added the help_wanted tag. Can you write down what difficulties you ran into? That will help people that want to help to decide whether they think they have the right knowledge to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Malfunctions that should be fixed to comply with the expected behavior help_wanted If you have suggestions on how to fix, they are welcome prio-low Nice to haves, if we have time and aren't working on something else wontfix Feature requests that don’t align with desired design or no solution is available.
Projects
None yet
Development

No branches or pull requests

2 participants