During the searching the `searchCount` tracks the progress and notifies the observers (when 0 than completed).
When the crash When the `?edits` command is typed into the search field happens the `searchInViewport` m_onStarted callback is called but m_onStarted is not (in the core). m_onStarted is executed as a separate UI task. But for the `?edits` command it is not executed at all and produces the data race in the `searchCount` and breaks the UI updates for this debug command.
Since the `searchEverywhere` and `searchInViewport` are called simultaneously while typing the query there are no reason to track the `searchInViewport` searches. Only the `searchEverywhere` is enough. `searchInViewport` is not affecting the platform UI at all - its just show the marks on the map.
Signed-off-by: Kiryl Kaveryn <kirylkaveryn@gmail.com>
1. update style: bigger fonts and insets
2. update background blur
3. get rid of MWM prefix
4. replace the timer with the simplier dispatch async after. In this case there is no needed to create a timer for each toasts message just to add a timeout
5. reorder Toast class methods
6. replace the instance `show` method with a `static show`. Because there non needed to call show every time. We do not have stored toast that will be showed in different places thane created.
Signed-off-by: Kiryl Kaveryn <kirylkaveryn@gmail.com>
Signed-off-by: Kiryl Kaveryn <kirylkaveryn@gmail.com>
