What are the best #define or // to idiot-proof OS7?
Going to an event and I want to give a Saber to someone with zero knowledge of ProffieOS.
The OS7 features are great, so I do want to keep it versus 6.
I know there was some significant changes. New DISABLES and additional Defines namely “Edit Setting Menu via define” (what is the define for that?), but with OS7 still not quite prime-time, detailed documentation is a touch fragmented. That is, unless I’m missing a good list.
I only want them to:
-On/Off (duh)
-Change volume
-Change font
For sure:
-NO battle mode
Maybe:
-NO color change, unless that’s not an option and “revert” is very easy
The font should still be kept on the same one when retracted and reignited though. Not even sure if font revert to first is a thing.
OR…not save anything if they screw it up.
OR…the ability for me to revert to default. Kill switch /on/off? Edit mode, click AUX to revert?
Thinking its a line here, but they do need some editing ability
So is it this? #define EDIT_SETTING_MENU
// #define FETT263_EDIT_MODE_MENU
//#define ENABLE_ALL_EDIT_OPTIONS
See below for the current config that I think addresses most of it.
If you mean giving to an end user with no knowledge of how to update or use Proffieboard then I would NOT recommend OS7 seeing as it’s still in Beta and we’re still updating and testing.
I would just go “barebones” OS6 (don’t include my prop) and don’t add any defines, it will be the most basic set up and will not save anything. That would be my recommendation.
You can use the Config helper tool to generate the CONFIG_TOP, just set OS to OS6.x and then deselect my prop, this will be the simplest set up for OS6 (or you can further change things using the tool if you want), then you can also produce the controls at the bottom.
That’s fair. I know it’s still Beta and seems to work fine for my purposes. The uninitiated can have 6. Super bare sounds boring
Do I have any obvious conflicts with my OS7 TOP_CONFIG? Been playing and don’t want to make any stupid define goofs. Kinda mashed it together given interesting things in the beta thread and elsewhere.
What is the correct CONFIG_TOP combo to make “Edit Setting Menu” work? Or is it not coded yet in the release? Seems worth a look.
You can use that tool for OS7 defines as well, just read the options and make your selections based on what you’re after. That’s why I spent the time building it
I would still shy away from giving a saber with a Beta loaded, there are additional changes coming and still more testing needed. The beta is not a finished product, its for testing by experienced users, giving it to someone inexperienced before final release is a mistake IMHO.
Oooh there are significant changes to the builder. I didn’t check/uncheck all the boxes when you updated it for OS7, so I never saw the sub menus. Nicely done and much egg on face
Ive been reading trying to get up to speed on OS7. Its starting to sink in finally! Lots of new features, thank you to all of the folks who have been working hard to get OS7 across the finish line. Truely remarkable to watch Proffice evolve! I can’t hardly keep up.LOL
I don’t know if this might be too bare bones, but I’ve had some experience of handing hilts to people with zero knowledge, and even stuff like the difference between short clicks and long clicks can tie them in a knot, so they end up switching presets when they want to light the blade, or playing music tracks when they want to shut it off.
So I did a modified SA22C prop for 5.9 (though it should work with 6.9) specifically for this situation. The biggest difference is short click, long click or double click on MAIN will all light the blade; blaster block is short click aux, lockup is hold the aux, blade off is hold the main. Colour change is there but takes two simultaneous button press combos, so not easy to do accidentally.
If that helps, let me know and I can send the files over.
and much egg on face
