In recent implementation for class methods umbrello uses stereotypes to indicate specific method extensions for example "constexpr", "constructor", "destructor". According to http://coliru.stacked-crooked.com/view?id=4aafceef2486b6bf does a constructor also could be a constexpr which requires to have multiple stereotypes added to the method. This is not supported yet.
This task requires the following steps: 1. Migrate stereotype related class members to hold a list of stereotypes (class UMLObject) - related class members are m_pStereotype and m_SecondaryId 2. Refactor the internal api to get, set, add and remove stereotypes (class UMLObject) 3. Refactor client code depending on stereotype related api to use the new api 4. Refactor saving stereotypes into file and loading stereotypes from files (class UMLObject) - The xmi file format already supports a space separated list of stereotypes id references, see https://cgit.kde.org/umbrello.git/tree/doc/xml/01-02-16.dtd#n334 5. Extend gui to support multiple stereotypes in diagram widgets (widgets in umlwidgets subdir) 6. Extend property dialogs to support displaying, selecting and changing multiple stereotypes (class StereotypeWidget in dialogs/widgets subdir in combination with related dialogs)
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!
Still valid (as is the case for many other longstanding quiescent PRs)