- Added support for libavcodec 59.
- libavcodec 59 removed several deprecated APIs and avplugin code was updated
to use replacement APIs instead.
- No changes to avplugin when used with 58 or below.
- Note: Support for libavcodec 59 was added based on ffmpeg only. libav does
not have version 5
I guess everything you’ve written below about querying and requesting features
still falls into the hole of “stuff we could do with Swing, but can’t do with
JavaFX”. I don’t use Swing anymore, but every once in a while I run into one
of these issues. There are workarounds for some, like NSMenuF
> This cleans size and positioning code, reducing special cases, code
> complexity and size.
>
> Changes:
>
> - cached extents: 28, 1, 1, 1 are old defaults - modern gnome uses different
> sizes. It does not assume any size because it varies - it does cache because
> it's unlikely to vary on t
> This cleans size and positioning code, reducing special cases, code
> complexity and size.
>
> Changes:
>
> - cached extents: 28, 1, 1, 1 are old defaults - modern gnome uses different
> sizes. It does not assume any size because it varies - it does cache because
> it's unlikely to vary on t
> This cleans size and positioning code, reducing special cases, code
> complexity and size.
>
> Changes:
>
> - cached extents: 28, 1, 1, 1 are old defaults - modern gnome uses different
> sizes. It does not assume any size because it varies - it does cache because
> it's unlikely to vary on t
FX does (of course) support required ligatures, meaning those without
which some script (eg Arabic)
can't even be rendered.
But that is implementation, no API.
So this is about adding an API to request optional ligatures - and other
OpenType features.
For example I think we'd want to support
Something I noticed while experimenting with RichTextFX, when I set it to use
Fira Code for the font, like I do in NetBeans, I see that JavaFX doesn't
support ligatures. I found this issue that's been around for quite some time:
https://bugs.openjdk.org/browse/JDK-8091616
Is there any drive to
On Mon, 24 Oct 2022 14:51:55 GMT, Thiago Milczarek Sayao
wrote:
>> This cleans size and positioning code, reducing special cases, code
>> complexity and size.
>>
>> Changes:
>>
>> - cached extents: 28, 1, 1, 1 are old defaults - modern gnome uses different
>> sizes. It does not assume any si
> This cleans size and positioning code, reducing special cases, code
> complexity and size.
>
> Changes:
>
> - cached extents: 28, 1, 1, 1 are old defaults - modern gnome uses different
> sizes. It does not assume any size because it varies - it does cache because
> it's unlikely to vary on t
> This cleans size and positioning code, reducing special cases, code
> complexity and size.
>
> Changes:
>
> - cached extents: 28, 1, 1, 1 are old defaults - modern gnome uses different
> sizes. It does not assume any size because it varies - it does cache because
> it's unlikely to vary on t
> This cleans size and positioning code, reducing special cases, code
> complexity and size.
>
> Changes:
>
> - cached extents: 28, 1, 1, 1 are old defaults - modern gnome uses different
> sizes. It does not assume any size because it varies - it does cache because
> it's unlikely to vary on t
> This cleans size and positioning code, reducing special cases, code
> complexity and size.
>
> Changes:
>
> - cached extents: 28, 1, 1, 1 are old defaults - modern gnome uses different
> sizes. It does not assume any size because it varies - it does cache because
> it's unlikely to vary on t
12 matches
Mail list logo