057d0c565e
Remove the workaround, to the approach of using the complete last word event, for three letters seed-words. The three letters condition introduced another side effect when completing the "sentence" and made the _internal.mnemonicInput contain an extra duplicate word. Unify the event `doneInsertingWord` generation for the internal purpose with the external. This will trigger a secondary for some usage but I see no problem with even in other usages. Fix corner case when user enters a correct seed word that is not singular and uses the mouse to jump. In that case the doneInsertingWord is not triggered Fixes: #7715 |
||
---|---|---|
.. | ||
doc | ||
sandbox | ||
src | ||
tests | ||
vendor | ||
.gitmodules | ||
CHANGELOG.md | ||
CMakeLists.txt | ||
README.md |
README.md
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