ListView Suggestions

[WildByDesign]

@HotCakeX I wasn't sure if this needed an actual Issue or not but wanted your opinion first. If it makes sense, I am happy to create a proper suggestion in the Issues.

I'm referring specifically to the beautiful ListView used in System Information. But if you have other ListViews, it may be useful there too.

• use a monospaced font (Cascadia Mono or, if not available, Consolas)

The purpose here would be to make it easier when viewing the Policy ID's and Base Policy ID's. The spacing of the font lines them up nice and evenly and less crammed together like default font. It's easier on the eyes.

• convert Policy ID's and Base Policy ID's to uppercase

I am not 100% decided on this. I understand that CiTool reports Policy ID's and Base Policy ID's in lowercase. The XML files generally store the ID's in uppercase and they get switched to lowercase once deployed, same as filenames in C:\Windows\System32\CodeIntegrity\CIPolicies\Active.

Converting to uppercase would really depend on what looks most appropriate for viewing in the GUI. For this, I would say try and see if it looks better or not. Like I said, I'm not fully decided on converting to uppercase yet or not. But I do believe using the monospaced font would be best.

By the way, keep up the incredible work!

[WildByDesign]

I just did a quick test on my end and the second suggestion of converting to uppercase ended up being worse, in my opinion. The Policy ID's and Base Policy ID's in the ListView ended up appearing much "busier" on the eyes. Not so wonderful.

First suggestion of monospaced font is still fantastic, at least in my testing.

[HotCakeX]

Hi,
Thanks for the suggestion ^^

Here is a screenshot for the current design

And this is with Consolas

And this is with Cascadia Mono

I think Cascadia Mono looks better than Consolas and better than the normal font too.

[HotCakeX]

The reason why i haven't worked on this yet is because changing the fonts while a ListView has like thousands of data in it would need the data to be re-evaluated to adjust column sizes based on the new font.

I have ideas about changing ListViews to accommodate virtually unlimited data but it's gonna need structural changes and only after that i can offer different fonts for them.

so i'm prioritizing a bit but it's definitely coming ^_^

[WildByDesign]

Thanks. I appreciate that you're following up on this. I understand that the structural changes may take time. It definitely looks really great in the screenshot, particularly the Cascadia Mono. Take as much time as you need. :)

[WildByDesign]

I was just thinking about this for a few minutes right now. I don’t know this programming language at all.

However, isn’t there any way that you can set the font right before the LV control is created and immediately change the font back to your default font so that any controls created after LV will still get your default?

Changing the font after the LV control is created seems more complex way to go.

But like I said, I don’t know this language so I am just thinking out loud.

[HotCakeX]

The problem is the data loaded in the LV. We have to calculate the width of the columns based on the available data and selected font, it only happens once. If user changes the LV font in the settings and comes back to the page with LV, the data will overflow because the previous column widths are too small for the new font, so column widths should be re-calculated.

I'm going to implement incremental collections so that the column widths are actively calculated when new data comes into view.

https://learn.microsoft.com/en-us/windows/uwp/debug-test-perf/listview-and-gridview-data-optimization

[WildByDesign]

I understand what you mean now. That makes sense.

[HotCakeX]

Hi @WildByDesign
I finally implemented this by offering an option to select any font you like for list view items, you can give it a try and let me know what you think ^^
#848

[WildByDesign]

@HotCakeX Thank you for the update, Violet. I still can't get over how fast your app is! Great work.

I think that the ListViews look fantastic now being able to select any font. Particularly the monospaced fonts. But it's great to have choice.

The only nitpick that I have is that the font family list is not completely in alphabetical order. Minor thing. But at first it made me think that Cascadia Code was missing. It ended up being down near the very bottom of the list.

[HotCakeX]

Ah thanks so much!

That's a great idea, it'll be sorted in the next version. if the fonts list gets too big i'll add a search box too.