Skip to content
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

Fix for ESPNow remote causing output glitches #4386

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

DedeHai
Copy link
Collaborator

@DedeHai DedeHai commented Dec 13, 2024

Processing of received button command is no longer done in the interrup-callback, instead the value is saved to a variable and processed in the main loop.
The actual fix is to not access the file system while data is being sent out: even just trying to open a (non-existing) file causes glitches on the C3. Waiting for the bus to finish updating soves this BUT it can cause a frame-delay. A short delay however is the lesser evil and much less noticeable than random color flashes.

Processing of received button command is no longer processed in the callback, instead the value is saved to a variable and processed in the main loop.
The actual fix is to not access the file system while data is being sent out: even just trying to open a non-existing file causes glitches on the C3. Waiting for the bus to finish fixes this BUT it causes a frame-delay which is the lesser evil than random color flashes.
@DedeHai DedeHai mentioned this pull request Dec 13, 2024
1 task
@DedeHai DedeHai changed the base branch from main to 0_15 December 13, 2024 07:15
@DedeHai
Copy link
Collaborator Author

DedeHai commented Dec 13, 2024

note: I did not realize I should base for main so this is still 0_15 based. shold I rebase or merge to 0_15 and then cherry pick?

@softhack007 softhack007 added this to the 0.15.1 candidate milestone Dec 15, 2024
@netmindz
Copy link
Collaborator

I should be able to just change the base of the PR, no need to cherry-pick

@netmindz netmindz changed the base branch from 0_15 to main December 16, 2024 13:16
@DedeHai
Copy link
Collaborator Author

DedeHai commented Dec 16, 2024

I had lots of conflicts initially when using main as a target, that is why I switched from main to 0_15.
@netmindz Should all still pending PRs that have 0_15 as a target also be switched to main? I did merge a PR into 0_15 yesterday... how long is that still a valid process?

@netmindz
Copy link
Collaborator

Yeah if you opened before I merged 0_15 into main you would have seen all sorts of issues.

At the moment they are basically the same, but if you could please use main for anything new.

I'm going through cleaning up anything that is still 0_15 and will make sure all changes to 0_15 have been merged before I finally delete 0_15

@DedeHai
Copy link
Collaborator Author

DedeHai commented Dec 19, 2024

if there are no objections to the updated function names @softhack007 @netmindz this is ready to merge. tested and working.

@softhack007
Copy link
Collaborator

@DedeHai I possibly have time tomorrow to take a look at your changes. In case I can't review until Saturday, please feel free to merge. Tho overall idea looks sound to me.

@DedeHai
Copy link
Collaborator Author

DedeHai commented Dec 20, 2024

this is not urgent, no worries.
please also consider the alternative implementation of this by @blazoncek blazoncek@43a9663

the outcome is the same, code structure is different. as mentioned in that commit, I'd rather keep the code for the remote contained in remote.cpp as much as possible for clarity and maintainability but maybe my approach has flaws I have not considered.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants