-
Notifications
You must be signed in to change notification settings - Fork 674
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
Verify correct use of Viewport
vs. ContentSize
#3455
Comments
General future commentary based on this: An analyzer would be helpful for these situations, to catch them at design-time, in-context. Not worth it if they're super-temporary, though, usually, of course. Otherwise, whenever there's a simple heuristic to follow for something, writing an analyzer is pretty darn simple. It's essentially the language syntax-aware, code-aware, compilation-aware, and various other context-aware bigger cousin of Edit -> Find with fancy output capabilities and optional fix proposals. The rest1 of the story...
|
I think there may still be cases where built-in Views are using
Viewport.Size
for things where they should be usingContentSize
.This Issue should be closed once an audit is completed any issues are fixed.
Example: The
Pulse
function inProgressBar
It should be possible to write an "All views" unit test that tests for these issues.
The text was updated successfully, but these errors were encountered: