MonitorProtocol

public protocol MonitorProtocol : ObjectProtocol

The MonitorProtocol protocol exposes the methods and properties of an underlying GdkMonitor instance. The default implementation of these can be found in the protocol extension below. For a concrete class that implements these methods and properties, see Monitor. Alternatively, use MonitorRef as a lighweight, unowned reference if you already have an instance you just want to use.

GdkMonitor objects represent the individual outputs that are associated with a GdkDisplay.

GdkDisplay keeps a GListModel to enumerate and monitor monitors with [methodGdk.Display.get_monitors]. You can use [methodGdk.Display.get_monitor_at_surface] to find a particular monitor.

Show on GitHub
  • ptr

    Untyped pointer to the underlying GdkMonitor instance.

    Declaration

    Swift

    var ptr: UnsafeMutableRawPointer! { get }
    Show on GitHub
  • monitor_ptr Default implementation

    Typed pointer to the underlying GdkMonitor instance.

    Default Implementation

    Return the stored, untyped pointer as a typed pointer to the GdkMonitor instance.

    Declaration

    Swift

    var monitor_ptr: UnsafeMutablePointer<GdkMonitor>! { get }
    Show on GitHub

  • Required Initialiser for types conforming to MonitorProtocol

    Declaration

    Swift

    init(raw: UnsafeMutableRawPointer)
    Show on GitHub

Monitor Class

  • Bind a MonitorPropertyName source property to a given target object.

    Declaration

    Swift

    @discardableResult
@inlinable
func bind<Q, T>(property source_property: MonitorPropertyName, to target: T, _ target_property: Q, flags f: BindingFlags = .default, transformFrom transform_from: @escaping GLibObject.ValueTransformer = { $0.transform(destValue: $1) }, transformTo transform_to: @escaping GLibObject.ValueTransformer = { $0.transform(destValue: $1) }) -> BindingRef! where Q : PropertyNameProtocol, T : ObjectProtocol

    Parameters

    source_property

    the source property to bind
    target

    the target object to bind to
    target_property

    the target property to bind to
    flags

    the flags to pass to the Binding
    transform_from

    ValueTransformer to use for forward transformation
    transform_to

    ValueTransformer to use for backwards transformation

    Return Value

    binding reference or nil in case of an error

    Show on GitHub
  • get(property:) Extension method

    Get the value of a Monitor property

    Declaration

    Swift

    @inlinable
func get(property: MonitorPropertyName) -> GLibObject.Value

    Parameters

    property

    the property to get the value for

    Return Value

    the value of the named property

    Show on GitHub
  • set(property:value:) Extension method

    Set the value of a Monitor property. Note that this will only have an effect on properties that are writable and not construct-only!

    Declaration

    Swift

    @inlinable
func set(property: MonitorPropertyName, value v: GLibObject.Value)

    Parameters

    property

    the property to get the value for

    Return Value

    the value of the named property

    Show on GitHub

Monitor signals

  • Connect a Swift signal handler to the given, typed MonitorSignalName signal

    Declaration

    Swift

    @discardableResult
@inlinable
func connect(signal s: MonitorSignalName, flags f: ConnectFlags = ConnectFlags(0), handler h: @escaping SignalHandler) -> Int

    Parameters

    signal

    The signal to connect
    flags

    The connection flags to use
    data

    A pointer to user data to provide to the callback
    destroyData

    A GClosureNotify C function to destroy the data pointed to by userData
    handler

    The Swift signal handler (function or callback) to invoke on the given signal

    Return Value

    The signal handler ID (always greater than 0 for successful connections)

    Show on GitHub

  • Connect a C signal handler to the given, typed MonitorSignalName signal

    Declaration

    Swift

    @discardableResult
@inlinable
func connect(signal s: MonitorSignalName, flags f: ConnectFlags = ConnectFlags(0), data userData: gpointer!, destroyData destructor: GClosureNotify? = nil, signalHandler h: @escaping GCallback) -> Int

    Parameters

    signal

    The signal to connect
    flags

    The connection flags to use
    data

    A pointer to user data to provide to the callback
    destroyData

    A GClosureNotify C function to destroy the data pointed to by userData
    signalHandler

    The C function to be called on the given signal

    Return Value

    The signal handler ID (always greater than 0 for successful connections)

    Show on GitHub
  • onInvalidate(flags:handler:) Extension method

    Emitted when the output represented by monitor gets disconnected.

    Note

    This represents the underlying invalidate signal

    Declaration

    Swift

    @discardableResult
@inlinable
func onInvalidate(flags: ConnectFlags = ConnectFlags(0), handler: @escaping (_ unownedSelf: MonitorRef) -> Void) -> Int

    Parameters

    flags

    Flags
    unownedSelf

    Reference to instance of self
    handler

    The signal handler to call Run the given callback whenever the invalidate signal is emitted
    Show on GitHub
  • invalidateSignal Extension method

    Typed invalidate signal for using the connect(signal:) methods

    Declaration

    Swift

    static var invalidateSignal: MonitorSignalName { get }
    Show on GitHub

  • The notify signal is emitted on an object when one of its properties has its value set through g_object_set_property(), g_object_set(), et al.

    Note that getting this signal doesn’t itself guarantee that the value of the property has actually changed. When it is emitted is determined by the derived GObject class. If the implementor did not create the property with G_PARAM_EXPLICIT_NOTIFY, then any call to g_object_set_property() results in notify being emitted, even if the new value is the same as the old. If they did pass G_PARAM_EXPLICIT_NOTIFY, then this signal is emitted only when they explicitly call g_object_notify() or g_object_notify_by_pspec(), and common practice is to do that only when the value has actually changed.

    This signal is typically used to obtain change notification for a single property, by specifying the property name as a detail in the g_signal_connect() call, like this: (C Language Example):

    g_signal_connect (text_view->buffer, "notify::paste-target-list",
                  G_CALLBACK (gtk_text_view_target_list_notify),
                  text_view)

    It is important to note that you must use canonical parameter names as detail strings for the notify signal.

    Note

    This represents the underlying notify::connector signal

    Declaration

    Swift

    @discardableResult
@inlinable
func onNotifyConnector(flags: ConnectFlags = ConnectFlags(0), handler: @escaping (_ unownedSelf: MonitorRef, _ pspec: ParamSpecRef) -> Void) -> Int

    Parameters

    flags

    Flags
    unownedSelf

    Reference to instance of self
    pspec

    the GParamSpec of the property which changed.
    handler

    The signal handler to call Run the given callback whenever the notifyConnector signal is emitted
    Show on GitHub
  • notifyConnectorSignal Extension method

    Typed notify::connector signal for using the connect(signal:) methods

    Declaration

    Swift

    static var notifyConnectorSignal: MonitorSignalName { get }
    Show on GitHub

  • The notify signal is emitted on an object when one of its properties has its value set through g_object_set_property(), g_object_set(), et al.

    Note that getting this signal doesn’t itself guarantee that the value of the property has actually changed. When it is emitted is determined by the derived GObject class. If the implementor did not create the property with G_PARAM_EXPLICIT_NOTIFY, then any call to g_object_set_property() results in notify being emitted, even if the new value is the same as the old. If they did pass G_PARAM_EXPLICIT_NOTIFY, then this signal is emitted only when they explicitly call g_object_notify() or g_object_notify_by_pspec(), and common practice is to do that only when the value has actually changed.

    This signal is typically used to obtain change notification for a single property, by specifying the property name as a detail in the g_signal_connect() call, like this: (C Language Example):

    g_signal_connect (text_view->buffer, "notify::paste-target-list",
                  G_CALLBACK (gtk_text_view_target_list_notify),
                  text_view)

    It is important to note that you must use canonical parameter names as detail strings for the notify signal.

    Note

    This represents the underlying notify::display signal

    Declaration

    Swift

    @discardableResult
@inlinable
func onNotifyDisplay(flags: ConnectFlags = ConnectFlags(0), handler: @escaping (_ unownedSelf: MonitorRef, _ pspec: ParamSpecRef) -> Void) -> Int

    Parameters

    flags

    Flags
    unownedSelf

    Reference to instance of self
    pspec

    the GParamSpec of the property which changed.
    handler

    The signal handler to call Run the given callback whenever the notifyDisplay signal is emitted
    Show on GitHub
  • notifyDisplaySignal Extension method

    Typed notify::display signal for using the connect(signal:) methods

    Declaration

    Swift

    static var notifyDisplaySignal: MonitorSignalName { get }
    Show on GitHub

  • The notify signal is emitted on an object when one of its properties has its value set through g_object_set_property(), g_object_set(), et al.

    Note that getting this signal doesn’t itself guarantee that the value of the property has actually changed. When it is emitted is determined by the derived GObject class. If the implementor did not create the property with G_PARAM_EXPLICIT_NOTIFY, then any call to g_object_set_property() results in notify being emitted, even if the new value is the same as the old. If they did pass G_PARAM_EXPLICIT_NOTIFY, then this signal is emitted only when they explicitly call g_object_notify() or g_object_notify_by_pspec(), and common practice is to do that only when the value has actually changed.

    This signal is typically used to obtain change notification for a single property, by specifying the property name as a detail in the g_signal_connect() call, like this: (C Language Example):

    g_signal_connect (text_view->buffer, "notify::paste-target-list",
                  G_CALLBACK (gtk_text_view_target_list_notify),
                  text_view)

    It is important to note that you must use canonical parameter names as detail strings for the notify signal.

    Note

    This represents the underlying notify::geometry signal

    Declaration

    Swift

    @discardableResult
@inlinable
func onNotifyGeometry(flags: ConnectFlags = ConnectFlags(0), handler: @escaping (_ unownedSelf: MonitorRef, _ pspec: ParamSpecRef) -> Void) -> Int

    Parameters

    flags

    Flags
    unownedSelf

    Reference to instance of self
    pspec

    the GParamSpec of the property which changed.
    handler

    The signal handler to call Run the given callback whenever the notifyGeometry signal is emitted
    Show on GitHub
  • notifyGeometrySignal Extension method

    Typed notify::geometry signal for using the connect(signal:) methods

    Declaration

    Swift

    static var notifyGeometrySignal: MonitorSignalName { get }
    Show on GitHub

  • The notify signal is emitted on an object when one of its properties has its value set through g_object_set_property(), g_object_set(), et al.

    Note that getting this signal doesn’t itself guarantee that the value of the property has actually changed. When it is emitted is determined by the derived GObject class. If the implementor did not create the property with G_PARAM_EXPLICIT_NOTIFY, then any call to g_object_set_property() results in notify being emitted, even if the new value is the same as the old. If they did pass G_PARAM_EXPLICIT_NOTIFY, then this signal is emitted only when they explicitly call g_object_notify() or g_object_notify_by_pspec(), and common practice is to do that only when the value has actually changed.

    This signal is typically used to obtain change notification for a single property, by specifying the property name as a detail in the g_signal_connect() call, like this: (C Language Example):

    g_signal_connect (text_view->buffer, "notify::paste-target-list",
                  G_CALLBACK (gtk_text_view_target_list_notify),
                  text_view)

    It is important to note that you must use canonical parameter names as detail strings for the notify signal.

    Note

    This represents the underlying notify::height-mm signal

    Declaration

    Swift

    @discardableResult
@inlinable
func onNotifyHeightMm(flags: ConnectFlags = ConnectFlags(0), handler: @escaping (_ unownedSelf: MonitorRef, _ pspec: ParamSpecRef) -> Void) -> Int

    Parameters

    flags

    Flags
    unownedSelf

    Reference to instance of self
    pspec

    the GParamSpec of the property which changed.
    handler

    The signal handler to call Run the given callback whenever the notifyHeightMm signal is emitted
    Show on GitHub
  • notifyHeightMmSignal Extension method

    Typed notify::height-mm signal for using the connect(signal:) methods

    Declaration

    Swift

    static var notifyHeightMmSignal: MonitorSignalName { get }
    Show on GitHub

  • The notify signal is emitted on an object when one of its properties has its value set through g_object_set_property(), g_object_set(), et al.

    Note that getting this signal doesn’t itself guarantee that the value of the property has actually changed. When it is emitted is determined by the derived GObject class. If the implementor did not create the property with G_PARAM_EXPLICIT_NOTIFY, then any call to g_object_set_property() results in notify being emitted, even if the new value is the same as the old. If they did pass G_PARAM_EXPLICIT_NOTIFY, then this signal is emitted only when they explicitly call g_object_notify() or g_object_notify_by_pspec(), and common practice is to do that only when the value has actually changed.

    This signal is typically used to obtain change notification for a single property, by specifying the property name as a detail in the g_signal_connect() call, like this: (C Language Example):

    g_signal_connect (text_view->buffer, "notify::paste-target-list",
                  G_CALLBACK (gtk_text_view_target_list_notify),
                  text_view)

    It is important to note that you must use canonical parameter names as detail strings for the notify signal.

    Note

    This represents the underlying notify::manufacturer signal

    Declaration

    Swift

    @discardableResult
@inlinable
func onNotifyManufacturer(flags: ConnectFlags = ConnectFlags(0), handler: @escaping (_ unownedSelf: MonitorRef, _ pspec: ParamSpecRef) -> Void) -> Int

    Parameters

    flags

    Flags
    unownedSelf

    Reference to instance of self
    pspec

    the GParamSpec of the property which changed.
    handler

    The signal handler to call Run the given callback whenever the notifyManufacturer signal is emitted
    Show on GitHub
  • notifyManufacturerSignal Extension method

    Typed notify::manufacturer signal for using the connect(signal:) methods

    Declaration

    Swift

    static var notifyManufacturerSignal: MonitorSignalName { get }
    Show on GitHub

  • The notify signal is emitted on an object when one of its properties has its value set through g_object_set_property(), g_object_set(), et al.

    Note that getting this signal doesn’t itself guarantee that the value of the property has actually changed. When it is emitted is determined by the derived GObject class. If the implementor did not create the property with G_PARAM_EXPLICIT_NOTIFY, then any call to g_object_set_property() results in notify being emitted, even if the new value is the same as the old. If they did pass G_PARAM_EXPLICIT_NOTIFY, then this signal is emitted only when they explicitly call g_object_notify() or g_object_notify_by_pspec(), and common practice is to do that only when the value has actually changed.

    This signal is typically used to obtain change notification for a single property, by specifying the property name as a detail in the g_signal_connect() call, like this: (C Language Example):

    g_signal_connect (text_view->buffer, "notify::paste-target-list",
                  G_CALLBACK (gtk_text_view_target_list_notify),
                  text_view)

    It is important to note that you must use canonical parameter names as detail strings for the notify signal.

    Note

    This represents the underlying notify::model signal

    Declaration

    Swift

    @discardableResult
@inlinable
func onNotifyModel(flags: ConnectFlags = ConnectFlags(0), handler: @escaping (_ unownedSelf: MonitorRef, _ pspec: ParamSpecRef) -> Void) -> Int

    Parameters

    flags

    Flags
    unownedSelf

    Reference to instance of self
    pspec

    the GParamSpec of the property which changed.
    handler

    The signal handler to call Run the given callback whenever the notifyModel signal is emitted
    Show on GitHub
  • notifyModelSignal Extension method

    Typed notify::model signal for using the connect(signal:) methods

    Declaration

    Swift

    static var notifyModelSignal: MonitorSignalName { get }
    Show on GitHub

  • The notify signal is emitted on an object when one of its properties has its value set through g_object_set_property(), g_object_set(), et al.

    Note that getting this signal doesn’t itself guarantee that the value of the property has actually changed. When it is emitted is determined by the derived GObject class. If the implementor did not create the property with G_PARAM_EXPLICIT_NOTIFY, then any call to g_object_set_property() results in notify being emitted, even if the new value is the same as the old. If they did pass G_PARAM_EXPLICIT_NOTIFY, then this signal is emitted only when they explicitly call g_object_notify() or g_object_notify_by_pspec(), and common practice is to do that only when the value has actually changed.

    This signal is typically used to obtain change notification for a single property, by specifying the property name as a detail in the g_signal_connect() call, like this: (C Language Example):

    g_signal_connect (text_view->buffer, "notify::paste-target-list",
                  G_CALLBACK (gtk_text_view_target_list_notify),
                  text_view)

    It is important to note that you must use canonical parameter names as detail strings for the notify signal.

    Note

    This represents the underlying notify::refresh-rate signal

    Declaration

    Swift

    @discardableResult
@inlinable
func onNotifyRefreshRate(flags: ConnectFlags = ConnectFlags(0), handler: @escaping (_ unownedSelf: MonitorRef, _ pspec: ParamSpecRef) -> Void) -> Int

    Parameters

    flags

    Flags
    unownedSelf

    Reference to instance of self
    pspec

    the GParamSpec of the property which changed.
    handler

    The signal handler to call Run the given callback whenever the notifyRefreshRate signal is emitted
    Show on GitHub
  • notifyRefreshRateSignal Extension method

    Typed notify::refresh-rate signal for using the connect(signal:) methods

    Declaration

    Swift

    static var notifyRefreshRateSignal: MonitorSignalName { get }
    Show on GitHub

  • The notify signal is emitted on an object when one of its properties has its value set through g_object_set_property(), g_object_set(), et al.

    Note that getting this signal doesn’t itself guarantee that the value of the property has actually changed. When it is emitted is determined by the derived GObject class. If the implementor did not create the property with G_PARAM_EXPLICIT_NOTIFY, then any call to g_object_set_property() results in notify being emitted, even if the new value is the same as the old. If they did pass G_PARAM_EXPLICIT_NOTIFY, then this signal is emitted only when they explicitly call g_object_notify() or g_object_notify_by_pspec(), and common practice is to do that only when the value has actually changed.

    This signal is typically used to obtain change notification for a single property, by specifying the property name as a detail in the g_signal_connect() call, like this: (C Language Example):

    g_signal_connect (text_view->buffer, "notify::paste-target-list",
                  G_CALLBACK (gtk_text_view_target_list_notify),
                  text_view)

    It is important to note that you must use canonical parameter names as detail strings for the notify signal.

    Note

    This represents the underlying notify::scale-factor signal

    Declaration

    Swift

    @discardableResult
@inlinable
func onNotifyScaleFactor(flags: ConnectFlags = ConnectFlags(0), handler: @escaping (_ unownedSelf: MonitorRef, _ pspec: ParamSpecRef) -> Void) -> Int

    Parameters

    flags

    Flags
    unownedSelf

    Reference to instance of self
    pspec

    the GParamSpec of the property which changed.
    handler

    The signal handler to call Run the given callback whenever the notifyScaleFactor signal is emitted
    Show on GitHub
  • notifyScaleFactorSignal Extension method

    Typed notify::scale-factor signal for using the connect(signal:) methods

    Declaration

    Swift

    static var notifyScaleFactorSignal: MonitorSignalName { get }
    Show on GitHub

  • The notify signal is emitted on an object when one of its properties has its value set through g_object_set_property(), g_object_set(), et al.

    Note that getting this signal doesn’t itself guarantee that the value of the property has actually changed. When it is emitted is determined by the derived GObject class. If the implementor did not create the property with G_PARAM_EXPLICIT_NOTIFY, then any call to g_object_set_property() results in notify being emitted, even if the new value is the same as the old. If they did pass G_PARAM_EXPLICIT_NOTIFY, then this signal is emitted only when they explicitly call g_object_notify() or g_object_notify_by_pspec(), and common practice is to do that only when the value has actually changed.

    This signal is typically used to obtain change notification for a single property, by specifying the property name as a detail in the g_signal_connect() call, like this: (C Language Example):

    g_signal_connect (text_view->buffer, "notify::paste-target-list",
                  G_CALLBACK (gtk_text_view_target_list_notify),
                  text_view)

    It is important to note that you must use canonical parameter names as detail strings for the notify signal.

    Note

    This represents the underlying notify::subpixel-layout signal

    Declaration

    Swift

    @discardableResult
@inlinable
func onNotifySubpixelLayout(flags: ConnectFlags = ConnectFlags(0), handler: @escaping (_ unownedSelf: MonitorRef, _ pspec: ParamSpecRef) -> Void) -> Int

    Parameters

    flags

    Flags
    unownedSelf

    Reference to instance of self
    pspec

    the GParamSpec of the property which changed.
    handler

    The signal handler to call Run the given callback whenever the notifySubpixelLayout signal is emitted
    Show on GitHub
  • notifySubpixelLayoutSignal Extension method

    Typed notify::subpixel-layout signal for using the connect(signal:) methods

    Declaration

    Swift

    static var notifySubpixelLayoutSignal: MonitorSignalName { get }
    Show on GitHub

  • The notify signal is emitted on an object when one of its properties has its value set through g_object_set_property(), g_object_set(), et al.

    Note that getting this signal doesn’t itself guarantee that the value of the property has actually changed. When it is emitted is determined by the derived GObject class. If the implementor did not create the property with G_PARAM_EXPLICIT_NOTIFY, then any call to g_object_set_property() results in notify being emitted, even if the new value is the same as the old. If they did pass G_PARAM_EXPLICIT_NOTIFY, then this signal is emitted only when they explicitly call g_object_notify() or g_object_notify_by_pspec(), and common practice is to do that only when the value has actually changed.

    This signal is typically used to obtain change notification for a single property, by specifying the property name as a detail in the g_signal_connect() call, like this: (C Language Example):

    g_signal_connect (text_view->buffer, "notify::paste-target-list",
                  G_CALLBACK (gtk_text_view_target_list_notify),
                  text_view)

    It is important to note that you must use canonical parameter names as detail strings for the notify signal.

    Note

    This represents the underlying notify::valid signal

    Declaration

    Swift

    @discardableResult
@inlinable
func onNotifyValid(flags: ConnectFlags = ConnectFlags(0), handler: @escaping (_ unownedSelf: MonitorRef, _ pspec: ParamSpecRef) -> Void) -> Int

    Parameters

    flags

    Flags
    unownedSelf

    Reference to instance of self
    pspec

    the GParamSpec of the property which changed.
    handler

    The signal handler to call Run the given callback whenever the notifyValid signal is emitted
    Show on GitHub
  • notifyValidSignal Extension method

    Typed notify::valid signal for using the connect(signal:) methods

    Declaration

    Swift

    static var notifyValidSignal: MonitorSignalName { get }
    Show on GitHub

  • The notify signal is emitted on an object when one of its properties has its value set through g_object_set_property(), g_object_set(), et al.

    Note that getting this signal doesn’t itself guarantee that the value of the property has actually changed. When it is emitted is determined by the derived GObject class. If the implementor did not create the property with G_PARAM_EXPLICIT_NOTIFY, then any call to g_object_set_property() results in notify being emitted, even if the new value is the same as the old. If they did pass G_PARAM_EXPLICIT_NOTIFY, then this signal is emitted only when they explicitly call g_object_notify() or g_object_notify_by_pspec(), and common practice is to do that only when the value has actually changed.

    This signal is typically used to obtain change notification for a single property, by specifying the property name as a detail in the g_signal_connect() call, like this: (C Language Example):

    g_signal_connect (text_view->buffer, "notify::paste-target-list",
                  G_CALLBACK (gtk_text_view_target_list_notify),
                  text_view)

    It is important to note that you must use canonical parameter names as detail strings for the notify signal.

    Note

    This represents the underlying notify::width-mm signal

    Declaration

    Swift

    @discardableResult
@inlinable
func onNotifyWidthMm(flags: ConnectFlags = ConnectFlags(0), handler: @escaping (_ unownedSelf: MonitorRef, _ pspec: ParamSpecRef) -> Void) -> Int

    Parameters

    flags

    Flags
    unownedSelf

    Reference to instance of self
    pspec

    the GParamSpec of the property which changed.
    handler

    The signal handler to call Run the given callback whenever the notifyWidthMm signal is emitted
    Show on GitHub
  • notifyWidthMmSignal Extension method

    Typed notify::width-mm signal for using the connect(signal:) methods

    Declaration

    Swift

    static var notifyWidthMmSignal: MonitorSignalName { get }
    Show on GitHub

Monitor Class: MonitorProtocol extension (methods and fields)

  • getConnector() Extension method

    Gets the name of the monitor’s connector, if available.

    Declaration

    Swift

    @inlinable
func getConnector() -> String!
    Show on GitHub
  • getDisplay() Extension method

    Gets the display that this monitor belongs to.

    Declaration

    Swift

    @inlinable
func getDisplay() -> DisplayRef!
    Show on GitHub
  • get(geometry:) Extension method

    Retrieves the size and position of the monitor within the display coordinate space.

    The returned geometry is in ”application pixels”, not in ”device pixels” (see [methodGdk.Monitor.get_scale_factor]).

    Declaration

    Swift

    @inlinable
func get<RectangleT>(geometry: RectangleT) where RectangleT : RectangleProtocol
    Show on GitHub
  • getHeightMm() Extension method

    Gets the height in millimeters of the monitor.

    Declaration

    Swift

    @inlinable
func getHeightMm() -> Int
    Show on GitHub
  • getManufacturer() Extension method

    Gets the name or PNP ID of the monitor’s manufacturer.

    Note that this value might also vary depending on actual display backend.

    The PNP ID registry is located at https://uefi.org/pnp_id_list.

    Declaration

    Swift

    @inlinable
func getManufacturer() -> String!
    Show on GitHub
  • getModel() Extension method

    Gets the string identifying the monitor model, if available.

    Declaration

    Swift

    @inlinable
func getModel() -> String!
    Show on GitHub
  • getRefreshRate() Extension method

    Gets the refresh rate of the monitor, if available.

    The value is in milli-Hertz, so a refresh rate of 60Hz is returned as 60000.

    Declaration

    Swift

    @inlinable
func getRefreshRate() -> Int
    Show on GitHub
  • getScaleFactor() Extension method

    Gets the internal scale factor that maps from monitor coordinates to device pixels.

    On traditional systems this is 1, but on very high density outputs it can be a higher value (often 2).

    This can be used if you want to create pixel based data for a particular monitor, but most of the time you’re drawing to a surface where it is better to use [methodGdk.Surface.get_scale_factor] instead.

    Declaration

    Swift

    @inlinable
func getScaleFactor() -> Int
    Show on GitHub
  • getSubpixelLayout() Extension method

    Gets information about the layout of red, green and blue primaries for pixels.

    Declaration

    Swift

    @inlinable
func getSubpixelLayout() -> GdkSubpixelLayout
    Show on GitHub
  • getWidthMm() Extension method

    Gets the width in millimeters of the monitor.

    Declaration

    Swift

    @inlinable
func getWidthMm() -> Int
    Show on GitHub
  • connector Extension method

    The connector name.

    Declaration

    Swift

    @inlinable
var connector: String! { get }
    Show on GitHub
  • display Extension method

    The GdkDisplay of the monitor.

    Declaration

    Swift

    @inlinable
var display: DisplayRef! { get }
    Show on GitHub
  • heightMm Extension method

    Gets the height in millimeters of the monitor.

    Declaration

    Swift

    @inlinable
var heightMm: Int { get }
    Show on GitHub
  • isValid Extension method

    Returns true if the monitor object corresponds to a physical monitor.

    The monitor becomes invalid when the physical monitor is unplugged or removed.

    Declaration

    Swift

    @inlinable
var isValid: Bool { get }
    Show on GitHub
  • manufacturer Extension method

    The manufacturer name.

    Declaration

    Swift

    @inlinable
var manufacturer: String! { get }
    Show on GitHub
  • model Extension method

    The model name.

    Declaration

    Swift

    @inlinable
var model: String! { get }
    Show on GitHub
  • refreshRate Extension method

    Gets the refresh rate of the monitor, if available.

    The value is in milli-Hertz, so a refresh rate of 60Hz is returned as 60000.

    Declaration

    Swift

    @inlinable
var refreshRate: Int { get }
    Show on GitHub
  • scaleFactor Extension method

    Gets the internal scale factor that maps from monitor coordinates to device pixels.

    On traditional systems this is 1, but on very high density outputs it can be a higher value (often 2).

    This can be used if you want to create pixel based data for a particular monitor, but most of the time you’re drawing to a surface where it is better to use [methodGdk.Surface.get_scale_factor] instead.

    Declaration

    Swift

    @inlinable
var scaleFactor: Int { get }
    Show on GitHub
  • subpixelLayout Extension method

    Gets information about the layout of red, green and blue primaries for pixels.

    Declaration

    Swift

    @inlinable
var subpixelLayout: GdkSubpixelLayout { get }
    Show on GitHub
  • widthMm Extension method

    Gets the width in millimeters of the monitor.

    Declaration

    Swift

    @inlinable
var widthMm: Int { get }
    Show on GitHub