Complete STV versus imports in 2.1?

[jdbrown]

Would someone clarify the difference between using a complete custom STV like those listed in sticky and using the vailable import STV functions? Specifically, can I choose any STV - original2 or custom and then also add additional functionality using any/all of the import STVs?

With this new import STV functionality, it seems everyone can create their own custom version of a customized or original STV. Am I understanding correctly?

[Opus4]

See page 149 of the v2.1 manual. Loading an STV loads a completely new interface file & makes it the active one. Loading an import module loads the update into an existing STV, adding to it or changing its functionality. Use with caution.

Some imports are available here: STV IMPORTS: Nielm STV Modules

- Andy

[stanger89]

A complete STV is just that, Complete, it needs nothing else to run. An import is... I guess patch would probably be the correct term. An import STV has the potential to add new functionality, change current functionality, change the current look/feel, etc. They aren't really plugins since, at present, there's no way to "un-import" an imported STV.

You can import any STV into any other STV, however the results are not guaranteed. For example an STV import could expect/rely on parts of the OriginalV2 STV, but if you import it into, say mlbude's SageMC STV, some things might be missing. Before importing an STV, I'd make a backup copy of the one you'll be importing into, just in case.

[jdbrown]

Thanks - that makes sense.