Replace string with path (or vice versa) should not change the value (data)

[Jim_Kring]

When you right-click on a String Constant or Path Constant and choose to Replace it with a Path Constant or String Constant (respectively), the value is lost.  Since strings and paths are somewhat interchangeable, it seems that the data should be preserved (coerced) during the Replace operation.

Note: It might be nice if there were a faster way to change a path to a string and vice versa, as suggested here.

[Darin.K]

Let's see, Jim Kring, right-click, something is coming to mind.  If only there were some sort of framework out there for adding operations to right-click menus.....

For those hip to the RCF, you can try this out.

http://decibel.ni.com/content/docs/DOC-13163

[Jim_Kring]

That's great, Darin -- you ROCK!!!

Now if only there were a free tool for creating installable packages of VIs that you want to share with the community... 😉

(Seriously, you should totally package this RCF plugin as a VI Package)

Cheers,

[Darin.K]

\begin{hijack}

I tried a couple of times to create packages with the community version of VIPM with less than optimal results.  After my last attempt, the package size was several MB, compared to the LLB size of maybe 100 kB.  Totally willing to assume pilot error on this.

I will preface the following by saying that I completely understand the rationale.  Certain things in the community edition are (intentionally) a pain, and these painful things are strategically chosen.  That means that it is a bit of a pain to use for creating packages.  For installing packages, it works stupendously well.

\end{hijack}

Having tried out the idea via the plugin, it is completely natural and expected behavior to keep the data and this would make a nice addition to the LV IDE.

[Jim_Kring]

Hey Darin,

I'd be happy to take a look into why the resulting package is so large.  And, I'm not sure which pain points you're mentioning.  Did you try the package builder in VIPM 2010 Community Edition?  It's been TOTALLY overhauled and is full of features.  Let me know and if you're still having issues (pain points or with the large package size), I'd be happy to take a look at what's going on.

Thanks,

[Darin.K]

I'll give the 2010 version a whirl when I get a chance.

[Darren]

If you do a Quick Drop Replace (select object, Ctrl-Space, type new object name, Ctrl-P), I do my best to preserve the data in the replaced item. Both of the use cases in your image above are supported with Quick Drop Replace in LabVIEW 2011 and later.

I do agree, though, that right-click > Replace with the palettes should support this behavior as well.