How to change the Report object names in Configure DIAdem Report Dialog Box (Figure 1 &Figure 3)?

[yangafreet]

How to change the Report object names in Configure DIAdem Report Dialog Box (Figure 1 &Figure 3)?

Use the same Free Text in Report Edit Panel in DIAdem (Figure2 & Figure 4), the example of DIAdem can assign different names to different Report objects. But the users can’t assign Report object to Free Text objects, the DIAdem assign names auto as “Text1”, “Test2”, etc. the user can’t change them.

I want to change them, how to do it?

yangafreet

[Brad_Turpin]

Hi yangafreet,

The bad news is that DIAdem does not give you an easy way to name your REPORT objects yourself.

The good news is that there is nothing stopping you from doing so in a text editor.  Simply determine the name of the object in REPORT (you can hover over the object with your mouse and look in the extreme lower left of the DIAdem window-- the gray part), then open up that *.TDR file in WordPad or any other text editor.  Now execute the "Edit>>Replace" menu to automatically find and replace all instances of the DIAdem object name with your own object name.  Then save the *.TDR file and re-load it into DIAdem.

There is no limitation to the naming of REPORT objects except that they must all be unique (on the same sheet).

Brad Turpin
DIAdem Product Support Engineer
National Instruments

[Twigeater]

Hello yangafreet!

I have to add two comments to Brad's suggestion:

• do not use cut/copy/paste on the patched object. This will change the name!
• There are limitations for the name! The name may not contain characters with special meaning in XML like '>'.

After many years using DIAdem I still hope to get a clean&save way for identifiying report objects. Perhaps in DIAdem 11?!

Matthias

[yangafreet]

Thanks for replies!

First time use the DIAdem, I find it is not very convenient to use it.

[inversion]

Hi yangafreet,

I completely agree and understand you in this situation... this is so lame! not something i would have expected from an application costing 1000euro+... this is basic/fundamental functionality were talking about here, its not rocket science to implement a small dialog on creation of a new "free text" (bad name i think, perhaps lock text?) or to even add a field in the properties window of the object. DIAdem seems to have everything else but this feature. Sort it out NI! Wake up chaps!

Alex. 

[Otmar]

---

ali66b wrote:

Hi yangafreet,

I completely agree and understand you in this situation... this is so lame! not something i would have expected from an application costing 1000euro+... this is basic/fundamental functionality were talking about here, its not rocket science to implement a small dialog on creation of a new "free text" (bad name i think, perhaps lock text?) or to even add a field in the properties window of the object. DIAdem seems to have everything else but this feature. Sort it out NI! Wake up chaps!

Alex. 

---

Hello Alex,

Thank you for your feedback on this issue. We are constantly working on improving exiting functionality and adding new functionality to DIAdem. And from an outside perspective, there are supposedly small things (like adding a little dialog or property) that would make working with DIAdem just a little easier (I have often been in the same situation you are in with this request myself).

What I have learned over the years I have been communicating with the DIAdem R&D group is that they are very aware of the issues in DIAdem, and they are working hard to improve and add features to DIAdem all the time. They have to look at requests like this from a lot of different perspectives. I'll just give you a few examples:

- How many people are affected by the current issue? How does the issue need to be prioritized vs. other requests made by customers? What other feature are we willing to drop to make this happen?

- How does a change affect compatibility of DIAdem with older versions?

- How does a change affect the long term ability to add or make changes to a specific area of DIAdem?

- What is the long term plan for this part of DIAdem?

Any small change to DIAdem requires testing for compatibility, usability, stability and performance (not all of them might apply to this particular feature, it's more of a general list). So, making small changes is "expensive" (in terms of time spent) and will lead to something else not being done.

We have long term plans for this, and it will be addressed. We would obviously like to address all of our customers and users requests as quickly as possible, but we also have to look at the big picture long term.