|
|
Post by graulscepter on Mar 1, 2022 5:01:19 GMT -5
So a few weeks ago I got my first proffie saber from Sabertrio and I've been playing around with some new fonts and bladestyles. (A bit of background with my coding knowledge, I've taken a few python courses and I've learned some microcontrollers with Arduino before so I can read code but I'm just going need to get used to the formatting as I haven't done c++ before.) Sabertrio doesn't officially support tracks at the moment so I switched over to using fett263s button config file. This worked great but I found that sometimes I would accidentally change a font over to a different blade-style, which was frustrating because I was just trying to change my preset. I heard about the sa22c button config so I decided to try it out and I liked the much more simple controls, but the battery level was spoken, which I really dislike. I've been trying to change the sa22c button config so that it has the other, (I'm not sure if this is default) battery meter where the saber itself ignites to indicate the battery level. It seems both people have designed their button configs a little differently like with fett263 using functions and calling them later on, like "DoBattery()" (I'm not sure what they're called in c++ but I know them as functions). I tried inputting the same battery code into the sa22c config but it didn't seem to work, just wondering if there's an easy way to transfer this battery meter function into this new config? Maybe it would be easier just editing fett263's config so it doesn't have the edit mode, which I might try but I want to see if I can get the battery effect on the other config. Thanks in advanced  |
|
|
|
Post by fett263 on Mar 1, 2022 8:17:54 GMT -5
Sa22c's file isn't updated for OS6, I worked with him to merge some of his functions into mine to support OS6 for his users. You'd have to do a ton of updates to try to move functions from mine into his as there is a lot of code required to enable the various features, it's not just a function or line. If you don't want Edit Mode just don't include the FETT263_EDIT_MODE_MENU define. But I'm guessing you're using 1 button controls and confusing 2 clicks and long click with 3 clicks and long click and activating ChangeFont. This isn't actually Edit Mode. If you want to remove this function just comment out this line with "//" github.com/profezzorn/ProffieOS/blob/master/props/saber_fett263_buttons.h#L4586But it won't fix you doing the wrong button combo, it just won't change your font when you do it wrong. The real fix is do the right button combo for the function you want. The multiple clicks is the reason I personally HATE 1 button sabers. I just added 1 button support for users but I personally feel 1 button sabers are the biggest PITA, they are severely limiting in being able to support all that Proffieboard offers. |
|
|
|
Post by nosloppy on Mar 1, 2022 23:42:49 GMT -5
graulscepter If it's 1 button, you might find saber_BC_buttons to your liking?
|
|
|
|
Post by graulscepter on Mar 2, 2022 2:02:27 GMT -5
Sa22c's file isn't updated for OS6, I worked with him to merge some of his functions into mine to support OS6 for his users. You'd have to do a ton of updates to try to move functions from mine into his as there is a lot of code required to enable the various features, it's not just a function or line. If you don't want Edit Mode just don't include the FETT263_EDIT_MODE_MENU define. But I'm guessing you're using 1 button controls and confusing 2 clicks and long click with 3 clicks and long click and activating ChangeFont. This isn't actually Edit Mode. If you want to remove this function just comment out this line with "//" github.com/profezzorn/ProffieOS/blob/master/props/saber_fett263_buttons.h#L4586But it won't fix you doing the wrong button combo, it just won't change your font when you do it wrong. The real fix is do the right button combo for the function you want. The multiple clicks is the reason I personally HATE 1 button sabers. I just added 1 button support for users but I personally feel 1 button sabers are the biggest PITA, they are severely limiting in being able to support all that Proffieboard offers. It's got two buttons but I just wanted to make sure I couldn't accidentally move any fonts or bladestyles around, I will comment out the two button version of the code line you mentioned above and see how it works. Thanks for responding, you have done so much for the saber community, I really appreciate the effort and time you put in to helping people |
|
|
|
Post by graulscepter on Mar 2, 2022 4:05:19 GMT -5
I thought I'd removed the 'change font' function but I've been finding when I was fiddling with the buttons sometimes the preset I last used duplicates itself (this solves itself once I flash the board, but I would like to not have to), I'm not at all sure what is causing this, could it be to do with the 'copy preset' function? Would removing it be similar to the ChangeFont function?
|
|
|
|
Post by fett263 on Mar 2, 2022 8:10:39 GMT -5
Sa22c's file isn't updated for OS6, I worked with him to merge some of his functions into mine to support OS6 for his users. You'd have to do a ton of updates to try to move functions from mine into his as there is a lot of code required to enable the various features, it's not just a function or line. If you don't want Edit Mode just don't include the FETT263_EDIT_MODE_MENU define. But I'm guessing you're using 1 button controls and confusing 2 clicks and long click with 3 clicks and long click and activating ChangeFont. This isn't actually Edit Mode. If you want to remove this function just comment out this line with "//" github.com/profezzorn/ProffieOS/blob/master/props/saber_fett263_buttons.h#L4586But it won't fix you doing the wrong button combo, it just won't change your font when you do it wrong. The real fix is do the right button combo for the function you want. The multiple clicks is the reason I personally HATE 1 button sabers. I just added 1 button support for users but I personally feel 1 button sabers are the biggest PITA, they are severely limiting in being able to support all that Proffieboard offers. It's got two buttons but I just wanted to make sure I couldn't accidentally move any fonts or bladestyles around, I will comment out the two button version of the code line you mentioned above and see how it works. Thanks for responding, you have done so much for the saber community, I really appreciate the effort and time you put in to helping people  I have to ask, did you do the Set Up and read through the controls for my prop in OS6, I wouldn't recommend "fiddling" with the buttons as there is a lot of new functionality in place. Read through the Set Up and actual controls and familiarize yourself with what each control does, that's the easiest fix. You can't "accidentally" do anything if you use the controls how they are set up (unless) you're missing the Voice Prompts (which are required per the Set Up instructions hence original question) and/or don't use the right controls. You can go through and comment out any of the features you want but to me it just seems easier to familiarize yourself with the controls and do the right control for what you want to actually have happen and don't do the control for what you don't want to have happen. Make sure you read through the entire top section of the prop or this entire page, everything is documented for a reason: www.fett263.com/proffieOS6-fett263-prop-file.htmlSince you have 2 button it seems a lot harder to just "accidentally" change the font so you must be just mashing away on the buttons, which I would never recommend with or without commenting out. But if you still want to remove the ChangeFont functionality you'll have to comment out this line instead, the one I sent earlier is for 1 button. Change Font on 2 button is Hold AUX, Long Click PWR while Off ChangeFont() github.com/profezzorn/ProffieOS/blob/master/props/saber_fett263_buttons.h#L4859Now if you're actually getting a copy of a preset that means you're doing "Copy Preset" instead of "Change Font" so it would be this line you want to comment out, but again probably just easier to do the right control off the bat, because in the future you'll have to remember what you're commenting out if you ever update the OS again. It's a whole lot simpler to use the controls correctly IMHO, especially with 2 button as it's a lot harder to get the button combos wrong if you know what you want to do. 1 button is much harder because of the multiple clicks but 2 button is pretty straightforward on each control really hard to do the wrong thing unless you're not sure what you're actually pressing. Copy Preset on 2 button is Hold PWR, Long Click AUX while Off CopyPreset() github.com/profezzorn/ProffieOS/blob/master/props/saber_fett263_buttons.h#L4719Good luck. |
|
