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

We can ignore warnings if the request for background execution is not waiting #5509

Merged
merged 2 commits into from
Feb 6, 2025

Conversation

andydotxyz
Copy link
Member

@andydotxyz andydotxyz commented Feb 6, 2025

as discussed on #5508 , main (not waiting) from main is OK now.

Checklist:

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

@coveralls
Copy link

coveralls commented Feb 6, 2025

Coverage Status

coverage: 62.562% (-0.02%) from 62.586%
when pulling dd4146f on andydotxyz:fix/threadwarningignore
into 3f7f987 on fyne-io:develop.

Copy link
Member

@Jacalz Jacalz left a comment

Choose a reason for hiding this comment

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

This is a great idea. With fyne.Do and the unbounded channel this makes a lot of sense. Just one minor nitpick inline that makes the stack output a bit cleaner.

internal/driver/mobile/driver.go Outdated Show resolved Hide resolved
Jacalz added a commit to Jacalz/fyne that referenced this pull request Feb 6, 2025
Once fyne-io#5509 is merged, running binding callbacks from main no longer print a warning so we cna avoid checking the thread. The result is much faster performance.

I also fixed a bug where we ere scheduling s.DataChanged() onto main, which then runs a trigger() which schedules other work onto main. That was unnecessary overhead.
@andydotxyz andydotxyz merged commit af19611 into fyne-io:develop Feb 6, 2025
11 checks passed
@andydotxyz andydotxyz deleted the fix/threadwarningignore branch February 6, 2025 18:00
Jacalz added a commit to Jacalz/fyne that referenced this pull request Feb 7, 2025
Once fyne-io#5509 is merged, running binding callbacks from main no longer print a warning so we cna avoid checking the thread. The result is much faster performance.

I also fixed a bug where we ere scheduling s.DataChanged() onto main, which then runs a trigger() which schedules other work onto main. That was unnecessary overhead.
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.

3 participants