LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
crelf

Add "Clone Method" right click menu item to LVOOP methods

Status: Declined

Any idea that has received less than 3 kudos within 3 years after posting will be automatically declined.

I like that I can create methods from templates, but I think the "Clone Method" is sorely missing from the LVOOP meothod right click menu.  Note: installing the Symbio GDS adds this - I'd like to see it native.





Copyright © 2004-2024 Christopher G. Relf. Some Rights Reserved. This posting is licensed under a Creative Commons Attribution 4.0 License.
7 Comments
AristosQueue (NI)
NI Employee (retired)

To clarify for other readers, I'm pretty sure crelf doesn't want "Save As". What he's looking for is a function to "Take VI A which takes class X as input and create a duplicate of VI A which takes class Y as input."

crelf
Trusted Enthusiast

Right - sorry, I didn't make that clear.  I'd even be happy if it gave me a list of other classes in the current project (including those listed in the dependancies) to choose from, although the option to browse outside of the project could be useful.





Copyright © 2004-2024 Christopher G. Relf. Some Rights Reserved. This posting is licensed under a Creative Commons Attribution 4.0 License.
AristosQueue (NI)
NI Employee (retired)

What is the use case here? Normally, we* advocate against copying code, pointing you toward other options (common subVI, common inheritance (with overrides for details)), etc. What are you working on that the code maintenance generated by copying is desirable? Could some other feature fill your need without generating copied code?

 

 

* and by "we", I mean NI, yes, but you, also, crelf... this isn't usually a point you'd support, so I figure there's gotta be something interesting you've tripped over.

crelf
Trusted Enthusiast

To be honest, it's only a little idea, and nothing that I* would support too much time being taken away from efforts to implement other idea excahnge ideas.  The use cans is that I occasionally (think maybe three or four times) have wanted to clone a method between classes - at least two of those times were because I had 2 classes that wr extremely similar (reuse classes) whose only schism reason was to support different versions of LabVIEW (in this case, when a new feature is requested, I can't just work on the latest version of LabVIEW and then save the class for a previous version, as that would wipe out code in identically-named methods that have version-specific code).  I have a manual work-around, so, as I said, this isn't an idea that too much effort should go into.

 

* and by "I", I mean NI, yes, but me, also... even if you did implement this idea, I can't say that I'd have too much time to dedicate testing it in the beta programme, other than once or twice.  Sorry that there's nothing really interesting that I've tripped over 🙂





Copyright © 2004-2024 Christopher G. Relf. Some Rights Reserved. This posting is licensed under a Creative Commons Attribution 4.0 License.
Darren
Proven Zealot
Status changed to: Declined

Any idea that has received less than 3 kudos within 3 years after posting will be automatically declined.

crelf
Trusted Enthusiast
I'm okay with that, let it die.




Copyright © 2004-2024 Christopher G. Relf. Some Rights Reserved. This posting is licensed under a Creative Commons Attribution 4.0 License.
drjdpowell
Trusted Enthusiast

One can "Clone Method" with LVOOP Assistant.