Hello all,
I am trying to build up a library of useful components customised to be the way I'd like them. In doing so, I have noticed that there is a little yellow triangle which is invisible unless you happen to click on one of the elements within the component which has a conflict of name, but there is no indication as to whether giving it a unique name will adversely affect the operation of the skin without further tweaking etc.

It would be great if Pano2VR would handle all of this... to be able to rename all elements in a custom made component such that each element has a unique name and cannot conflict if added to an existing skin. Most importantly too, that this renaming would also ripple down into the actions, variables, logic block and Hotspot Properties that relate specifically and only to this component so one would not have to remember each area where you'd have to manually rename actions/varialbles/logic block and hotspot items.

Hi Mark,
Unique ID's are a must if you are targeting them with a button to do something with it.
Example you have a button to show a "Rectangle" and you have two of then in the skin editor.
What will happen is the first element with the ID will be shown.
You can add a # to the ID so it looks like: #Rectangle. Then every element with that ID will be opened.

If you click on the yellow triangle it should add a number to the ID. Rectangle_1, then Rectangle_2 etc.
However if the element does not get referenced by any actions then it does not matter if there are multiple elements with the same ID, but it a tad messy.
Regards,
Hopki

Hi, thanks Martin,
Yep, I get how it works, but I was thinking it would be a lot better if one did not have to do this manual linking graft... just add elements and the behind the scenes renaming/connecting etc happens automatically.
Cheers,
Mark.