Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Calculate local clipping rectangle per-primitive run #2200

Merged
merged 2 commits into from Dec 25, 2017

Commits on Dec 25, 2017

  1. Calculate local clipping rectangle per-primitive run

    Instead of using the hierarchical nature of the ClipScrollTree to
    calculate local clipping rectangles for primitives, do it when we are
    about to render a particular primitive run. This will allow us to
    handle custom clip chains while maintaining local clipping rectangle
    optimizations. It also allows us to greatly simplify a lot of shader
    code that used to deal with both clipping and scrolling nodes, as the
    local clipping rectangle is now bundled into the primitives
    local_clip_rect.
    
    TransformOrOffset is the main struct that handles the efficient
    transformation of clipping rectangles between compatible coordinate
    systems. It will avoid doing expensive matrix operations as much as
    possible, which should make these calculations cheaper -- important now
    that they are done per-primitive run.
    mrobinson committed Dec 25, 2017
  2. Remove parent_combined_viewport_rect from TransformUpdateState

    It's unused now.
    mrobinson committed Dec 25, 2017
You can’t perform that action at this time.