Disabling Set Package as Namespace Root (for a root Node)

[Eve]

I am still eagerly awaiting a reply on how to hierarchise the example of my post dated September 06, 2021, 06:15:59 pm. This should give an idea of, to quote Paolo, how suboptimal the use or namespaces is in Sparx EA.

All the blue packages become the one conceptual namespace. The 'root' namespace.

By the way, the reason for the example is because somehow I can see an interplay between how namespaces are used/can be used and how to create UML profiles for used in MDG.

I don't think they are used at all by profiles or MDG.

Also sharing my latest reply to an exchange with the support team regarding this:

The issue is around consistency of user experience. The issue is not about being able to set the namespace root property through the GUI for root nodes. If standard functionality is for all root nodes to be namespace roots, I have no problem with it. But I have a problem with an inconsistent user experience which leads me (and other users) to believe root nodes are not always namespace roots.

How is it reflected in the user interface?

The fixes are so simple that I do not understand why it has to be debated:

The debate isn't about possible fixes. It's you saying EA should offer an option and me/sparx saying there's no reason for it. If we decide something needs to be fixed, the method that happens also won't be up for debate.

[Modesto Vega]

By the way, the reason for the example is because somehow I can see an interplay between how namespaces are used/can be used and how to create UML profiles for used in MDG.

I don't think they are used at all by profiles or MDG.

I'll address this separately when I have more time.

Also sharing my latest reply to an exchange with the support team regarding this:

The issue is around consistency of user experience. The issue is not about being able to set the namespace root property through the GUI for root nodes. If standard functionality is for all root nodes to be namespace roots, I have no problem with it. But I have a problem with an inconsistent user experience which leads me (and other users) to believe root nodes are not always namespace roots.

How is it reflected in the user interface?

In 2 ways, the user interface:

• creates all root nodes with the namespace property set to NULL or 0.
• the "Set Package as Namespace root" and "Supress Namespace" menu items are both active for root nodes - i.e., can be used - but do nothing as discuss at length in this thread.

The correct functionality should be:

• ensuring that all root nodes are created with namespace property correctly set (to 1)
• disabling the "Set Package as Namespace root" and "Supress Namespace" menu items for root nodes

[Eve]

I don't think they are used at all by profiles or MDG.

I'll address this separately when I have more time.
[/quote]
Save your time. Wanting to use it for something else it's not intended for doesn't mean that thing is wrong.

creates all root nodes with the namespace property set to NULL or 0.

Which is exactly what I'm saying is expected and what EA should be doing.

the "Set Package as Namespace root" and "Supress Namespace" menu items are both active for root nodes - i.e., can be used - but do nothing as discuss at length in this thread.

Where? I can't see any place where that is showing. The good news is that the handler is not relying on the item being disabled or hidden and is correctly not changing anything.