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.


Topics - fwoolz

Pages: 1 ... 3 4 [5] 6 7
61
General Board / Synch State Capacity
« on: November 17, 2002, 08:28:48 am »
Hi all,

Is there any way to change the capacity of the synch state in a statechart from * to an integer?  At least one book on UML describes this capability.  This allows the synch state to act as a Petri net "place" with a limited token capacity, allowing access to a state to be guarded based on the number of times the connecting transition has fired.

Cheers,
Fred Woolsey

62
General Board / Containers for 1..n relationships
« on: October 26, 2002, 02:08:58 pm »
Hi all,

Under the "Java" code generation options, there is a field for specifying the container class for 1..n associations.  I set this to "Vector," even imported the Vector class, but it seems to have no effect on the generated code.  Any tips?

Thanks,
Fred Woolsey

63
Bugs and Issues / EA 9 beta 1, UML 2.3, and SysML 1.2 ports
« on: March 12, 2011, 06:18:44 am »
UML 2.3 defines the following properties (custom properties in EA) for ports:

UML 2.3 spec (Superstructure), 9.3.11
Quote
Attributes
• isService: Boolean
If true, indicates that this port is used to provide the published functionality of a classifier. If false, this port is used to implement the classifier but is not part of the essential externally-visible functionality of the classifier and can, therefore, be altered or deleted along with the internal implementation of the classifier and other properties that are considered part of its implementation. The default value for this attribute is true.
• isBehavior: Boolean
Specifies whether requests arriving at this port are sent to the classifier behavior of this classifier (see “BehavioredClassifier (from BasicBehaviors, Communications)” on page 448). Such ports are referred to as behavior port. Any invocation of a behavioral feature targeted at a behavior port will be handled by the instance of the owning classifier itself, rather than by any instances that this classifier may contain. The default value is false.
• isConjugated: Boolean
Specifies the way that the provided and required interfaces are  derived from the Port’s Type. The default value is false.
These properties are inherited by SysML 1.2 ports. Also, use of "isConjugated" and "isAtomic" as tagged values (from UML SysML 1.1) is deprecated; as a result, EA SysML 1.2 no longer provides these tags. However, EA does not implement the custom property "isConjugated," as specified by UML 2.3 and SysML 1.2. In addition, the requirement to show a tilde (~) in front of the name type of a conjugated port isn't implemented:

UML 2.3 spec (Superstructure), 9.3.11
Quote
The type of a port may be shown following the port name, separated by colon (“:”). When isConjugated is true for the port, the type of the port is shown with a tilde “~” prepended. (emphasis mine)
EA does not correctly implement UML 2.3 or SysML 1.2 in this area. As it now stands, the only way to indicate port conjugation is to use the deprecated tagged value, resulting in a shaded port (also deprecated).

64
Bugs and Issues / Importing #define FOO (bar) in C
« on: March 07, 2011, 01:25:39 pm »
It seems that define statements with parentheses are imported as methods rather than attributes when C files are imported. For example,

Code: [Select]
#define MIN_CA_ENGINE_RPM    (700)
winds up being imported as

Code: [Select]
void MIN_CA_ENGINE_RPM(700)
with a tagged value define = true!

All #define statements should be imported as attributes (if that option is turned on for code generation).

Bug report is being filed...

Cheers,
Fred W

65
Bugs and Issues / TaggedValues vs. TaggedValuesEx
« on: August 16, 2010, 01:04:11 pm »
While Element.TaggedValues and Element.TaggedValuesEx both return collections of type TaggedValue, apparently Collection.GetByName(name) only works on TaggedValues, not TaggedValuesEx. Is this intentional?

Running EA 8.0 build 861, BTW...

UPDATE:

Here's the code that didn't work:
Code: [Select]
try
{
...
TaggedValue tag = elem.TaggedValuesEx.GetByName(name);
...
}
catch ...
{
...
return null;
}
This always returns null.

Here's the workaround:
Code: [Select]
           try
            {
                TaggedValue tag = null;

                foreach (TaggedValue t in elem.TaggedValuesEx)
                {
                    if (t.Name == name)
                    {
                        tag = t;
                        break;
                    }
                }

                return tag;
            }
            catch (Exception e)
            {
                EAConnector.LastError = e.Message;
                return null;
            }
I kept the try-catch for the time being.

66
Bugs and Issues / C# properties and getter/setter access
« on: August 16, 2010, 05:16:46 am »
C# allows the get and set methods of a property to have different access levels. For example, the following:
Code: [Select]
public TreeView CurrentTree { get; protected set; }
is perfectly acceptable. Yet EA does not allow different access levels for get and set for C# properties (it does for other languages).

UPDATE:

The property above could be shown something like this:

+CurrentTree {+get; #set} : TreeView

Provided that no sacred tenets of UML are transgressed.

67
Bugs and Issues / Xml schema generation and global attributes
« on: July 07, 2010, 11:34:43 am »
In spite of the fact that the only tagged values for the XSDtopLevelAttribute stereotype are 'default', 'fixed', and 'form', schema generation insists on including 'use="optional"' as an attribute for generated global attributes. This results in a validation error when the generated schema is opened in a tool like Visual Studio or Eclipse.

Error in Eclipse:
Quote
s4s-att-not-allowed: Attribute 'use' cannot appear in element 'attribute'.
Error in VS:
Quote
Warning 2 The 'use' attribute is not allowed.

68
Bugs and Issues / MDG Link for VS 2010 optional param problem
« on: July 02, 2010, 12:52:42 pm »
I just installed the MDG link for VS 2010 and tried to sync with a C# project and got a parse error in one file with a method with an optional parameter. I received a download link a few months back from Sparx to make the older MDG add-in recognize optional parameters (it worked), but apparently this didn't make it into the beta release.

CORRECTION: The fix described was for built-in code engineering, NOT the MDG link!

69
Bugs and Issues / Tags linked by GUID & new EAP file from existing
« on: June 25, 2010, 10:32:09 am »
I have a base .EAP file with a SysML View whose 'viewpoint' tagged value is linked to a Viewpoint named 'Viewpoint1'. When creating a new EAP file using this file as a base, the View element 'viewpoint' tagged value is now (in the new file) a string value equal to the EA GUID of the Viewpoint. In addition, the ability to select a Viewpoint element from the Project Tree by clicking on the button to the right of the 'viewpoint' tag value field is gone (as is the button itself). This appears to be similar to an older bug that produced the same results when copying elements and pasting them as new.

(Bug report filed.)

70
Bugs and Issues / EA 8.0 Beta 1 and C# default param values
« on: February 19, 2010, 10:58:13 am »
All,

While this may be jumping ahead a bit (after all, VS 2010 and .NET 4.0 are still in the RC phase) I thought it would be good to bring it up since 8.0 is still in beta...

EA reports the following error when importing C# code with default method parameter values:

Quote
There was an error parsing C:\Users\fred\Documents\Visual Studio 2010\Projects\SpecifyxDocumentConverter\SpecifyxRtfDocument\BaseClasses\RtfElement.cs on line 59.  Unexpected symbol: =      
The corresponding code is:
Code: [Select]
public  virtual bool FromRtfAll(ParseType parseType = ParseType.Basic)
{
      return false;
}
I realize this is a recent addition to C#, but it would be great if Sparx could include C# 4.0 code features in the 8.0 release (or "soonly" thereafter). I should note that VS 2010 is set for an April 2010 release.

Cheers,
Fred W

71
Bugs and Issues / Generated profile XML file has no
« on: February 05, 2010, 07:55:31 am »
Bug report filed-----

=========================================
I have the latest and greatest release of EA Ultimate (7.5.850), running on Windows 7. I've just tried creating a profile for the first time with this particular combination of EA and Windows, and have encountered a problem. When extending a MetaClass, the "extend" association stereotype shows as "Extends" (Upper case E); this of course resists correction within EA to "extends" (lower case e). Exporting the profile to XML results in an XML file with no <AppliesTo> elements; thus importing the profile XML results in an EMPTY profile in the Resources window.

Using Access to link to the EAP file, I then corrected "Extends" to "extends" for each profile connector, then repeated the process. Now the profile imports correctly!

Case-(in)sensitivity of stereotype names in EA has never been completely consistent in its behavior; this seems to be another example. Has anyone else seen this issue?

Cheers,
Fred Woolsey

72
Bugs and Issues / Bugzilla and EA
« on: December 23, 2009, 08:10:36 am »
I was thinking (dangerous, I know) about bug reporting in EA and wondered to myself ("Self?," I wondered) why the Sparxians don't move the whole Megillah to Bugzilla? That way we Earthlings would not only enjoy improved bug reporting, but we would also be able to check on other bugs that have been reported and inquire as to status of said bugs...

73
Bugs and Issues / Template editor crash and burn
« on: September 24, 2009, 01:09:46 am »
In the template editor, when attempting to define list levels for a list override (which is, I must say, implemented in a very clunky and confusing way), EA invariably crashes when trying to set several list levels without closing the dialog in between each list level being edited (it sometimes crashes even if it is closed between edits).

BTW - I am using an Access 2007 repository (which isn't on the "Repository Type" dropdown list on the bug reporting page), if that makes any difference.

BTW again: I'm using EA Ultimate Edition, 7.5 Build 848.

74
Bugs and Issues / Object state and classifier state machines
« on: August 11, 2009, 07:26:48 am »
Under the help topic "Define an object state," EA help sez:

Quote
Note:
 
If the associated classifier has a child State Machine element, those states propagate into the drop-down list for this field, and you can select one of them instead.

So I create a classifier with a child State Machine, then create an instance of that classifier, right click and pick until I get to the "Set instance state" dialog (an aside: it would be good if the menu option and the corresponding dialog used the same terminology - minor point) and... the combo box is not automatically populated with the states in the child State Machine.

What gives?

BTW, I'm running version 7.5.847, Ultimate edition, .EAP file repository.

Thanks,
Fred Woolsey

75
Bugs and Issues / OCL and constraint attached to connector
« on: June 06, 2009, 12:14:41 pm »
The drop-down list for "Constraint Type" that pops up when you double-click an attached constraint doesn't include an option for an OCL constraint. Shouldn't this be included here (along with OCL expression validation) as it is when adding a constraint to an element from the "Constraints" tab in the property dialog?

Cheers,

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