Skip to content

3d artist objects need clear and unified way to get/set 3d coordinate data #1483

Closed as not planned

Description

@WeatherGod

Because get_offsets() need to remain 2-D based for draw(), a separate function is needed to get and set the 3d coordinate data. Currently, one would set the 2d offsets, and then use set_3d_properties() to set the 3rd dimension data, which is awkward.

Perhaps this is an opportunity to create a function in the base artist class strictly for raw coordinate data? get/set_offsets() would then be intended more for display/transform purposes but would often be the same as the new methods. Also, this would help clear up confusion where some artists have get/set_array(), get/set_data() and get/set_offsets() all for coordinate data. A unified method would be valuable for documentation purposes.

Activity

  1. modified the milestones: , on Aug 17, 2014
  2. WeatherGod commented on Jun 30, 2015

    @WeatherGod
    MemberAuthor

    This would be a great low-hanging fruit task for SciPy 2015 sprints

  3. pelson commented on Jul 1, 2015

    @pelson
    Member

    I agree that the doing of this is simple, but I don't think it is an easy thing todo unless we can be very specific about what is required (unless one of us were doing it, rather than a newcomer to the project).

  4. OceanWolf commented on Jul 4, 2015

    @OceanWolf
    Member

    Hmm, by the description above, do I understand that we want to separate out the screen stuff from the axes stuff because we shouldn't assume them as identical...?

    I would imagine we should make this generic for all coordinate systems, not just 3d, what do we do with polar axes coordinates, and basemap?

  5. added
    Difficulty: Easyhttps://matplotlib.org/devdocs/devel/contribute.html#good-first-issues
    and removed on Jun 1, 2019
  6. modified the milestones: , needs sorting on Oct 6, 2022
  7. jklymak commented on Feb 9, 2023

    @jklymak
    Member

    I'm ging to close this as being very old, and probably not pertinent, or if it is, no one has picked up on it... Feel free to request a re-open...

  8. removed this from the future releases milestone on Feb 9, 2023
  9. scottshambaugh commented on May 16, 2024

    @scottshambaugh
    Contributor

    Related to #784

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

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions