This is the long press issue in Color Editing. I’m still testing solution. There is no zoom if you use ColorChange mode for Edit Mode styles. I have to prevent users from doing a long press when Color Editing is active because you leave Editing without turning off the dedicated style.
Right now, if you use Color List you need to just click to end, long click or hold in ColorChange mode will cause the style to be locked.
1 Like
Alright, I’ll leave zoom alone until the pull request and fix is in.
So, now I’m moving on. I have added a font on my SD that is not included in my config file. I’m going to go into edit mode, and copy an existing preset, then I’m going to go to the copied preset in edit mode, and changing it to the font that was not on my config file to test how that works. So, its the ultimate test of the maximum benefit of OS6.0 for non Arduino users. A way to add fonts to your saber without the need to reprogram. So, I’m sure I’ll be testing some things that Afrojedi already tested; however, in a new way.
Next I also want to test some of the styles you wrote, which you cannot test. What do I need to do there? Is there a specific bladestyle that will test some/all of those features? If so, which one?
BTW, irregardless of the zoom and long press on power having some minor issues, I think that the new functionality, and the spoken stuff from Brian Conner is incredible. Sometimes, as we find stuff that is wrong, some may lose sight of how incredible it all is.
Fredrik, Brian, and Fernando, etc. have done some incredible work here. This is very awesome stuff, and I’m having a lot of fun with the sabers so far. The blue tooth BLE edits are out of this world, and actually change the game for blue tooth being handy. I know plugging in is also cool, but you can edit your saber on your phone, and that is VERY COOL. I think all this is next level stuff. You all should be very proud of this Technological Terror you’ve constructed!!!
Tom
2 Likes
Success in edit mode. Copied preset, changed font to new font on SD card that was not in my config file. Changed color to match new font. BINGO. Only issue I had was that I guess when you copy preset, my initial presets were “font name; common”. So, when I looked for the track in the new preset, I guess it need to be in my original folder “common/tracks”. Pretty cool. Next, I’m going to repeat in BLE on a different track, via plugging into computer.
Track Player and Edit Tracks look in current font and common folder, if you have a track in the font and you change the font then it wouldn’t see it anymore. Putting Tracks in common/tracks/ will make the track available no matter which font you use.
1 Like
I understand. Next, Im going to change through ble app, then on other saber, ble on cell phone. While I didnt need this, the masses did. Great work.
What about the new styles/functions tgat you cant test because you authored them? What can I do to help there?
Tom
They are almost all already in the Edit Mode test styles, so they are technically tested if you used the test styles during normal operation or you can build your own to test.
ColorSelect
StaticFire
TrCenterWipeX
TrCenterWipeInX
TrSelect
TrSparkX
ClashImpactF
HoldPeakF
IntSelect
LinearSectionF
It would be great if they were tested individually since that would mean that people can understand the documentation enough to use those styles/transitions/functions.
2 Likes
Copied preset via bluetooth ble app. Edited preset in workbench app on phone. Added a font that was on my sd card, but not on my config! That is easy, people will love that.
Im reading docs on the styles that need testing. I still have much to learn about cpp. I guess its time.
Fredrik for testing, I have tested the following:
FETT263 Prop Features:
Edit Mode Menu
Battle Mode 2.0
Preset Menu
FETT263 Menus:
Color List
FETT263 Prop Defines:
FETT263_EDIT_MODE_MENU
FETT263_SAY_COLOR_LIST
FETT263_SAY_COLOR_CC
FETT263_BM_CLASH_DETECT
ProffieboardV3 support, as one of my test sabers is my 3.7 Proffieboard Beta Saber.
There was no specified testing of the new workbench in your app, but I have tested that as well. That application is awesome, and easy. I have only tested it via bluetooth, but I intend on plugging into computer and testing it there as well.
1 Like
Nice! Top post updated.
Hi @profezzorn,
Any updates on the hum issue where changing presets causes the hum to continue despite turning off.
Not yet.
My original thought was that it was something that happend with preon+monophonic fonts+turning the saber off quickly, but since my fix didn’t work I need to dig deeper.
1 Like
do you need me to do any test, I’m here to help.
Maybe you need to label your presets… (Add a string after all the styles.)
Actually, could you try the hum staying on thing again? It seems that I checked in the “fix” on the wrong branch on github, so I don’t think you actually ended up trying what I intended for you to try.
1 Like
I checked in something that might fix this on the master branch, could you try it and see if it works?
oh hey I got these on the TOP section and was wondering how do you show the serial monitor output that this is working?
can this be used with one button? I tried to use it but it doesn’t disable the power button from turning off.
do you need a video of this working? works great I fully charged the battery and it states 100%
During my testing though I ran into both my original issues hum continues after turning OFF And edit mode disables the hum.
I think I’m just going to test everything against the new test file. And see if that causes any issues…my old v5.9 config is what I’m testing with.
As seen here
It’s not mute mode cause in my video blast sounds and so does the preon and pstoff it is just the hum that isn’t working.
@NoSloppy how do I check if the wav files are formatted correctly on audacity?
This only applies to 2 buttons where a click PWR turns saber off. 1 button is a hold so not needed.
1 Like
Thanks for clarifying.
wouldn’t some error handling like the below be useful just so that peeps (like me) don’t use it
#if defined(FETT263_BM_DISABLE_OFF_BUTTON) && NUM_BUTTONS == 1
#error FFETT263_BM_DISABLE_OFF_BUTTONcannot be used with 1 Button Controls
#endif