Split iced_futures into different backend implementations
This commit is contained in:
parent
5dab5a327e
commit
167be45a7d
19 changed files with 280 additions and 318 deletions
12
src/time.rs
12
src/time.rs
|
|
@ -1,12 +1,2 @@
|
|||
//! Listen and react to time.
|
||||
pub use crate::runtime::time::{Duration, Instant};
|
||||
|
||||
use crate::Subscription;
|
||||
|
||||
/// Returns a [`Subscription`] that produces messages at a set interval.
|
||||
///
|
||||
/// The first message is produced after a `duration`, and then continues to
|
||||
/// produce more messages every `duration` after that.
|
||||
pub fn every(duration: Duration) -> Subscription<Instant> {
|
||||
iced_futures::time::every(duration)
|
||||
}
|
||||
pub use iced_futures::backend::default::time::*;
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue