[REQUEST] Feature suggestion regarding display

[nixxou]

I have some suggestion around display that i try to implement, but probably too big to handle for me (and even if i manage to succed my code will probably be an horrible mess not up to the standard to implement), so i leave it here as feature suggestion.

• Icon status top bar : Instead of writing the full profile name, just leave an icon for the profile on the top right corner, instead of the text, put the toggle icon like solenoid status, control mode, mamehooker status ...

• Pause menu with icons : Instead of text for option, just showing 3 row at a time, use icons, you can show like 15 18x12 icons, navigate with either buttons or directional pad, it will be much quicker and in one glance you can see the active status of the option.

pocmenu.mp4

• Have an options for mamehooker ammo that show actual bullets, kinda like that :
  https://streamable.com/rfr94a
  When the number of bullet go up, you "recalibrate" the bullets size, when it goes from 1 to 0 you show a blinking "Reload !"

[SeongGino]

Regarding top bar:

• 1306-style OLEDs with split pigment options only allows us a sixteen-pixels-tall section of display area to draw in, so displaying only a simple title text (in this case, Profile Name) is all that can fit in that area. Icons for sub info like FFB devices available could be done, but for now we are thinking of having the title text alternate between current profile (now) and another line of sub-information (see [REQUEST] Display: idle operations #25)

Regarding Icons-based Pause:

• Possible, but improbable; remember that the interface as it is now is designed to function with as little as one-button guns like the Virtua Gun or other Konami-style home light guns from that era. Icons-based menus can only realistically function with GunCon 2's or others with an analog joystick (like in Cabela's), as there are several guns which lack any directional inputs at all.

Regarding ammo display:

• This could actually be a nice thing to have. I'll make a separate issue for this.