Ahhh yes, the display! People seem to have a love hate relationship with the display.
first off, no offence taken, i do get this question quite a bit, asking when it is going to step up to be on par with other systems like the MX2 and such with a larger display.
So when I first started on the controller, there was no display at all. Just a couple knobs and some buttons. it was fairly basic, and it did not take long for me to outgrow it. I had gone out of my way to develop a system that was extremely fast to use and required no menus. I am NOT a big fan of menus. I built out my own MX2 a long time ago and hated the interface. tap tap tap. tap tap taptaptap tap tap, tap, tap tap, tap tap tap tap tap. tappity tap. I couldnt stand how many buttons i had to press to get a routine going, i also was not a fan of the DC motor, i dont like playing the guessing game when it comes to motion, and i despise doing math (hmm lets see this setting gets me 1.23 inches per minute with 50 inches of travel and 5 second intervals how many shots will i have?.... hell no! I would rather tell it what i want. So i had quickly been turned off by menu systems.
The first visual feedback i added was a pair of LED's, the number of blinks represented the number of shots X100 it would take, etc. It worked well and only required me to add in 2 LED's and 2 resistors, but it really surprised me exactly how much more i could do with just a couple LED's. Th capability easily increase by 10x.
I finally gave in and started looking for a display, i was not interested in the 16x2 LCD display that everyone else uses. I wanted to be able to shoot in the col and those displays freeze. Finally i ran across this 4 DIgit LED display. It works fine at -40 degrees, it uses almost no power, and requires very very little code overhead.
It worked great, and i had a lot of people challenging me on the decision to use this display, but i could actually get a LOT out of it. Forward a year later, the code has really developed and i did find myself in a bit of a squeeze trying to figure out how to display certain things that it cannot display, such as M. hahahaha
I feel i got it worked out pretty well, and the display is adequate for the job, it is a tough little display, it has a unique look to it which helps set our system apart, it also forced me to stay away from menu systems (i hate menus) and hold onto a very fast and easy to use control system.
However, i realize it is not everyones cup of tea. I have looked into other displays from time to time, but in the end they all either use too many pins, or some libraries which take up space in the code (and right now the code size is pretty much maxed out)
So if somebody were to introduce one of those OLED displays (which i think look awesome by the way) you will run into one big problem. Code space. To overcome this you could simply use an Arduino Mega instead of the UNO, however that will not fit in our current enclosures, so you would need a custom box. After that, you would need to upload the library and update the code to display things the way you ant to display it.
If you want to take that challenge, i would be happy to lend any assistance.
In fact, i think i will go order a couple of those displays right now.