This is a VERY high priority on R&D's roadmap. Unfortunately, it is also a very time consuming and dangerous feature. If we started from scratch we would have to come up with some way to re-use existing TDR files and VBScripts, something like the AUT ==> VBS converter we added in DIAdem 8.0 when we introduced VBScript as the new scripting language. There are other implementation options that could natively continue to support existing TDR files and Graph...() VBScript commands, but those approaches may restrict what we can accomplish.
I personally believe this will happen, but it's not something we can do quickly, both from an implementation and a testing perspective. I use the non-object Graph...() functions too, and I've been asking for an object-oriented approach for REPORT for a long time now. Know that I continue to lobby for this and that R&D agrees that it needs to be done.
Brad Turpin
DIAdem Product Support Engineer National Instruments
How would you like to use this API in .NET ? There is no specific .NET wrapper for DIAdem, but what you can do today is using the Active-X interface to launch DIAdem and execute scripts. Those scripts then can also use the REPORT API.
Do you think about using DIAdem as a pure report generation engine from .NET ?
Describing what you have in mind can help us to better understand the benefits you expect.
Yes using .net as an interface would allow us in LabVIEW to alter reports (add graphs, change channels) etc. so we can in a for us well-known environment adjust our reports.
For this purpose a Head-less DIADem would suffice.
This feature is available in the DIAdem 2012 BETA version (http://www.ni.com/beta). We would greatly appreciate everyone who was interested in this feature to test the 2012 Beta version and provide feedback before DIAdem 2012 releases.
