Closed ghost closed 2 months ago
I am not able to reproduce this behavior. However I tried it Java not Scala, on Ubuntu not Fedora, with Qt 5.15.13 not 5.15.14.
This is most likely not a QtJambi bug. Either it is a matter of addressing the methods from Scala or of Qt on your system.
What happens if you start the application with argument -platform xcb
?
I am not able to reproduce this behavior. However I tried it Java not Scala, on Ubuntu not Fedora, with Qt 5.15.13 not 5.15.14. This is most likely not a QtJambi bug. Either it is a matter of addressing the methods from Scala or of Qt on your system. What happens if you start the application with argument
-platform xcb
?
It seems that -platform xcb
solves the problem with the decorations.
I don't think you'd be able to reproduce this issue if you deliberately choose not to use identical configuration to set it up, like using Scala over Java (despite being JVM) oder a RedHat-based distribution of Linux.
EDIT: You do however lose out on HiDPI scaling, so now you'd have to deliberately resize the window twice to get the exact same resolution you'd get if it was properly scaled. Perhaps this ist a bug with GNOME Wayland on certain distributions, oder a bug with Qt itself?
I am not able to reproduce this behavior. However I tried it Java not Scala, on Ubuntu not Fedora, with Qt 5.15.13 not 5.15.14. This is most likely not a QtJambi bug. Either it is a matter of addressing the methods from Scala or of Qt on your system. What happens if you start the application with argument
-platform xcb
?It seems that
-platform xcb
solves the problem with the decorations.I don't think you'd be able to reproduce this issue if you deliberately choose not to use identical configuration to set it up, like using Scala over Java (despite being JVM) oder a RedHat-based distribution of Linux.
Yes I agree. However I don't have you configuration available on the fly. Since Xcb behaves as expected I think it's something between Qt and Wayland or specific to Fedora. I suggest to search specific Qt forums for this issue.
In general, you don't need to set window flags at all to let min/max/close appear. It shows up by default.
I am not able to reproduce this behavior. However I tried it Java not Scala, on Ubuntu not Fedora, with Qt 5.15.13 not 5.15.14. This is most likely not a QtJambi bug. Either it is a matter of addressing the methods from Scala or of Qt on your system. What happens if you start the application with argument
-platform xcb
?It seems that
-platform xcb
solves the problem with the decorations. I don't think you'd be able to reproduce this issue if you deliberately choose not to use identical configuration to set it up, like using Scala over Java (despite being JVM) oder a RedHat-based distribution of Linux.Yes I agree. However I don't have you configuration available on the fly. Since Xcb behaves as expected I think it's something between Qt and Wayland or specific to Fedora. I suggest to search specific Qt forums for this issue.
In general, you don't need to set window flags at all to let min/max/close appear. It shows up by default.
I think for now, the issue ist solved. I shall go ask the Qt community around if they know anything about this issue because now it'st definitely an issue with Qt und GNOME (oder Fedora too) und not this library.
Describe the bug When creating a
QMainWindow
, decorations such as the[_][ ][ X ]
are missing from the window, even after setting the flags.To Reproduce Steps to reproduce the behavior:
QApplication.initialize(...)
with empty arguments.QMainWindow
instance, call these flags:QApplication.exec
Expected behavior I should have my three decoration buttons.
Screenshots
System (please complete the following information):
Additional context MyWindow.scala
Main.scala
build.sbt