Create New Root Node

[alext]

Does anyone know if there's  a way for creating a new Root node from C#?

[Frank Horn]

EA.Repository.Models.AddNew()

[alext]

Thanks for your quick reply Frank...
I have tried the following :

EA.Package newModel = (EA.Package)repository.Models.AddNew("My Test", "");
repository.GetProjectInterface().ReloadProject();
repository.RefreshModelView(newModel.PackageID);

But unfortunatly nothing happens (= MyTest does not appear as a new Model)

What am I doing wrong?

Thanks for your help!

[Frank Horn]

After

Code: [Select]

EA.Package newModel = (EA.Package)repository.Models.AddNew("My Test", "");
call

Code: [Select]

repository.Models.Refresh()

[alext]

hmmmm.... that doesn't seem to do the job.
I still don't see the new Module

[«Midnight»]

Reload the project, if you had it open at the time.

[alext]

Allright...the following code still doesn't do anythin :

           EA.Package newModel = (EA.Package)repository.Models.AddNew("My Test", "");
            repository.Models.Refresh();
            repository.RefreshModelView(newModel.PackageID);
            repository.GetProjectInterface().ReloadProject();

[«Midnight»]

After the first line add:

newModel.Refresh();

Better now?

[alext]

hmmm... I don't have a Package.Refresh() method.
Do I have an older version of the API? I have EA 7.1.834....

[alext]

Okay ... there's a Package.Update() however... and this seems to work!
Thanks for all the help!

[«Midnight»]

You have to call Update whenever you add an item to any collection in EA. This call has to be made before you reference the item in any way. In particular, the Refresh method of the parent collection will not 'see' the item unless you have previously called Update.

For a few items you need to set one or more values before you call Update. An example is a connector, where you add it to one element, but need to set the other end (to the ElementID of whatever is on the other end) before you call Update.

There are also a small number of attributes that it is 'safe' to set before you call Update. An example is the Stereotype attribute.

The general rule of thumb is that you cannot refer to the new item from elsewhere before you call Update. Another rule is that you should not refer to the ID or GUID properties of the new item before calling Update.

One more thing: whenever you change values for an item you also have to call Update. The new values will not be saved until you have done so.

HTH, David

[edit]PS: Once you have Update figured out, Refresh makes sense. The Refresh call affects collections rather than individual elements. It tells EA to reload (i.e. refresh) the collection with current information about each contained element. This will cause the collection to reset its Count attribute if required. It will also ensure that GetByName and GetAt work correctly, and reflect the elements that are currently in the collection.

You don't need to call Refresh unless you have added, or deleted elements, or changed element attributes that might affect retrieval. Note that not all these properties are immediately obvious. The Name of an element is certainly significant, but modifying the Pos attribue (where it exists) or the Position attribute of a Parameter might also affect how the collection behaves.[/edit]

[alext]

Thanks for your reply!