Hi again,
I'm pretty sure it's the perspective, or more insidiously the perspective
category, that trips you up.
Perspectives don't work properly, and they confuse people. It's another misguided attempt to simplify the GUI, but Sparx didn't actually work out exactly how this new way of controlling aspects of functionality would interact with all other ways of controlling aspects of functionality before they released it, and they've been floundering around ever since. There were several changes in 15, major changes in 15.1, and I'd expect more of them going forward.
Here's what I think happened.
The User Technologies perspective falls under the Specialized category (introduced in 15.0), which refers specifically to technologies
imported into the project -- not to user-defined ones in general.
The perspective acts as a filter in certain EA functions, primarily in dialogs such as New Diagram. However, the underlying technology is still loaded into the client and all its contents are still available for various uses. (One of the recent changes was to allow document and code templates from a technology to be used even though the technology is not in perspective, another was to allow the creation of composite diagrams from a not-in-perspective technology.)
The Manage MDG Technologies dialog shows which technologies are available, whether from a file or the project, and/or loaded (= selected). It isn't affected by perspectives.
So if you have deployed your technology to a file, and loaded it, the User Technologies perspective will hide its diagram types in New Diagram.
If you then import the same technology into the project, the perspective will allow you to see the diagram type since the technology is now a "user" (ie imported) technology. But the client in fact has two identical diagram type definitions available to it from two identical technologies, one loaded from the file and one from the project.
So internally in EA, the dialog presumably retrieves the list of diagram types from the technology manager, then for each diagram type asks the perspective manager whether the type is in perspective. Since there are two copies of the technology loaded, the technology manager will supply two copies of the diagram type to the dialog, the dialog will ask the perspective manager about the "same" diagram type twice, and the perspective manager will say Yes both times. There's nothing else it can do, really.
What needs to be changed is that EA should baulk when asked to load a technology (when opening a project or changing the technology configuration) that is already loaded, regardless of where the technology is located. In your case, that would have prevented you from loading the technology into the project without first unloading the file version.
HTH,
/Uffe