Class Display<TDriver>

Namespace

Sdl3Sharp.Video.Windowing

Assembly

Sdl3Sharp.dll

Represents a display connected to the system

public sealed class Display<TDriver> : Display, ISpanFormattable, IFormattable where TDriver : IWindowingDriver

Type Parameters

TDriver

The windowing driver associated with this display

Inheritance

object

Display

Display<TDriver>

Implements

ISpanFormattable

IFormattable

Inherited Members

Display.Bounds

Display.ConnectedDisplays

Display.ContentScale

Display.CurrentDisplayMode

Display.CurrentOrientation

Display.DesktopDisplayMode

Display.FullscreenDisplayModes

Display.Id

Display.IsHdrEnabled

Display.Name

Display.NaturalOrientation

Display.PrimaryDisplay

Display.Properties

Display.UsableBounds

Display.ToString()

Display.ToString(IFormatProvider)

Display.ToString(string)

Display.ToString(string, IFormatProvider)

Display.TryFormat(Span<char>, out int, ReadOnlySpan<char>, IFormatProvider)

Display.TryGetClosestFullscreenDisplayMode(int, int, out DisplayMode, float, bool)

Display.TryGetFromPoint(in Point<int>, out Display)

Display.TryGetFromRect(in Rect<int>, out Display)

object.Equals(object)

object.Equals(object, object)

object.GetHashCode()

object.GetType()

object.ReferenceEquals(object, object)

Remarks

The Id of a display is unique, remains unchanged while the display is connected to the system, and is never reused for the lifetime of the application. If a display is disconnected and then reconnected, it will get assigned a new Id.

For the most part Display<TDriver>s are not thread-safe, and most of their properties and methods should only be accessed from the main thread!

Display<TDriver>s are concrete display types, associated with a specific windowing driver.

If you want to use them in a more general way, you can use them as Display instances, which serve as common abstractions.