Skip to content

Conversation

@geeksville
Copy link
Contributor

(I just updated this old change based on current master and put it in a separate feature branch)

ESP32 targets are still supported (my project targets both)

Backstory here:
#277

    On my app I noticed that each time I called setTargetFPS the transitions
    would become faster and faster, until finally they don't even take one
    frame.  The problem was that the FP math for calculating changeRatio
    would (because of rounding err) keep shrinking the number of ticksPerFrame.

    This change instead computs ticksPerFrame/perTransition based on the
    requested display time, so error can't accumulate from a series of calls.

    (In my app I only bump up target FPS before each transition but then
    I lower it down again afterwards to save CPU)
(Also makes it easier to share code when users of library are targeting
multiple platforms)
@geeksville
Copy link
Contributor Author

easier to view here: https://github.com/ThingPulse/esp8266-oled-ssd1306/pull/291/files. If you would prefer me to squash into one commit I can do that.

@marcelstoer
Copy link
Member

If you would prefer me to squash into one commit I can do that.

No need to, thanks. We usually do a "Squash and merge" when we merge PRs.

Your video and my own very brief visual inspection is all I have to assess this. I don't have the hardware to test, but hey, LGTM.

@marcelstoer marcelstoer merged commit b55edff into ThingPulse:master Jun 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants