I recently had a tough nut to crack. I had created an XControl whose "Label" (i.e. Visible name) I wanted to be able to change at run-time. This was a label INSIDE the XControl, not the label of the XControl itself.
My naive self decided to create a property node named "Label" with a read and write VI.
Guess what happened.... The property nodes attached themselves to the already existing "Label" property for the XControl itself. Only by going into XML-editing mode could I undo this effect and rename the short AND long versions of my property node. While I was intrigued and almost wanted to see how many other properties I could access this way I thought better of it and want to change the behaviour for future generations of LV. If a user tries to create a property node for an already existing property, please let them know they are doing so.
I had briefly, through non-reproducible steps, managed to create a property node for WRITING the "Label" (the inbuild one, not the one I WANTED to create) reference to my XControl. I refrained from seeing what would happen if I did so.....