Alright, I’ve got kind of a funny idea here, and I’m wondering if this has been approached before.
So, my little boy just had a birthday party with a handful of friends over, and they (obviously ) immediately all became enamored with my quite massive saber collection. I started passing a few out for them to mess with, and before you know it: one kid accidentally changed fonts, one kid turned on the backing track, one kid accidentally entered color change mode, another has edit mode going off, etc. .
I eventually just had them turn in the proffies, and I handed out Disney legacy and force fx hilts . Honestly, it worked out nicely with twist and lock blades, batteries charged, only one button/function, etc.
This got me wondering about maybe enabling a “kid mode” or something on the proffies. Like guided access on your phone? So maybe on/off and blaster deflection (or something) are the only buttons that work. I’m thinking you could push a combo like two short followed be three long presses, or something, to enter/exit the mode, like a passcode.
Seems like this is something that has probably been done before. Any thoughts? How challenging would that be?
It would be great if defines were selected with manual blade array as well as presets. That would give you various user modes. So you could have Master with all of the functions, knight that takes out editing, and padawan that keeps on/off and blast.
The biggest combo we have available (at the moment) is 4 button presses:
4 short clicks
or
3 short plus one long
But you could do 4 clicks (4 short or 3 short+1 long) on Power while holding AUX. Or 4 clicks on AUX while holding Power.
Enabling 5 clicks wouldn’t be too hard but it would still only be:
5 short clicks
or
4 short plus one long
That can be achieved by modifying common/event.h
To have more than 1 long, you would need to add code for “SAVED_CLICK_LONG” so ProffieOS “remembers” that a long click has already happened and ProffieOS can count the amount of short plus long clicks that has already happened. I think that would need to be added in common/button_base.h. Unfortunately, I do not understand how that part of the code works or how it needs to be modified to add “SAVED_CLICK_LONG”. (this is the hard part)
Then the prop file would need to be modified, probably something similar to “battle_mode_”. You would need to create a new bool variable, something like bool padawan_mode_ = false (or true if you want it to be on by default) and go over every single event in the Event2 section of the prop and decide with an if padawan_mode_ or if (!padawan_mode_) wether or not you give “access” to each button combo or not. (this would not be particularly hard but it would be very long and time consuming)
Finally you would need to add the newly created 2 short clicks + 3 long clicks as a new event in the Event2 to toggle the “padawan mode” ON or OFF. (once everything else is done, this is the easy part)
Sounds like probably a little more work than it’d be worth. I just thought it was an interesting idea worth throwing it out there. Thanks for humoring me !
It’s kind of funny though, because in a lot of ways, what we started out with was pretty close to “kid mode”. The “saber” prop still doesn’t have a lot of complicated buttons or features.
The neat trick would be to have both saber.h & any of the other “more complex” saber prop with the ability to switch back and forth, on the fly, between the two with a button sequence.
Kind of like dual_prop.h but for saber1 to saber2 (except blade detect can’t be the trigger) or my multi_prop.h
Time permitting, I might try to adapt my multi_prop.h to do saber1 to saber2 instead of saber to blaster to detonator to jetpack (one prop to rule them all, and in your config bind them).
If anyone wants to have a go at modifying it, multi_prop.h can be found here:
Out of curiosity, is there an interest for a “dual_saber.h” prop ?
I can “dumb down” my multi_prop.h to allow for 2 saber props to be used. I personally would not be using it but I don’t mind doing the code work if I can count on at least one person willing to do some testing & reporting.
A saber/test-bed with two buttons (or more) will be needed as the switching will need to happen with AUX (or AUX2) because after comparing the official saber props, there is no POWER button combo still available for the taking (on a one button setup).
) immediately all became enamored with my quite massive saber collection. I started passing a few out for them to mess with, and before you know it: one kid accidentally changed fonts, one kid turned on the backing track, one kid accidentally entered color change mode, another has edit mode going off, etc. 
.