You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current implementation of vibration couples vibration patterns with the animation frame (stepSimulation). See the step function of vibrationManater.
This allows us to know exactly when the phone is vibrating, when the device is in uptime/downtime during a vibration pattern. However, we can't have vibration patterns that are faster than the framerate.
We suspect that we could support faster vibration patterns if we move the navigator.vibrate calls out of step. It is worth it to sacrifice the knowledge of uptime/downtime in a vibration pattern to have this. We may be able to still guess the uptime/downtime in a vibration pattern (at least good enough for the VibrationChart visualization).
The text was updated successfully, but these errors were encountered:
After discussion with @liquatics .
Current implementation of vibration couples vibration patterns with the animation frame (stepSimulation). See the
step
function of vibrationManater.This allows us to know exactly when the phone is vibrating, when the device is in uptime/downtime during a vibration pattern. However, we can't have vibration patterns that are faster than the framerate.
We suspect that we could support faster vibration patterns if we move the
navigator.vibrate
calls out ofstep
. It is worth it to sacrifice the knowledge of uptime/downtime in a vibration pattern to have this. We may be able to still guess the uptime/downtime in a vibration pattern (at least good enough for the VibrationChart visualization).The text was updated successfully, but these errors were encountered: