`Manager::startAllHiding`: don't treat fading in notifications specially
Previously, `Window::Notifications::Default::Manager` would not start
hiding notifications that are fading in when other notifications should
hide. This would lead to some notifications never hiding, e.g., when the
cursor passes through the notification too quickly and there was not
enough time for the notification to fade in completely.
Also renamed `Widget::isShowing` -> `Widget::isFadingIn` for clarity.
Fixes #28811.
telegramdesktop/tdesktop/dev • 03af444 • 1 files, +4/-0
Notifications: stop fading in before starting to fade out
When a notification is to start hiding (i.e., fade out), it is supposed
to start fading out from the maximum opacity, even if it was not fully
restored (which only happens if the cursor passed through the
notification too quickly). Thus, call `.stop()` for the previous
animation, if any, before `.start()`ing the next animation.
telegramdesktop/tdesktop/dev • 4950b52 • 1 files, +1/-4
Don't set CMAKE_EXPORT_COMPILE_COMMANDS via cmake.configureSettings
It's controlled by cmake.exportCompileCommandsFile and defaults to true
#tdesktop