Skip to content

When / how to generate a new SpatialId? #3705

@fschutt

Description

@fschutt

I'm currently in the progress of upgrading from WR 58.0 to 60.0 - and I've noticed that there is a new parameter called SpaceAndClipInfo that is now needed almost everywhere. However, there doesn't seem to be a SpatialId::new() and most examples however just generate a SpaceAndClipInfo::root_scroll() and then copy the root_info.spatial_id to all the nodes. So what's the point?

  1. How is a SpatialId different from a PipelineId?
  2. Do scroll frames need a new scroll ID?
  3. Is it wrong if every node has a distinct SpatialId?
  4. Why is a SpatialId required to define a new clip?
  5. Can there be an example of when / how to generate a new SpatialId?

Also I've noticed that the scrolling example doesn't actually scroll anymore (at least on Windows), maybe it's because the spatial IDs of the scrolling and non-scrolling content are the same?

PS: A CHANGELOG.md or something like that would be great to have.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions