| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
| actives=[l.get_visible() for l in lines_by_label.values()], | ||
| label_props=[{'color': 'k'}, {'color': 'r'}, {'color': 'g'}], | ||
| frame_props={'edgecolor': ['k', 'r', 'g']}, | ||
| check_props={'facecolor': ['k', 'r', 'g']}, |
There was a problem hiding this comment.
I looked at the rendered doc and noticed that the Xs are still black, I think maybe edgecolor is what was intended here?
| check_props={'facecolor': ['k', 'r', 'g']}, | |
| check_props={'edgecolor': ['k', 'r', 'g']}, |
Sorry, something went wrong.
There was a problem hiding this comment.
No, the bug is in widgets.py; I just need to work out what exactly the semantics for color/facecolor/edgecolor will be.
Sorry, something went wrong.
|
@QuLogic I think you had indicated in alternate communication channels that this was ready for review, but it is still marked as draft. |
Sorry, something went wrong.
|
@ksunden Ah, sorry, I thought I pushed the button here; maybe an outdated browser page or something. |
Sorry, something went wrong.
|
Probably should have a whatsnew entry to highlight the api changes |
Sorry, something went wrong.
|
Added the what's new and handling of activecolor as mentioned in call yesterday. |
Sorry, something went wrong.
There was a problem hiding this comment.
Lots of suggestions and minor comments. The major change request I have is to double check this is working - I think it's worth adding a test that doesn't compare new API to new API, and looking at the what's new entry some of the styling for check buttons doesn't seem to be applied.
Sorry, something went wrong.
|
I modified a test image to include old and new versions, and I think should've handling your other comments in a previous push. |
Sorry, something went wrong.
…838-on-v3.7.x Backport PR #24838 on branch v3.7.x (Add styling support to Check and Radio buttons )
| Back | FazBrowse Home | New Git URL |
PR Summary
This implements arguments to override the styling of CheckButtons and RadioButtons, in a manner similar to the existing ToolHandles or Selectors. This depends on #23457 to avoid the conflicts on the arguments. I updated the examples to show what this looks like, but not the tests or documentation yet. I have two questions:
Fixes #24583
PR Checklist
Documentation and Tests
Release Notes