Per-Tab-Sessions

[Kaze-Kami]

So, you have some sort of session: If you configure something, then close the tab and re-open it the setup you made is still there.
You can also open multiple tabs, and set up different builds - or compare stuff, etc...
However if you close and re-open the browser with 2 configurations (tabs) open, they will then both contain the same setup.

I am aware that I can save and load these, however it would be nice if it would 'just work out of the box', remembering the last state for each tab independently.

[Kaze-Kami]

I've never written rust nor do I know the libraries you're using but from some looking around I think the answer would be somewhere along the lines of:

1. Use Session-Storage (which is tab specific, unlike Local-Storage) to save some kind of 'Tab-Id' (https://stackoverflow.com/a/36807854/10330869)
2. Save/Load the current setup specifically using that 'Tab-Id' somewhere here (just as if the user pressed the save/load buttons from the ui):

• space-engineers-calculator/code/gui/src/app/mod.rs

  Line 56 in a7a2bfb

  pub fn new(ctx: &eframe::CreationContext<'_>) -> Self {

• space-engineers-calculator/code/gui/src/app/mod.rs

  Line 297 in a7a2bfb

  fn save(&mut self, storage: &mut dyn eframe::Storage) {

3. Omit these 'auto-saves' from the list in the 'Load' menu. (e.g. prefix them so they can be filtered)

[Gohla]

Sorry for the late response and thanks for the suggestion!

Currently, all data is indeed stored per browser session. If you open multiple tabs, the session is loaded into the tab on load, and whenever you save, the data is stored (overridden) into the local browser data. This actually makes it problematic to have multiple tabs open, as saving in tab 1, and then saving in tab 2, the data from 2 will override the data from tab 1.

A proper solution to the problem would:

1. Store the "current grid" in the URL, update the URL whenever a change is made. Many similar kind of tools (such as https://factoriolab.github.io) do this, and also allows easily linking a grid to someone else.
2. Store the saved grids in local data, but instead of overriding the data there, always merge the data so multiple tabs can safely load/save stuff. This requires checking the local storage every time a load/save is done.
3. Determine when and where to store the rest of the settings: dark mode, font size, enabled mods, etc. GUI settings are probably fine to store in local storage and override, while enabled mods belong with the grid and in the URL I think.

However, there does not seem to be an easy way to do 1 with egui, so a custom solution using web-sys needs to be made. Also, I currently cannot spend a lot of time on this app. I would be open to a PR that implements this though.