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 - Helmut Ortmann

Pages: 1 ... 57 58 [59] 60 61
871
Hi,

you can use the tagged value type:
Type=Memo;

With this type you have no limits in entering text.

Seach in the help for: Tagged Value, Types
for the available types.

Best regards,

Helmut


872
Automation Interface, Add-Ins and Tools / Re: Attribute values
« on: June 27, 2013, 07:28:42 pm »
Hi,

you want the value of an Attribute?

An Attribut has a buch of properties/attributes but no property value. The possible properties are described in the help (Automation and Scripting, Reference, Element Feature Package, Attribut Class).

Valuable information you can also find in Thomas Kilians book ScriptingEA.

Best regards,

Helmut

873
Hi,

as far as I'm familiar with DOORS: Chances are good that there are no changes in DOORS regarding the essential features.

Therefore just give it a try. The matter isn't that complicate.

Kind regards,

Helmut

874
Automation Interface, Add-Ins and Tools / Re: Script Groups in MDG
« on: May 29, 2013, 06:15:43 pm »
Script goups are not really supported by MDG.

Therfore it's a good idea not to include scripts in your MDG. Export your scripts  as 'Reference Data' and import it in the repositories where you need the scripts and script groups. You have to restart the repository.

Best regards,

Helmut


875
Automation Interface, Add-Ins and Tools / Re: Script Groups in MDG
« on: May 27, 2013, 04:39:59 pm »
I don't think there is an easy way to put the scripts in the correct Group.

I see the following two possibilities:
  • Make an Addin to change the table t_script
  • Modify the import script.xml file  


The concept for both solutions is the same.
Groups:
ScriptCategory: fix GUID
3955A83E-9E54-4810-8053-FACC68CD4782
ScriptName:  GUID
AcriptAuthor: Null
Notes:
<Group Type="PROJBROWSER" Notes=""/>  or
<Group Type="MODELSEARCH" Notes=""/>  or
<Group Type="DIAGRAM" Notes=""/>           or
<Group Type="NORMAL" Notes=""/>            or
<Group Type="MODELSEARCH" Notes=""/> or
<Group Type="PROJBROWSER" Notes="Scripts which are shown in the browser context menue."/>  

Script: Name of the Group  

Scripts:
ScriptCategory: fix GUID
605A62F7-BCD0-4845-A8D0-7DC45B4D2E3F
ScriptName: GUID
ScriptAuthor: GUID of ScriptName of Group

With knowing this you can easily create your own Group or use it by existing scripts.

@Thomas, a possable content for your book


Good luck,

Helmut



876
Hello,

an easy way is to install an Addin (e.g. Geerts Navigator). Then you can see it.

Best regards,

Helmut

877
Hello André,

I've found the example.

- Go into the EA help (F1)
- Search
- Select search for subject/title or so
- Search item is "Model Validation Example"

There you find an example.

Best regards,

Helmut

878
Hi,

a year ago I wrote an EA validation. If I remember right I used an Example of the EA documentation. It wasn't just writing a single function. It's more a framework for rules organized in categories and more...

If you follow the rules you can add your own rules and categories.  

Have a look in the EA documentation and resources. If you can't find anything I can send you my pretty complex validation or search for myself. Just ask.


Best regards,

Helmut

879
Hi,

in %appdata%Sparx System\EA\DBerr.txt
you find the original error message.

Best regards,

Helmut

880
Automation Interface, Add-Ins and Tools / Re: Accessing options
« on: April 16, 2013, 04:54:22 pm »
Hello,

in my opinion the options are stored in the registry:
HKEY_CURRENT_USER\Software\Sparx System\EA400\EA

Therefore the options are stored for a user.

I don't know an EA API to manipulate all the options stored.

Best regards,

Helmut

881
Hi,

thanks a lot for your valuable advice,

Kind regards,

Helmut

882
Hello,

the MDG creation wizards creates a group with the name of the MDG and the selected scripts inside the group.

Because I want to have the script in the context menue I have to copy them manually in the desired groups.

Maybe it's only possible by hand or SQL.

Kind regards,

Helmut

883
Automation Interface, Add-Ins and Tools / MDG with Script in a ScriptGroup
« on: February 14, 2013, 01:20:13 am »
Hello,

is it possible to define a MDG with a script in óne or more groups like
  • Project Browser Group
  • Diagram Group
  • Model Search Group

Thanks for your help,

Helmut

884
Hi,

enclosed part 2.

Kind regards,

Helmut
#DB=ORACLE#
#DB=Other#                left(x.description,38),
                                      mid(x.description,40,38),
                                      mid(x.description,79,38),
                                      mid(x.description,118,38),
                                      mid(x.description,157,38),
                                      mid(x.description,196,38),
                                      mid(x.description,235,38),
                                      mid(x.description,274,38),
                                      mid(x.description,313,38),  
                                      mid(x.description,352,38)
#DB=Other#  
  )
  
  
order by 3,4,5

885
Automation Interface, Add-Ins and Tools / Re: SQL for ConveyedItems
« on: January 30, 2013, 12:06:12 am »
Hi,

see enclosed SQL. It's a bit tricky. I send it in two parts.

Kind regards

Helmut
SELECT DISTINCT o.ea_guid as CLASSGUID, o.Object_Type as CLASSTYPE,
 o.name As Item, o.Object_Type As ItemType, o.stereotype As ItemStereotype, 'Connector' As ConnectorType, c.Name, c.Stereotype
 
FROM t_object o,
          t_xref xCon, t_xref xFlow,
          t_connector c,
    t_connector flow
where
  c.connector_ID = <Search Term>
and   c.ea_guid = xCon.Client
and   xCon.Behavior = 'abstraction'
and flow.ea_guid in
(
#DB=SQLSVR#             substring(xCon.description,0,39),
                                      substring(xCon.description,39,39),
                                      substring(xCon.description,78,39),
                                      substring(xCon.description,117,39),
                                      substring(xCon.description,156,39),
                                      substring(xCon.description,195,39),
                                      substring(xCon.description,234,39),
                                      substring(xCon.description,273,39),
                                      substring(xCon.description,312,39),  
                                      substring(xCon.description,351,39)
#DB=SQLSVR#  
#DB=ORACLE#
                                                        SubStr(Cast(xCon.description As Varchar(39)),0,38),
                                      SubStr(Cast(xCon.description As Varchar(39)),40,38),
                                      SubStr(Cast(xCon.description As Varchar(39)),79,38),
                                      SubStr(Cast(xCon.description As Varchar(39)),118,38),
                                      SubStr(Cast(xCon.description As Varchar(39)),157,38),
                                      SubStr(Cast(xCon.description As Varchar(39)),196,38),
                                      SubStr(Cast(xCon.description As Varchar(39)),235,38),
                                      SubStr(Cast(xCon.description As Varchar(39)),274,38),
                                      SubStr(Cast(xCon.description As Varchar(39)),313,38),  
                                      SubStr(Cast(xCon.description As Varchar(39)),352,38)

#DB=ORACLE#
#DB=Other#                left(xCon.description,38),
                                      mid(xCon.description,40,38),
                                      mid(xCon.description,79,38),
                                      mid(xCon.description,118,38),
                                      mid(xCon.description,157,38),
                                      mid(xCon.description,196,38),
                                      mid(xCon.description,235,38),
                                      mid(xCon.description,274,38),
                                      mid(xCon.description,313,38),  
                                      mid(xCon.description,352,38)
#DB=Other#  
  )
AND         flow.ea_guid = xFlow.client
AND         o.ea_guid in  
(
#DB=SQLSVR#             substring(xFlow.description,0,39),
                                      substring(xFlow.description,39,39),
                                      substring(xFlow.description,78,39),
                                      substring(xFlow.description,117,39),
                                      substring(xFlow.description,156,39),
                                      substring(xFlow.description,195,39),
                                      substring(xFlow.description,234,39),
                                      substring(xFlow.description,273,39),
                                      substring(xFlow.description,312,39),  
                                      substring(xFlow.description,351,39)
#DB=SQLSVR#    
#DB=ORACLE#
                                                        SubStr(Cast(xFlow.description As Varchar(39)),0,38),
                                      SubStr(Cast(xFlow.description As Varchar(39)),40,38),
                                      SubStr(Cast(xFlow.description As Varchar(39)),79,38),
                                      SubStr(Cast(xFlow.description As Varchar(39)),118,38),
                                      SubStr(Cast(xFlow.description As Varchar(39)),157,38),
                                      SubStr(Cast(xFlow.description As Varchar(39)),196,38),
                                      SubStr(Cast(xFlow.description As Varchar(39)),235,38),
                                      SubStr(Cast(xFlow.description As Varchar(39)),274,38),
                                      SubStr(Cast(xFlow.description As Varchar(39)),313,38),  
                                      SubStr(Cast(xFlow.description As Varchar(39)),352,38)

#DB=ORACLE#
#DB=Other#                left(xFlow.description,38),

Pages: 1 ... 57 58 [59] 60 61