https://bugs.kde.org/show_bug.cgi?id=374224
--- Comment #29 from Yichao Yu <yyc1...@gmail.com> --- The usage is basically unsupported by Qt and is a hack from the very beginning so unless Qt provide a proper way to do it this is always a bug of the style. The only question is that what's a better way to hack it. Setting `WA_TranslucentBackground` was indeed what I started with https://github.com/QtCurve/qtcurve/blame/58a4438b901311914d0d453c3987bfabbf258047/qt5/style/qtcurve.cpp#L406 . However, (at least in Qt 5.0/5.1) it causes many side effects that needs to be undone and calling the private API/interact with the backend directly caused much less trouble so I decided to switch to the current approach in https://github.com/QtCurve/qtcurve/commit/c1543d2f27e5ac6f6424537a53e3764233967e68 The main issue with setting `WA_TranslucentBackground` is that applications actually test/set it and messing with it creates lots of confusions in the application/high level libs (iirc kwin and plasma together with their widget libraries caused a lot of issues). OTOH, there are much fewer backends so backend specific hacks are much easier to write without worrying about application specific behaviors. Therefore, IMHO, the best solution (other than having deeper support from Qt) is to interact with the backend directly and make sure the native windows created have the correct events etc. -- You are receiving this mail because: You are watching all bug changes.
