Summary: | keyboard navigation in auto complete does not works as expected | ||
---|---|---|---|
Product: | [Applications] rkward | Reporter: | mho94v+3w6u2x0n9t6xjry3upq3n9b58t2oa4rvy9sa7s5ki6wngzw4ux2c0g |
Component: | User Interface | Assignee: | RKWard Team <rkward-devel> |
Status: | REPORTED --- | ||
Severity: | normal | CC: | thomas.friedrichsmeier |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Debian unstable | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
mho94v+3w6u2x0n9t6xjry3upq3n9b58t2oa4rvy9sa7s5ki6wngzw4ux2c0g
2020-10-06 09:07:38 UTC
Thanks for reporting. The default key combination to navigate completions is set to Alt+Up/Down in RKWard, while Up/Down navigates the script, whether or not completions are shown. This may be a debatable choice, but in the upcoming RKWard 0.7.2, the R Console Window will share the same completion interface. Here, keeping the default Up/Down-behavior to navigating the command history seemed rather important. And then it seemed reasonable to use a consistent key-binding for navigating the completion list in both cases. The setting is configurable in Settings->Configure RKWard->(Script editor/Console). Perhaps you have an idea, where/how you would have been more likely to find the setting? Wow - that was a fast answer! Thanks a lot! This was something that had driven me mad in past a few times. And such an easy solution (/me hides under some rock in shame). I guess the reason I didn't notice the setting, is that when I parsed the whole configuration and its tabs and sections and everything, my brain skipped this tiny little item, as it noticed it only as some section headline. I totally missed the checkbox on the side. So my proposal would be try to move the checkbox to the other side, so it aligns with the drop-downs below. Not sure if it works, but maybe worth a try? Also maybe adding a list of useful keyboard shortcuts to the FAQ. I like this kinds of lists a lot, they are not only a quick reference to the keys, but also give some hints on functions I haven't discovered yet. See for example https://inkscape.org/sk/doc/keys.html And I guess there is an maybe halfway easy way to extract this from the code. For example by putting an description near the code where the keycode is assigned. Doxygen is just one way to extract documentation from code comments. |