Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 119233

Summary: [StyledText] StyledText.getBaseline(int) gives wrong value in multi-font scenario
Product: [Eclipse Project] Platform Reporter: Dani Megert <daniel_megert>
Component: SWTAssignee: Platform-SWT-Inbox <platform-swt-inbox>
Status: CLOSED WONTFIX QA Contact: Felipe Heidrich <eclipse.felipe>
Severity: normal    
Priority: P3 Keywords: triaged
Version: 3.2   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug
Attachments:
Description Flags
Image showing error squiggles too high none

Description Dani Megert CLA 2005-12-05 06:27:41 EST
As a prototype I enabled multi-font support in the Java editor. It looks like the base line is gives a wrong value (see attached picture).
Comment 1 Dani Megert CLA 2005-12-05 06:28:32 EST
Created attachment 31109 [details]
Image showing error squiggles too high
Comment 2 Felipe Heidrich CLA 2009-08-19 16:10:34 EDT
Your bug has been moved to triage, visit http://www.eclipse.org/swt/triage.php for more info.
Comment 3 Leo Ufimtsev CLA 2017-08-03 12:28:21 EDT
This is a one-off bulk update. (The last one in the triage migration).

Moving bugs from swt-triaged@eclipse to platform-swt-inbox@eclipse.org and adding "triaged" keyword as per new triage process:
https://wiki.eclipse.org/SWT/Devel/Triage

See Bug 518478 for details.

Tag for notification/mail filters:
@TriageBulkUpdate
Comment 4 Eclipse Genie CLA 2020-08-01 18:57:04 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. 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.