Rody Davis

> Ah thanks for the explanation. So this is not a workaround for `RenderBox` hit-test culling but a feature that allows developers to apply the current transform themselves? That is...

> Stack -> [...nodes, IV] Just tested and the example works: ```dart Stack( clipBehavior: Clip.none, children: [ for (final node in nodes) Builder( builder: (context) { final matrix = controller.value;...

That does work as expected! https://github.com/user-attachments/assets/686aa5be-d59d-470b-b3f3-82bda9aa384e The issue with having it split like this is the stack has to rebuild the children any time a new node is added/edited/removed and...

Per the offline discussion: https://github.com/user-attachments/assets/b4f5463d-832f-4c77-883d-80401f1cb296 Added the .raw constructor

> But I can't really think of a concrete use case where one would want a finite canvas (e.g. finite `bounaryMargin`) and at the same time does not want the...

> As for hit-test culling example, I'm not sure that we should include that since it's really a RenderBox problem and imo probably requires a RenderBox solution. I'm a bit...

I moved the example to DartPad which should help clean up the code comment and also show the grid background for a more complete example.

I was able to recreate my example by restructuring the layout. This comes at the cost of a lot of extra code, and a dependency on **vector_math** just to make...

> What if we pulled the passive detection logic out of InteractiveViewer and into a new widget? Working title InteractionDetector. I think that would be the best approach! It would...

I think that the boundary could be delegated to the InteractiveViewer for detection based on the child size. InteractiveDetector could handle all events like GestureDetector.