No, "pi" wouldn't. It wouldn't parse as a token. You can do alphanumeric entry, but it has to pass tokenization. If LV cannot parse your input string into something meaningful, the input is rejected. "pi" is not currently a token.
> It's definitely possible to type "pi" in a numeric. Reading it with
> numeric.text also works. I've tested it before the previous post.
I just tested 2018 back to 2015: drop a numeric control, type "pi", hit enter. The text in the numeric it immediately reverted to the previous value (zero). I tried typing other valid values in, committing those, then typed "pi", hit enter. Again, reverted to the previous value. I could not find any way to enter "pi" as the value for a numeric.
Well, isn't that where the idea comes in? I know "pi" isn't excepted as value... When "pi" is entered, and the value is committed, before (or during) tokenizing it should be replaced with a pi constant. That's the idea, not how it is right now.
On Linux, it's the root folder ("/") of the file system. On Windows, listing the contents of an empty path will return all the driver letters. So, it might be tricky to do this. Maybe it would magically show up as a forwardslash ("/") if empty -- but, that might be confusing (although informative, for what it's worth).
Part of the problem is that a string diagram constant that is empty is actually wider than a string diagram constant containing a single space (at least using a proportional font, I assume). Another solution would be if an empty string diagram constant would be narrower than any constant containing text. For example, the interior could be only 2-3 pixels wide, just enough to click and insert text if needed.
