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
Braille doesn't scroll to same-line search result in Notepad #5410
Comments
Comment 1 by dkager on 2015-10-15 19:17 |
Comment 2 by dkager on 2015-10-18 12:01 |
Comment 3 by dkager on 2015-10-18 18:31 |
Comment 4 by jteh on 2015-10-21 05:07 Also, I'd rather not have TextInfoRegion specific code there. One solution is to set brailleCursorPos and have a showCursor attribute which could be set to False for selection. However, Since some users want selection to be indicated with dots 7 and 8 for list items (#1953), I guess the best solution is to have selectionStart/End and brailleSelectionStart/End attributes in Region and have Region.update handle the underlining instead of TextInfoRegion.update. The patch for #1953 is then pretty trivial. Let me know if you're willing to do this. Otherwise, I'll do it when I get some time. |
Comment 5 by dkager on 2015-10-21 06:42 |
Comment 6 by dkager on 2015-10-24 18:59 |
* Move the marking of a selection to braille.Region. * Add Region.brailleSelectionStart/End. * If there is a selection but not a cursor, e.g. in a TextInfoRegion, scroll the braille display to the selection start.
Code is now here on GitHub. I'll drop the BitBucket repo linked to in earlier comments. |
… (e.g. when searching in a text editor for text which occurs on the same line), the braille display will be scrolled if appropriate. On a pending caret move if there is no cursor, try to scroll the braille display to the selection. * Move the marking of a selection to braille.Region. * Add Region.brailleSelectionStart/End. * If there is a selection but not a cursor, e.g. in a TextInfoRegion, scroll the braille display to the selection start. Fixes #5410.
Incubated in f53054b. |
Ug. I was reviewing #5198 and discovered that the selection indicator still shows when the cursor is disabled. I just realised that even with this fixed, the selection indicator doesn't appear/disappear when you toggle the option from a script, since the region isn't updated.
|
Very quick comment (more this afternoon when I have time to read the other comments in #5198): it wasn’t my intention to also disable the selection indicator when the cursor is toggled off. It is arguably not the same thing as a cursor indicator. Even without a blinking cursor I might still want to know what I selected in an edit control. From: James Teh [mailto:notifications@github.com] Ug. I was reviewing #5198 #5198 and discovered that the selection indicator still shows when the cursor is disabled. I just realised that even with this fixed, the selection indicator doesn't appear/disappear when you toggle the option from a script, since the region isn't updated.
— |
I'm confused. In #5198, I wrote:
And you replied:
So, is this a re-think or am I missing something? |
This is a re-think, I don’t want to fall into the trap of emulating an existing product. I’ll give it some serious thought and come up with a proper argument in #5198. From: James Teh [mailto:notifications@github.com] I'm confused. In #5198 #5198 , I wrote: I think the command should toggle both the cursor and selection. And you replied: I agree. ... SuperNova also uses one command to toggle both. So, is this a re-think or am I missing something? — |
* On a pending caret move if there is no cursor, try to scroll the braille display to the selection. * Move the marking of a selection to braille.Region. * Add Region.brailleSelectionStart/End. * If there is a selection but not a cursor, e.g. in a TextInfoRegion, scroll the braille display to the selection start. * Add a global command to move braille to the focus, and the caret or cursor within the focus object if possible. * If tethered to review, move braille to the focus object. * Otherwise, move braille to the main buffer's last region, which should contain the focus. If it has a cursor/caret, scroll to it. If instead it has a selection, scroll to that. * Check that there are actually some regions before selecting one. * If no cursor is found, try scrolling to the selection. Requires #5410. * Make the script documentation a bit clearer. * Sync submodules.
Reported by dkager on 2015-10-11 20:03
STR:
The text was updated successfully, but these errors were encountered: