Interface operation properties not reflected

[g.makulik]

Can someone explain this strange difference of the operation properties from an interface with the properties showing up in the corresponding Method element from the EA object API:



Of course these properties are implicit for operations appearing in interface elements, though it's pretty strange that this isn't reflected in the EA.Method interface   ...

I think this is worth a bug report, anyone else came over this??

Regards,
Günther

[Makulik]

I just noticed that it takes a notable amount of time until the image that demonstrates my concern is loaded. Any readers, please be patient ...

Here's a thumbnail

[qwerty]

That one does not render better than the picture in the first post.

q.

[g.makulik]

submitted a bug report:

An interface operations properties are not correctly reflected in the corresponding EA.Method class in the EA object API. In particular I'm referring to the 'Abstract' and 'IsPure' properties, both evaluate to 'false' despite the GUI suggests them being 'true'.

I have appended a screen shot of the relevant operation property pages shown in the GUI and the property container shown for this operation in the EnarSpy utility (same behavior if I'm debugging my C# code).

Steps to Reproduction:
1. Create an interface element
2. Add an operation
3a. Select the operation and show element details with EnarSpy
3b. Alternatively create some automation code in C#, refer to the associated EA.Method object and check the Abstract and IsPure properties.