@ogoffart I also implemented the behavior for the qt style. It works but on macos the focus state is not displayed. Do you have an idea?

Sorry for the duplicated code

It seems to me that maybe StandardListView should be implemented on a layer above the styles, so that one implementation suffices, which will derive from the ListView of the current style (and probably uses a display item from the style, too). Pretty much as if the StandardListView was part of the application Slint code. Is something like that possible?

Btw, personally I would expect StandardListView to be a thin convenience wrapper on top of ListView. It's weird to me to see stuff like "current item" and focus handling to be done only for the StandardListView, where I expect that due to the limited customization options provided by StandardListView, most people will need to rely on ListView instead and then will need to re-implement all that stuff too.

I also thought about it. I would love also to have a generic variant of the StandardListView that give you the possibility to define the fields and also the look of the items. But I think at the moment it is difficult to split the StandardListView from the style. The problem is that in the ListView itself is the magic for the virtualization. For the scrollbars it needs to inherit the ScrollViewer what is style dependent and so you have also the style dependency from the StandardListView. I. think we need to find a way for the future to better decouple that stuff.

I think also something like delegates in qml would also be a plus.

To maybe clarify a little what I meant with putting StandardListView in another layer, maybe it could work by putting it in a different import, for example:

import { ... } from "std-widgets.slint";
import { StandardListView } from "std-portable-widgets.slint";

Such that std-portable-widgets.slint could be from a different path, independent of the current style, and from that file one could implement it as follows:

import { ListView, ListItem } from "std-widgets.slint";

component StandardListView inherits ListView {
    in property <[StandardListViewListItem]> items;

    // ...

    for item[index] in items: ListItem {
        text: item.text;
        selected: index == root.current-item;

        // ...
    }
}

So that it will pick up the needed customization from whatever is the current style as usual.

At the same time, some of the focus and current item handling code could be moved into ListView, since it would be useful for any list, not just a "standard list".

Edit: Hmm, maybe it doesn't even need to be in a different file, but each std-widgets-base.slint could just have:

import { StandardListView } from "../common/standardlistview.slint";
export { StandardListView }

I see this is already a recurring pattern. Is there a reason it couldn't work for StandardListView? Its import may just need to be changed to:

import { ListView, ListItem } from "std-widgets-impl.slint";

To avoid recursive importing.

I see this is already a recurring pattern. Is there a reason it couldn't work for StandardListView? Its import may just need to be changed to:

Ah yes. Sorry I was a little bit confused. I will give it a try.

@bjorn thank you a lot for the hint. Sure that works. Is now implemented. All styles references now the same StandardListView implementation.