https://bugs.kde.org/show_bug.cgi?id=399757
--- Comment #39 from tr...@yandex.com --- Can PreviewButton be directly derived from KDecoration2::DecorationButton and QQuickPaintedItem ? And for class PreviewButton: Using KDecoration2::paint() like this: https://stackoverflow.com/questions/42736889/c-multiple-inheritance-same-method-names-can-i-somehow-remove-one-of-them/42737015 Because I think, currently, when PreviewButton::paint() is called, it will be redirected to m_button->paint(). It's ok for draw the button. https://github.com/KDE/kwin/blob/master/kcmkwin/kwindecoration/declarative-plugin/previewbutton.cpp#L135 But from BreezeEnhanced, when animation is running > opacity changes > update > BreezeEnhanced::paint() is called. But this time, it don't know about the *painter -> we don't see the animation. https://github.com/tsujan/BreezeEnhanced/blob/master/breezebutton.h#L93 So, my idea is, we make PreviewButton derived directly from KDecoration2::Decorationbutton, so its paint method will be called directly (we do not have to redirect it to m_button->paint() anymore) > it knows about the *painter to repaint when opacity changes > we will see the animation. -- You are receiving this mail because: You are watching all bug changes.
