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.

Sign up for GitHub

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

Jump to bottom

Enforcing that haptics are generate on the main thread #7

Open
bengilroy opened this issue Feb 19, 2019 · 0 comments
Open

Enforcing that haptics are generate on the main thread #7

bengilroy opened this issue Feb 19, 2019 · 0 comments

Comments

@bengilroy
Copy link

Generating haptics on a background thread can cause crashes (problem briefly discussed in #6).

This issue is to discuss the following:

  • Should it be responsibility of HapticGenerator to ensure that haptics are called on the main thread?
  • If so, what are the potential solutions? Should it flag when it's being run on a non-main thread? Should it just enforce that it's run on a main thread by moving to the main thread if necessary (or perhaps non-silently using an assertionFailure)?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bengilroy