Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix tiny typo in readme #5

Merged
merged 2 commits into from
Jul 3, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Testing egui and tokio
Just my demo project on how one can use tokio to make a fluid egui user interface when processing data from the internet.
The primitives are no located in the "lazy_async_promise" crate, which can be found on [crates.io](https://crates.io/crates/lazy_async_promise)
The primitives are now located in the "lazy_async_promise" crate, which can be found on [crates.io](https://crates.io/crates/lazy_async_promise)
and [github](https://github.com/ChrisRega/lazy_async_promise).
Maybe you will find them useful, too :)

Expand Down Expand Up @@ -52,7 +52,7 @@ pub fn make_immediate_post_request(
})
}
```
The specialty for egui is, that we don't actually get drawn / updated if nothing is going own.
The specialty for egui is, that we don't actually get drawn / updated if nothing is going on.
Imagine downloading the post without a spinner - nothing changes, no update call therefore no polling.
But without polling we will never get notified about the finish. This will not happen in this use case since we would usually
use a spinner for indicating that we are fetching main page content. But imagine a select!-macro
Expand Down