Session loss saved (Perdita sessione salvata).

[admin]

Went this way:

Code: Select all

    + Tabs: Added a tweak that effectively allows you to start each session with the same 
      tabs, regardless of what changes you made to the tabs during the last session.
        TabsetsExplicitSaveOnly=1
      As the name suggests, the tweak protects the current tabset from changes made by 
      "Save Configuration". Now the only way to change the current tabset permanently 
      (i.e. on disk) is the command Tabsets | Save.
      If I find a catchy name for it, I'll add it to UI soon.

[Rosso Fuoco]

Per risolvere il problema, XYplorer dovrebbe partire da un set con nome fisso (es.:XY1 pannello 1, XY2 pannello 2).
Nel salvare si dà un nome al SET e in automatico XYplorer ritorna a quello fisso (XY), con le cartelle aperte assegnate al set salvato.
La funzione salva dovrebbe sovrascrivere l'ultimo set caricato.

To solve the problem, XYplorer should start from a set with a fixed name (e.g. XY1 panel 1, XY2 panel 2).
When saving, a name is given to the SET and automatically XYplorer returns to the fixed one (XY), with the open folders assigned to the saved set.
The save function should overwrite the last loaded set.

[admin]

Forget the journey, focus on the destination: Where do you want to go? Where do you want to be? What do you want?

[RalphM]

I still don't see what the OP's problem was?
I tried to explain a way to achieve such behavior.

I work with various different tabsets, which are loaded either in pane 1 or 2 and the only thing that bugged me every now and then was the inability to see whether the loaded tabset was still "as saved", so a "dirty" marker would have been helpful at times.

Shouldn't the new tweak rather force the tabsets in both panes - that were present when the session was closed, if available - to be revert to their saved state on startup?

Where are the voices of other tabset & session manager users? This will affect them too, I assume.

[admin]

I work with various different tabsets, which are loaded either in pane 1 or 2 and the only thing that bugged me every now and then was the inability to see whether the loaded tabset was still "as saved", so a "dirty" marker would have been helpful at times.

Are you using the TabsetsCanRevertAcrossSessions tweak? (Then a tabset can be dirty a long time, and across sessions, which would explain why you're unsure whether it's dirty )

Shouldn't the new tweak rather force the tabsets in both panes - that were present when the session was closed, if available - to be revert to their saved state on startup?

Isn't that what it does?

[RalphM]

Are you using the TabsetsCanRevertAcrossSessions tweak?

Yes, seems like it, though I don't recall ever setting this.
Was this the new default when it was introduced?
The only time I restart XY is after an update to the newest beta, otherwise it is always open.

Isn't that what it does?

I don't know, haven't tested it yet but the name doesn't necessarily suggest such behavior.

[admin]

Code: Select all

v19.80.0131 - 2019-03-30 13:55
    * Tabsets: Before, tabsets were revertible across sessions. If you did not 
      explicitly save a tabset you could always go back to the last-saved state 
      by clicking "Revert to Saved", and that worked across sessions. There was 
      a "temporary-saved state" in a folder called "t" (saved when doing a "File 
      | Save Settings") and a "final-saved state" in the folder above "t" (saved 
      when doing a "Tabsets | Save").
      Now this behavior is a bit crazy since all other settings in XYplorer are 
      handled differently. Therefore I changed it: From now on tabsets are NOT 
      revertible anymore across sessions, but only within the session. If you 
      save settings, or exit the app with "Save settings on exit" enabled, then 
      the current tabsets (one in each pane) are *finally* saved to disk. 
      Clicking "Revert to Saved" will go back to that saved state.
      Since this is an important change I cared for a soft transition:
      - I added a tweak that allows you to stay with the old behavior:
          TabsetsCanRevertAcrossSessions=1
      - On upgrading to this version this tweak is automatically set to 1, so 
        nothing will change for you unless you explicitly change that tweak to 0:
          TabsetsCanRevertAcrossSessions=0
      - In a fresh installation, of course, that tweak is now set to 0 to enable 
        the new behavior.
      - Note that, if TabsetsCanRevertAcrossSessions=0, any still existing 
        temporary states (in "t"-folders) are still *read*, otherwise you would 
        lose the last temporary-saved states of your tabsets and fall back hard 
        to the last final-saved states. After the next "Save Settings" these 
        folders will just disappear and never come back again.

[RalphM]

Okay, I see the logic in these two tweaks now.
However, for me it still makes more sense to keep tabsets revertible across sessions and not force them to be revert to saved on restart automatically but maybe that's just me.
I always looked at them as templates that I saved when needed but would always let me go back to a "clean" state after messing tabs up.

Still a "dirty" marker would help to know which state your tabset is in.

[admin]

Not as easy. There are sooo many different things that belong to a tabset. The good news is: After some time you can almost be sure it's dirty.