-
Notifications
You must be signed in to change notification settings - Fork 116
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
Refactors and Comments #80
Conversation
Commented hpatimer.c Commented user_main.c
Cleaned up configurable struct Added #define for SAVE_LOAD_KEY Added custom command information in README.md
Added custom_commands.h Added functions to check for and get Added hpaRunning to hpatimer.c, removed hpa_running from user_main.c Made sure variables have initial values
uuhh... mind looking at those conflicts, @AEFeinstein ? |
Aah just saw your note in #77 ... I will look into this soon. |
@AEFeinstein Can you pull and refresh? Or should this be closed? |
Created AEFeinstein#2, will manually merge in the near future. |
@cnlohr, do you really need image.elf-0x00000.bin checked in? |
Pulled and refreshed |
@AEFeinstein Can you test colorchord desktop edition based on your changes here? |
I've just compared @cnlohr master on a nodemcu with @AEFeinstein PR. Both seem to work with no major problems. Compatible with my recent changes. Tried with and without SORT_NOTES and APPROXNORM. I like @AEFeinstein handling of the configuration parameters. I vote to accept the PR. I will be fixing a few bugs and have additional output options. It will easier if I work with on this new code. I get no warnings compiling @cnlohr, but get these after the PR
Here is the space used:
|
I made some variables volatile because they were used inside and outside interrupts, but I guess the compiler isn't thrilled with that. I should be able to clean up those warnings with some casting later today. |
Fixed the volatility thing. I'm getting this warning too:
The code it's whining about seems perfectly reasonable though. 16 binary digits in a uint16_t looks good to me
|
I had noticed this warning when trying @cnlohr master which has #define LUXETRON at line 55 in ws2812_i2s.c which then defines INVERT. You won't get this if comment out the #define LUXETRON (which I did in my tests, (it should be in ccconfig.h or user.cfg). Maybe (???) the compiler views 0b1000100010001000 as negative, so warns when trying to bitwise invert it. Explicitly writing the inverted values should get rid of the warning.
|
Or maybe appending a u? Just brainstorming while out on the town.
…On Tue, May 28, 2019, 11:13 PM bbkiwi ***@***.***> wrote:
I had noticed this warning when trying @cnlohr <https://github.com/cnlohr>
master which has #define LUXETRON at line 55 in ws2812_i2s.c which then
defines INVERT. You won't get this if comment out the #define LUXETRON
(which I did in my tests, (it should be in ccconfig.h or user.cfg). Maybe
the compiler views 0b1000100010001000 as negative, so warns when bitwise
invert it??? Explictly writing the inversioned values should get rid of the
warning.
static const uint16_t bitpatterns[16] = { 0b0111011101110111, ...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#80?email_source=notifications&email_token=AABYODFPSHKRR3YIPZ5XISLPXXYHFA5CNFSM4GKWIZV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWOBBBQ#issuecomment-496767110>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABYODHOHEIF3VPOSC336ODPXXYHFANCNFSM4GKWIZVQ>
.
|
Appending u didn't work. I forgot to include ccconfig.h in my last PR. So I've done that and made the above fix in a new PR. |
Sounds good. Any other changes anyone wants me to make here?
…On Wed, May 29, 2019, 1:12 AM bbkiwi ***@***.***> wrote:
Appending u didn't work.
This get rid of the warnings
static const uint16_t bitpatterns[16] = { 0b0111011101110111,
0b0111011101110011, 0b0111011100110111, 0b0111011100110011,
0b0111001101110111, 0b0111001101110011, 0b0111001100110111,
0b0111001100110011, 0b0011011101110111, 0b0011011101110011,
0b0011011100110111, 0b0011011100110011, 0b0011001101110111,
0b0011001101110011, 0b0011000100110111, 0b0011001100110011, };
I forgot to include ccconfig.h in my last PR. So I done that and made the
above fix in a new PR.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#80?email_source=notifications&email_token=AABYODGNO3OMPRUCNDRAF3TPXYGENA5CNFSM4GKWIZV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWOF44Q#issuecomment-496787058>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABYODBIPWL7WXXUIOG4T23PXYGENANCNFSM4GKWIZVQ>
.
|
PR #91 will make the changes, or you can fix it in your's and Charles can ignore mine. |
#91 is already up, so lets just use that |
Closing PR based on comments. |
Shouldn't have any functional changes