Enum notify_rust::Urgency
source · pub enum Urgency {
Low = 0,
Normal = 1,
Critical = 2,
}
Expand description
Levels of Urgency.
§Specification
Developers must use their own judgement when deciding the urgency of a notification. Typically, if the majority of programs are using the same level for a specific type of urgency, other applications should follow them.
For low and normal urgencies, server implementations may display the notifications how they choose. They should, however, have a sane expiration timeout dependent on the urgency level.
Critical notifications should not automatically expire, as they are things that the user will most likely want to know about. They should only be closed when the user dismisses them, for example, by clicking on the notification.
— see Galago or Gnome specification.
§Example
Notification::new()
.summary("oh no")
.icon("dialog-warning")
.urgency(Urgency::Critical)
.show()?;
Variants§
Low = 0
The behavior for Low
urgency depends on the notification server.
Normal = 1
The behavior for Normal
urgency depends on the notification server.
Critical = 2
A critical notification will not time out.
Trait Implementations§
impl Copy for Urgency
impl Eq for Urgency
impl StructuralPartialEq for Urgency
Auto Trait Implementations§
impl Freeze for Urgency
impl RefUnwindSafe for Urgency
impl Send for Urgency
impl Sync for Urgency
impl Unpin for Urgency
impl UnwindSafe for Urgency
Blanket Implementations§
source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
source§impl<T> CloneToUninit for Twhere
T: Clone,
impl<T> CloneToUninit for Twhere
T: Clone,
source§unsafe fn clone_to_uninit(&self, dst: *mut T)
unsafe fn clone_to_uninit(&self, dst: *mut T)
clone_to_uninit
)