Ok, but that doesn’t answer the question, which is: Should we make it pretty?
Or should we focus on utility?
My point is that displays are basically eye candy, so having a menu system that looks bad would be self-defeating.
3 Likes
I there an in-between?
Until such time I have some experience with cool color display and layers stuff, I can only speak to128x32 monochrome OLEDs. For those, following suit of the existing operation of bmp use would make sense to me.
I just think if you enter a settings menu, and go forward to blade length edit, seeing those “title screens” would seem like a natural extension of what it already does with boot, font, idle etc…
1 Like
i don’t hear that well, and process audible information poorly. I process written language much better than spoken. i would very much like to be able to write messages to the OLED display.
1 Like
I agree, BUT for users that did spring for the “eye candy” if we’re able to support (if they want) then I don’t see harm. For my prop I’d make it an optional define as I assume you’d be sacrificing memory for said “eye candy”, so the user has to make that choice.
My thought is to pair it with the Say functions in Sound Library when we announce menus, as this would just provide a visual prompt. Ideally, if we could append the Say functions in Sound Library with an image to display that might be the way to go, as then we wouldn’t need to go into the various individual menus and add new functions, and since most of the Say functions are “announcing” the active menu, they line up with each “step” already. It would also allow new menus to take advantage if they wanted as the sound library already acts as a “prompt” roadmap.
As to the level of detail and/or utility, I’m of the mind that we take a phased approach. If we can get the menu names/modes added simply enough, then that’s the first step. If displaying things like blade length, volume, etc. is more challenging or requires more thought and time, we do that as a future update/phase after initial feedback from the first phase.
Pardon my ignorance, but I was wondering—what if I wanted to make a saber without sounds? For example, by setting all the configuration options to make the sounds silent. However, instead of sounds, I would love to see the commands displayed on the OLED. Would that be possible, or is it something that can already be done?
You mean, Ignite Muted? There’s already a control, that’s been available since the original OS.
Or you can set BOOT_VOLUME to 0 and use Volume Menu to increase when you want to use sounds.
or unsolder your speaker 
"No, I mean the voice feedback when navigating the settings menu, like when it says 'Blade length, Clash threshold, Exit, Save.
pardon my English
You “could” replace all of sounds in /common with silence, but good luck navigating or using the menus.
Even if we add OLED support, all of the menus use hilt rotation, so you would need to turn yourself with the hilt to be able read the screen at all times, which seems highly impractical. The screen would be an “eye candy” feature, not a viable replacement for the audio IMHO.
1 Like
This is a bit beyond the scope of this thread, I’d start a separate thread for this or submit a PR.
Fair enough. Hoping it makes it to a future version so I don’t have to patch it later… based on my research there are others who are looking for a solution and lots that has been tried. My method is a super clean way to do it.