Calling the V7 plugin manager from a custom STV

[GKusnick]

The new V7 UI continues to support the ability for third-party STVs to invoke menus in the stock STV (e.g. the Detailed Setup menu) and then return to the calling STV via gCurCustomSTVFilePath. This is all good, except for the case of calling into the V7 plugin manager. If the user does something that entails a restart of the app, then the STV callback state is lost and the user must reload the third-party STV the old-fashioned way, through Detailed Setup.

Is it feasible for the plugin manager to detect this case and save/restore the STV callback state across a restart, so that the return to the calling STV remains seamless?

[Opus4]

Before I make any changes, how exactly are you looking for this to work?

I'm not sure whether it is better to return directly to the custom STV upon restart, or whether the default STV should be loaded, but keep it aware that it is in custom STV mode.

- Andy

[GKusnick]

Good question. I can imagine a situation in which you upgrade a plugin but can't configure it until after the restart. So in that case you'd probably want to reload the stock STV and maybe even jump straight back into the plugin manager on restart. If that's not what you wanted, you can always hit Home to get out.

That seems friendlier than the alternative, which would be to return to the custom STV on restart and then have to navigate back into the plugin manager to finish your configuration.

But if someone has a contrary opinion I'm open to persuasion.