Orbiter now searches for graphics client plugins within an optional module subfolder #183
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As discussed in this thread, with the help of @Face-1 I've changed plugin load behavior to:
This is useful for cases where plugin A.dll depends on B.dll. Currently orbiter searches for DLLs on the PATH. This means users must install all dependency plugin DLLs to Modules or Modules/Plugins, which adds clutter and potential conflicts between plugins. With this new behavior, a plugin and all its dependencies can be installed to its own subfolder, and will not interfere with the loading of other plugins.
I have only introduce this behavior for graphics clients. If this feature is successful, it would be good to extend the behavior to all module types (vessels etc) as well.