Bug 550324 - [mac] Rendering problem in Java editor views with long lines
Summary: [mac] Rendering problem in Java editor views with long lines
Status: CLOSED DUPLICATE of bug 567615
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 4.12   Edit
Hardware: PC Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-08-22 05:28 EDT by Juergen Baier CLA
Modified: 2020-12-28 05:32 EST (History)
3 users (show)

See Also:

Attachments
Second screenshot (scroll back to left) (99.27 KB, image/png)
2019-08-22 05:28 EDT, Juergen Baier CLA 		no flags Details
First screenshot (scroll to right) (18.41 KB, image/png)
2019-08-22 05:30 EDT, Juergen Baier CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Juergen Baier CLA 2019-08-22 05:28:43 EDT 
Created attachment 279656 [details]
Second screenshot (scroll back to left)

I noticed that there are rendering problems when my Java file has long lines (macOS 10.14.6).

The first screenshot shows the effect when I scroll to the right. The second shows how the editor windows looks like when I then scroll back to the beginning.

Not sure if this is related, but code minings are turned on (only "Show parameter names").
Comment 1 Juergen Baier CLA 2019-08-22 05:30:01 EDT 
Created attachment 279657 [details]
First screenshot (scroll to right)
Comment 2 Richard Groote CLA 2020-12-11 08:52:27 EST 
Hello,

I've similar issues but not only in the java editor also in other views, for instance the GIT history view. The text is no longer readable anymore.
Another situation that happened to me is when debugging with Java code, the text was completely messed up. 
The solution for both is to resize the view.

I didn't see this is any other programs, only within eclipse.
It would be nice if there is some solution.

Thanx in advanced.

Richard

Running on MAC Book Pro 10.15.6 (NOT Big Sur)
Comment 3 Richard Groote CLA 2020-12-11 08:52:42 EST 
Hello,

I've similar issues but not only in the java editor also in other views, for instance the GIT history view. The text is no longer readable anymore.
Another situation that happened to me is when debugging with Java code, the text was completely messed up. 
The solution for both is to resize the view.

I didn't see this is any other programs, only within eclipse.
It would be nice if there is some solution.

Thanx in advanced.

Richard

Running on MAC Book Pro 10.15.6 (NOT Big Sur)
Comment 4 Andrey Loskutov CLA 2020-12-11 09:58:58 EST 
(In reply to Richard Groote from comment #3)
> Running on MAC Book Pro 10.15.6 (NOT Big Sur)

Which exact Eclipse version do you use? Can you please try 4.18 RC2?
Comment 5 Richard Groote CLA 2020-12-11 10:15:55 EST 
Hereby my version:

Eclipse IDE for RCP and RAP Developers (includes Incubating components)

Version: 2020-09 (4.17.0)
Build id: 20200910-1200
Comment 6 Richard Groote CLA 2020-12-11 10:18:55 EST 
Could not find rc2 version, but will try eclipse-rcp-2020-12-RC1-macosx-cocoa-x86_64.dmg
Comment 7 Richard Groote CLA 2020-12-17 05:33:49 EST 
I've used the RC1 for awhile now and i've not seen any strange screens anymore.

Most of these issues are probably fixed within the SWT plugin. Are those fixes also available within earlier versions of eclipse. The reason for this question is, we're developing a eclipse RCP application and that is currently running on java 8 and 2018-12 SimRel target platform and i see similar issue there.
In the near future we are going to upgrade to 2020-06 and hope that most of the issues are then resolved.
Comment 8 Juergen Baier CLA 2020-12-17 07:01:16 EST 
I cannot reproduce this anymore with 4.18.
Comment 9 Lakshmi P Shanmugam CLA 2020-12-28 05:32:30 EST 
(In reply to Juergen Baier from comment #8)
> I cannot reproduce this anymore with 4.18.

Thanks for the confirmation. Looks like duplicate of Bug 567615, fixed in 4.18.

*** This bug has been marked as a duplicate of bug 567615 ***