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 - Geert Bellekens

Pages: 1 ... 3 4 [5] 6 7 ... 513
Bugs and Issues / Re: Bug when copying package
« on: October 20, 2017, 02:59:48 pm »
adding a relation to an element should be considered changing it as much as adding an attribute
Depends on the direction.
With adding relation to element I mean adding a relation owned by the element.

When copying something my expectation is that everything it owns is copied as well, but I don't expect or want it to copy anything it doesn't own.
And that is exactly what EA is doing. It is duplicating relations not owned by the element I'm copying.
That seems like a clear and simple bug to me.


Cool, thanks Simon!


General Board / Re: Security Disabled - How to reset security
« on: October 20, 2017, 02:25:12 am »
Or you can change the setting directly in the database ;D


Bugs and Issues / Re: Case Sensitive Problem with Searches
« on: October 19, 2017, 11:50:12 pm »
Searches are not stored in the DB but in an xml file in your %appdata%

I think EA's dropdown simply filters out duplicates but does it case insensitive.

If you really need direct control just edit the xml file.


I guess that is the reason why they developed the profile helper.

I'm lucky as I never had to work without it, so I never payed much attention to the actual resulting attributes.


Bugs and Issues / Re: Bug when copying package
« on: October 19, 2017, 05:51:41 pm »

It wasn't clear from the original post if it was JUST Generalization that has the problem.  If so, then it's a bug (as probably is demonstrated by your workaround).  ;D

It isn't just Generalization. It happens with dependencies too, and I suppose with most, if not all, relations.
But anyhow, it is still a bug if copying a package changes elements in entirely different packages all over the model. (adding a relation to an element should be considered changing it as much as adding an attribute)
I don't see any way you could justify that, not even conceptually.


Is there a reason why you can't or don't want to use the API?

Two reasons actually.
1. IIRC EA opens each and every diagram before saving its image
2. Performance.

Context: One of the add-ins I'm working on exports a part of the model to xmi and uploads that to a web-server to get processed.
I was asked if I could include all the diagram images of the exported part as well.

The thing is that this export/upload/download is an interactive process where the users usually waits for it to finish.
So obviously performance is of the essence here, and opening each and every diagram would simply be pretty darn annoying.

And also, in 99% of the cases, at least 99% of the diagrams haven't changed, so it would make sense to get them from the cache instead of having EA generate the images each time around.

Unless of course you are saying that I can somehow ask the API to get the image from the cache rather then to re-generate it. That would really be the ideal case. :)


You'll need to use the API provided to save that image.

Unless you enlighten us and tell us how to get the image from the cache :D
Please.. pretty please...? :P


Bugs and Issues / Re: Bug when copying package
« on: October 19, 2017, 02:33:13 pm »
I don't agree with that Paolo.

On the conceptual level making a copy of package A should never ever change elements in package B.
Adding a generalization to elements in package B is definitely changing them.

On the practical level this bug has the potential to really mess up you model. Nobody is expecting or wanting that behavior, and nobody will know all the elements that have a dependency to elements in the copied class.

Workaround to fix it:

- Export the copy of package A to xmi
- Delete the copy of package A
- Import the xmi into a new empty model
- Export the copy of package A back to xmi
- Import the new xmi back into the model


Bugs and Issues / Bug when copying package
« on: October 19, 2017, 12:31:55 am »
When copying a package you can get nasty side effect if other classes are depending on classes in the copied package.
E.g. classes in other packages that have a generalization to classes being copied now have two generalizations. One to the original, and one to the copied class.

Steps to Reproduce:
- create packageA with classA
- create packageB with classB
- create generalization from classB to classA
- copy packageA (full structure for duplication)
- paste packageA resulting in a copy of packageA
- notice that classB now has two generalizations. One to the original ClassA, and one to the copied ClassA.



The error is a database error, not an XmlDom error, so it should be something on the database side.

EA does some pre-processing with the SQL's we send trough, so it might be related to that. I would really look into the dbError.txt and what you can see on the profiler.

Might not be related, but if you are only interested in the DiagramID, why are you returning all those other fields in your query?


Look into %appdata%\Sparx Systems\DBerror.txt or turn on the profiler on your SQL server.

That should given you some more info on the error you are getting. It will probably be something other then this actual query.


It was, I didn't read it properly. :-[

So did you also add the tagged value definition to the MDG file?
And did you use the profile helper to select the tagged value type?

The devil is often in those minute details when dealing with MDG's and stuff.


I haven't seen SfSTime as a valid tagged value type.

I see Time and TimeStamp as alternatives



General Board / Re: Help with the help
« on: October 18, 2017, 09:49:02 pm »
But from there the Odyssey goes on. The tree-structure of the former object model is completely gone.

It isn't gone, it just hides behind the [TOPICS] button.
Took me a while to figure that out as well.


Pages: 1 ... 3 4 [5] 6 7 ... 513