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 - LurkingGrue

Pages: [1]
1
I've successfully written several small add-ins in C# that build menus, respond to menu clicks and interact with the repository via automation interface just fine.  However, I've never been able to get the EA_ShowHelp event to fire in any of them (EA 6.x or 7.x).  EA just brings up its own help screen without ever calling the function in my add-in dll.

Here's the method signature that I've been trying:
Code: [Select]
public void EA_ShowHelp(EA.Repository repository, string menuLocation, string menuName, string itemName)
{ \\ this never gets called }
Is that incorrect so EA isn't finding my event?  Or does this just not really work as described in the docs? It's not super-critical to using the add-ins, but would be nice to get going and finally just bugged me enough to post about it :)

2
Thanks, Midnight!  The parametrized class info was available via the get_MiscData(2) method. Here is an example with two parameters, T and C:

Code: [Select]
<PRM1>=T;<TYP1>=string;<DEF1>=helloWorld;<PRM2>=C;<TYP2>=int;<DEF2>=13;
Unfortunately, it is read-only as you indicated, and it is not accessible via Properties or CustomProperties either.  I'm hesitant to try anything else, but at least I have read-only access for now.

3
On the Details tab of the Class Properties dialog, there is an area for adding parameters to a class. How can I access this information from the automation interface?

4
Hi guys, I'm not sure if the is the correct forum for this topic, but the its brief description mentioned Profiles, so...

I can't find any reference to StandardProfileL2 or StandardProfileL3 or their custom stereotypes as defined in the UML specs in the EA docs or forums.  Do we have to recreate these profiles ourselves, or does support already exist for them in EA and I just haven't found it yet?

5
Thank you both for clearing up my confusion between keywords and stereotypes!  The specification quote was very enlightening, and I appreciate the historical perspective on how the notational confusion has been perpetuated.

I agree that there is still a problem here, though.  The spec suggests that keywords and stereotypes for a given element be comma-separated between a single pair of guillemets.  That might justify listing them together in the StereotypeEx property.

However, anything appearing in the single Stereotype property should appear in StereotypeEx as the automation interface docs suggest.  Otherwise, both properties have to be checked every time.  And you can't just concat them if you're building a list, since Stereotype usually (but not always!) will appear in StereotypEx.  This inconsistent behavior certainly makes for messy code, but at least there is a workaround for now.

6
I'm fairly new to EA and have been playing with the automation interface via custom add-ins.

My understanding is that the StereotypeEx property is a comma-separated list of all stereotypes for a given object, and the Stereotype property just gives the first one from that list.

However, I noticed when iterating through stereoptypes that a Realization connector with Stereotype = "realize" does not have any values in the StereotypeEx property (which = "" if there are no others).  Is this by design because it is a special built-in value?  Are there other examples of this to watch out for in EA?

Or perhaps one should always read Stereotype and StereotypeEx together to get all stereotypes for a given object?

Pages: [1]