|
|
Assigned to Rusty to review wording, probably with 5.0.1 target ? |
|
|
If we keep the current wording it could look like: When typing in a view: [Filter matches/Scroll to match/Take no action] [x] Show results after pressing ENTER HOWEVER, The current UI 'when typing in a view' implies that something always happens when typing--which is no longer the case. To make it a bit clearer, we might want to switch to the wording/structure slightly: Search current view Search mode: _Filter matches, Scroll to match_ Show results: _while typing, after pressing ENTER, only when using the Search bar_ btw, if we wanted to address the other issue raised by drakinite, we could modify search modes as follows: Search mode: _Filter matches, Scroll to match (primary sort field), Scroll to match (all displayed fields)_ My personal opinion is that the current approach of limiting Scroll to: to the primary sort field is confusing for most users (especially considering that 'powerscroll' has been added back to the tree for users who want it). |
|
|
BTW: With some language options/locales like "Dutch" and "The Netherlands" the Ctrl+Alt+M hotkey results in typing the character 'ยต' -- deatils in [Ticket # 4835] So the current workaround is to redefine the hotkey or to have the option to "Take no action" when typing. |
|
|
image-2.png (21,798 bytes) |
|
|
Implemented in 5.1.0.2800 Because the 'Show results after pressing ENTER' can be useful also in case of global search then I added it above the 'Search current view' section (see the image above). Default state is disabled for the checkbox. As for the options to enhance 'Scroll to match' , this is tracked separately as 0019457 Just a small wording change suggestion: 'Show results after pressing ENTER' => 'Show results only after pressing ENTER' to be clearer => changed in build 2800 |
|
|
Verified 2803 Added ToTranslate TAG |
- Anonymous
