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 - Paolo F Cantoni

Pages: [1] 2 3 ... 403
Bugs and Issues / Re: V14RC: [Alt+Z] functionality Gone!
« on: April 20, 2018, 10:36:36 am »
It still (mostly) works for me, although sometimes the ribbon appears to eat the combination.
Yes, that's the problem.  For me, it doesn't seem to work at all so far.  I'll reboot at some time and confirm the problem is still there. I'm on Windows 7.


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).

There is some "method in their madness".



I had a look at the time aware modelling feature and decided that it is not useful for me or my clients.
It really quickly becomes a mix of elements from different versions, all linked to each other.
Definitely not how I would design a feature like that.

Geert, Any cloning system will end up as a "mix of elements from different versions".  The trick is how to manage it properly.  We're looking at implementing our own cloning system (hopefully compatible with Sparx's) to do it a bit better.


Bugs and Issues / Re: Time-aware models: revert clone
« on: April 20, 2018, 10:14:32 am »
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?

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.


Bugs and Issues / Re: Time-aware MDG Technology models
« on: April 20, 2018, 10:10:52 am »
... No it won't, and no it won't.

Thanks for the "heads up".

As per my reply to the Import/Export topic, I suspect it's working correctly (at present).  I'll have a look (when I get a minute or two) to better understand your point.


Bugs and Issues / Re: Import/export of time-aware models
« on: April 20, 2018, 10:02:17 am »
Hi Uffe,

Like you, having delved into TAM, I'm a bit concerned about some of the current functionality (and more particularly, the UI).

However, from my (still limited) knowledge of TAM, the export is working correctly.  The uncloned vertices are (and probably should) NOT part of the versioned folder.  Consequently, the export should be the same as for a non-TAM package.  I thought these days, the export exported "stubs" for the out-of-branch vertices.  If you're saying the stubs are missing, then that's a bug.

The problem (as I see it) with what you are asking is that (as I said above) the uncloned vertices are in a different structure.  If you force EA to export them as part of this structure, you are exporting a corrupted model.  However, that having been said, there may be use cases where such an export is useful.  Can you elaborate on yours?


Bugs and Issues / Re: Data Model - bug on saving the diagram
« on: April 20, 2018, 09:55:56 am »
Still a problem 8 years later in 13.5.

Working on a saved diagram, deleting and recreating the association in between the tables, with no other changes, causes the diagram to be flagged as needing saved. Trying to close the diagram without saving still results in the FK constraint being deleted. The diagram still shows the correct association link in between the tables with all of the correct labels, but without the constraint in place.
Hi lweath,

I'm not sure it's a bug (in Sparx's view).  As part of standard diagram processing, if you don't a diagram on closing with a NEW vertex or arc, EA assumes that you didn't want them and will purge them from the model.

In your case deleting (I assume yo9u mean purging from the model - not just hiding on the diagram) and creating the NEW arc will "dirty" the diagram.  Thus, it needs to be saved.  In the case of a Foreign Key Constraint, the issue is more complicated because you (effectively) have a two-step process.  Have you confirmed that saving the "dirty" diagram correctly saves the FK Constraint?

I have some sympathy for Sparx's view but the EAUI could have been better framed to alert users to what may happen.



As an alternative, you could compare the xml files "functionally".

I had this same requirement to compare XSD files in a "functional" way -> ignoring the order of elements (where not important), whitespace, order of attributes, etc...
(we are migrating a Magicdraw model + XSD generation to EA + XSD generation and we need to know if the XSD's (about 500 of them) are functionally still 100% the same while allowing non-important differences)
What I end up doing was building my own comparer based on a code sample I found on a Microsoft website.

I uploaded it to github. I think you only need to change the (hardcoded) .xsd extension to .xml to make it compare xml file.

Thanks, Geert!

That should be really useful!  I'll give it a try when I get to work.

However, that doesn't change my need to know the expected output order.  You know my views on consistency.  Why is that outlier present?  I'm always nervous with "unknowns".


Metatypes too, please!  We're trying to wean our users off stereotypes - which in our MDG are quite cryptic and move them to metatypes.
Did you even look at what was being requested? It's used metatypes for years.
My Bad, I was only looking at the column headings (which, of course, on reflection, includes both Types and Metatypes)


Bugs and Issues / V14RC: [Alt+Z] functionality Gone!
« on: April 19, 2018, 02:51:02 pm »
V14RC: The [Alt+Z] key combination no longer resizes to the default element sizing.

Is there a ribbon/menu command to do that?  We use it all the time!


Where would that order be important? I guess in the toolbox? If so (IIRC) EA does not offer an ordering from the MDG export (since IIRC I tried that once and could not figure it out).

Well, we have an existing MDG which is in a particular order  Arcs (alphabetical) followed by Vertices (alphabetical).  We are trying to regenerate the same content from the repository, so we use file comparators to compare what we generate with what we wanted to generate.  The file comparators work on text and so the order of the output is important, to help up do the comparison.

The generated MDG appears to have output the  Vertices (corrupted alphabetical) followed by Arcs (alphabetical).  I say corrupted alphabetical because the Vertices had an outlier (from close to the end alphabetically) stuck at the front, but the rest appear alphabetical.   (EAUI?)

Also, at the moment, the metatypes are intermingled in the same package and we want to separate them for ease of management, we'd like to know if that will affect the output.

So, could anyone, but especially a Sparxian, indicate how the output order is determined?
(For example, if it IS/should be Vertices (alphabetical) followed by Arcs (alphabetical), then we can easily cut and paste our original MDG file and swap.  Then "we're off and racing"!  :) )


We've started to look at converting our "hand-rolled" MDG file to a formal MDG metamodel using the MDG Generator.

One nice thing about our hand-rolled version is that WE decide what the order of the stereotypes is.  Is it possible to influence the output order via the generator?


General Board / Re: Glossary plural terms
« on: April 18, 2018, 09:38:04 am »
Now, Now children,

Both of you go sit in the opposite corners and say sorry!   :D

You can only come out when you've agreed to behave!      ;)

I believe it was irony, Joyce.


General Board / Re: 'Link' Connector type - did I imagine it ?
« on: April 17, 2018, 09:54:04 am »
Hi Ian,

IIRC, Links are instances of Associations.  As you say, they are used to link a specific instance (of a classifier) to another specific instance (of another, possibly the same, classifier).

I guess you could also use stereotyped versions to handle aggregation and composition links.


Bugs and Issues / Re: Log file from XMI import
« on: April 13, 2018, 04:39:44 pm »
You are right. I overlooked that since the im-/export dialog restricts display to .xm* files (as an Apple user I'm used to see other files greyed out; hum - Windoze). Anyway, the log just tells me that everything is find while the import croaks with an error. And after close/open EA everything is imported. Time for a new bug report :-/

Sparx has a conceptual problem with "logs".  They obviously didn't didn't watch Startrek (especially series 1).  Logs are to be written in real time and with a timestamp.  Otherwise, they aren't logs!  (That's why the show is interrupted with the log (to make the log)).


Pages: [1] 2 3 ... 403