UI Message help

[paulmw]

Lawrence,

I think my update/reply beat your last reply...  Check my last reply, I think it is exactly what you are looking for.

Paul

[lmd2]

Thanks Paul
just read the knowlegebase article, sounds like just what I was looking for.
if I understand correctly, the file in the article is the modified .dll and can be used to replace the dll in my \\User\Models\TestStandModels directory.
let me play with this a little,
good find, thanx

[paulmw]

I would suggest doing...

"(Note: Before you modify any source files, copy the TestStandModels directory over to the <TestStand>\Components\User\Models\ directory.)"

Or copy/backup/rename the existing .dll first.

---

Sorry, didn't fully read your relpy:

you wrote: "replace the dll in my \\User\Models\TestStandModels directory"

I missed the "user".  Looks like you got it under control.

Message Edited by paulmw on 07-09-2007 11:26 AM

[lmd2]

ok the dll is replaced; but this isn't completely clear:
"To post a message to the function, create a new step in the TestStand Sequence Editor that uses the C/C++ DLL Adapter and use the following parameters: ..."

this tells you the adapter, but not the step type
I looked at 'Property Loader' but that looks to load properties from a file or DB. am thinking an 'action step' which allows defining parameters, but what module and function would I reference? or am I still looking at the wrong step type?

[lmd2]

yes, that's it
the module is the newly modified dll and the function is PostParallelUUTStatusMessage

thanks for all your help

[lmd2]

For the dialog handle, the knowlegebase article says:
use "RunState.Root.Parameters.ModelData.DialogHandle"

but I get the following error: 'unknown variable or property name'
could this have changed slightly in TS 4.0?

[paulmw]

I think you can ignore this error.  The data/handle is not available untill runtime.  If you pause in your sequence and browse the context, the path is there.

Message Edited by paulmw on 07-09-2007 12:58 PM

[paulmw]

You do bring up another point to consider.  I don't know exactly what version of .dll was based from.  The article list Teststand version 3.5.  If you have 4.0, you may be missing some functionality implement with the upgrade if you use the version that was downloaded.  If this is a concern, you may want to consider making your own build from your existing TS 4.0 .dll.  Again you will need CVI.

For now we can see if this .dll works in updated the status string.  Let us know how it works.

[lmd2]

yeah, under Root I just have (Object Reference) so I typed it in by hand, no problem. I just forgot about it not being there until the sequence was run. we did go over that in class, I just forgot.
thank you, guess I'll try running it.

[lmd2]

IT WORKS!!