-
Notifications
You must be signed in to change notification settings - Fork 229
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
[Bug] Scrolling issue on Aplite #163
Comments
@bellangerq thank you for submitting this issue :) We may ask for more information as we try to reproduce.. @Meiguro This might be related to #161? Have we had any other reports of scrolling being jittery on Aplite? |
Ah, I forgot to apply the fix to dynamic windows as well. |
Stage was using the same content size resizing logic as Card which requires the same fix. Don't update the content size unless necessary since updating the content size cancels the scroll animation on certain firmware versions.
Thanks @cat-haines, that was helpful. This should be the last occurrence, seeing as there are only three types of windows, two of which are scrollable by semi-non-system means. @bellangerq Nice use of dynamic windows! The fix is on master, I'll request a CloudPebble update. |
@bellangerq - Just tested with your project, and this resolves the issue. Please merge master into your project again, and post a comment here saying whether it fixed it for you (once you've got it working we'll close this issue). |
Hey, it's working! The scroll is way better on aplite:) Thank you so much @cat-haines @Meiguro for your help and the quick answers. Have a nice day! |
Still have this bug using CloudPebble... Any plans updating CloudPebble version of Pebble.js with the fix? |
After updating Pebble.js to the lastest version, there is a scrolling bug on Aplite on the local SDK (Basalt and Chalk are working well) as you can see on this GIF: http://g.recordit.co/emhdaYO5Rn.gif.
Here is the link to my project: https://github.com/bellangerq/quebble/tree/scroll.
Thanks for helping :)
The text was updated successfully, but these errors were encountered: