8214e64684
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
StatusQ
An emerging reusable QML UI component library for Status applications.
Usage
StatusQ introduces a module namespace that semantically groups components so they can be easily imported. These modules are:
- StatusQ.Core
- StatusQ.Core.Theme
- StatusQ.Core.Utils
- StatusQ.Components
- StatusQ.Controls
- StatusQ.Layout
- StatusQ.Platform
- StatusQ.Popups
Provided components can be viewed and tested in the sandbox application that comes with this repository. Other than that, modules and components can be used as expected.
Example:
import Status.Core 0.1
import Status.Controls 0.1
StatusInput {
...
}
Viewing and testing components
To make viewing and testing components easy, we've added a sandbox application to this repository in which StatusQ components are being build. This is the first place where components see the light of the world and can be run in a proper application environment.
Using Qt Creator
The easiest way to run the sandbox application is to simply open the provided CMakeLists.txt file using Qt Creator.
Using command line interface
To run the sandbox from within a command line interface, run the following commands:
$ git clone https://github.com/status-im/StatusQ
$ cd StatusQ
$ git submodule update --init
$ ./sandbox/scripts/build
Once that is done, the sandbox can be started with the generated executable:
$ ./build/sandbox/Sandbox