Adding some communication between UI and backend to ensure sync at connection start

[Apokalip]

Signed-off-by: Apokalip simeon@manta.network

Add invoke and static bool to track when front end is ready.

Changing how connection event happens, so until now we were sending a single connect event when the back end was ready to connect. There are a few issues with that as Rust code in release would probably be faster than the JS code which may send the connect event before the UI is listening for it. This was happening in the Linux Freezing #91. There are Tauri issues from other devs with the same problem with syncing at the start of the App, but Tauri was just not planned to be used as this, as normally you can work with the UI without being fully in sync with the backend. In some of those issues Tauri devs mention they are working on a solution but for now we are using a normal pinging method. What we are changing is instead of sending connect event once, we start emitting continuously connection events until we get an answer from the UI, in this case invoking ui_connected() and tracking UI_CONNECTED state. If connected we stop emitting or if not we timeout of course.

This should work in all cases, as we know the UI will always wait at

manta-signer/ui/src/App.js

Line 26 in 3ba2a1e

await once('connect', (event) => {

for the connect event, then we just invoke the ui_connected to signal the backend that the UI is connected and we can continue normally.

Old:
This is caused by misuse of how Tauri works. In this case we are trying to control the UI from the "back-end". While you would want the Rust code to generate the Front end, but after that the front end needs to "control" the backend by invoking methods and reacting to events as a UI should. For now this will work properly as this is not a workaround. But if we want to scale this, it is recommended to be changed as mentioned above.

fixes: #146
fixes: #91

---

Before we can merge this PR, please make sure that all the following items have been checked off:

• Linked to an issue with discussion and accepted design OR have an explanation in the PR that describes this work.
• Added one line describing your change in CHANGELOG.md and added the appropriate changelog label to the PR.
• Re-reviewed Files changed in the GitHub PR explorer.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
manta-signer	✅ Ready (Inspect)	Visit Preview	Aug 24, 2022 at 9:28PM (UTC)