Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Uffe

Pages: [1] 2 3 ... 80
1
Bugs and Issues / CallOperationActions in project browser
« on: April 20, 2018, 10:04:54 pm »
Hi all,


A CallBehaviourAction is displayed with its classifier in the project browser on the form action_name : classifier_name.
A CallOperationAction, on the other hand, doesn't display its operation.

Shouldn't it?

Something like action_name : element_name::operation_name, where element is the interface, class, component or whatever that holds the operation?


/Uffe

2
If you create a stereotype for Action and assign it a shape script which prints the Classifier or Classifier.Name property, the expected behaviour for a CallOperationAction is that the name of the operation (when set) is printed. It is not.

When you set the action's operation, the name of that operation is printed -- but only until the diagram is closed. When next it is opened, nothing is printed although you can still Find the operation from the action.

It appears that classifiers defined by the GUID string and not the integer ID aren't handled correctly by the shape script engine.

/Uffe

3
If you create a stereotype for CallOperationAction on the fly, then assign it a shape script in Configure -- UML Types, and then create a CallOperationAction in an activity diagram and give it that stereotype, the shape script is not executed.

If you modify the stereotype to apply to Action, it is executed correctly on the same CallOperationAction.


/Uffe

4
Oh, and I found that if you've got the situation I had above, then select the non-cloned package in the cloned diagram and hit Clone Element as New Version, the old package is replaced by the new one in the diagram, and subsequently, the Clone Element menu item is greyed out.
As per my previous comments in the other TAM posts, I suspect it's working correctly.  Since the requirement for the initial clone of the diagram is to NOT clone any vertex, it is incumbent upon the user to determine which vertices to clone (including folders).
I'm not convinced. The way it works, the package has been cloned, but the original is shown in the cloned diagram.
Why would you want that?

Only reason I can see is that the cloned package doesn't contain any elements so you need the original in order to show package contents. But that only makes sense in the first generation anyway, so this is still more bug than feature in my book.

Still, if you're aware of it you can fix it immediately after parthenogenesis.1

/U


1 That's "creating a clone", children.

5
Bugs and Issues / Re: Time-aware MDG Technology models
« on: April 20, 2018, 06:49:05 pm »
Yes, and I agree with you, but there was also something that specifically didn't work when you exported from the diagram. Wish I could remember what.

OTOH, if you want to reuse a toolbox page between toolbox profiles you've got to export from the diagram. Unless they've done something with that in recent versions?

/Uffe

6
Bugs and Issues / Re: Time-aware models: revert clone
« on: April 20, 2018, 06:43:41 pm »
As far as I'm aware there's not.  I can also tell you why (I think).  In my topic on TAM where I discuss sequential versus parallel cloning; when you clone an early version which has subsequent versions, you get the latest version ONLY.  The cloned element has NO memory of where it was cloned from and so you can't revert.  It doesn't know which version to revert to.

Ah, but it does -- I'm reverting to the previous version. I'm not talking about parallel branches here, just a basic "undo check-out" if you will, of a single element.

The element I'm reverting has the special-dodgy-kludgy trace connector to its predecessor. Which diagrams that predecessor is in is easily checked, so restoring those occurrences to the cloned diagrams (where the predecessor has been replaced by the clone) should be no harder when reverting than when cloning the diagram in the first place.

I'm fully prepared to accept that you can't revert an element which has already been cloned in turn (ie has an inbound special-dodgy-kludgy trace relationship), but you should be able to back up from the head.

Amirite?


/Uffe

7
Bugs and Issues / Re: Time-aware MDG Technology models
« on: April 20, 2018, 04:52:26 pm »
Hi Paolo, and thanks for taking the time. I was hoping you would. :)

MDG Technology development is my use case for time-aware exports. Rather than using the diagram's context menu item to generate a profile (which isn't an XMI export, but still an export of sorts) I've always used the project browser's.1

Being able to maintain TAM-style version-controlled MDG Technology models would be useful, but it would require that profile generation from cloned models included the non-cloned elements.

I should mention here that I haven't tested generating a profile from a TAM-cloned diagram, which might well work. My overall point is that the TAM functionality should be better integrated, and the generate-profile-from-browser function is an example of how it isn't.2


/Uffe


1There was something that didn't use to work when you used the diagram's menu. I can't remember what now and I don't know if it's ever been resolved but the two menu items did not yield the same result (!) (!!) (!!!!) (why isn't there an emoji with its hair on end?) so I went with the one that worked for me.

2Also I'm pretty much making this up as I go.

8
Bugs and Issues / Re: Custom Script fragments not working in 13.5.1352
« on: April 20, 2018, 04:08:23 pm »
Aww.... Killjoy.  :'(

9
General Board / Re: Where are user passwords stored?
« on: April 20, 2018, 12:46:49 am »
Ha!

I was gonna say, as a joke, "it's probably in t_xref." :)

/Uffe

10
Oh, and I found that if you've got the situation I had above, then select the non-cloned package in the cloned diagram and hit Clone Element as New Version, the old package is replaced by the new one in the diagram, and subsequently the Clone Element menu item is greyed out.

FWIW.

/Uffe

11
Yeah, it's looking that way from my perspective too. Kind of a cool demo feature, but it doesn't seem to have been integrated in any meaningful way, it doesn't support multiple branches and it doesn't seem to be possible to revert changes.

I'm trying to imagine what use case it's been designed for, but I'm coming up empty. It looks like something put together by someone who's never actually worked with version control or configuration management.

/Uffe

12
Bugs and Issues / Time-aware models: revert clone
« on: April 19, 2018, 10:14:14 pm »
Hi boys & girls,

I can't find a function to revert a cloned element in a diagram, in other words destroy the cloned element and replace it in the diagram with the original.

Isn't there one?


/Uffe

13
Bugs and Issues / Re: Time-aware MDG Technology models
« on: April 19, 2018, 10:10:58 pm »
... No it won't, and no it won't.

/U

14
Bugs and Issues / Re: Import/export of time-aware models
« on: April 19, 2018, 10:05:04 pm »
I've tested XMI export, which doesn't include the old versions. Most likely the same goes for CSV.

In order for time-aware models to be useful, they need to be fully integrated with other EA functions, like export. There should be a setting which allows you to specify whether exports should be time-aware or not; alternatively there should be a question pop-up when exporting from a cloned version.

Similarly, in the API, a new method Repository.ExportPackageXMITimeAware() should be added, which includes all the non-cloned contents for a time-aware package structure.

/Uffe

15
Bugs and Issues / Import/export of time-aware models
« on: April 19, 2018, 09:41:36 pm »
Hellu,


If I clone a package structure to a new version, and then export the new version as XMI, will the exported XMI include the non-cloned elements from the original version?

Similarly, if I do a CSV export will the non-cloned elements be included?


/Uffe

Pages: [1] 2 3 ... 80