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

Avoid internal packages when starting and stopping infinite progress bar #4848

Conversation

Jacalz
Copy link
Member

@Jacalz Jacalz commented May 18, 2024

Description:

This refactors the code to use a better mechanism for triggering start and stop in the renderer. The code now used Refresh() to indicate a state change to the renderer; this is a lot more consistent with other widgets.

Checklist:

  • Tests included.
  • Lint and formatter run with no errors.
  • Tests all pass.

This refactors the code to use a better mechanism for triggering start and stop in the renderer. The code now used Refresh() to indicate a state change to the renderer; this is a lot more consistent with other widgets.
@coveralls
Copy link

coveralls commented May 18, 2024

Coverage Status

coverage: 65.058% (-0.04%) from 65.095%
when pulling 6ec160d on Jacalz:better-communication-with-progressbarinf-renderer
into 4fa888a on fyne-io:develop.

@Jacalz
Copy link
Member Author

Jacalz commented May 20, 2024

Requesting a review from you Andrew, because this change can also be applied to the Activity widget later on if this change looks like a good one.

Copy link
Member

@andydotxyz andydotxyz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice, this is how it should have been all along :)

@Jacalz Jacalz merged commit bdb1061 into fyne-io:develop May 21, 2024
12 checks passed
@Jacalz Jacalz deleted the better-communication-with-progressbarinf-renderer branch May 21, 2024 15:26
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.

None yet

4 participants