I didn't answer you before because I didn't understand what you were referring to.
One day I checked that the annoying bug with the automation button had disappeared.
Actually the bug is not in Qtractor but in Qt and the implementation of QSS.
When it disappeared I assumed that either I had updated the Qt libraries, or Rui had found a solution.
And now it turns out that the general definition of buttons in my QSS fixed it. XD XD XD.
On the other hand it makes sense. Most of the QSS bugs are because when applying it, the default behaviors and styles of the Qt theme engine are unconfigured.
So creating complete general definitions of the elements (buttons, sliders...) in QSS mitigates these bugs.
It's good that you realized this, we already know it in case we want to create new QSS themes for Qtractor or any other Qt application.
You have to create general and complete definitions for each Qt general widget, and from there go on to customize further down the cascade.
I didn't answer you before because I didn't understand what you were referring to.
One day I checked that the annoying bug with the automation button had disappeared.
Actually the bug is not in Qtractor but in Qt and the implementation of QSS.
When it disappeared I assumed that either I had updated the Qt libraries, or Rui had found a solution.
And now it turns out that the general definition of buttons in my QSS fixed it. XD XD XD.
On the other hand it makes sense. Most of the QSS bugs are because when applying it, the default behaviors and styles of the Qt theme engine are unconfigured.
So creating complete general definitions of the elements (buttons, sliders...) in QSS mitigates these bugs.
It's good that you realized this, we already know it in case we want to create new QSS themes for Qtractor or any other Qt application.
You have to create general and complete definitions for each Qt general widget, and from there go on to customize further down the cascade.