//! DPI is important, so read the docs for this module if you don't want to be confused. //! //! Originally, `winit` dealt entirely in physical pixels (excluding unintentional inconsistencies), but now all //! window-related functions both produce and consume logical pixels. Monitor-related functions still use physical //! pixels, as do any context-related functions in `glutin`. //! //! If you've never heard of these terms before, then you're not alone, and this documentation will explain the //! concepts. //! //! Modern screens have a defined physical resolution, most commonly 1920x1080. Indepedent of that is the amount of //! space the screen occupies, which is to say, the height and width in millimeters. The relationship between these two //! measurements is the *pixel density*. Mobile screens require a high pixel density, as they're held close to the //! eyes. Larger displays also require a higher pixel density, hence the growing presence of 1440p and 4K displays. //! //! So, this presents a problem. Let's say we want to render a square 100px button. It will occupy 100x100 of the //! screen's pixels, which in many cases, seems perfectly fine. However, because this size doesn't account for the //! screen's dimensions or pixel density, the button's size can vary quite a bit. On a 4K display, it would be unusably //! small. //! //! That's a description of what happens when the button is 100x100 *physical* pixels. Instead, let's try using 100x100 //! *logical* pixels. To map logical pixels to physical pixels, we simply multiply by the DPI (dots per inch) factor. //! On a "typical" desktop display, the scale factor will be 1.0, so 100x100 logical pixels equates to 100x100 physical //! pixels. However, a 1440p display may have a scale factor of 1.25, so the button is rendered as 125x125 physical pixels. //! Ideally, the button now has approximately the same perceived size across varying displays. //! //! Failure to account for the scale factor can create a badly degraded user experience. Most notably, it can make users //! feel like they have bad eyesight, which will potentially cause them to think about growing elderly, resulting in //! them entering an existential panic. Once users enter that state, they will no longer be focused on your application. //! //! There are two ways to get the scale factor: //! - You can track the [`DpiChanged`](crate::event::WindowEvent::DpiChanged) event of your //! windows. This event is sent any time the scale factor changes, either because the window moved to another monitor, //! or because the user changed the configuration of their screen. //! - You can also retrieve the scale factor of a monitor by calling //! [`MonitorHandle::scale_factor`](crate::monitor::MonitorHandle::scale_factor), or the //! current scale factor applied to a window by calling //! [`Window::scale_factor`](crate::window::Window::scale_factor), which is roughly equivalent //! to `window.current_monitor().scale_factor()`. //! //! Depending on the platform, the window's actual scale factor may only be known after //! the event loop has started and your window has been drawn once. To properly handle these cases, //! the most robust way is to monitor the [`DpiChanged`](crate::event::WindowEvent::DpiChanged) //! event and dynamically adapt your drawing logic to follow the scale factor. //! //! Here's an overview of what sort of scale factors you can expect, and where they come from: //! - **Windows:** On Windows 8 and 10, per-monitor scaling is readily configured by users from the display settings. //! While users are free to select any option they want, they're only given a selection of "nice" scale factors, i.e. //! 1.0, 1.25, 1.5... on Windows 7, the scale factor is global and changing it requires logging out. //! - **macOS:** The buzzword is "retina displays", which have a scale factor of 2.0. Otherwise, the scale factor is 1.0. //! Intermediate scale factors are never used, thus 1440p displays/etc. aren't properly supported. It's possible for any //! display to use that 2.0 scale factor, given the use of the command line. //! - **X11:** On X11, we calcuate the scale factor based on the millimeter dimensions provided by XRandR. This can //! result in a wide range of possible values, including some interesting ones like 1.0833333333333333. This can be //! overridden using the `WINIT_X11_SCALE_FACTOR` environment variable, though that's not recommended. //! - **Wayland:** On Wayland, scale factors are set per-screen by the server, and are always integers (most often 1 or 2). //! - **iOS:** scale factors are both constant and device-specific on iOS. //! - **Android:** This feature isn't yet implemented on Android, so the scale factor will always be returned as 1.0. //! - **Web:** scale factors are handled by the browser and will always be 1.0 for your application. //! //! The window's logical size is conserved across DPI changes, resulting in the physical size changing instead. This //! may be surprising on X11, but is quite standard elsewhere. Physical size changes always produce a //! [`Resized`](crate::event::WindowEvent::Resized) event, even on platforms where no resize actually occurs, //! such as macOS and Wayland. As a result, it's not necessary to separately handle //! [`DpiChanged`](crate::event::WindowEvent::DpiChanged) if you're only listening for size. //! //! Your GPU has no awareness of the concept of logical pixels, and unless you like wasting pixel density, your //! framebuffer's size should be in physical pixels. //! //! `winit` will send [`Resized`](crate::event::WindowEvent::Resized) events whenever a window's logical size //! changes, and [`DpiChanged`](crate::event::WindowEvent::DpiChanged) events //! whenever the scale factor changes. Receiving either of these events means that the physical size of your window has //! changed, and you should recompute it using the latest values you received for each. If the logical size and the //! scale factor change simultaneously, `winit` will send both events together; thus, it's recommended to buffer //! these events and process them at the end of the queue. //! //! If you never received any [`DpiChanged`](crate::event::WindowEvent::DpiChanged) events, //! then your window's scale factor is 1. pub trait Pixel: Copy + Into { fn from_f64(f: f64) -> Self; fn cast(self) -> P { P::from_f64(self.into()) } } impl Pixel for u8 { fn from_f64(f: f64) -> Self { f.round() as u8 } } impl Pixel for u16 { fn from_f64(f: f64) -> Self { f.round() as u16 } } impl Pixel for u32 { fn from_f64(f: f64) -> Self { f.round() as u32 } } impl Pixel for i8 { fn from_f64(f: f64) -> Self { f.round() as i8 } } impl Pixel for i16 { fn from_f64(f: f64) -> Self { f.round() as i16 } } impl Pixel for i32 { fn from_f64(f: f64) -> Self { f.round() as i32 } } impl Pixel for f32 { fn from_f64(f: f64) -> Self { f as f32 } } impl Pixel for f64 { fn from_f64(f: f64) -> Self { f } } /// Checks that the scale factor is a normal positive `f64`. /// /// All functions that take a scale factor assert that this will return `true`. If you're sourcing scale factors from /// anywhere other than winit, it's recommended to validate them using this function before passing them to winit; /// otherwise, you risk panics. #[inline] pub fn validate_scale_factor(dpi_factor: f64) -> bool { dpi_factor.is_sign_positive() && dpi_factor.is_normal() } /// A position represented in logical pixels. /// /// The position is stored as floats, so please be careful. Casting floats to integers truncates the fractional part, /// which can cause noticable issues. To help with that, an `Into<(i32, i32)>` implementation is provided which /// does the rounding for you. #[derive(Debug, Copy, Clone, PartialEq)] #[cfg_attr(feature = "serde", derive(Serialize, Deserialize))] pub struct LogicalPosition

{ pub x: P, pub y: P, } impl

LogicalPosition

{ #[inline] pub const fn new(x: P, y: P) -> Self { LogicalPosition { x, y } } } impl LogicalPosition

{ #[inline] pub fn from_physical>, X: Pixel>( physical: T, dpi_factor: f64, ) -> Self { physical.into().to_logical(dpi_factor) } #[inline] pub fn to_physical(&self, dpi_factor: f64) -> PhysicalPosition { assert!(validate_scale_factor(dpi_factor)); let x = self.x.into() * dpi_factor; let y = self.y.into() * dpi_factor; PhysicalPosition::new(x, y).cast() } #[inline] pub fn cast(&self) -> LogicalPosition { LogicalPosition { x: self.x.cast(), y: self.y.cast(), } } } impl From<(X, X)> for LogicalPosition

{ fn from((x, y): (X, X)) -> LogicalPosition

{ LogicalPosition::new(x.cast(), y.cast()) } } impl Into<(X, X)> for LogicalPosition

{ fn into(self: Self) -> (X, X) { (self.x.cast(), self.y.cast()) } } impl From<[X; 2]> for LogicalPosition

{ fn from([x, y]: [X; 2]) -> LogicalPosition

{ LogicalPosition::new(x.cast(), y.cast()) } } impl Into<[X; 2]> for LogicalPosition

{ fn into(self: Self) -> [X; 2] { [self.x.cast(), self.y.cast()] } } /// A position represented in physical pixels. /// /// The position is stored as floats, so please be careful. Casting floats to integers truncates the fractional part, /// which can cause noticable issues. To help with that, an `Into<(i32, i32)>` implementation is provided which /// does the rounding for you. #[derive(Debug, Copy, Clone, PartialEq)] #[cfg_attr(feature = "serde", derive(Serialize, Deserialize))] pub struct PhysicalPosition

{ pub x: P, pub y: P, } impl

PhysicalPosition

{ #[inline] pub const fn new(x: P, y: P) -> Self { PhysicalPosition { x, y } } } impl PhysicalPosition

{ #[inline] pub fn from_logical>, X: Pixel>( logical: T, dpi_factor: f64, ) -> Self { logical.into().to_physical(dpi_factor) } #[inline] pub fn to_logical(&self, dpi_factor: f64) -> LogicalPosition { assert!(validate_scale_factor(dpi_factor)); let x = self.x.into() / dpi_factor; let y = self.y.into() / dpi_factor; LogicalPosition::new(x, y).cast() } #[inline] pub fn cast(&self) -> PhysicalPosition { PhysicalPosition { x: self.x.cast(), y: self.y.cast(), } } } impl From<(X, X)> for PhysicalPosition

{ fn from((x, y): (X, X)) -> PhysicalPosition

{ PhysicalPosition::new(x.cast(), y.cast()) } } impl Into<(X, X)> for PhysicalPosition

{ fn into(self: Self) -> (X, X) { (self.x.cast(), self.y.cast()) } } impl From<[X; 2]> for PhysicalPosition

{ fn from([x, y]: [X; 2]) -> PhysicalPosition

{ PhysicalPosition::new(x.cast(), y.cast()) } } impl Into<[X; 2]> for PhysicalPosition

{ fn into(self: Self) -> [X; 2] { [self.x.cast(), self.y.cast()] } } /// A size represented in logical pixels. /// /// The size is stored as floats, so please be careful. Casting floats to integers truncates the fractional part, /// which can cause noticable issues. To help with that, an `Into<(u32, u32)>` implementation is provided which /// does the rounding for you. #[derive(Debug, Copy, Clone, PartialEq)] #[cfg_attr(feature = "serde", derive(Serialize, Deserialize))] pub struct LogicalSize

{ pub width: P, pub height: P, } impl

LogicalSize

{ #[inline] pub const fn new(width: P, height: P) -> Self { LogicalSize { width, height } } } impl LogicalSize

{ #[inline] pub fn from_physical>, X: Pixel>(physical: T, dpi_factor: f64) -> Self { physical.into().to_logical(dpi_factor) } #[inline] pub fn to_physical(&self, dpi_factor: f64) -> PhysicalSize { assert!(validate_scale_factor(dpi_factor)); let width = self.width.into() * dpi_factor; let height = self.height.into() * dpi_factor; PhysicalSize::new(width, height).cast() } #[inline] pub fn cast(&self) -> LogicalSize { LogicalSize { width: self.width.cast(), height: self.height.cast(), } } } impl From<(X, X)> for LogicalSize

{ fn from((x, y): (X, X)) -> LogicalSize

{ LogicalSize::new(x.cast(), y.cast()) } } impl Into<(X, X)> for LogicalSize

{ fn into(self: LogicalSize

) -> (X, X) { (self.width.cast(), self.height.cast()) } } impl From<[X; 2]> for LogicalSize

{ fn from([x, y]: [X; 2]) -> LogicalSize

{ LogicalSize::new(x.cast(), y.cast()) } } impl Into<[X; 2]> for LogicalSize

{ fn into(self: Self) -> [X; 2] { [self.width.cast(), self.height.cast()] } } /// A size represented in physical pixels. #[derive(Debug, Copy, Clone, PartialEq, Eq, Hash)] #[cfg_attr(feature = "serde", derive(Serialize, Deserialize))] pub struct PhysicalSize

{ pub width: P, pub height: P, } impl

PhysicalSize

{ #[inline] pub const fn new(width: P, height: P) -> Self { PhysicalSize { width, height } } } impl PhysicalSize

{ #[inline] pub fn from_logical>, X: Pixel>(logical: T, dpi_factor: f64) -> Self { logical.into().to_physical(dpi_factor) } #[inline] pub fn to_logical(&self, dpi_factor: f64) -> LogicalSize { assert!(validate_scale_factor(dpi_factor)); let width = self.width.into() / dpi_factor; let height = self.height.into() / dpi_factor; LogicalSize::new(width, height).cast() } #[inline] pub fn cast(&self) -> PhysicalSize { PhysicalSize { width: self.width.cast(), height: self.height.cast(), } } } impl From<(X, X)> for PhysicalSize

{ fn from((x, y): (X, X)) -> PhysicalSize

{ PhysicalSize::new(x.cast(), y.cast()) } } impl Into<(X, X)> for PhysicalSize

{ fn into(self: Self) -> (X, X) { (self.width.cast(), self.height.cast()) } } impl From<[X; 2]> for PhysicalSize

{ fn from([x, y]: [X; 2]) -> PhysicalSize

{ PhysicalSize::new(x.cast(), y.cast()) } } impl Into<[X; 2]> for PhysicalSize

{ fn into(self: Self) -> [X; 2] { [self.width.cast(), self.height.cast()] } } #[derive(Debug, Copy, Clone, PartialEq)] #[cfg_attr(feature = "serde", derive(Serialize, Deserialize))] pub enum Size { Physical(PhysicalSize), Logical(LogicalSize), } impl Size { pub fn new>(size: S) -> Size { size.into() } pub fn to_logical(&self, dpi_factor: f64) -> LogicalSize

{ match *self { Size::Physical(size) => size.to_logical(dpi_factor), Size::Logical(size) => size.cast(), } } pub fn to_physical(&self, dpi_factor: f64) -> PhysicalSize

{ match *self { Size::Physical(size) => size.cast(), Size::Logical(size) => size.to_physical(dpi_factor), } } } impl From> for Size { #[inline] fn from(size: PhysicalSize

) -> Size { Size::Physical(size.cast()) } } impl From> for Size { #[inline] fn from(size: LogicalSize

) -> Size { Size::Logical(size.cast()) } } #[derive(Debug, Copy, Clone, PartialEq)] #[cfg_attr(feature = "serde", derive(Serialize, Deserialize))] pub enum Position { Physical(PhysicalPosition), Logical(LogicalPosition), } impl Position { pub fn new>(position: S) -> Position { position.into() } pub fn to_logical(&self, dpi_factor: f64) -> LogicalPosition

{ match *self { Position::Physical(position) => position.to_logical(dpi_factor), Position::Logical(position) => position.cast(), } } pub fn to_physical(&self, dpi_factor: f64) -> PhysicalPosition

{ match *self { Position::Physical(position) => position.cast(), Position::Logical(position) => position.to_physical(dpi_factor), } } } impl From> for Position { #[inline] fn from(position: PhysicalPosition

) -> Position { Position::Physical(position.cast()) } } impl From> for Position { #[inline] fn from(position: LogicalPosition

) -> Position { Position::Logical(position.cast()) } }