Community
Participate
Working Groups
20021126 As of build 20021203 the eclipse workbench will now support declarative fonts. This will eliminate the need for the PropogatingFontFieldEditor. There is a new extension point fontDefinition for defining fonts so that they can be viewed and managed by the workbench fonts preference page. There is also a defaultTo attribute which when set keeps the entry for the fontDefinition consistent with the defaultsTo entry if the preference for the fontDefinition is not set. For example if a font called org.eclipse.myplugin.textfont had a defaultsTo of org.eclipse.jface.textfont the value in the font registry for org.eclipse.myplugin.textfont will be the same as the value for org.eclipse.jface.textfont until the user sets a preference for org.eclipse.myplugin.textfont . see the org_eclipse_ui.fontDefinition doc for more details
*** Bug 26985 has been marked as a duplicate of this bug. ***
Not for RC1
Waiting for better fix...
What do you mean by a better fix? Is there a requirement of the font support you have?
See bug 32921.
[Oops, made comments to wrong bug. My last two comments were for bug 26990. For this one I don't need a better fix :-]
reopened for 2.1
fixed > 20030304