All of the tools are there in the screen to implement what you want. There is no LED in the wxWidgets framework. So that "element" was custom coded. This is different than buttons, as the wxWidgets framework implements stock Windows buttons. In other words, a button on the Mach screen will look like a button in any other standard Windows application (that hasn't been dressed up). The Terminal program Putty is a good example. That being said, we allow the user to pretty much dress up any button they wish with the bitmap button and custom bitmaps. My point is just because you don't see a screen element that does exactly what you want at first glance, don't assume that it can't be done.
Back to the LEDs. LED is an acronym for light emitting diode, as seen on many physical machine control panels. And that is what I tried to make them look like. Generally, people like the round LEDs because a round LED in Mach3 was not possible. But sometimes a round LED is not what is needed or wanted, so there are properties in the control to set the shape. You have a choice of round or square (rectangular, really). But if you just plop a LED down on the screen in the screen editor, it is round by default and if no cursory glance at the properties is given, you may not realize that they can be made to be rectangular. But either way, the LED screen element is rather graphical in nature under the hood. Not textual. It would not be easy to program it to ALSO be textual (although I'm thinking about it).
BTW, there is a sticky topic in this forum titled "Mach 4 Feature Request". I look at each and every post. I don't respond in there very often, as it would consume my time that could otherwise be used to actually make the things happen. If I think the idea has merit and I think that the majority of our user base could benefit from it, I'll implement it.
But seeing as how text based LEDs do not exist at the present time, now it is time to start thinking outside of the box. If I were to want a text based "Boolean" value (we won't call it an LED now), I'd start with a Static Text control and tie it to a register. You can create a register in the regfile plugin's configuration. Registers can contain text values, so basically whatever is put in that register will be what the Static Text control displays on the screen. You can then tie the register's value to any signal in the signal script (or use the siglib) with a small bit of LUA code. One could even change the color of what is displayed. Yeah, it isn't as easy as plopping down a control and instantly having it appeal to your taste or sense of style, but it isn't THAT hard either.
I'm not a young guy either. And plenty on this forum know my thoughts on LUA. Just to summarize them, I can't stand LUA. We chose LUA not for it's looks, but because of it's speed and flexibility. But I won't let that stand in my way of getting what I want.
Here is an example of a screen set that looks NOTHING like our stock screens.
https://www.machsupport.com/forum/index.php?topic=35438.0Steve