On Tue, 1 Feb 2022 21:40:53 GMT, Dmitry Batrak wrote:
>> The proposed fix makes fonts with and without fallback components
>> distinguishable (in terms of `equals` method), so that
>> font metrics cache (and other similar code) can handle them separately. This
>> is achieved by adding a new boo
On Tue, 1 Feb 2022 21:40:53 GMT, Dmitry Batrak wrote:
>> The proposed fix makes fonts with and without fallback components
>> distinguishable (in terms of `equals` method), so that
>> font metrics cache (and other similar code) can handle them separately. This
>> is achieved by adding a new boo
On Thu, 24 Mar 2022 02:49:49 GMT, Phil Race wrote:
>> Dmitry Batrak has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> remove 'headful' requirement from test case
>
> I know .. I know .. I just (a) don't like it, and (b) don't have a good
On Tue, 1 Feb 2022 21:40:53 GMT, Dmitry Batrak wrote:
>> The proposed fix makes fonts with and without fallback components
>> distinguishable (in terms of `equals` method), so that
>> font metrics cache (and other similar code) can handle them separately. This
>> is achieved by adding a new boo
On Tue, 1 Feb 2022 21:40:53 GMT, Dmitry Batrak wrote:
>> The proposed fix makes fonts with and without fallback components
>> distinguishable (in terms of `equals` method), so that
>> font metrics cache (and other similar code) can handle them separately. This
>> is achieved by adding a new boo
On Sun, 6 Feb 2022 19:53:45 GMT, Phil Race wrote:
>> Dmitry Batrak has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> remove 'headful' requirement from test case
>
>> As you say, one could possibly also try to compare font2DHandle-s instead
On Tue, 1 Feb 2022 21:40:53 GMT, Dmitry Batrak wrote:
>> The proposed fix makes fonts with and without fallback components
>> distinguishable (in terms of `equals` method), so that
>> font metrics cache (and other similar code) can handle them separately. This
>> is achieved by adding a new boo
On Tue, 1 Feb 2022 21:40:53 GMT, Dmitry Batrak wrote:
>> The proposed fix makes fonts with and without fallback components
>> distinguishable (in terms of `equals` method), so that
>> font metrics cache (and other similar code) can handle them separately. This
>> is achieved by adding a new boo
On Wed, 2 Feb 2022 21:29:28 GMT, Sergey Bylokhov wrote:
>> src/java.desktop/share/classes/java/awt/Font.java line 1861:
>>
>>> 1859: pointSize == font.pointSize &&
>>> 1860: withFallback == font.withFallback &&
>>> 1861: name.equals(font.name)) {
>
On Wed, 2 Feb 2022 18:32:10 GMT, Phil Race wrote:
> Serialization of Font objects is just serializing the fields liek name and
> style and size but there's no guarantee that it will behave the same .. I
> mean if I serialize Segoe UI on WIndows and try to deserialize it on Linux
> nothing in t
On Tue, 1 Feb 2022 21:40:53 GMT, Dmitry Batrak wrote:
>> The proposed fix makes fonts with and without fallback components
>> distinguishable (in terms of `equals` method), so that
>> font metrics cache (and other similar code) can handle them separately. This
>> is achieved by adding a new boo
> The proposed fix makes fonts with and without fallback components
> distinguishable (in terms of `equals` method), so that
> font metrics cache (and other similar code) can handle them separately. This
> is achieved by adding a new boolean field
> to `Font` class, specifically denoting fonts wi
On Tue, 1 Feb 2022 19:50:47 GMT, Sergey Bylokhov wrote:
>> The proposed fix makes fonts with and without fallback components
>> distinguishable (in terms of `equals` method), so that
>> font metrics cache (and other similar code) can handle them separately. This
>> is achieved by adding a new b
On Tue, 1 Feb 2022 19:47:59 GMT, Sergey Bylokhov wrote:
>> The proposed fix makes fonts with and without fallback components
>> distinguishable (in terms of `equals` method), so that
>> font metrics cache (and other similar code) can handle them separately. This
>> is achieved by adding a new b
On Tue, 1 Feb 2022 18:38:39 GMT, Dmitry Batrak wrote:
> The proposed fix makes fonts with and without fallback components
> distinguishable (in terms of `equals` method), so that
> font metrics cache (and other similar code) can handle them separately. This
> is achieved by adding a new boolean
The proposed fix makes fonts with and without fallback components
distinguishable (in terms of `equals` method), so that
font metrics cache (and other similar code) can handle them separately. This is
achieved by adding a new boolean field
to `Font` class, specifically denoting fonts with fallbac
16 matches
Mail list logo
