wakefield: MainWindow WLToolkit CCE fix#9004
Conversation
yep the JBR SDK ships wakefield. I prefer the most direct approach to test things though. Building JDKs is super easy. |
the first workaround makes sense to me and is mostly harmless. I can't access the second issue unfortunately so I don't know if it makes sense to keep it. But its probably ok to stay as long X11 still exists, removing edit: archive.org to the rescue! lets take another look |
|
regarding #198639 / archive (the second workaround which was also the cause of the startup error). I believe the better option there is to remove the workaround entirely. It could cause side effects and it appears that it was implemented for GTK LAF + old gnome version + X11 specifically, without checking if it is even active. E.g users reported that switching to metal fixed it - which should also apply to FlatLAF. The more encapsulation breaking hacks we get rid off the better. Will update the PR. |
remove old GTK workaround which causes launch failure with wayland toolkit active (-Dawt.toolkit.name=WLToolkit) old bugzilla issue ID: 198639
language level and IDE warning fixes
fec6bba to
496f09a
Compare
|
@mbien followed your great instructions, but did not build this PR but ran "vanilla" 27 and it works nicely. What you see "popups are all over the place and some overlays" etc may be the fact that I have AMD and you NVidia? For me it just works. Started with NB27 "trick" as @neilcsmith-net pointed out to me: |
|
@cstamas thanks for testing! Yeah my system isn't a good indicator since I am still using cinnamon where wayland support is still considered experimental. I do actually like how simple and stable the window manager is, but if this doesn't improve with the upcoming releases I will switch to something else at some point. |
first commit is the fix, second is just cleanup
only run x11 workarounds when x11 toolkit is active-Dawt.toolkit.name=WLToolkit)The
#183739might be still useful, unfortunately I don't know what#198639does since bugzilla isn't loading the issue for me. edit: see #9004 (comment)symptom: startup failure
Details
I don't think project wakefield has made builds available yet, so to test this (linux+wayland) it would require the following:
start nb using the wakefield JDK with the following flags:
you should see something like this in the log instead of the exception:
Doesn't look great on my system though. Something is wrong with the font AA, popups are all over the place and some overlays (e.g editor highlighting layer) don't work. It runs at least.
thanks to @cstamas for noticing this.