AnacondaSpokeWindow

AnacondaSpokeWindow — Window for displaying single spokes

Functions

Signals

Types and Values

Object Hierarchy

    GObject
    ╰── GInitiallyUnowned
        ╰── GtkWidget
            ╰── GtkContainer
                ╰── GtkBin
                    ╰── AnacondaBaseWindow
                        ╰── AnacondaSpokeWindow

Implemented Interfaces

AnacondaSpokeWindow implements AtkImplementorIface and GtkBuildable.

Description

A AnacondaSpokeWindow is a widget that displays a single spoke on the screen. Examples include the keyboard and language configuration screens off the first hub.

The AnacondaSpokeWindow consists of two areas:

  • A navigation area in the top of the screen, inherited from AnacondaBaseWindow and augmented with a button in the upper left corner.

  • An action area in the rest of the screen, taking up a majority of the space. This is where widgets will be added and the user will do things.

CSS nodes

1
2
AnacondaSpokeWindow
╰── #anaconda-spoke-window-button

The button in the upper left is accessible as the name "anaconda-spoke-window-button" for the purposes of CSS selectors.

Functions

anaconda_spoke_window_new ()

GtkWidget *
anaconda_spoke_window_new ();

Creates a new AnacondaSpokeWindow, which is a window designed for displaying a single spoke, such as the keyboard or network configuration screens.

Returns

A new AnacondaSpokeWindow.

Types and Values

struct AnacondaSpokeWindow

struct AnacondaSpokeWindow;

The AnacondaSpokeWindow struct contains only private fields and should not be directly accessed.


struct AnacondaSpokeWindowClass

struct AnacondaSpokeWindowClass {
    AnacondaBaseWindowClass parent_class;

    void (* button_clicked)  (AnacondaSpokeWindow *window);
};

Members

button_clicked ()

Function pointer called when the “button-clicked” signal is emitted.

 

Signal Details

The “button-clicked” signal

void
user_function (AnacondaSpokeWindow *window,
               gpointer             user_data)

Emitted when the button in the upper left corner has been activated (pressed and released). This is commonly the button that takes the user back to the hub, but could do other things. Note that we do not want to trap people in spokes, so there should always be a way back to the hub via this signal, even if it involves canceling some operation or resetting things.

Parameters

window

the window that received the signal

 

user_data

user data set when the signal handler was connected.

 

Flags: Action

Since: 1.0