On 13/05/10 08:34, Bob Tarling wrote: > I'm investigating http://argouml.tigris.org/issues/show_bug.cgi?id=6086 > > At the moment the list of Operations that could belong to a CallEvent > is restricted. > > What's the purpose of this restriction? I see nothing in the spec that > limits what Operation a CallEvent can reference. Am I missing a WFR > here? > > Bob > >
Hi Bob, et al., Be sure to read issue 2288 and 4395. http://argouml.tigris.org/issues/show_bug.cgi?id=2288 http://argouml.tigris.org/issues/show_bug.cgi?id=4395 IIRC, it would be best that you can include only visible operations. Hence, if an elementImport causes an operation to be visible, it should also be included. If you show all operations in the model, then you will have to show the complete path, not only the operation name itself. This because many classes have equally named operations. So, it would be easiest to show only the operations of the context of the statemachine: then we can limit ourselves to only show the operation name. I do not know if we best limit to operations of the context of the statemachine, or the namespace of the statemachine, or something else... We can cover all possibilities with a button to progressively disclose further choices, as described in issue 4395 (but maybe even multiple levels). Regards, Michiel ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=2608568 To unsubscribe from this discussion, e-mail: [[email protected]]. To be allowed to post to the list contact the mailing list moderator, email: [[email protected]]
