Inter-process communication (IPC) implementation about amulet-editor HOT 4 OPEN

In terms of handling multiple versions of Amulet, I think that each version should be treated as a different application since I don't think we want to deal with the bugs that such a feature could introduce.

from amulet-editor.

So what kind of data we expect to transfer between instances of Amulet? The way we resolve this will probably vary depending on what all needs to be transferred and how that information will be stored by each instance.

For instance, plugins will be saved as files somewhere on the user's computer so we probably won't need to send plugin files between instances. User selections probably will need to be transferred but I'm curious if we could hook into the clipboard on the user's computer to transfer that data. I'm not familiar with the complexity and limitations of the clipboard.

from amulet-editor.

I came across QLocalServer and QLocalSocket yesterday which seem like a better option. I have added them to the top post.

Transfer of data is one component I am thinking about. Eg moving a copied structure between processes.
This problem could also be solved with QSharedMemory or by just saving the data to a file.

The extended version is being able to call functions in a remote process.
PySide6 has QDBus which allows calling slots across processes but it is linux only.
I think we could implement a cross-platform version of this using the socket mechanism.

A mechanism like this will be required to notify all processes that a plugin has been enabled or disabled globally.

from amulet-editor.

When we are doing world conversion with a source world that is already open we will need to either close the process that holds the source world or use IPC to pull the data for each chunk to paste into the destination world.

from amulet-editor.