routing stack and restoring states ?

[moolight-seashell]

Is there a way to create a router things, to navigate between pages
like for example "a stack" routing like flutter allowing to push new page while be able to restore se state of older page is we pop the current page ?

even with scroll list or event custom lazy loading scrolls list ... ?

because from what i've understand , there is no "components" in the available property types

[lzm-build]

See if this helps.

[moolight-seashell]

nope this d'ont awnser the state part

[moolight-seashell]

Given a custom component:

import { Button } from "std-widgets.slint";

export component Counter {
    in-out property <int> value: 0;

    VerticalLayout {
        Text {
            text: "Value: " + value;
        }

        Button {
            text: "Increment";
            clicked => {
                value += 1;
            }
        }
    }
}

Approach 1, Using if statment

export component MainWindow inherits Window {
    in-out property <bool> show_counter: true;

    VerticalLayout {
        Button {
            text: show_counter ? "Hide" : "Show";
            clicked => {
                show_counter = !show_counter;
            }
        }

        if (show_counter) : Counter {
        }
    }
}

Behavior

• The component is destroyed and recreated every time
• Internal state (value) is not preserved

Approach 2, Using visible propety

export component MainWindow inherits Window {
    in-out property <bool> show_counter1: true;

    VerticalLayout {

        Button {
            text: show_counter1 ? "Show 2" : "Show 1";
            clicked => {
                show_counter1 = !show_counter1;
            }
        }

        Rectangle {
            Counter {
                visible: show_counter1;
            }

            Counter {
                visible: !show_counter1;
            }
        }

        Text {
            text: "test";
        }
    }
}

Behavior

• Components stay instantiated
• Internal state is preserved

Drawbacks

• All components are always loaded
• Hidden components still affect layout size calculations
• Requires workarounds (e.g., wrapping in Rectangle)
• Makes layouting more complex and less predictable

While it might be tempting to combine both approaches:

• It quickly becomes impractical
• Still does not provide a proper navigation stack, and a fine control of what is loaded
• You cannot easily maintain multiple instances of the same component (like a real router would)