Connector.ReturnValueAlias

[qwerty]

This one also came with 12.1. The help says

Shows the 'Return Value Alias' field of the operation.

This enigmatic in several aspects. I have no idea where that Shows the 'Return Value Alias' might be. And what operation is connected with a connector? So: anyone has any clue what that might mean?

q.

[KP]

If a sequence message has a return value which is a Class element (for example), and that Class element has an alias, it is stored in t_connector.StyleEx as 'rva=Alias;'

You seem to have a lot of these queries. It might be worth putting them all together in a single bug report.

[Paolo F Cantoni]

If a sequence message has a return value which is a Class element (for example), and that Class element has an alias, it is stored in t_connector.StyleEx as 'rva=Alias;'

You seem to have a lot of these queries. It might be worth putting them all together in a single bug report.

qwerty is performing two functions here. 
1 reporting the bug - I assume he/has will submit a formal bug report.
2 alerting the rest of us to the issue.

Separate posts helps #2 - and doesn't hurt #1

Paolo

[KP]

and doesn't hurt #1

From a user point of view, I would imagine that submitting a dozen forms is a lot more effort than submitting one. From a support point of view, receiving separate reports is preferable when they are unrelated subject areas because they will probably be allocated to different developers to investigate; that probably isn't the case here, hence the invitation to bundle them all together. In general though, we're happy with whatever is easiest for the customer

[RoyC]

Yes - note that KP was talking about the bug report, whereas Paolo seems to have assumed he was talking about the forum posts. Paolo's points are good for forum posts, KP's suggestion entirely logical for bug reports.

[Paolo F Cantoni]

Yes - note that KP was talking about the bug report, whereas Paolo seems to have assumed he was talking about the forum posts. Paolo's points are good for forum posts, KP's suggestion entirely logical for bug reports.

I was actually referring to both.  It's not that hard (as you may have noticed) to generate a pile of formal reports quickly and efficiently even using the web forms.

One report one issue.  Make life simpler.

Paolo

[qwerty]

Actually I was just not simply going through new functionality introduced since I first wrote my Scripting book, but wanted to test the new functions to see how they work. I was not expecting this flood of (as it looks) bugs so I posted one question for the first observation, then the second and so forth. If I had some bit of clairvoyance I had put it all together in a single post. But who, I ask you, could have expected bugs in dozens?

Thanks KP for the clarification, I'll try that. Maybe this explanation could go to the help as well.

q.

P.S. Ok. So how do I specify a class as return value for a message? The return value field is just plain text.

[KP]

P.S. Ok. So how do I specify a class as return value for a message? The return value field is just plain text.

You assign an operation to the message, the operation has a return value.

[KP]

It's not that hard (as you may have noticed) to generate a pile of formal reports quickly and efficiently even using the web forms.

One report one issue.  Make life simpler.

From a user point of view, I would imagine that submitting a dozen forms is a lot more effort than submitting one. From a support point of view, receiving separate reports is preferable when they are unrelated subject areas because they will probably be allocated to different developers to investigate; that probably isn't the case here, hence the invitation to bundle them all together. In general though, we're happy with whatever is easiest for the customer

[qwerty]

Hu. Tricked by EA once more. That came right through the back door. Could anyone have guessed that from the pure help?

Honestly, I will not submit a single bug report. I once spent too much time in sending bug reports and saw nothing in return. So you can take my posts here and do whatever you might think is appropriate.

q.