Skip to content
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

Fix for CenterPlayButton UI bug when using Material 3 #669

Merged
merged 6 commits into from
Sep 9, 2022

Conversation

luis901101
Copy link
Contributor

When using Material 3, the AnimatedOpacity of CenterPlayButton expands to fill the available space, and looks like this:

IMG_0638

This PR fixes it, and in addition:

  • It exposes MaterialDesktopControls to allow devs to explicitly use it.
  • Some lints fixed for better performance

@diegotori
Copy link
Collaborator

Gonna try them out on my end very shortly, but if they look good, then they'll get merged.

@diegotori
Copy link
Collaborator

LGTM, merging very shortly.

@diegotori diegotori merged commit d85efbf into fluttercommunity:master Sep 9, 2022
diegotori added a commit that referenced this pull request Sep 9, 2022
lg8294 added a commit to lg8294/chewie that referenced this pull request Sep 22, 2022
* master:
  Version 1.3.5. Addresses PRs fluttercommunity#658 and fluttercommunity#669.
  Added slight fix to analysis_options.yaml.
  Updated video_player to version 2.4.7.
  Upgraded wakelock to version 0.6.2.
  Library is now using flutter_lints.
  - Removed leading underscores for local identifiers
  - CenterPlayButton padding improved
  - Example AppTheme updated to useMaterial3
  - Several lints fixed for better performance
  - CenterPlayButton UI bug fixed when using Material 3
  - Exposing MaterialDesktopControls
  Add transformationController to Interactive Viewer
  fix: Typos in `ChewieController` docs
  Fixed a typo in the most recent CHANGELOG.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants