Example #1
0
 /// <summary>
 /// called when the selected item changes
 /// This operation will show the guid of the selected element in the eaControl
 /// </summary>
 /// <param name="Repository">the EA.Repository</param>
 /// <param name="GUID">the guid of the selected item</param>
 /// <param name="ot">the object type of the selected item</param>
 public override void EA_OnContextItemChanged(EA.Repository Repository, string GUID, EA.ObjectType ot)
 {
     if (this.eaControl == null)
     {
         this.eaControl = Repository.AddWindow("Explorer", "EAExplorer.EAExplorerControl") as EAExplorerControl;
     }
     if (this.eaControl != null)
     {
         this.eaControl.showObjectProperties(Repository, GUID, ot);
     }
 }
Example #2
0
 /// <summary>
 /// EA_Connect events enable Add-Ins to identify their type and to respond to Enterprise Architect start up.
 /// This event occurs when Enterprise Architect first loads your Add-In. Enterprise Architect itself is loading at this time so that while a Repository object is supplied, there is limited information that you can extract from it.
 /// The chief uses for EA_Connect are in initializing global Add-In data and for identifying the Add-In as an MDG Add-In.
 /// Also look at EA_Disconnect.
 /// </summary>	
 /// <param name="Repository">An EA.Repository object representing the currently open Enterprise Architect model.
 /// Poll its members to retrieve model data and user interface status information.</param>
 /// <returns>String identifying a specialized type of Add-In: 
 /// - "MDG" : MDG Add-Ins receive MDG Events and extra menu options.
 /// - "" : None-specialized Add-In.</returns>
 public override string EA_Connect(EA.Repository Repository)
 {
     this.eaControl = Repository.AddWindow("Explorer","EAExplorer.EAExplorerControl") as EAExplorerControl;
     return base.EA_Connect(Repository);
 }
Example #3
0
 /// <summary>
 /// called when the selected item changes
 /// This operation will show the guid of the selected element in the eaControl
 /// </summary>
 /// <param name="Repository">the EA.Repository</param>
 /// <param name="GUID">the guid of the selected item</param>
 /// <param name="ot">the object type of the selected item</param>
 public override void EA_OnContextItemChanged(EA.Repository Repository, string GUID, EA.ObjectType ot)
 {
     if (this.eaControl == null)
         this.eaControl = Repository.AddWindow("Explorer","EAExplorer.EAExplorerControl") as EAExplorerControl;
     if (this.eaControl != null)
         this.eaControl.showObjectProperties(Repository,GUID,ot);
 }
Example #4
0
 /// <summary>
 /// EA_Connect events enable Add-Ins to identify their type and to respond to Enterprise Architect start up.
 /// This event occurs when Enterprise Architect first loads your Add-In. Enterprise Architect itself is loading at this time so that while a Repository object is supplied, there is limited information that you can extract from it.
 /// The chief uses for EA_Connect are in initializing global Add-In data and for identifying the Add-In as an MDG Add-In.
 /// Also look at EA_Disconnect.
 /// </summary>
 /// <param name="Repository">An EA.Repository object representing the currently open Enterprise Architect model.
 /// Poll its members to retrieve model data and user interface status information.</param>
 /// <returns>String identifying a specialized type of Add-In:
 /// - "MDG" : MDG Add-Ins receive MDG Events and extra menu options.
 /// - "" : None-specialized Add-In.</returns>
 public override string EA_Connect(EA.Repository Repository)
 {
     this.eaControl = Repository.AddWindow("Explorer", "EAExplorer.EAExplorerControl") as EAExplorerControl;
     return(base.EA_Connect(Repository));
 }