Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 317742 - StyledText moves caret to wrong position on down arrow in lower left corner
Summary: StyledText moves caret to wrong position on down arrow in lower left corner
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.6.2   Edit
Hardware: Macintosh Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2010-06-23 15:20 EDT by Doug M CLA
Modified: 2020-02-24 12:05 EST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Doug M CLA 2010-06-23 15:20:41 EDT
Using swt-I20100608-0911-cocoa-macosx-x86_64/Mac OS 10.6.4

With caret in lower left corner of editable area, type down arrow. Caret moves to one space past end of the line above. It should stay where it is.

Typing into Snippet213 will demonstrate the error.
Comment 1 Scott Kovatch CLA 2010-06-28 13:50:11 EDT
Confirmed in HEAD. For me the cursor seems to disappear as opposed to move back to the previous line.
Comment 2 Felipe Heidrich CLA 2010-06-29 12:48:00 EDT
Yes, this is a bug in StyledText.

StyledText uses the idea of caret alignment when the position of the caret offset is ambiguous (end/start of wrapped lines, boundary bidi direction).

caret alignment is either caret offset lead or previous caret offset trail.

In this case the correct alignment is caret offset lead. During line down the framework wrongly sets the alignment to default (which is previous offset trail).
Comment 3 Lakshmi P Shanmugam CLA 2017-07-03 07:46:45 EDT
Bug triaged, visit https://wiki.eclipse.org/SWT/Devel/Triage for more
information.
Comment 4 Eclipse Genie CLA 2020-02-24 04:14:45 EST
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.
Comment 5 Doug M CLA 2020-02-24 12:05:58 EST
Dear Eclipse Genie,

Thank you for automatically closing the bug report that I filed in 2010, almost ten years ago, without ever fixing it. At this point, I have moved on to other interests. The desktop app I was working on in 2010 was a complete failure, due to the numerous bugs in SWT's text handling, many of which could not be worked around. The response of SWT's developers was glacial or entirely non-existent. 

I can truly say that choosing SWT over Swing for this project was the worst design decision I have ever made in my long career. I am sure that SWT is highly tuned to the limited needs of Eclipse, but as a UI for general apps it is unfit for purpose. This fact should be declared upfront to preclude any other naive developer from making a similar disastrous decision.

Thanks for listening, if anyone is.