LabVIEW Idea Exchange

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

Enable modification of VI history via property nodes

Status: Declined

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

VI history is mostly read-only but can be cleared.

Adding lines is only possible manually.

While I understand and honor the original intention it is obvious that nowadays the versioning abilities that come with LabView are just a fig-leaf compared to a proper Source Code Control history.

It would be nice to be able to synchronize the SCC history and the VI history.

The way the feature works right now is way too limited to be of any use. Even the ability to just import the current SCC history into the VI (which usually would be a file change that needs to be checked back in... welcome in the endless loop) would be better than the existing situation.

 

It would help a lot just to be able to write the history and revision numbers via property nodes without limitations.

5 Comments
crossrulz
Knight of NI

My opinion is that the VI History should be completely removed.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
wiebe@CARYA
Knight of NI

>My opinion is that the VI History should be completely removed.

I decided not to post the exact remark, but now you mention it I have to agree...

Bluegraf
Member

I could also go with that as the current VI history implementation is pretty pointless. I hardly think a lot people would miss (or even notice) it.

 

But out in the plant without proper SCC connection I sometimes miss the opportunity to easily see the version numer and SCC comments. Opening up the property would be only little effort for R&D, I guess, and make the feature at least a little bit useful... for tool programmers.

AristosQueue (NI)
NI Employee (retired)

R&D will not be spending any time on VI history. The only reason it hasn't been removed is that removing it would take time, and there's no compelling reason to remove it.

 

> Opening up the property would be only little effort for R&D

 

That is not true. Adding a property means implementing the feature, creating test suites around it, writing documentation for it (including localization), and validating it on all platforms. There are many secondary effects to even minor user features.

Darren
Proven Zealot
Status changed to: Declined

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