-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Make RangeTool
respect Range.{min,max}_interval
#13561
Conversation
07cfeb0
to
c868b58
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## branch-3.4 #13561 +/- ##
===========================================
Coverage 92.57% 92.58%
===========================================
Files 323 323
Lines 20525 20530 +5
===========================================
+ Hits 19002 19007 +5
Misses 1523 1523 |
c868b58
to
1e763fe
Compare
1e763fe
to
3006e9f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
3006e9f
to
43e7883
Compare
43e7883
to
2a05459
Compare
* Make RangeTool respect Range.{min,max}_interval * Replace custom code with View.on_transitive_change() * Add visual integration tests * Simplify usage of View.on_transitive_change() * Update unit tests
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Makes
RangeTool
respect itsx_range
andy_range
limits. Also adds support for{min,max}_{width,height}
constraints toBoxAnnotation
. These constraints work, but overall the support is cumbersome in edge cases and will require additional work in a future PR, to polish the behavior. This PR also addsView.on_transitive_change
for connectingchange
signals of transitive models in a view. I originally added this in PR #13538, but it's useful here as well and harder to miss in a much smaller PR. This approach is generic enough to later be used in all other context where previously we either had custom code or no signal reconnect/cleanup at all.fixes #13483