Fix timer ID mismatch in Windows table indeterminate progress bar #3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi @petabyt
A timer ID mismatch was occurring in the Windows table implementation during indeterminate progress bar (progress value -1) animation processing.
Issue Details
SetTimer()andKillTimer()were using different timer IDsSetTimer(): Used(UINT_PTR) tKillTimer(): Used(UINT_PTR) (&t)(incorrect)KillTimer()to fail, resulting in timer resource leaksSee libui-ng/libui-ng#324