Opened 5 years ago
Closed 3 years ago
#11187 closed feature request (fixed)
BASE: Plugins - Must load entire Engine implementation to access the corresponding MetaEngine
| Reported by: | henke37 | Owned by: | sev- |
|---|---|---|---|
| Priority: | normal | Component: | --Other-- |
| Version: | Keywords: | metaengine, plugin | |
| Cc: | Game: |
Description
The plugin system allows loading engines on demand. At least, that's the theory.
But there is one notable design weakness: the metaengines are included in the plugins. As such the launcher can't add or edit games without loading the entire plugin for the engine.
This wouldn't be so bad, if it wasn't for the fact that you need the metaengine to know which engine, and thusly plugin, will handle a game that the user is trying to add. This effectively leads to loading every plugin (unloading the previous one first) and hoping that it can detect a game in the folder. The mass adding system is even worse off due to loading the plugin for every possible game anew for every scanned folder.
Change History (2)
comment:1 by , 4 years ago
| Summary: | Must load entire Engine implementation to access the corresponding MetaEngine → BASE: Plugins - Must load entire Engine implementation to access the corresponding MetaEngine |
|---|---|
| Type: | defect → enhancement |
comment:2 by , 3 years ago
| Owner: | set to |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
This has been addressed with splitting out the detection into separate plugins.