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
I just saw your library, actually liked it and thought to give it a try.
After attaching a flip detection listener in my activity, I see that the events are continuously getting fired. Like,
private FlipDetector.FlipListener mFlipListener = new FlipDetector.FlipListener() {
@Override
public void onFaceUp() {
// Device Facing up
Timber.d("DEVICE UP");
}
@Override
public void onFaceDown() {
// Device Facing down
Timber.d("DEVICE DOWN");
}
};
in this code, I am getting continuous logs for "DEVICE UP" when the device is facing up and continuous logs for "FACE DOWN" when the device is facing down.
But my requirement is something different. If the device is facing up, it should just give one single onFaceUp() callback, and if the device is facing down it should just give one single onFaceDown() callback.
Is it possible with your library? If not, I will have to implement it myself. Just wanted to check if your library can do that or if you are willing to add it as an enhancement.
The text was updated successfully, but these errors were encountered:
I just saw your library, actually liked it and thought to give it a try.
After attaching a flip detection listener in my activity, I see that the events are continuously getting fired. Like,
in this code, I am getting continuous logs for "DEVICE UP" when the device is facing up and continuous logs for "FACE DOWN" when the device is facing down.
But my requirement is something different. If the device is facing up, it should just give one single onFaceUp() callback, and if the device is facing down it should just give one single onFaceDown() callback.
Is it possible with your library? If not, I will have to implement it myself. Just wanted to check if your library can do that or if you are willing to add it as an enhancement.
The text was updated successfully, but these errors were encountered: