Be Advised: Classified, FOUO, and PII Content is Not Permitted

  • Replies 16 replies
  • Subscribers 462 subscribers
  • Views 50568 views
  • Users 0 members are here
Related

Magic Draw / Cameo Bugs

Rhett Zimmer

Use this thread to compile Magic Draw / Cameo bugs, along with system/version information, work arounds, and fixes.

 

1. Character Spacing on Comments/Notes when Zoom is not at 100% is off.  (Windows 7, Cameo Systems Modeler, SP1)

2. Comment Anchors to Frames pass through the comment obscuring visibility. (Windows 7, Cameo Systems Modeler, SP1)

3. Ctrl/Shift consistency between selecting Elements in diagram and containment tree. (Windows 7, Cameo Systems Modeler, SP1)

 

If anyone has encountered the same bugs, please list the number and your version/configuration.

 

I intend to contact No Magic at some point in the future.

Parents
  • One of the most annoys me with CSM 18.5 SP2 is how stereotypes are not completely implemented according to UML specification as a disjoint/orthogonal extension mechanism. Specifically, SysML and UPDM profiles have MD Customizations where the SysML and/or UPDM elements are targets of Customization Elements that have the Hide Metatype attribute set to True.

    docs.nomagic.com/.../Hide Metatype

    This creates some real problems when using UPDM according to it's standard or when mixing custom profiles with built in profiles.

    For example, Activities, Interactions and State Machines are all UML metaclasses that are specializations of UML::Class. Thus it should be perfectly allowable to apply the Block stereotype to them. However, this is not the case in CSM. UPDM::Capability has the same issue. In fact I think using UPDM::Capability to extend a UML::Behavior instance is probably better than using it to extend a UML::Class instance.. but not possible thanks to the fact that Hide Metatype for a UPDM::Capability is set to True in the MD Customization.
Reply
  • One of the most annoys me with CSM 18.5 SP2 is how stereotypes are not completely implemented according to UML specification as a disjoint/orthogonal extension mechanism. Specifically, SysML and UPDM profiles have MD Customizations where the SysML and/or UPDM elements are targets of Customization Elements that have the Hide Metatype attribute set to True.

    docs.nomagic.com/.../Hide Metatype

    This creates some real problems when using UPDM according to it's standard or when mixing custom profiles with built in profiles.

    For example, Activities, Interactions and State Machines are all UML metaclasses that are specializations of UML::Class. Thus it should be perfectly allowable to apply the Block stereotype to them. However, this is not the case in CSM. UPDM::Capability has the same issue. In fact I think using UPDM::Capability to extend a UML::Behavior instance is probably better than using it to extend a UML::Class instance.. but not possible thanks to the fact that Hide Metatype for a UPDM::Capability is set to True in the MD Customization.
Children
No Data