Bug 68082 - [api] Need ability to set font in text editor
Summary: [api] Need ability to set font in text editor
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Platform-Text-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-21 15:47 EDT by Amy Wu CLA
Modified: 2019-09-04 01:56 EDT (History)
0 users

See Also:

Attachments
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 Amy Wu CLA 2004-06-21 15:47:49 EDT 
There is no nice way to set the font in a text editor.

AbstractTextEditor's getSymbolicFontName and getFontPropertyPreferenceKey 
should be made into protected methods that subclasses can override.

I came across this problem because I have a text editor as part of a 
multipageeditorpart, and there is no way for me to assign a symbolic font name 
to the text editor when it is in the MultiPageEditor.  I define both the 
MultiPageEditorPart and the stand-alone text editor using the 
org.eclipse.ui.editors extension point and I provide an editor font using the 
symbolicFontName attribute in the extension point.  But neither are being used 
when I have a text editor inside a MultiPageEditor.
Comment 1 Dani Megert CLA 2004-06-22 02:42:14 EDT 
I agree that this would help in your scenario, but it does still not allow you
to declare the fonts for each sub-editor if there is more than one in the
multi-page editor.

The more general problem is covered in bug 68082.
Comment 2 Amy Wu CLA 2004-07-20 20:50:58 EDT 
In regards to the above comment.  This is bug 68082.  Did you mean to 
reference another bug?
Comment 3 Dani Megert CLA 2004-07-22 08:47:56 EDT 
Sorry, of course. It's bug 37718.
Comment 4 Lars Vogel CLA 2019-09-04 01:56:36 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 and remove the stalebug whiteboard tag. 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.

--