-
-
Notifications
You must be signed in to change notification settings - Fork 360
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
feat(util): add settings api (#191) #211
Conversation
Features
Commit-Lint commandsYou can trigger Commit-Lint actions by commenting on this PR:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some tests need to be added.
7549e83
to
3903c7a
Compare
@lc-soft , I'm tracking down one test failure related to this and wondering if you might have any ideas. The first time we do the frame rate comparison above, it is always using the 120 cap instead of the one supplied in the settings. Subsequent calls to LCUI_ApplySettings do work. It's not related to the frame rate cap value itself, I've tried using 5 the first time and seen it fail. I feel like event fired by using LCU_ResetSettings() while initializing LCUI is getting evaluated instead of the one fired during LCUI_ApplySettings(), but there should be no event handler bound at this time. |
d2b4d80
to
879886f
Compare
46933c7
to
c218614
Compare
In the output of this run (https://travis-ci.org/github/lc-soft/LCUI/jobs/703866145), the code in the event handler isn't getting reached in the failing test so we're either not firing the event, or we haven't set the handler: |
bc463bc
to
8f60c60
Compare
11b2625
to
d77bcef
Compare
I fixed an incorrect call to LCUI_Quit() instead of LCUI_Destroy() in the preceding tests which allows the first frame rate check to pass. However it seems to crash while running the destroy event handler now. This also happens if I disable preceding settings tests. Still investigating. |
e1ad809
to
4fa7eec
Compare
BREAKING CHANGE: LCUIDisplay_EnablePaintFlashing() has been removed. - Add API for retrieving and modifying global settings - Utilize this API in the codebase - Add event for when global settings are changed - Add event handler for updating the frame rate cap - Add event handler to notify paint flashing changes - Add unit tests Fixes lc-soft#192
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you have nothing to add, I will merge it.
Thanks. I have no other changes planned. |
Sorry, I found the
Please add a compatible implementation of |
Restore and re-implement LCUIDisplay_EnablePaintFlashing. Fixes lc-soft#192
Restore and re-implement LCUIDisplay_EnablePaintFlashing. Fixes lc-soft#191
I created a separate PR #212 for this. |
- Add API for retrieving and modifying global settings - Utilize this API in the codebase - Add event for when global settings are changed - Add event handler for updating the frame rate cap - Add event handler to notify paint flashing changes - Add unit tests Fixes #192 Co-authored-by: James Duong <[email protected]> feat: add settings api (#191) (#211) (#212) Restore and re-implement LCUIDisplay_EnablePaintFlashing. Fixes #191
Fixes #191.
Changes proposed in this pull request:
@lc-soft
IssueHunt Summary
Referenced issues
This pull request has been submitted to: