Skip to content

Feature request: add edit_parameters to toolbar for all GUI backends #13195

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

Closed
BYT3M3 opened this issue Jan 16, 2019 · 6 comments · May be fixed by #17105
Closed

Feature request: add edit_parameters to toolbar for all GUI backends #13195

BYT3M3 opened this issue Jan 16, 2019 · 6 comments · May be fixed by #17105
Labels
Difficulty: Medium https://matplotlib.org/devdocs/devel/contribute.html#good-first-issues GUI: gtk New feature status: closed as inactive Issues closed by the "Stale" Github Action. Please comment on any you think should still be open. status: inactive Marked by the “Stale” Github Action

Comments

@BYT3M3
Copy link

BYT3M3 commented Jan 16, 2019

Dear maintainer

So I have developed a PyQt application with matplotlib in the past and now I wanted to try it with Gtk because prettier (in my humble opinion) and probably easier on the dependencies.

However, I very much miss the "edit parameters" button on the Gtk toolbar, which is present on the Qt toolbar. I would very much like it if this button is also implemented for the Gtk backend or preferably straight into the matplotlib.backend_bases.NavigationToolbar2 class, because I also miss the "edit parameter" button when using pyplot for quickly hacking a graph together.

Thank you for matplotlib, I love it!

@QuLogic QuLogic added New feature GUI: gtk Difficulty: Medium https://matplotlib.org/devdocs/devel/contribute.html#good-first-issues labels Jan 16, 2019
@tacaswell
Copy link
Member

I agree it would be great if the gtk backends also had the 'edit parameters' button! I do not think it can go into the base class though as to make that GUI nice, it should be implemented using the native widgets of the given toolkit.

One of the limiting factors in this case in expertise in gtk among the current core-developers, if you are currently work on a Gtk application @BYT3M3 I am going to assume you do have expertise in gtk, would you be interested in developing (at least the start) of that window?

@BYT3M3
Copy link
Author

BYT3M3 commented Jan 18, 2019

@tacaswell : I don't have any gtk experience ­— let alone expertise — whatsoever. I just wanted my UI to look a little fancier and to possibly have less issues with packaging the final program, because PyQt is a PITA to package.

Anyway, I might find some time to hack together a start for the GUI, I could certainly throw a design together in glade and provide some interface. It's writing the actual methods that change everything that may be a little out of my comfort zone. I can't give any guarantees on when I'll do this, but it's good to know that effort I put in could lead to completing the feature.

@tacaswell
Copy link
Member

It's writing the actual methods that change everything that may be a little out of my comfort zone.

Luckily that is what people around here have expertise in! If you have any questions about how to update artist properties please ask!

That is the function in the Qt case that actually does the Artist update, that would probably be a good place to start (also to get an idea of what 'feature parity' would look like).

@github-actions
Copy link

This issue has been marked "inactive" because it has been 365 days since the last comment. If this issue is still present in recent Matplotlib releases, or the feature request is still wanted, please leave a comment and this label will be removed. If there are no updates in another 30 days, this issue will be automatically closed, but you are free to re-open or create a new issue if needed. We value issue reports, and this procedure is meant to help us resurface and prioritize issues that have not been addressed yet, not make them disappear. Thanks for your help!

@github-actions github-actions bot added the status: inactive Marked by the “Stale” Github Action label May 29, 2023
@BYT3M3
Copy link
Author

BYT3M3 commented May 29, 2023

I'm still interested in having this feature. Unfortunately, I have not found the time to implement it myself.

@oscargus oscargus removed the status: inactive Marked by the “Stale” Github Action label May 29, 2023
Copy link

This issue has been marked "inactive" because it has been 365 days since the last comment. If this issue is still present in recent Matplotlib releases, or the feature request is still wanted, please leave a comment and this label will be removed. If there are no updates in another 30 days, this issue will be automatically closed, but you are free to re-open or create a new issue if needed. We value issue reports, and this procedure is meant to help us resurface and prioritize issues that have not been addressed yet, not make them disappear. Thanks for your help!

@github-actions github-actions bot added the status: inactive Marked by the “Stale” Github Action label Jan 10, 2025
@github-actions github-actions bot added the status: closed as inactive Issues closed by the "Stale" Github Action. Please comment on any you think should still be open. label Feb 11, 2025
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Difficulty: Medium https://matplotlib.org/devdocs/devel/contribute.html#good-first-issues GUI: gtk New feature status: closed as inactive Issues closed by the "Stale" Github Action. Please comment on any you think should still be open. status: inactive Marked by the “Stale” Github Action
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants