Sorry, I disagree completely.
There is enough information in the code and the proof is my software that uses both features and runs perfectly in Elements.2409. I understand that you redesigned enums after that, but this broke a lot of my code and took away the functionality which is, I believe, not essential just for me, but for the clarity of Oxygene in general.
The only feature that I really need is setting an enum value from a string for any enum type, as explained in Elements 2513 and 2521: Setting enum value from String.
I know I can make a tiny stringlist for each declared enum and search through the list to match the string with the corresponding enum value. But I don’t want to do this because:
(1) This requires a manual declaration of a string list for each and every declared enum type (which I have many),
(2) this clutters the code and
(3) makes it less manageable, as the same information is entered twice in two places,
(4) and is simply a shameful workaround for a high-level language claiming to support enums.
I spent a lot of time trying to find a suitable solution myself, and failed. I also spent a lot of effort to communicate the issue with you and explain why it is important for me and Oxygene in general. I apparently failed, too. However, please don’t chase me away with the “impossible” argument, I am not buying it. I know the solution is possible. It was possible in Elements.2409. If I can make those tiny string lists myself, I see no reason why the compiler cannot make them silently for me behind the scenes. It does have all the information in the code and it is your compiler, FGS.
I give up. Until this is resolved, I am stuck with Elements.2409.