Skip to content

add scroll-to zoom to main codebase #4540

Closed

Description

@tacaswell

I have an example of how to install a scroll event call back to zoom, this should be moved over to be in core.

see https://gist.github.com/tacaswell/3144287 + comments on how to improve it.

Activity

  1. changed the title [-]add scroll[/-] [+]add scroll-to zoom to main codebase[/+] on Jun 19, 2015
  2. added this to the milestone on Jun 19, 2015
  3. tacaswell commented on Jun 19, 2015

    @tacaswell
    MemberAuthor
  4. OceanWolf commented on Jun 19, 2015

    @OceanWolf
    Member

    Which part(s) do you want to go in to core? As far as I see it mainly looks like this should go in with MEP 22...

  5. tacaswell commented on Jun 19, 2015

    @tacaswell
    MemberAuthor

    Enough parts so that every new axes is scroll-zoomable.

    Getting mep22 into more backends should be a priority.

  6. OceanWolf commented on Jun 19, 2015

    @OceanWolf
    Member

    I agree, I think MEP27 looks done on GTK3 (other stuff can get added later), waiting for @fariza to confirm, before sending a call out to all developers but I haven't heard from him in a week...

    Once the MEP27 main branch gets in we can make PRs for the other backends.

  7. tacaswell commented on Jun 19, 2015

    @tacaswell
    MemberAuthor

    I have lost track of which MEP is which, I think the toolbar work needs to be moved to the other backends ASAP to try and make the next point release and the gcf refactor is not going to make the next point release.

  8. OceanWolf commented on Jun 19, 2015

    @OceanWolf
    Member

    MEP22 = Toolbar, MEP27 = Window (Gcf).

    In terms of other backends, MEP27 by far the farthest ahead (see the checklist at the top of the PR #4143) the backends "converted" just need a slight tweaking to update them to a slightly newer MEP27 API. Also I feel MEP27 will make MEP22 a lot easier to implement, on the other hand doing just MEP22 now means we have to put Gcf into the new backend_tools which will make it more complicated to remove later on and require more dirty hacking...

  9. OceanWolf commented on Jun 19, 2015

    @OceanWolf
    Member

    @tacaswell bottom line, we can make the release date of end of July for MEP22+MEP27, but with just MEP22 that becomes more difficult, especially when you consider backends such as WebAgg (which MEP27 has already solved), but also for the SubplotTool class which with just MEP22 we will have create a subclass per backend, but with with MEP27 we have just the one class. We just need to get MEP27 off the launchpad (reviewed), and then clear sailing from then on.

  10. fariza commented on Jun 21, 2015

    @fariza
    Member
  11. reopened this on Jun 21, 2015
  12. fariza commented on Jun 21, 2015

    @fariza
    Member

    @tacaswell I reopened because I didn't know if you wanted this outside MEP22 (NavigationToolbar2)

  13. modified the milestones: , on Jul 11, 2015
  14. fariza commented on Aug 7, 2015

    @fariza
    Member

    Closing it because it's solved by MEP22

  15. QuLogic commented on Aug 11, 2026

    @QuLogic
    Member

    I'd say this is more directly resolved by #30405.

  16. modified the milestones: v2.1, v3.11.0 on Aug 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions