Community
Participate
Working Groups
When I'm in block selection and refactor a variable name the cursor jumps to the first line after entering the first letter. See the link below for an example video. http://www.vidup.de/v/SmVkK/ This happens with the Luna SR0.
I think this is a bug in StyledText: We call StyledText.setCaretOffset(int) this clears the block selection and this sets blockXAnchor = blockYAnchor = -1; As a result the next insertBlockSelectionText(...) call causes the block selection to the first line.
Created attachment 253205 [details] Partially working patch. This bug needs more investigation, moving out of Mars.
Another situation where the issue occurs: 1. switch to block selection 2. type "if(" 3. ")" is inserted automatically 4. type "a" Bug: "a" is inserted in first line; cursor does not scroll into view! I've set a conditional breakpoint in StyledTest.setCaretOffset() in first line with condition offset == 0 to let the debugger stop in this situation. Unfortunately, I do not understand what happens before and what leads to the issue, but maybe this helps you to debug, too. Best regards, Thomas
(In reply to Thomas Schulze zur Wiesch from comment #3) > Another situation where the issue occurs: > 1. switch to block selection > 2. type "if(" > 3. ")" is inserted automatically > 4. type "a" > Bug: "a" is inserted in first line; cursor does not scroll into view! > > I've set a conditional breakpoint in StyledTest.setCaretOffset() in first > line with condition offset == 0 to let the debugger stop in this situation. > Unfortunately, I do not understand what happens before and what leads to the > issue, but maybe this helps you to debug, too. > > Best regards, > Thomas Raised separate bug 481085 to trace this issue.
This bug needs more investigation, moving it out of Neon.
*** Bug 496686 has been marked as a duplicate of this bug. ***
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.