You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't understand these linese yet. FocusOverlay uses TransformTracker for transformations up the trail, will that be sufficient since the cues are added as children to the focus highlights? Why do we need to prepend nodes matrix?
I think I understand now. The pink FocusHighlightFromNode surrounds the node's local bounds, but is added to the global coordinate frame in FocusOverlay. So likewise, the cue nodes (or children added to the focus highlights) need to be transformed by the node's local transformation matrix to be positioned correctly when transformed by the node's localToGlobalMatrix in FocusOverlay.update().
Yes this is less than ideal, and it was the cause of phetsims/friction#181. I would love to find a different solution that was more robust.
We haven't run into trouble with transforming the cue Node thus far (with 4 production usages). Perhaps we can work on it if we every run into trouble. Presumably it would be very obvious when the matrix is off (I'm sorta shrugging over here).
It would be good to improve this. We haven't had problems over several years, so it is probably low priority until we do.
The text was updated successfully, but these errors were encountered:
From #447, there is a remaining piece of work:
It would be good to improve this. We haven't had problems over several years, so it is probably low priority until we do.
The text was updated successfully, but these errors were encountered: