-
-
Notifications
You must be signed in to change notification settings - Fork 286
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
Dev Mode: setting to change the post frame callback duration #1764
Comments
@g123k Beyond setting a decent minimum duration, are you sure there are no other ways to detect "the right moment"? Like somme callback, some event? Not 100% related: would that be possible to limit the camera to the top half of the screen? I mean, not just processing rather the top part, but using a camera viewer Widget whose height is only half of the screen height? That would be less to process, and anyway the bottom half of the screen is already occupied. |
@monsieurtanuki I don't think we can do it otherwise, unfortunately. For the camera, it won't change anything (or at least, only be marginal), as the stream sent from the camera is exactly the same. |
Maybe all these problems come from the fact that we're virtually displaying 3 pages while hiding 2 of them. Things would perhaps be easier if the scan page was a normal page users go to and go back to. Thinking out loud. |
Actually we have "one real" visible Widget and two hidden (via an Offstage). I will experiment this, as part of #1047 |
Following the PR #1732, a timeout is set to detect if we have to relaunch the camera.
In some cases, it seems that this duration is not enough.
To find a correct value, a setting in the dev mode would be nice
The text was updated successfully, but these errors were encountered: