The culprit here is at the very bottom, in StatusListItem: the toplevel item was a MouseArea handling the clicks and this causes problems as any extra buttons placed on top of it get their mouseClick events delivered in wrong order (after StatusListItem). Fix this by having a MouseArea handling click events behind the actual toplevel item as a last resort, catch all handler plus the actual "sensor" being just a MouseArea that handles merely the hover events - drop unneeded onPressed/onReleased handlers in StatusChatListCategoryItem - fix some warnings (typos, unreachable code, shadowed variables) Fixes: #6733 |
||
---|---|---|
.. | ||
android | ||
controls | ||
demoapp | ||
dictionaries | ||
examples | ||
images | ||
pages | ||
scripts | ||
CMakeLists.txt | ||
DemoApp.qml | ||
ThemeSwitch.qml | ||
main.cpp | ||
main.qml | ||
qml.qrc | ||
sandboxapp.cpp | ||
sandboxapp.h | ||
spellchecker.cpp | ||
spellchecker.h | ||
statuswindow.cpp | ||
statuswindow.h | ||
statuswindow_mac.mm |