replace selected is grayed out when trying to replace global variables.

[bleach_dave]

I am not able to find and replace global variables as the replace selected is grayed out. It is under a project tree, and yet I still have issues. Why Can I not replace it?

Thanks,

bleach_dave

[Charlie_P]

Good Evening bleach_dave,

I created a simple test project here and have found the same results.  I imagine you see a strikeout icon (circle with a slash through it) on find's results page.  This indicates that the object cannot be replaced (as you have discovered).  You can read some more information about this in the LabVIEW Help file, under "Search Results Window".

I will look into this behavior and let you know if I find a workaround and/or a reason for this.

[comrade]

sorry to bring this old thread up again:

I am experiencing the same difficulty when trying to replace TypeDefs. I am only allowed to replace them when they come as constants on the BD. All respective indicators or controls found in my VI hierarchy are striked out. Unfortunately LabVIEW Help keeps somewhat quiet about what could be the cause for a strikeout.

Has there been any update in this matter?

Thank you.

[comrade]

For reference I attach a screenshot of the Search Result Window...

[Esteban.R]

Hi Comrade

I was trying to reproduce your error but I have not been able to do it.

Could you give more information or the steps in order to reproduce this error.

Regards

Esteban R.

[comrade]

Esteban: thanks for the effort - NI support Germany informed me yesterday that when using the Search & Replace Window, controls or indicators cannot be replaced by a different control or indicator. This seems to be a limitation of the function itself, as it obviously deems the replacement of one type of control with another type of control as nonsense - usually it would cause broken wires all over the place.

Here is the thread they pointed me to:

http://forums.ni.com/t5/LabVIEW/Find-and-replace/td-p/1705646

There is a VI scripting solution also that's posted there.

For completeness's sake:

I have a bunch of VIs that all use a certain TypeDef (TD) as IN and OUT, where all application-relevant data is stored, such as FP-element refs, IMAQ-refs and the like. Now I noticed that I want to have some additional information available in the TD. Of course I could just update the TD with what I additionally need. Somehow (I don't even remember why) I thought it a better idea to create a new TD with all the TDs I wanted to group together. So I created that new TD and let LabVIEW search for all the places I had to replace the old, incomplete TD. Then the screenshot shown in my last post popped up - saying I can't replace them via this function by showing a strikeout symbol to the left of the TD instances found.

[JÞB]

If you dig just a bit more I bet you will find that only those controls and indicators that are struck out for a good reason.

(think about it for a bit.... The hierarchy view is driven by CP connections and you are thinking of replacing items that drive hierarchy.  Did you ever turn the ignition key in your car after the engine was already running?)

I would call this expected behavior.

Scripting is the ony way to do this since the hierarchy view is not necessary for scripting

[comrade]

Thanks for the short in-depth information. Never knew about this. Guess it really is a long way towards CLA

[JÞB]

---

@comrade wrote:

Thanks for the short in-depth information. Never knew about this. Guess it really is a long way towards CLA

---

Every step counts though! The forums are a great way to gain insight.