1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77

// This file was generated by gir (https://github.com/gtk-rs/gir)
// from gir-files (https://github.com/gtk-rs/gir-files.git)
// DO NOT EDIT

use crate::LayoutManager;
use glib::object::Cast;
use glib::translate::*;
use std::fmt;

glib::wrapper! {
    /// [`FixedLayout`][crate::FixedLayout] is a layout manager which can place child widgets
    /// at fixed positions.
    ///
    /// Most applications should never use this layout manager; fixed positioning
    /// and sizing requires constant recalculations on where children need to be
    /// positioned and sized. Other layout managers perform this kind of work
    /// internally so that application developers don't need to do it. Specifically,
    /// widgets positioned in a fixed layout manager will need to take into account:
    ///
    /// - Themes, which may change widget sizes.
    ///
    /// - Fonts other than the one you used to write the app will of course
    ///  change the size of widgets containing text; keep in mind that
    ///  users may use a larger font because of difficulty reading the
    ///  default, or they may be using a different OS that provides different
    ///  fonts.
    ///
    /// - Translation of text into other languages changes its size. Also,
    ///  display of non-English text will use a different font in many
    ///  cases.
    ///
    /// In addition, [`FixedLayout`][crate::FixedLayout] does not pay attention to text direction and
    /// thus may produce unwanted results if your app is run under right-to-left
    /// languages such as Hebrew or Arabic. That is: normally GTK will order
    /// containers appropriately depending on the text direction, e.g. to put labels
    /// to the right of the thing they label when using an RTL language;
    /// [`FixedLayout`][crate::FixedLayout] won't be able to do that for you.
    ///
    /// Finally, fixed positioning makes it kind of annoying to add/remove UI
    /// elements, since you have to reposition all the other elements. This is a
    /// long-term maintenance problem for your application.
    ///
    /// # Implements
    ///
    /// [`LayoutManagerExt`][trait@crate::prelude::LayoutManagerExt], [`trait@glib::ObjectExt`]
    #[doc(alias = "GtkFixedLayout")]
    pub struct FixedLayout(Object<ffi::GtkFixedLayout, ffi::GtkFixedLayoutClass>) @extends LayoutManager;

    match fn {
        type_ => || ffi::gtk_fixed_layout_get_type(),
    }
}

impl FixedLayout {
    /// Creates a new [`FixedLayout`][crate::FixedLayout].
    ///
    /// # Returns
    ///
    /// the newly created [`FixedLayout`][crate::FixedLayout]
    #[doc(alias = "gtk_fixed_layout_new")]
    pub fn new() -> FixedLayout {
        assert_initialized_main_thread!();
        unsafe { LayoutManager::from_glib_full(ffi::gtk_fixed_layout_new()).unsafe_cast() }
    }
}

impl Default for FixedLayout {
    fn default() -> Self {
        Self::new()
    }
}

impl fmt::Display for FixedLayout {
    fn fmt(&self, f: &mut fmt::Formatter) -> fmt::Result {
        f.write_str("FixedLayout")
    }
}