Me deleting the first highlight is proper, its just removing highlight from the parent, however the highlight I deleted from the other part seemed to disable highlight for both?
Expected Behavior
Only the parent should be highlighted
Isn’t this feature in beta still? I honestly haven’t heard of them announcing this feature yet. I went into studio and still doesn’t work at all.
Did you enable any flag or something to use it? In the meantime, since I believe is still under development, I think you should use the SelectionBox instead though is not what you really want.
When a highlight is in a model, if a secondary highlight is placed in that same model, then even if the secondary highlight has transparency set to 1 and is disabled, it will still occlude the first highlight.
My script sets the parent of the highlight to the part the user is hoving over, but the previous part stays highlighted if the parent of the highlight isn’t set to nil before it’s being set to another part.
So to move over the highlight without having the other part keeping its highlight, you have to first set its parent to nil before setting its parent to another parent.
Edit: I hope this is helpful, for myself it was very helpful once I figured this out.
Thanks - although we shouldn’t have to do that - this is a change in behaviour in the last couple of days. It should be reverted back to the way it was.
Bumping this post with some footage of highlight bugs:
When the children of a model, with a highlight, are reparented they remain highlighted.
Same bug applies to the new selection tool.
Destroying the highlight of a model causes the highlight to linger.
Same applies when the adornee is set to nil, and/or destroyed.
The effect of the Adornee property is lost when the highlight is reparented to another instance of the Model class.
There also seems to be some sort of entangling between highlights that causes them to all share the same properties when they shouldn’t, but this is difficult to replicate so there’s no footage for this.
