Book a Demo

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] 2 3 ... 899
1
Bugs and Issues / Re: Moving up/down class attributes does not work?
« on: January 21, 2026, 12:23:18 am »
Are you using the features window?

That is where I do it using ctrl-up or ctrl-down

Geert

2
I think the term "composite diagram" is a bit unfortunate as it has connotations that it probably shouldn't have.

When explaining the concept to EA users I often use "linked diagram". I explain to them that this works like a hyperlink. It is the diagram that is opened when doubleclicking on the element.
For me it does not have any other meaning, and it only exists to help us humans navigate the model.

Geert




3
Hi Neil,

Just to give you a heads up. Posting here is to make other users aware of the issue. If you want to report it to Sparx, you have to use the report a bug form on the website:

https://sparxsystems.com/support/forms/bug_report.html

Geert

4
Hi Takeshi,

Looks nice and all, but I'm afraid I'm still a bit underwhelmed by all this.

It looks to me like this AI agent does only does the stuff I can easily do myself.
I would be really enthousiastic if it would do the hard stuff

- Do proper layout of my diagram
   - all elements the same size
   - elements as the same horizontal/vertical level
   - elements the same distance from eachother
   - all connectors the correct style (mostly orthogonal rounded)
   - all connectors correctly attached to the correct point of an element (mostly center, unless there are multiple connectors on the same side)
- link pools/Lanes with the proper elements (e.g. PartnerRole etc...)
- make blackbox pools (such as customer) actually blackbox.

To make it actually work in a serious modelling environment, it should need to learn and follow the guidelines of the organisation.

I don't want to rain on your parade, and I'm sure it's really technically a very advanced tool.
But for now I'm not yet able to recommend usage of such a tool to my clients.

Geert

5
MDG technologies are stored in the xml file. The individual steroeotypes and tagged values are not stored in the database.

You will have to update your automation to parse the MDG xml instead of relying on the database to get the stereotypes and tagged values.

Geert

6
You either work with the child-packages/child-elements in your template, or you define the structure yourself using Model Documents.

In some cases I have created multiple copies of the same template, but with a different heading level.
A bit annoying, but only a one-time effort.

Geert

7
Check the document generation options.
Some of them are related to the diagram. If you play with them, it might get solved.

Also, don't generate directly to PDF. In my experience it works better if you first generate to .docx, and then save to .pdf.

Geert

8
General Board / Re: Document Generation - Connector target is a diagram
« on: December 09, 2025, 08:51:27 pm »
You don't use the template to point to a single element, but the model document.

And yes, if you have 50 use cases in a single package, you would have 100 model documents (one for each use case, and one for each interaction)
That's why I usually automate the creation of the virtual document with a script.

I have an article on my website that explains this in more detail: https://bellekens.com/2015/11/12/tutorial-generate-complex-documents-from-enterprise-architect-with-a-two-step-semi-automated-approach/

Geert

9
General Board / Re: Document Generation - Connector target is a diagram
« on: December 06, 2025, 01:49:11 am »
I think this would give me the same issue whereby I would struggle to get the document to generate with a Use Case followed by it's diagrams. I don't think there is a way to point fragments at diagrams ?? as they are just called within a template which is associated to a Model Document element.

If I can point a fragment at a package that would fix my issue.
The fragment will always point to the package/element is was called upon.
With different model documents however you can use one model document that points to the use case, and the next that points to the Interaction.
Or you can put them in different packages and let the model document point to the package by dragging the package onto the model document.

Geert

10
General Board / Re: Keep on getting the login dialog on sparxsystems.com
« on: December 05, 2025, 10:50:37 pm »
I only get that when going to the registered section: https://sparxsystems.com/registered/index.html

Geert

11
General Board / Re: Document Generation - Connector target is a diagram
« on: December 04, 2025, 05:39:35 pm »
and I wasn't sure how to point the template at the Interaction/State Machine - how would you go about this?
I use a search that returns an element based on it's guid.

Geert

12
General Board / Re: Document Generation - Connector target is a diagram
« on: December 03, 2025, 11:03:43 pm »
There's no easy way to do that in a single template.

The easiest way is to create a virtual document with model documents that point to
- the use case
- the Interaction/State Machine that owns the diagram.

There are ways of making template fragments that use code to fetch the correct diagram, but is rather complicated.

Geert

13
Did you notice the 32-bit - 64-bit difference also?
No, didn't test that one.

Geert

14
I can confirm this behavior in v17, but also in v15.2.1560

Geert

15
Class A contains activity A() and a subclass B containing activity B().
But when A() calls B() a code error is generated:
   public void A(a, b) {
      // behavior is a Activity
      /*Warning: B - Invoking behaviors from other classes - Not Supported!!*/
   }
So how does an activity invoke a behavior defined in a subclass of its own class?
Don't you think it's a bit weird that a class knows about it's subclasses? I think that violates the Open/Closed principle

But regardless of that, apparently, as indicated by the warning messages, invoking behaviors defined in other classes (whether they are subclases or not) is not supported.

Geert


Pages: [1] 2 3 ... 899