PopoverProtocol

public protocol PopoverProtocol : BinProtocol

GtkPopover is a bubble-like context window, primarily meant to provide context-dependent information or options. Popovers are attached to a widget, passed at construction time on gtk_popover_new(), or updated afterwards through gtk_popover_set_relative_to(), by default they will point to the whole widget area, although this behavior can be changed through gtk_popover_set_pointing_to().

The position of a popover relative to the widget it is attached to can also be changed through gtk_popover_set_position().

By default, GtkPopover performs a GTK+ grab, in order to ensure input events get redirected to it while it is shown, and also so the popover is dismissed in the expected situations (clicks outside the popover, or the Esc key being pressed). If no such modal behavior is desired on a popover, gtk_popover_set_modal() may be called on it to tweak its behavior.

GtkPopover as menu replacement

GtkPopover is often used to replace menus. To facilitate this, it supports being populated from a GMenuModel, using gtk_popover_new_from_model(). In addition to all the regular menu model features, this function supports rendering sections in the model in a more compact form, as a row of icon buttons instead of menu items.

To use this rendering, set the ”display-hint” attribute of the section to ”horizontal-buttons” and set the icons of your items with the ”verb-icon” attribute.

<section>
  <attribute name="display-hint">horizontal-buttons</attribute>
  <item>
    <attribute name="label">Cut</attribute>
    <attribute name="action">app.cut</attribute>
    <attribute name="verb-icon">edit-cut-symbolic</attribute>
  </item>
  <item>
    <attribute name="label">Copy</attribute>
    <attribute name="action">app.copy</attribute>
    <attribute name="verb-icon">edit-copy-symbolic</attribute>
  </item>
  <item>
    <attribute name="label">Paste</attribute>
    <attribute name="action">app.paste</attribute>
    <attribute name="verb-icon">edit-paste-symbolic</attribute>
  </item>
</section>

CSS nodes

GtkPopover has a single css node called popover. It always gets the .background style class and it gets the .menu style class if it is menu-like (e.g. GtkPopoverMenu or created using gtk_popover_new_from_model().

Particular uses of GtkPopover, such as touch selection popups or magnifiers in GtkEntry or GtkTextView get style classes like .touch-selection or .magnifier to differentiate from plain popovers.

The PopoverProtocol protocol exposes the methods and properties of an underlying GtkPopover 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 Popover. Alternatively, use PopoverRef as a lighweight, unowned reference if you already have an instance you just want to use.

Show on GitHub
  • ptr

    Untyped pointer to the underlying GtkPopover instance.

    Declaration

    Swift

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

    Typed pointer to the underlying GtkPopover instance.

    Default Implementation

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

    Declaration

    Swift

    var popover_ptr: UnsafeMutablePointer<GtkPopover>! { get }
    Show on GitHub

  • Required Initialiser for types conforming to PopoverProtocol

    Declaration

    Swift

    init(raw: UnsafeMutableRawPointer)
    Show on GitHub

Popover Class

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

    Declaration

    Swift

    @discardableResult
@inlinable
func bind<Q, T>(property source_property: PopoverPropertyName, 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 Popover property

    Declaration

    Swift

    @inlinable
func get(property: PopoverPropertyName) -> 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 Popover property. Note that this will only have an effect on properties that are writable and not construct-only!

    Declaration

    Swift

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

    Parameters

    property

    the property to get the value for

    Return Value

    the value of the named property

    Show on GitHub

Popover signals

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

    Declaration

    Swift

    @discardableResult
@inlinable
func connect(signal s: PopoverSignalName, 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 PopoverSignalName signal

    Declaration

    Swift

    @discardableResult
@inlinable
func connect(signal s: PopoverSignalName, 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
  • onClosed(flags:handler:) Extension method

    This signal is emitted when the popover is dismissed either through API or user interaction.

    Note

    This represents the underlying closed signal

    Declaration

    Swift

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

    Parameters

    flags

    Flags
    unownedSelf

    Reference to instance of self
    handler

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

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

    Declaration

    Swift

    static var closedSignal: PopoverSignalName { 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::constrain-to signal

    Declaration

    Swift

    @discardableResult
@inlinable
func onNotifyConstrainTo(flags: ConnectFlags = ConnectFlags(0), handler: @escaping (_ unownedSelf: PopoverRef, _ 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 notifyConstrainTo signal is emitted
    Show on GitHub
  • notifyConstrainToSignal Extension method

    Typed notify::constrain-to signal for using the connect(signal:) methods

    Declaration

    Swift

    static var notifyConstrainToSignal: PopoverSignalName { 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::modal signal

    Declaration

    Swift

    @discardableResult
@inlinable
func onNotifyModal(flags: ConnectFlags = ConnectFlags(0), handler: @escaping (_ unownedSelf: PopoverRef, _ 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 notifyModal signal is emitted
    Show on GitHub
  • notifyModalSignal Extension method

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

    Declaration

    Swift

    static var notifyModalSignal: PopoverSignalName { 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::pointing-to signal

    Declaration

    Swift

    @discardableResult
@inlinable
func onNotifyPointingTo(flags: ConnectFlags = ConnectFlags(0), handler: @escaping (_ unownedSelf: PopoverRef, _ 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 notifyPointingTo signal is emitted
    Show on GitHub
  • notifyPointingToSignal Extension method

    Typed notify::pointing-to signal for using the connect(signal:) methods

    Declaration

    Swift

    static var notifyPointingToSignal: PopoverSignalName { 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::position signal

    Declaration

    Swift

    @discardableResult
@inlinable
func onNotifyPosition(flags: ConnectFlags = ConnectFlags(0), handler: @escaping (_ unownedSelf: PopoverRef, _ 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 notifyPosition signal is emitted
    Show on GitHub
  • notifyPositionSignal Extension method

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

    Declaration

    Swift

    static var notifyPositionSignal: PopoverSignalName { 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::relative-to signal

    Declaration

    Swift

    @discardableResult
@inlinable
func onNotifyRelativeTo(flags: ConnectFlags = ConnectFlags(0), handler: @escaping (_ unownedSelf: PopoverRef, _ 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 notifyRelativeTo signal is emitted
    Show on GitHub
  • notifyRelativeToSignal Extension method

    Typed notify::relative-to signal for using the connect(signal:) methods

    Declaration

    Swift

    static var notifyRelativeToSignal: PopoverSignalName { 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::transitions-enabled signal

    Declaration

    Swift

    @discardableResult
@inlinable
func onNotifyTransitionsEnabled(flags: ConnectFlags = ConnectFlags(0), handler: @escaping (_ unownedSelf: PopoverRef, _ 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 notifyTransitionsEnabled signal is emitted
    Show on GitHub

  • Typed notify::transitions-enabled signal for using the connect(signal:) methods

    Declaration

    Swift

    static var notifyTransitionsEnabledSignal: PopoverSignalName { get }
    Show on GitHub

Popover Class: PopoverProtocol extension (methods and fields)

  • bind(model:actionNamespace:) Extension method

    Establishes a binding between a GtkPopover and a GMenuModel.

    The contents of popover are removed and then refilled with menu items according to model. When model changes, popover is updated. Calling this function twice on popover with different model will cause the first binding to be replaced with a binding to the new model. If model is nil then any previous binding is undone and all children are removed.

    If action_namespace is non-nil then the effect is as if all actions mentioned in the model have their names prefixed with the namespace, plus a dot. For example, if the action “quit” is mentioned and action_namespace is “app” then the effective action name is “app.quit”.

    This function uses GtkActionable to define the action name and target values on the created menu items. If you want to use an action group other than “app” and “win”, or if you want to use a GtkMenuShell outside of a GtkApplicationWindow, then you will need to attach your own action group to the widget hierarchy using gtk_widget_insert_action_group(). As an example, if you created a group with a “quit” action and inserted it with the name “mygroup” then you would use the action name “mygroup.quit” in your GMenuModel.

    Declaration

    Swift

    @inlinable
func bind(model: GIO.MenuModelRef? = nil, actionNamespace: UnsafePointer<gchar>? = nil)
    Show on GitHub
  • bind(model:actionNamespace:) Extension method

    Establishes a binding between a GtkPopover and a GMenuModel.

    The contents of popover are removed and then refilled with menu items according to model. When model changes, popover is updated. Calling this function twice on popover with different model will cause the first binding to be replaced with a binding to the new model. If model is nil then any previous binding is undone and all children are removed.

    If action_namespace is non-nil then the effect is as if all actions mentioned in the model have their names prefixed with the namespace, plus a dot. For example, if the action “quit” is mentioned and action_namespace is “app” then the effective action name is “app.quit”.

    This function uses GtkActionable to define the action name and target values on the created menu items. If you want to use an action group other than “app” and “win”, or if you want to use a GtkMenuShell outside of a GtkApplicationWindow, then you will need to attach your own action group to the widget hierarchy using gtk_widget_insert_action_group(). As an example, if you created a group with a “quit” action and inserted it with the name “mygroup” then you would use the action name “mygroup.quit” in your GMenuModel.

    Declaration

    Swift

    @inlinable
func bind<MenuModelT>(model: MenuModelT?, actionNamespace: UnsafePointer<gchar>? = nil) where MenuModelT : MenuModelProtocol
    Show on GitHub
  • getConstrainTo() Extension method

    Returns the constraint for placing this popover. See gtk_popover_set_constrain_to().

    Declaration

    Swift

    @inlinable
func getConstrainTo() -> GtkPopoverConstraint
    Show on GitHub
  • getDefaultWidget() Extension method

    Gets the widget that should be set as the default while the popover is shown.

    Declaration

    Swift

    @inlinable
func getDefaultWidget() -> WidgetRef!
    Show on GitHub
  • getModal() Extension method

    Returns whether the popover is modal, see gtk_popover_set_modal to see the implications of this.

    Declaration

    Swift

    @inlinable
func getModal() -> Bool
    Show on GitHub
  • getPointingTo(rect:) Extension method

    If a rectangle to point to has been set, this function will return true and fill in rect with such rectangle, otherwise it will return false and fill in rect with the attached widget coordinates.

    Declaration

    Swift

    @inlinable
func getPointingTo<RectangleT>(rect: RectangleT) -> Bool where RectangleT : RectangleProtocol
    Show on GitHub
  • getPosition() Extension method

    Returns the preferred position of popover.

    Declaration

    Swift

    @inlinable
func getPosition() -> GtkPositionType
    Show on GitHub
  • getRelativeTo() Extension method

    Returns the widget popover is currently attached to

    Declaration

    Swift

    @inlinable
func getRelativeTo() -> WidgetRef!
    Show on GitHub
  • getTransitionsEnabled() Extension method

    Returns whether show/hide transitions are enabled on this popover.

    get_transitions_enabled is deprecated: You can show or hide the popover without transitions using gtk_widget_show() and gtk_widget_hide() while gtk_popover_popup() and gtk_popover_popdown() will use transitions.

    Declaration

    Swift

    @available(*, deprecated)
@inlinable
func getTransitionsEnabled() -> Bool
    Show on GitHub
  • popdown() Extension method

    Pops popover down.This is different than a gtk_widget_hide() call in that it shows the popover with a transition. If you want to hide the popover without a transition, use gtk_widget_hide().

    Declaration

    Swift

    @inlinable
func popdown()
    Show on GitHub
  • popup() Extension method

    Pops popover up. This is different than a gtk_widget_show() call in that it shows the popover with a transition. If you want to show the popover without a transition, use gtk_widget_show().

    Declaration

    Swift

    @inlinable
func popup()
    Show on GitHub
  • setConstrainTo(constraint:) Extension method

    Sets a constraint for positioning this popover.

    Note that not all platforms support placing popovers freely, and may already impose constraints.

    Declaration

    Swift

    @inlinable
func setConstrainTo(constraint: GtkPopoverConstraint)
    Show on GitHub
  • setDefault(widget:) Extension method

    Sets the widget that should be set as default widget while the popover is shown (see gtk_window_set_default()). GtkPopover remembers the previous default widget and reestablishes it when the popover is dismissed.

    Declaration

    Swift

    @inlinable
func setDefault(widget: WidgetRef? = nil)
    Show on GitHub
  • setDefault(widget:) Extension method

    Sets the widget that should be set as default widget while the popover is shown (see gtk_window_set_default()). GtkPopover remembers the previous default widget and reestablishes it when the popover is dismissed.

    Declaration

    Swift

    @inlinable
func setDefault<WidgetT>(widget: WidgetT?) where WidgetT : WidgetProtocol
    Show on GitHub
  • set(modal:) Extension method

    Sets whether popover is modal, a modal popover will grab all input within the toplevel and grab the keyboard focus on it when being displayed. Clicking outside the popover area or pressing Esc will dismiss the popover and ungrab input.

    Declaration

    Swift

    @inlinable
func set(modal: Bool)
    Show on GitHub
  • setPointingTo(rect:) Extension method

    Sets the rectangle that popover will point to, in the coordinate space of the widget popover is attached to, see gtk_popover_set_relative_to().

    Declaration

    Swift

    @inlinable
func setPointingTo<RectangleT>(rect: RectangleT) where RectangleT : RectangleProtocol
    Show on GitHub
  • set(position:) Extension method

    Sets the preferred position for popover to appear. If the popover is currently visible, it will be immediately updated.

    This preference will be respected where possible, although on lack of space (eg. if close to the window edges), the GtkPopover may choose to appear on the opposite side

    Declaration

    Swift

    @inlinable
func set(position: GtkPositionType)
    Show on GitHub
  • set(relativeTo:) Extension method

    Sets a new widget to be attached to popover. If popover is visible, the position will be updated.

    Note: the ownership of popovers is always given to their relative_to widget, so if relative_to is set to nil on an attached popover, it will be detached from its previous widget, and consequently destroyed unless extra references are kept.

    Declaration

    Swift

    @inlinable
func set(relativeTo: WidgetRef? = nil)
    Show on GitHub
  • set(relativeTo:) Extension method

    Sets a new widget to be attached to popover. If popover is visible, the position will be updated.

    Note: the ownership of popovers is always given to their relative_to widget, so if relative_to is set to nil on an attached popover, it will be detached from its previous widget, and consequently destroyed unless extra references are kept.

    Declaration

    Swift

    @inlinable
func set<WidgetT>(relativeTo: WidgetT?) where WidgetT : WidgetProtocol
    Show on GitHub
  • set(transitionsEnabled:) Extension method

    Sets whether show/hide transitions are enabled on this popover

    set_transitions_enabled is deprecated: You can show or hide the popover without transitions using gtk_widget_show() and gtk_widget_hide() while gtk_popover_popup() and gtk_popover_popdown() will use transitions.

    Declaration

    Swift

    @available(*, deprecated)
@inlinable
func set(transitionsEnabled: Bool)
    Show on GitHub
  • constrainTo Extension method

    Returns the constraint for placing this popover. See gtk_popover_set_constrain_to().

    Declaration

    Swift

    @inlinable
var constrainTo: GtkPopoverConstraint { get nonmutating set }
    Show on GitHub
  • defaultWidget Extension method

    Gets the widget that should be set as the default while the popover is shown.

    Declaration

    Swift

    @inlinable
var defaultWidget: WidgetRef! { get nonmutating set }
    Show on GitHub
  • modal Extension method

    Sets whether the popover is modal (so other elements in the window do not receive input while the popover is visible).

    Declaration

    Swift

    @inlinable
var modal: Bool { get nonmutating set }
    Show on GitHub
  • position Extension method

    Sets the preferred position of the popover.

    Declaration

    Swift

    @inlinable
var position: GtkPositionType { get nonmutating set }
    Show on GitHub
  • relativeTo Extension method

    Returns the widget popover is currently attached to

    Declaration

    Swift

    @inlinable
var relativeTo: WidgetRef! { get nonmutating set }
    Show on GitHub
  • transitionsEnabled Extension method

    Returns whether show/hide transitions are enabled on this popover.

    get_transitions_enabled is deprecated: You can show or hide the popover without transitions using gtk_widget_show() and gtk_widget_hide() while gtk_popover_popup() and gtk_popover_popdown() will use transitions.

    Declaration

    Swift

    @inlinable
var transitionsEnabled: Bool { get nonmutating set }
    Show on GitHub
  • parentInstance Extension method

    Undocumented

    Declaration

    Swift

    @inlinable
var parentInstance: GtkBin { get }
    Show on GitHub