Tabs not restored on restart (Godot 4.6 and 0.5-DEV-3.0.0.1)

[adancau]

I haven't seen an option on this in Editor settings, but my personal expectation as a developer would be that it probably should. I sometimes have quite a bunch of tabs open with specific sets of files, and restoring them from the side-panel isn't the most straight forward.

Case in point:
This is what my current session looks like:

I'm now restarting Godot. This is the active tab now:

I want to press one of the + buttons to create a split - however they are all disabled:

I need to double-click and open a file from the side panel to get the buttons to enable and be able to create a split. I'm expecting the buttons enable on an open file sort of signal - which isn't getting fired or is not caught when the IDE is first opened

[CodeNameTwister]

You mention two points:

1. Persistence of divisions and tabs

Reopening the split and tab settings could be an optional setting that i could add as a optional feature, but you should keep in mind point number 2.

2. Loading the entire list on startup

If you only see one tab when you launch the plugin or restart godot,

splitting isn't possible because no other files are loaded.

The plugin v0.5 follows the same logic as Godot: lazy loading, / lazy selection..

Even though you see other scripts in the script list after restarting, they aren't loaded into memory internally; they're loaded when you select them.

Script Splitter haved an optional option in its settings to load all those scripts at once on restart, but it was inefficient because it placed a large load on memory when the editor started.

In conclusion, an option to restore the configuration along with all tabs could be made optional feature.

However, in practice, this is inefficient, and given that experience in previous versions some scripts marked as @tool were checked internally in memory even when not referenced,

this could cause errors in current versions therefore, this feature should be something that is well thought out and tested for a good amount of time..

NOTE:
Perhaps you're coming from a previous version, 0.4.

Previous versions allowed reopening scripts, but this function was managed through a predefined split configuration, unlike version 0.5, which has a more flexible system for creating splits.

Therefore, it was an incompatible feature mentioned in Main Feature Removed #23

[adancau]

Understood. I actually come from 2 or 3 I think :) It's been a while.

Re: point no. 2 - lazy loading could still be performed I think, by loading only the scripts that are visible in the split panels. E.g. In a 2-split configuration you would only have 2 visible scripts (out of any number of scripts) - which could be loaded initially. The rest don't need to be loaded on start-up, since they are virtually hidden, and each of them can be loaded practically on demand when the user switches to their respective tab. I doubt people would have an insane amount of splits, my guess would be a 4-way split at maximum, with 2 and 3 being the majority - which isn't a super huge amount of scripts to load on start I think.

Obviously I don't know the architecture behind Script Splitter and how feasible my proposal is in context

[CodeNameTwister]

That sounds similar to what was done in previous versions.

Doing it that way in v0.5 would mean adding more lines of code compared to simply adding an option to keep the same view and restore split settings of open scripts upon exiting.

In short, fulfilling your suggestion of saving all the split configuration and open scripts in each split is better.

So, making it an optional feature that can be enabled in the editor settings will be enough to solve this problem.