Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 351224 - FontRegistry caches based on potentially incomplete font spec
Summary: FontRegistry caches based on potentially incomplete font spec
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Scout (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-05 13:04 EDT by Ivan Motsch CLA
Modified: 2021-08-19 10:57 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 Ivan Motsch CLA 2011-07-05 13:04:58 EDT 
The class FontRegistry is called by ISwtEnvironment.getFont and 
caches the font based on FontSpec.toPattern().
If the font spec is just a partial spec then the used cache key is ambiguous.
Comment 1 Ivan Motsch CLA 2011-07-05 13:17:31 EDT 
Fixed by completing newName, newStyle, newSize with template font values if null. The cache key is the concatenation of the three non-null values.
Comment 2 Matthias Zimmermann CLA 2012-07-09 06:50:08 EDT 
ticket closed.
deliverd as part of eclipse scout 3.8.0 (juno release train)