Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot hide/mask name of extension point on <<Extends>> relationship line #93

Closed
bobhairgrove opened this issue Feb 6, 2024 · 3 comments

Comments

@bobhairgrove
Copy link

I have use cases with extension points and other use cases which are in a «Extend» relation to the main use case as in the following diagram. This is to express as UML the main menu and its submenus which are to appear in the GUI of my application.

The extension points are already defined in the main (target) use case, but I cannot mask the duplicate name which appears on the line. When I select just the label, and select "Mask Selection" from the context menu, it hides the entire line, which I do not want. However, I also do not want to clutter up the diagram by duplicating the names of the extension points.

Here is a sample part of the diagram:
Use_Cases_cropped

My Modelio version is here:
about_Modelio

Is there some way to accomplish this?

Also, is there a way to increase the margin of whitespace around the diagram (without resorting to tricks such as creating text labels with invisible characters such as non-breaking spaces)?

@bobhairgrove
Copy link
Author

I just installed the newest Modelio (5.4), and the issue still exists.

If I do not reference an extension point in the target use case, Audit reports this as an error. If I select the extension point, it shows it on the diagram, and I cannot hide it.

@IrinaNeculita
Copy link

Hi,
No, the label for "extension relationship" cannot be hide.
Audit displays an "advice", R2900.

@bobhairgrove
Copy link
Author

Perhaps it is not a good idea to express menus and submenus like this in UML?

I think I will use packages with use cases instead of extension points. The menus which contain submenus or menu items have no functionality independent of the menu items, so maybe these higher-up menus would be best modelled as packages?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants