Skip to content

[ENH]: do_3d_projection could restore original verts order after draw() finishes #23155

Closed

Description

@anntzer

Problem

do_3d_projection() reorders vertices of various 3D collection artists in z-depth. Once the drawing is done, it would be useful to restore back the original order, so that e.g. interactive tools (mplcursors) reporting the index of a picked collection member get the original index as set by the user (anntzer/mplcursors#49). This should be reasonably cheap to do as we can probably just stash the original arrays somewhere and restore them as attributes at the end.

In practice, this probably means adding another API like doing_3d_projection() which returns a contextmanager (or letting do_3d_projection() possibly return a contextmanager and doing a typecheck on that) and replacing the calls to do_3d_projection() to stack.enter_context(artist.doing_3d_projection()) where stack = ExitStack() is defined at the top of Axes3D.draw().

Proposed solution

No response

Activity

  1. added this to the v3.7.0 milestone on May 27, 2022
  2. added
    🌱 Good first issueOpen a pull request against these issues if there are no active ones!
    Difficulty: Mediumhttps://matplotlib.org/devdocs/devel/contribute.html#good-first-issues
    on May 27, 2022
  3. tacaswell commented on May 27, 2022

    @tacaswell
    Member

    Tagging this as a good first issue because I think this can be done without adding any public API, but medium because you should be conversant with writing context managers and will need to read and understand the 3D artist code.

  4. evanandresen commented on Sep 17, 2022

    @evanandresen

    Could I work on this issue? This is my first time looking into matplotlib src and I would like to help out.

  5. tacaswell commented on Sep 18, 2022

    @tacaswell
    Member

    Yes, unless there is an active PR the issue is fair game!

    As noted above, you will need to be familiar with context managers and read/understand the 3D code which a bit complex. If you start on this and have any questions about the existing code please ask!

  6. QuLogic commented on Sep 20, 2022

    @QuLogic
    Member

    I did this for some cases in #18932; I should probably return to the rest.

  7. hukaidong commented on Dec 5, 2022

    @hukaidong
    Contributor

    PR #24491 would be enough to close this issue

  8. tacaswell commented on Dec 5, 2022

    @tacaswell
    Member

    Closed by #24491

  9. tacaswell commented on Dec 5, 2022

    @tacaswell
    Member

    Thank you for the triage work @hukaidong !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Difficulty: Mediumhttps://matplotlib.org/devdocs/devel/contribute.html#good-first-issuesNew featuretopic: mplot3d🌱 Good first issueOpen a pull request against these issues if there are no active ones!

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions