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 - Nizam Mohamed

Pages: 1 ... 11 12 [13]
 This should work in most cases, are you missing a Update (newObject.Update).

Please refer to the "Method Lifecycle Example" script supplied with EA8.0 which demonstrates adding, iterating and deleting tagged values to a method.

Same applies to connector and roles too.


In a submachine state, a transition to final state is internally elicited to its parent state , to facilitate executing the parent state's behaviors,(eg: state5's transition), similar to how a transition to a submachine state's initial(pseudo state) is transfered to the actual initial state(state4 in the diagram)
Code: [Select]
private void stateMachine_State2_State5(CommandType command)
{...nextState = StateType.StateMachine_State2}

private void stateMachine_State1(CommandType command)
{...nextState = StateType.StateMachine_State2_State4;}

whereas a transition to final state elsewhere will be rendered as is(eg: state3's transition)
Code: [Select]
private void stateMachine_State3(CommandType command)
{...nextState = StateType.ST_NOSTATE/*Final State*/;}

The "specificaiton" in EA is a simplified way to model various event kinds.

For Change and Time triggers, the "When" and "ChangeExpression" will give the specification(shown in the transition's properties)

But, for Signal and Call triggers, the "Operation" and "Signal" will now(EA 8.0) return the GUID of the associated Operation or Signal respectively.
which can be retrieved something like
Code: [Select]
$sOpGUID =  %EASL_GET("Property", $Event, "Operation")%
$sExpression = %EASL_GET("Property", $sOpGUID, "Name")%

$sSigGUID =  %EASL_GET("Property", $Event, "Signal")%
$sExpression = %EASL_GET("Property", $sSigGUID, "Name")%

where $sExpression will give you the name of the associated operation or signal's name

AFAIK There are no hidden properties as such!

The specifications can be retrieved from the event information, please refer to the properties of the respective events, i.e. ChangeEvent, TimeEvent ,  CallEvent and SignalEvent in the help  or refer to their usages in the original "Trigger" template.

Sorry.. I'm afraid it isn't possible  :(

In 8.0 a couple of features were added to the Element List.. but it still holds all those toolbar buttons and functionality,

Element List can now be opened to show contents of root package.
Element List in non-recursive list of packages will now allow double click to navigate into child packages.

by defining do, entry or exit operations to the state, refer

to specify behavior , refer

for an example refer "Project Models.Systems Engineering Model.Implementation Model.Software.C++.IO.SearchExternalMedia.ReadSerialPorts" Node in the supplied EAExample.eap file.


The following link to the white paper on creating MDG Technology might help. The sample models and technology files associated with the white paper are also available for download from the paper.

Automation Interface, Add-Ins and Tools / Re: Expanded Local Path in Add-in
« on: September 09, 2008, 08:15:52 am »
Try using GetEnvironmentVariable method.

Did you have a chance to look at the "SDK for EA-> MDG Tech is SDK -> Create MDG Technologies->Add Code Modules" section of the help document, this shall facilitate you to include ur template changes to the resultant technology file, on top of the hitherto available templates.

Automation Interface, Add-Ins and Tools / Re: MDG Technologies
« on: February 27, 2009, 08:14:34 am »
Try Using these two options to regulate implementation files generation
<CodeOption name="HasImplementation">true/false</CodeOption><CodeOption name="ImplementationExtension">.XXX</CodeOption>

w.r.t Options page, please make sure you include "Code Modules" in the list of items to be included in the technology and choose the product you want to be included in the tech ( MDG Tech Wizard - Code Modules ) with appropriate "code options" file selected.

Pages: 1 ... 11 12 [13]