Enum notify_rust::Urgency [−][src]
pub enum Urgency {
Low,
Normal,
Critical,
}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
The behaviour for Low urgency depends on the notification server.
The behaviour for Normal urgency depends on the notification server.
A critical notification will not time out.
Trait Implementations
impl StructuralEq for Urgency[src]
impl StructuralEq for Urgency[src]impl StructuralPartialEq for Urgency[src]
impl StructuralPartialEq for Urgency[src]Auto Trait Implementations
impl RefUnwindSafe for Urgency
impl RefUnwindSafe for Urgencyimpl UnwindSafe for Urgency
impl UnwindSafe for Urgency