Locked objects should give info when trying to delete

[Yamaeda]

So, due to massive lag in the project environment, borked graphics drivers on the virtual machine and the resulting random rearrengement of objects on the front panels, i've Locked all objects.

Now, trying to delete a control from the block diagram nothing happens, which is technically correct. No information or warning, however, is borderline Bug in my book. I'd expect a popup "Object is locked", not just a silent denial.

LV2014SP1f3 (which for some reason is 14.0.1.3 instead of 14.1.3.x, but that is another discussion)

/Y

[RavensFan]

---

@Yamaeda wrote:

LV2014SP1f3 (which for some reason is 14.0.1.3 instead of 14.1.3.x, but that is another discussion)

/Y

---

Back in the day, there were versions 8.0, 8.2, 8.5, 8.6.  Each were separate full versions that could be installed concurrently.  They also had service packs would would make them 8.00 and 8.0.1.   8.2.0 8.2.1

In 2009, NI changed the numbering so that the main version number coincided with the year of release.  So 2009 is 9.0  and thus 9.0.0 and 9.0.1 for the Service Pack.  They have abandoned the use of the 2nd version digit.

[Yamaeda]

Yes, i remember 8.2 and the ilk being full releases. However, the standard for version numbering is Major.Minor.Fix.Compile, so a fix-update should increase the 3rd number. By that logic 8.0 ==> 8.2 was a minor relase and change, and i assume the code was compatible between them as is usual within the same Major release?

As i said, that's another discussion, what about the suggestion? 🙂

/Y

[RavensFan]

I'll agree with you that it makes sense to move to a 16.0, 16.1 numbering system.  Although Major.MInor.Fix.Compile seems to be the standard, it has always been the software vendor's prerogative to determine what is a major version and what is a minor version.  The jump from 7.1 to 8.0 was definitley a major change.  The jumps from 8.0, 8.2, 8.5, 8.6 weren't as big, but at the end of the day, they were still pretty distinct versions.  One software company that makes no sense to me is Oracle and their numbering for Java.  They are only at 1.7 and 1.8,  but they proceed to call that Java 7 and Java 8.  Factor in their different flavors and build numbers, and that different versions can't coexist, Java is a nightmare to figure out what is working.

But to your original question, I'll agree with you also and put in Kudoes.  I haven't run into this issue much because I've very rarely locked objects.  But I think I've seen a couple cases working on other VI's where I couldn't do something natural like deleting an object and couldn't figure out why it wasn't happening.  I may not have even been locking, but the fact it was grouped with other objects and I was only trying to delete one of them.  Some visual indication as to why something isn't working would be nice.   I don't think I'd want a full dialog to pop-up.  Perhaps something on the screen turning red, or a change in the cursor to indicate that a lock is in place preventing the action.

[X.]

I have experienced the "Delete" object that did not work. I have learned my lesson, but I guess I might forget about it until it happens next time.

I'd rather favor a way of figuring out on the BD that an object is locked with others (on the FP) than a dialog. What is the exact suggestion here?

[Yamaeda]

" I'd expect a popup "Object is locked", not just a silent denial."

Though, some graphical information, like a padlock on the control, would work also.

I want/need feedback. 🙂

/Y