Hi,
it just happened to me so was thinking it can be useful for others too : when using the Shared memory action, you don't directly see where your shared memory is going to be stored. So you may mess up a bit when re-opening a project from a server and not having selected the correct repository (like being on the local file one while your shared memories are in the space one).
When dealing with connectors, you exactly know where they are stored as you first select the repository and then see the connectors. With shared memories you actually don't know where they are stored and can then create your keys several times in different repos.
So I was wondering if it will be possible to have the space / repository information displayed (at least read-only) in the Shared memory action ?
Thanks !
Hi Olivier,
You can actually see the current location of the repository (and Shared Memory) in the application's status bar. The name changes whether it's a file or a server space.
Would that work for you?
Hi Dmitry,
That's actually a good hint. I never realized this info was there 
Regarding the shared memory, I just feel not at ease to manage them. For the connectors, you have a specific window where you can switch from Repo to Space, see if you have connectors with the same name in both side, delete the ones you don't want anymore and so on. Here, for the shared memory, to manage them (and see you may have duplicates between repo file and space), you have to create an action to list them, run it, then go connectors to change the repo, back to your action to list again. Then to remove one, you need to change the action to forget it and run the action.
I love the fact that you can manipulate shared memories on the run (and we should keep that) but it's difficult to clean up if you need to (error like mine, or removing the ones not used anymore after your project is finalized).
Clearly not a blocking point, but could be nice to have 
Thanks !
