Set Description property node bug?

[WNM]

Why is it that setting a "Description" property for a front-panel control (or indicator) steals key focus from another control that a user might be trying to update?  I can see this behavior in both LV 2014 & 2015 (I have not got anything later).  Is this intended behavior or just an unfortunate "feature"? 

I have attached a LV2014 example of this.

[RavensFan]

It happens in LV 2016 f2 as well.  That is very odd.  I don't know of any reason why it should behave that way. 

[Shezaan · Accepted solution]

Hello, 

It seems that a Corrective Action Report for this issue CAR#: 640817 has been filed. Thank you for bringing this to our attention!

Regards,

Shezaan Noorani

Applications Engineer

[WNM]

Yes, early today I came in to find an email nudge from the forum to accept something as an answer to my question. I decided to in turn nudge NI through our support channel for a CAR# for what looked to be a real bug.  I just received this note in response:

Looking into this I originally expected this to be expected behavior, but I played around with the code on the forum and it seems like even other documentation-related property nodes do not shift the key focus. Therefore, I have submitted a CAR on the inconsistent behavior from this. That CAR number, for your own reference, is 640817.

Mathew Howard
Applications Engineer
National Instruments

Hopefully the eventual fix for the "inconsistent behavior" will not be to make the other documentation-related property nodes also shift the key focus, bringing them in line with the obnoxious behavior of the set-description property node.