> On Oct 27, 2026, at 9:55 AM, Marius Hanl <[email protected]> wrote:
>
> Martin,
>
> interesting! I'm on KDE 6.8. I usually always use the newest JavaFX ea
> versions. It was 28-ea+11 back then. Still reproducable for me.
>
> Setup:
> - Left Built-in Screen with 125% (2560x1600)
> - Right external Screen with 100% (2560x1080)
You’re using a KDE version which was released two weeks ago so I can’t easily
reproduce your environment. The Xwayland version might be more relevant (I’m
running 24.1.10).
Xwayland doesn’t support per-monitor scaling because X11 doesn't. It can only
use one global scaling factor. When I set up per-monitor scaling the scaling
factor reported to JavaFX seems to be the ceiling of the greatest scale factor.
If the scaling is 100% and 125% I get a scaling factor of 2.0 for both
monitors. Still, when I have “Apply scaling themselves” JavaFX is not blurry,
it’s just at the wrong scale on at least one monitor (sometimes both). This is
the behavior I see on both Ubuntu 26 with Gnome and KDE and the behavior I
expect from JavaFX. Not sure why your system acts differently.
Martin
> -- Marius
>
> On 10/26/26 4:25 PM, Martin Fox wrote:
>> Marius,
>>
>> For the blurriness could you tell me which version of JavaFX and KDE you’re
>> running? With the latest version of JavaFX and Plasma 6.6 I see the opposite
>> of what you describe. “Scaled by the system” produces poor results and
>> “Apply scaling themselves” looks fine.
>>
>> KDE and JavaFX have a long history when it comes to High-DPI support. I
>> sorted out some of this last December (can’t recall which JavaFX version
>> that was).
>>
>> Martin
>>
>>> On Oct 24, 2026, at 10:12 PM, Thiago Milczarek Sayão
>>> <[email protected]> wrote:
>>>
>>> Xorg is being phased out, but the X11 protocol is still available through
>>> XWayland.
>>>
>>> I wasn't aware of this issue with KDE. Maybe I can take a look and try to
>>> fix it.
>>>
>>> Let's see how the AI usage policy evolves. I understand that the current
>>> policy is provisional and necessary for now. However, AI tools have made
>>> significant progress, and the code generated for this experiment is of good
>>> quality. It would be much easier to review the code and replace any
>>> questionable parts.
>>>
>>> For this experiment, I went with Vulkan. However, I also worked on an EGL
>>> implementation for ES2 some time ago, without using AI, so the rendering
>>> side is covered.
>>>
>>> Thanks for offering to help!
>>>
>>> -- Thiago
>>>
>>>
>>> Em sáb., 24 de out. de 2026 às 23:20, Marius Hanl <[email protected]>
>>> escreveu:
>>>
>>>> Good to see progress on that. I think for the long term, we should
>>>> really start implementing the Wayland backend in JavaFX.
>>>>
>>>> I saw that many other Open Source Frameworks did implement Wayland
>>>> support by now (or made it the default). So I really think we should
>>>> follow. The time seems to be right.
>>>> Also, it seems that some services and/or platforms start to phase out
>>>> X11 support bit by bit.
>>>>
>>>> On KDE, I was surprised that JavaFX looks very blurry, which is due to
>>>> scaling. Changing 'Legacy applications (X11)' to 'Scaled by the system'
>>>> fixes it. It seems that only JavaFX really suffers from it, because
>>>> everything else already seems to use Wayland or another approach. In any
>>>> case, for users not aware of this setting the experience will be rather
>>>> bad, at least on KDE.
>>>>
>>>> Thiago, if you need some help (code/review) or just more testing, feel
>>>> free to ping me.
>>>> I'm willing to invest some time into it. Maybe we find more people
>>>> interested, so that we get some results, similar as for the Direct3D12
>>>> backend.
>>>>
>>>>
>>>> -- Marius
>>>>
>>>>
>>>> On 10/24/26 3:10 AM, Thiago Milczarek Sayão wrote:
>>>>> I couldn't wait until I had everything fully implemented, so I took a
>>>>> shortcut to see how it would look and if it would fully work.
>>>>>
>>>>> So, here it is: JavaFX running 100% on Wayland, with either Vulkan or
>>>>> OpenGL rendering.
>>>>>
>>>>> https://github.com/tsayao/jfx-wayland
>>>>>
>>>>> We can reuse some of the ideas, but not the code.
>>>>>
>>>>> I kept it in a separate repository to avoid any legal issues. If I've
>>>> still
>>>>> made any mistakes in that regard, please let me know and I'll fix them.
>>>>>
>>>>> Regardless, it was an interesting experiment.
>>>>>
>>>>>
>>>>> -- Thiago
