Bug 283057

Summary: reverse text decorator Z-order to help small displays
Product: [Eclipse Project] Platform Reporter: James Mitchell <jimdesu>
Component: SWTAssignee: Felipe Heidrich <eclipse.felipe>
Status: NEW --- QA Contact:
Severity: enhancement    
Priority: P3 CC: daniel_megert, eclipse.felipe
Version: 3.5   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:
Attachments:
Description Flags
file showing partially obscured typeface fragments none

Description James Mitchell CLA 2009-07-09 13:55:56 EDT 
(Apologies in advance if I've filed this in the wrong place.)

On small displays that use small font-sizes, the spiffy decorators that the editor applies to characters, such as the box or wavy underline can tend to obscure a significant amount of the characters themselves, especially for full-height characters or those with descenders like "g".  Would it be possible to have the decorators painted first, then the characters painted over them, instead of the other way around?

This would really enhance legibility on notebook computers and others with small displays.
Comment 1 Dani Megert CLA 2009-07-13 10:01:36 EDT 
We use StyleRanges. No plans to change that. Moving to SWT for comment about setting the drawing order.
Comment 2 Felipe Heidrich CLA 2009-07-14 10:26:16 EDT 
Where are you having this problem ? (windows/mac/gtk)

Can you attach a screenshot too ?
Thanks
Comment 3 James Mitchell CLA 2009-07-14 15:09:14 EDT 
Eclipse on Windows.  Typeface is Terminal 6pt.

I'll turn on the decorators again and load a picture in a moment.
Comment 4 James Mitchell CLA 2009-07-14 15:25:32 EDT 
Created attachment 141559 [details]
file showing partially obscured typeface fragments

As you can see, most of the partially obscured text is easily guessable, but that's much less facile than simply being able to read the text.
Comment 5 James Mitchell CLA 2009-07-15 17:44:26 EDT 
Oh, I didn't think to show it, but word underlines can exactly obscure underscores too.
Comment 6 Eclipse Webmaster CLA 2019-09-06 16:07:09 EDT 
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.

If you have further information on the current state of the bug, please add it. 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.