[Feature] Saving the display/layout view for VMs

[ZoltrixGFC]

Love the project!

Describe the feature

When navigating to PVE Server > Resource Management, changing the display/layout view for VMs works temporarily, but navigating away and returning resets the window back to its default layout. The interface does not remember or persist user view preferences.

Use Case

It would be a great if the selected view state in Resource Management could persist - either by writing the user's preference to the browser's 'localStorage' or by updating the router's query parameters.

Alternatives considered

Manually re-clicking and toggling back to my preferred layout view every time I jump back to the node's resource page.

How important is this for you?

Just a nice to have 👍

Checklist

• I have searched existing issues and discussions to make sure this hasn't been requested before

[mkellermann97]

Good catch — and you've nailed the cause: the Diagram/Cards toggle in Resource Management is in-memory React state, so it falls back to the default every time the view remounts. localStorage is exactly the right approach; we already persist sibling view prefs that way (topology legend, collapsed nodes, taskbar height), so it slots in cleanly. One wrinkle I want to handle properly first: the Cards view is hidden in a multi-cluster context, so a restored "cards" preference needs a sane fallback there. It's a low-risk polish win and I've queued it. Thanks for the clear report and the localStorage suggestion — opencollective.com/pegaprox keeps these moving. — Marcus

[MrMasterbay]

Thanks for the suggestion, and apologies for the back-and-forth — Marcus had queued this, but after a closer look we're going to pass on it. The Diagram/Cards view toggle is shared between the standard and corporate layouts, and persisting it cleanly across both (Cards is hidden in multi-cluster and in the corporate layout) turned out fiddly enough that the regression risk to the layout outweighs the convenience of a nice-to-have. We'd rather not destabilise the layout for it. Closing as not planned — but if the reset actually disrupts a real workflow (rather than being mildly annoying), reopen with the detail and we'll happily reconsider. — NS