0 Members and 3 Guests are viewing this topic.
As best as I can yes. Its going to be confusing to write documentation through if I have to make extra columns or I would just have to clarify which token naming set the doc is using. The thing to keep in mind with this option though is that many people are going to be using either the new names or the old ones so as long as you're okay with knowing that you may receive the help in either of the 2 spellings and know how to convert them.Source code written with one token spelling set is obviously readable with the other don't forget so that part makes no difference.
Might be an idea, but make Alpha+Vars a menu instead of a trigger?You know, like Omnicalc. If you press prgm twice you get a special omnicalc menu with all their tokens.Maybe you should make such a menu under Alpha+Vars, would defenitely increase the ease on finding those tokens
Leaving things as they were would also prevent potential issues with future TI-OSes and third-party APPS releases for short periods of time before Axe is updated.
That's a very good idea, especially for the obscure ones you normally have to look through the catalog for. But this is a feature that could be implemented regardless of if I decide to keep the new token names or not. The only difference would be what is displayed on the menu. Its a possibility I can have the text on the menu be different than the token itself with the new spellings and when you select it it puts the regular BASIC token there. But that wouldn't help readability of the source which is the main purpose for the proposed name changes.EDIT: And yes. This entire thread is about the spelling of the tokens and nothing else. The physical bytes of the tokens are identical always and always compatible across the board. How the spelling affects documentation is one of the main concerns.
i'M NOT SURE WHAT A SWORD SKILL IS BUT HERE'S THE SWORD ANIMATION FROM THE TWO SPRITES ON PG 13