Messages

1

Automation Interface, Add-Ins and Tools / Re: Where to store project related settings for Ad

« on: March 11, 2008, 09:59:08 pm »

That's really useful. Many thanks for your input. I will put my thinking cap on again and will keep you informed as to want I end up doing.

Much appreciated.

2

Automation Interface, Add-Ins and Tools / Re: Where to store project related settings for Ad

« on: March 11, 2008, 09:04:59 pm »

My addin has a settings menu option that pops up a dialog box that allows a user to set these in a user friendly way and checks that entered values are acceptable.

3

Automation Interface, Add-Ins and Tools / Re: Where to store project related settings for Ad

« on: March 11, 2008, 08:34:27 pm »

Well I'm in the midst of writing Yet-Another-Requirements addin ( I know a number of addins have been produced in this space - but this is very specific to the company I work for and integrates tightly with the existing legacy requirements gathering tools that are in place.)

What I would like to store in the model/project are:

• the prefix, sequencecounter and format for new requirements. (I know EA has such a beast but I couldn't find how to get to it programmatically, and besides I have finer grain control over the requirements Ids if I have control over these settings;

• The GUID of the package/view that a particular project wants to store their requirements in - not all projects store them in the same place. Yes I could enforce a standard but it would be nicer to keep the flexibility if possible.

These are possibly not the best examples of what an addin needs to keep track of and that a user need not have access to in a uncontrolled way. But I think that generically there should be somewhere that addins can store information/settings in the model which can only be accessed programatically - ideally an EA.Package that has a hidden flag that causes it and it's children not to appear in the project browser.

4

Automation Interface, Add-Ins and Tools / Re: Where to store project related settings for Ad

« on: March 11, 2008, 06:28:45 pm »

Thanks for your thoughts.

I wanted to save the settings as tags against an EA.Package entity. I believe this is possible. However, I have to assume that someone using my addin probably won't have the required package or package structure that would allow me to find it reliably. Also, of course, if I just add in a package of my choosing it will show up in the project browser, hence arousing curiosity and also looking a bit tatty. (It seems that Model Views which are of an EA.Package type don't allow you to store tags against them. That would have been my ideal compromise, as I could have declared a new Model View dedicated to my addin.)

So I have looked high and low to find a convenient, easily locatable place in the model but have not found anywhere appropriate.

I wondered if other addin authors had had faced the same issue and how they had solved this.

5

Automation Interface, Add-Ins and Tools / Where to store project related settings for Addin

« on: March 10, 2008, 11:36:01 pm »

Hi,

I'm writing an addin for EA and wondered if anyone could advise where and how I could store settings for the addin within model. User settings I can put away in the registry but I need to find a place I can store the settings that relate to the open project, preferebly in a place where the can not be browsed by the user in the project view.

Any feedback appreciated.  

6

Automation Interface, Add-Ins and Tools / Re: Move a Requirement from one package to another

« on: April 25, 2007, 09:20:28 pm »

As simple as that! Tried it and works great.

Many thanks.

7

Automation Interface, Add-Ins and Tools / Move a Requirement from one package to another

« on: April 25, 2007, 05:55:10 am »

Hi,

I would like to programmatically move an Element of type "Requirement" from one package to another. I have tried the following approach:

element.ParentID = destPackage.PackageID
element.Update

This does not return an error (ie Update result is true) but neither is the read/write ParentID property updated to the new packageID

Anyone point me in the right direction.

Thanks in advance

PS I am using EA build 804

8

Automation Interface, Add-Ins and Tools / Problem getting 'Static View' Element in EA 4.0

« on: June 01, 2004, 04:55:42 am »

I have just migrated to EA 4.0 and find that some VB that I wrote to query EA for model data now no longer works.

Quite simply I would like to get the EAElement for the 'Static View' package. I used the following code:

Set p = EAR.Models.GetByName("Views")
Set e = p.elements.GetByName(“Static View”)

As I said this used to work but I now get the error:

DAO.Database [3075] Syntax error (missing operator) in query expression 'Name='Static View' AND Object_ID in ()'

I had reported this as a bug - but I think it must have fallen on the low priority list or it may be that this was not a bug but that things are done differently in EA 4.0.

I am posting this in case it is the latter.

(I am working with the assumption that if this was a bug then EA 4.0 would have stopped alot of VBA integrated stuff out there and this would have been seen as slightly higher priority.)

Any help greatly appreciated.

Khalid