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 - Graham_Moir

Pages: 1 2 3 [4] 5 6 ... 46
46
Bugs and Issues / Re: BPMN Template Elements don't honour the element size
« on: November 30, 2016, 08:31:17 pm »
Reported with the reply from Sparx of "This has been confirmed to be fixed in a future build."

47
Bugs and Issues / Re: BPMN Template Elements don't honour the element size
« on: November 28, 2016, 09:10:06 pm »

Thanks Paolo.  I'm sure you've reported it, but I will too.

48
Bugs and Issues / BPMN Template Elements don't honour the element size
« on: November 25, 2016, 04:31:25 am »
Version 13.  I have set the style attributes on a BPMN activity element in a template package and also resized the element.   When a new BPMN activity is added to a diagram,  EA picks up the style OK, but the default old size of the element seems to dominate.   I see a quick flash where the revised template element dimensions appear, but they immediately disappear to be replaced with the default much smaller size.   I assume this is because BPMN's origins in EA is as an MDG addin, although it is now delivered as standard by default with EA.   

Would you call this a bug?  Is it even fixable?

49
General Board / Re: Standardising Element Appearance
« on: November 23, 2016, 12:03:49 am »
The documentation is clear that this is on creation.
Agreed.

What's the aversion to using default appearance? If you set the default appearance of your element in the template package, that would apply on all future diagrams the elements are used on.

No aversion, it's just that it's easy to click on the element and use the Format Toolbar from the element icons to change the appearance in the template package.  This then works for new elements,  but in fact in the template package what you should be doing is changing the default appearance in order to get consistency for new elements and re-used elements.   The "Change Default Appearance" menu option is somewhat hidden (in comparison to the Format Toolbar icon) and not everyone knows about F4.

50
General Board / Re: V13: colour dialogues
« on: November 22, 2016, 09:00:40 pm »

Yes, depressing to find not much has changed.

51
General Board / Standardising Element Appearance
« on: November 22, 2016, 01:31:00 am »
This may have been raised before, not sure.

If I use the "Project Template Package" approach provided in EA I can set my own appearance for elements (font colour, size, border, background etc..) without using the 'default appearance' option, and this works fine.  EA notices the custom appearance in the template section and applies that style to a new element of the relevant type that I add to a diagram.   The problem is that this seems to be a one time operation.   By that I mean, if I re-use (link to) that element on a different diagram, a completely different appearance is applied, which I assume must be the default for the element.   I can of course also set the "default appearance" of the element, essentially repeating the changes made to customise the element in the template package, but why do I have to do this twice? Is this a bug? 

Would it be reasonable to expect that on re-use of an element, either
1) EA also applies the style it finds in the template package - if it looked that is, I have a feeling the lookup on the template package only happens for new elements.   In short shouldn't the style I specify in the template package override any default appearance ?
2) When an element is defined in a template package and its appearance changed, shouldn't then its 'default appearance' automatically be updated to reflect those changes?

thanks

52
Suggestions and Requests / Re: Find and delete orphanded items
« on: November 17, 2016, 09:40:41 pm »
Isn't an orphan an element that has zero relationships rather than an element that isn't on a diagram?

Also, Skiwi, point taken,  my comment was slightly ambiguous, but the main thrust of what I said related to elements and that still holds true I believe...   "pressing the delete key when an element is selected will never delete the element from the model/project browser.    You have to use control-delete to achieve that."


53
Bugs and Issues / Re: BPMN2 - Resize / center text
« on: November 17, 2016, 09:35:20 pm »
It looks to me as though the text is top centred with a fixed offset from the top of the element.  If you make the activity bigger the title/text stays in this position no matter how big the element is.   If you make the element smaller the same constraints apply which means you can actually end up with the text outside the element if you make it small enough. 

No sure how you adjust this.   I have a vague recollection of an option to centre or left/right justify the text but I can't find it any more. 

54
Bugs and Issues / Re: Pinned ends and line styles
« on: November 17, 2016, 09:15:16 pm »
I agree with Paolo that it would be handy, indeed user-friendly, if EA told the user that the pinned ends they carefully put in place are going to be, or at minimum have been, removed.

55
General Board / Re: UML2 import broken in 13?
« on: November 02, 2016, 05:51:52 am »
May be you should submit a formal support ticket? 

56
Suggestions and Requests / Re: Project Search - remember last active search
« on: November 02, 2016, 01:30:55 am »
+1

57

I raised a support issue about this.   Here's the response.

=======
Unfortunately the help documentation you refer to is out-of-date and no longer accurate.

To complete the setup of MDG Link for Eclipse, you will first need to browse to your EA installation directory.  (Default: C:\Program Files (x86)\Sparx Systems\EA).  Copy all org.sparx.mdg.eclipse.*.jar files to your Eclipse /plugins or /dropins directory, overwriting any existing files.

Run Eclipse, open Help | About Eclipse > Installation Details > Plug-ins and sort the list by Provider.  You should be able to see some plugins installed where Provider is "SparxSystems".
 
In EA, select Code > Add-Ins > Eclipse > Options.  Set the path to your eclipse.exe.

Once the jar files are properly installed and the path to eclipse.exe has been set, try using the MDG Link functionality by right-clicking on a package in your Project Browser and selecting Extensions | Eclipse | Connect External Project.  Are you able to see your currently open Eclipse projects and establish a connection to one of them?
======

This works for me on a machine with administrator rights.


58

The Eclipse (and Visual Studio) Link MDGs are now standard as part of the Professional edition and above and appear on the code tab in version 13.   But how do you get them to work? 

The help still seems to refer to the time when this was purchased separately as follows:

=================
The MDG Link for Eclipse is available for download from the MDG Link for Eclipse page on the Sparx Systems Website, once it has been downloaded the program will be in the .zip format. To install the MDG Link for Eclipse use the following instructions: 
 
 1. Download the EAEclipse.zip file from the Sparx Systems Website. 
 2. Ensure that you meet the System Requirements and have the appropriate versions of Enterprise Architect and Eclipse 3.0 installed on your system. 
 3. Remove any previous org.sparx.mdg.eclipse_1.nn directory from the Eclipse Plugins directory (if they exist). 
 4. Unzip the EAEclipse.zip file into a suitable directory (i.e. c:\EAEclipse) and copy then org.sparx.mdg.eclipse_1.nn directory into the Eclipse Plugins folder where your install of Eclipse is located (i.e. C:\eclipse\plugins). 
 5. Install the MDG Link for Eclipse component by double clicking on the EAEclipse.exe Installer executable. 
 6. Read the licensing agreement and if you accept the terms click on the next button. 
 7. Read the Readme information, and then click on the next button. 
 8. Enter the User name and the Organization names into the appropriate fields before proceeding by clicking the next button. (Optionally determine the users who have access this program by choosing between the all users or only registering users). 
 9. Choose an installation path for the program, and then click the next button. 

Note: The .nn in the org.sparx.mdg.eclipse_1.nn is indicative of the current version number of the MDG Link for Eclipse. 
===========

Step 4 seems critical.  But what do you do when the Eclipse link is already pre-installed?   I can't find it in the Sparx MDGTEchnologies folder  (C:\Program Files (x86)\Sparx Systems\EA\MDGTechnologies), so can't find the directory org.sparx.mdg.eclipse_1.nn

What's more when I have Eclipse running, if I click on the "View Eclipse Connections" option in EA, I get a blank panel plus the message  "Eclipse must be running to complete this action.  Launch Eclipse now?".   But if I click "Yes", I just get "Can't launch Eclipse".

Anyone any idea how to get this to work in EA 13?

Thanks

59
General Board / EA and Infosphere
« on: October 11, 2016, 10:26:17 pm »

Hi, can anyone advise if they have exported a data model from Infosphere and then successfully imported it into EA?

Thanks

60
General Board / Re: V 13 Schedule
« on: October 05, 2016, 02:50:05 am »

From memory, this beta, which started in June, is taking longer than the beta for previous major releases.  So I'm hoping the official release is imminent, i.e. October.

Pages: 1 2 3 [4] 5 6 ... 46