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

Pages: [1] 2 3 ... 40
1
General Board / Re: Value Type, Quantity Kind and Units
« on: January 03, 2020, 01:30:04 am »
A ValueType is used, typically, as a typing mechanism for Value Properties (in a Block), Flow Property (in an Interface Block), or for a Port (most likely a Proxy Port)

So yes, it can represent what you are trying to measure. For example, a Block that is monitoring temperature could have a Value Property named currentTemperature, typed to a ValueType named AmbientTemperature with Quantity Kind = temperature and Units = degree Celsius. This Block could also have a Proxy Port named Temperature In typed to ValueType named AmbientTemperature

Hope this helps

Phil

2
General Board / Re: restrict use stereotypes to other stereotypes
« on: November 23, 2019, 01:53:34 am »
I have just conducted some experiments using metaconstraints, which I agree with Geert as the approach that should work

The obvious candidate for the umlRole tag is ownedAttribute

This certainly has no effect when adding stereotyped attributes to stereotyped classes, (as indeed do any other umlRoles for example owner)

Reading the user guide, it states this constraint is typically used to validate nesting during Model Validation, I tried Model Validation guess what? No errors no warnings

I suppose a custom validation is required.

Sorry I could not be of more help, but if anyone does come up with an answer that does not involve coding or scripting (these can provide a psot validation of course), then I would very much like to know

All the best

Phil


3
Interesting

I just tried a very simple style sheet and used it with a very simple template in EA 1513 and it worked just fine.

I created a new style from scratch (did not copy an existing one)
Set Heading 1 to Comic Sans
Set Normal to Comic Sans Red

(I used Comic Sans only so I could definitely see if the stylesheet worked)

Then used this in a template

All was fine

The only difference I can see, is that your style sheet is based on a copy from Sparx, whereas mine is not?

I have always created my stylesheets from scratch using just the styles I need, but I agree it should work no matter how you approach your stylesheet creation.

Maybe give creating a stylesheet from scratch and see if that works for you

All the best

Phil

4
PCS General Board / Error running Webconfig
« on: November 22, 2019, 01:32:11 am »
Hi All

I have installed version 4 of PCS on localhost and have configured IIS with PHP, and confirmed that PHP is working with IIS.

The installation went smoothly and I have copied WebEA and WebConfig to c:\inetpub\wwwoot

Firewall inbound rules are fine, however when I try to navigate to localhost/WebConfig I receive the following:

Fatal error: Uncaught Error: Call to undefined function mb_strtolower() in C:\inetpub\wwwroot\WebConfig\globals.php:179 Stack trace: #0 C:\inetpub\wwwroot\WebConfig\globals.php(26): strIsTrue(false) #1 C:\inetpub\wwwroot\WebConfig\globals.php(14): Logging->__construct(false) #2 C:\inetpub\wwwroot\WebConfig\index.php(31): require_once('C:\\inetpub\\wwwr...') #3 {main} thrown in C:\inetpub\wwwroot\WebConfig\globals.php on line 179

Any ideas?

Thanks

Phil

5
Hi

There are no issues as far as I am aware, however ensure that all MDGs enabled in version 13 are present in the Perspective(s) used by EA users in EA version 14 and version 15

Ideally, users of versions 14 and versions 15 should use the same Perspective(s)

Phil


6
Hi Guillaume

I have sent you a PM with the e-mail to which to send your EA project so I can take a look

All the best

Phil

7
Ah

This puzzled me for a while and the answer is use metaconstraint relationships, in addition to stereotype relationships

Say, for example, that Stereotype A can only connect to Stereotype B via a stereotyped Association, then in addition to the stereotype relationship (the quicklinker definition), add a metaconstraint relationship from the stereotyped Association to B (or A), and set the tag value umlRole to target, or umlRole to source. This will enforce these constraints when using the diagram tool box and am error dialog will be displayed.

I presented this at the EAUG meeting Gdansk, so you might be able to download the example used in the presentation from the EAUG web site

A little experimentation with metaconstraints may be necessary in order to see how they work.

All the best

Phil

8
Hi All

I encountered this issue when writing my EA SafeDelete add in a few years ago. I could not find a definitive list, but through a bit of experimentation I found the following Object Types, simply tested with a switch case using element.Type:

Port
ActionPin
ProvidedInterface
RequiredInterface
ActivityParameter
ExpansionNode
ObjectNode
Part

This may provide a start for further investigations.

All the best

Phil

9
Many thanks Arshad that worked perfectly

@Sparx I humbly request that the MS Office MDG Installation instructions on the web page for the download is updated accordingly

Thanks again

Phil

10
Hi All

I am attempting to install the MS Office Integration MDG as detailed on

https://sparxsystems.com/products/mdg/int/office/office-integration.html

I have clicked the link for the MS Office 2010 Primary Interop Assemblies which appear to install correctly and do show up as installed in Windows Control Panel

However, upon running the MS Office Integration MDG installer, it just reports that the MS Office 2010 interop has not been installed!! The url specified in the error dialog, refers to a page simply stating "Download no Longer Available"

Restarting has no effect.

So, simple question, how does the MS Office Integration get installed?

All the best
Phil




11
General Board / Re: Special Characters in EA Properties View
« on: October 02, 2019, 06:57:11 pm »
Experienced in versions 14.1 and 15

After some experimentation I have discovered that the special characters can be displayed in the EA Workspace, I tested copy / paste from Excel and also direct entry.
I also discovered, that the raw CSV file contains the special characters, but after import using the usual CSV Import, the "transformation" occurs, so it appears that the issue lies within the CSV import.

I am going to perform the same import using the MS Office Integration MDG and see if that resolves the issue

All the best
Phil

12
General Board / Special Characters in EA Properties View
« on: October 02, 2019, 12:31:24 am »
Hi All

I have imported a number of elements from a CSV file the data for which contains characters such as č

However when this data is displayed in the EA Element properties, these characters are displayed as a black diamond with a white ? inside

The model repository is a centralised and hosted, I believe, on SQL Server

Can the EA properties display such special characters, and if so what is the configuration necessary?

Many thanks

Phil

13
General Board / Re: Can you create a 'checkbox' tagged value type?
« on: October 02, 2019, 12:18:18 am »
Hi

There is a tagged value type for check box list, however it is stored internally as a comma delimited string of 0 and 1 (representing unchecked and checked).

When output directly to a word document the tagged value prints as this comma delimited list.

I have worked-around this with a script driven fragment to map the zeros and ones to the check box fields specified in the tagged value description. Full details of this tagged value type can be found in the EA user guide

All the best

Phil

14
This is what is says in the Microsoft web site
Symptoms

If you use ADO to insert a new record through a client-side recordset into a SQL Server table that has a non-nullable datetime field with a default value, you receive the following error message if you do not supply a value for the datetime field:
Run-time error '-2147217887 (80040e21)': Multiple-step operation generated errors. Check each status value.
This error occurs whether you use the OLE DB Provider for SQL Server or the OLE DB Provider for ODBC Drivers. The error message may differ when you use Microsoft Data Access Components (MDAC) version 2.5 Service Pack 1 (SP1) or earlier. This error does not occur with a server-side cursor.
Cause

This error occurs in the Client Cursor Engine when it attempts to convert the value of type DBTYPE_DBTIMESTAMP to DBTYPE_VARIANT.
Resolution

There are several ways to work around this problem:
Use a server-side cursor for the recordset.
Remove the default value that is specified for the field in the database.
Always specify a value for the field when you add a new record.
Status

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

The workarounds probably won't help.

It might be worth having a look at the tables in SQL Server Management Studio and seeing if any date fields are non-nullable, and then making them nullable

That may work

We have the same problem with updating diagrams, but after ignoring the message a few times, it goes away.

Phil

15
This is what is says in the Microsoft web site
Symptoms

If you use ADO to insert a new record through a client-side recordset into a SQL Server table that has a non-nullable datetime field with a default value, you receive the following error message if you do not supply a value for the datetime field:
Run-time error '-2147217887 (80040e21)': Multiple-step operation generated errors. Check each status value.
This error occurs whether you use the OLE DB Provider for SQL Server or the OLE DB Provider for ODBC Drivers. The error message may differ when you use Microsoft Data Access Components (MDAC) version 2.5 Service Pack 1 (SP1) or earlier. This error does not occur with a server-side cursor.
Cause

This error occurs in the Client Cursor Engine when it attempts to convert the value of type DBTYPE_DBTIMESTAMP to DBTYPE_VARIANT.
Resolution

There are several ways to work around this problem:
Use a server-side cursor for the recordset.
Remove the default value that is specified for the field in the database.
Always specify a value for the field when you add a new record.
Status

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

The workarounds probably won't help.

It might be worth having a look at the tables in SQL Server Management Studio and seeing if any date fields are non-nullable, and then making them nullable

That may work

We have the same problem with updating diagrams, but after ignoring the message a few times, it goes away.

Phil

Pages: [1] 2 3 ... 40