DisplayName of Child Executions

[Mr._Jim]

Hi all,

Another day, another obscure question.

I'm using the batch process model, launching two new executions per test socket.

I'm also using the sequence editor.

For each launch of the new execution I'm selecting "Do not use a process model." I'm doing this for simplification of results processing and so that I can display each child thread in its own window, which is a requirement. (Otherwise I would have used new threads instead of executions)

Is there any way to set the DisplayName of each child execution?  I can't figure out if there's a way to modify the DisplayExpression or set each execution's DisplayName to something other than the sequence call.

I did run across this thread, but I'm not sure if there's a way to get to the DisplayExpression in my circumstance.

Has anyone done this successfully?

Thanks as always,

Mr. Jim

[sherlockholm]

Hi Mr. Jim,

Can you post a screenshot, or something to show exactly what you are trying to change?

[Mr._Jim · Accepted solution]

Hello Mr. Holm(es),

Thanks for your reply.

Here's an illustration of what I was trying to set:

From conversations with support, there is no officially sanctioned way of setting the DisplayName of child executions when executing via the sequence editor. (This confirms what Norbert was saying in the thread I alluded to above)  There is much more flexibility in this matter when customizing an RTOI, however.

I was able to employ some hackery to get my child executions labelled as above:

RunState.Thread.PostUIMessageEx(UIMsg_ModelState_Identified,0,Parameters.CallingSocket_SerialNumber + "_" + Str(Parameters.CallingSocket_SubIndex) ,ThisContext,True),
RunState.Thread.PostUIMessageEx(UIMsg_ModelState_BeginTesting,0,"",ThisContext,True)

Performing the above causes the sequence editor to update the name of the execution. The latter UIMessage, probably among many other things, causes the colored indicator in the Execution List to update.

It does work, but the official word I'm getting is, "Don't count on it to work in the future because it's more of an exploit than a feature."

Hopefully this'll help someone out down the road, because as Norbert summarized, it's pretty cryptic.

Regards,

Mr. Jim