Statusbar
Object Hierarchy:
Description:
[ Version ( deprecated = true , deprecated_since = "4.10" ) ]
public sealed class Statusbar : Widget, Accessible, Buildable, ConstraintTarget
Warning: Statusbar is deprecated since 4.10.
A `GtkStatusbar` widget is usually placed along the bottom of an application's main [class@Gtk.
This widget will be removed in GTK 5
Window].
![An example GtkStatusbar](statusbar.png)
A `GtkStatusBar` may provide a regular commentary of the application's status (as is usually the case in a web browser, for example), or may be used to simply output a message when the status changes, (when an upload is complete in an FTP client, for example).
Status bars in GTK maintain a stack of messages. The message at the top of the each bar’s stack is the one that will currently be displayed.
Any messages added to a statusbar’s stack must specify a context id that is used to uniquely identify the source of a message. This context id can be generated by [method@Gtk.Statusbar.get_context_id], given a message and the statusbar that it will be added to. Note that messages are stored in a stack, and when choosing which message to display, the stack structure is adhered to, regardless of the context identifier of a message.
One could say that a statusbar maintains one stack of messages for display purposes, but allows multiple message producers to maintain sub-stacks of the messages they produced (via context ids).
Status bars are created using [ctor@Gtk.Statusbar.new].
Messages are added to the bar’s stack with [method@Gtk.Statusbar.push].
The message at the top of the stack can be removed using [method@Gtk.Statusbar.pop]. A message can be removed from anywhere in the stack if its message id was recorded at the time it was added. This is done using [method@Gtk.Statusbar.remove].
CSS node
`GtkStatusbar` has a single CSS node with name `statusbar`.