Messages

1

General Board / Re: Managing parallel subprocesses

« on: October 10, 2015, 01:10:50 am »

I think you're making it more complicated than you need to... start with your basic process, and see if you need to add any exceptions.

2

Bugs and Issues / Re: Using multiple keywords

« on: October 13, 2015, 01:02:29 am »

Thanks for checking Uffe!
I guess it can't be done then...

3

Bugs and Issues / Re: Using multiple keywords

« on: October 12, 2015, 07:22:32 pm »

No one has any idea?

4

Bugs and Issues / Using multiple keywords

« on: October 02, 2015, 10:29:26 pm »

Hi,

I've tried EA user guide and searching on this forum, but can't seem to find much information - so any help would be appreciated!

I'm trying to create a diagram filter based on 'keywords' of an element.
So if I have
-Element 1, keyword A
-Element 2, keyword A B
-Element 3, keyword C

then a diagram filter set to "Keywords one of 'A';'B' " should show elements 1 and 2, but hide (/fade/...) element 3.

This works as long as there is only 1 keyword per element, but does not work once I have more than one keyword. Is there a kind of delimiter I should use? I've tried a space, comma, semicolon, brackets...

Edit: still on version 9.1 - but we should get an upgrade to V12 soon

5

Bugs and Issues / Re: corrupt diagrams

« on: December 02, 2014, 02:59:40 am »

Hi,

yes, unfortunately, that does sound similar.

I'll file a bug report.

Thanks for your reply!

6

Bugs and Issues / corrupt diagrams

« on: December 01, 2014, 07:08:38 pm »

Hi,

I’m somehow making ‘corrupt’ diagrams (not sure what to call it?).



-a ‘corrupt’ diagram freezes the screen. EA keeps running, but I can’t open another diagram. The project browser, menus,… keep working fine. After closing and reopening EA I can open and edit other diagrams (but not the corrupt ones, obviously).
-I’ve had several ‘corrupt diagrams. So far, they have been ‘User interface Diagrams’ (but that could be a coincidence).
-None of my colleagues seem to have the problem (but that too, could be a coincidence).
-So far I’ve only had the issue when working on the central repository (not with local .eap file) (again, could be a coincidence).
 
I am using:
- EA v10.0.1004 (short term pland to move to v 11)
-MySQL database

I’ve tried:
-exporting and importing with ‘strip GUIDs’
-‘Integrity check’ (incl. ‘Clean’)
-‘Repair’

Does anyone know what going on? Any tips on what else to try?
I don’t really care about recovering the data in the diagram, but I’m afraid of creating stuff in EA that I’ll lose…

P.S.: sorry for the n00b question, but is there any way I can add the XMI export to this post?

7

Automation Interface, Add-Ins and Tools / Re: hide connector roles with script?

« on: October 21, 2015, 10:21:57 pm »

Thanks for the answers! I'll have to play around a bit to see if I can it to work - but at least I know where I need to look :-)

I'll let you know the outcome (might be a few days).

8

Automation Interface, Add-Ins and Tools / hide connector roles with script?

« on: October 21, 2015, 08:27:20 pm »

Hi,

Is it possible to hide source and target roles of a connector using scripting? (roles for a certain connector would be hidden on all diagrams)
I.e. what you can do manually through: on connector, right-click / visibility / set label visibility

We would like to have the roles visible in the relations pane, but don’t want to make the diagrams too overloaded…

Any ideas?

9

Automation Interface, Add-Ins and Tools / Re: Scripting: copy diagram?

« on: October 15, 2015, 12:39:02 am »

Hi Geert, that works! (I should have been able to find that, but like I said...still new)

Problem solved... thanks again for your help!

10

Automation Interface, Add-Ins and Tools / Re: Scripting: copy diagram?

« on: October 15, 2015, 12:21:27 am »

Update - I can create a copy of the diagram (including layout) using something like this:

Code: [Select]

     for(var i = 0; i < sourceDiagramObjects.Count; i++)
      {      
            var sourceElement as EA.DiagramObject;
            sourceElement = sourceDiagramObjects.GetAt(i);
            
            var left, right, top, bottom;
            left = sourceElement.left;
            right = sourceElement.right;
            top = sourceElement.top;
            bottom = sourceElement.bottom;
            
            var position = "l="+left+";r="+right+";t="+top+";b="+bottom+";"
            
            diagramObject = diagramObjects.AddNew(position, "" );
            diagramObject.ElementID( sourceElement.ElementID );
            diagramObject.Update();
            
      }

However, the 'z-order' of the elements isn't always right. Is there any way I can get this info from the source diagram, or, alternatively, change this on the target diagram through scripting? (in this case, elements with a certain stereotype need to be at the bottom)

11

Automation Interface, Add-Ins and Tools / Re: Scripting: copy diagram?

« on: October 14, 2015, 11:17:52 pm »

Thanks for the replies!

Geert; I tried using the package clone:
+diagram layout is preserved
-additional scripting needed to remove old diagrams and rename new diagrams and move them to correct position

Qwerty; would there be an easy way to add the missing diagramObject with the same size and in the same position as in the 'master' diagram?
The only way I can think of is using AddNew with the coordinates (left, bottom, top, right) of the diagramObject in the master diagram?

BTW: I'm just getting started with scripting, I got this really helpful book to get me started - not sure if I'm allowed to link to it here  

12

Automation Interface, Add-Ins and Tools / Scripting: copy diagram?

« on: October 14, 2015, 09:07:37 pm »

Hi,

I'm looking for a way to automate a (shallow) copy of a diagram.
Is there any way to do this?

Context: we have one 'master' diagram, and several 'variants'. The variants are only different from the master in that some of the elements are coloured (depending on links with other elements). The colouring is done through scripting. Obviously each variant has different elements that are coloured.
so far so good.
But what if another element is added to the master diagram? Our current workaround is to manually emty the variant diagram, and then copy-paste the elements from the master diagram (and then run the colouring script).

In other words: we don't need the 'old' variant diagram anymore, but need a copy of the master diagram: all elements and their layout.