You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently move references are different between the app Move List interface, and the Gear Gestures. The Move List uses the long, descriptive names (e.g. "Fast Wag"); however, the Gear Gestures use the short terminal command names (e.g. "TAIILFA"). For consistency/clarity, commands should be named consistently throughout the app UI.
The text was updated successfully, but these errors were encountered:
Actually Ive just had a play - it uses the full names to select the moves in gestures, it just "reveals" the underlying codename once selected (sitting in the grey box) - it would be nice to show the human name, but perhaps some might like to know the underlying command?
Actually Ive just had a play - it uses the full names to select the moves in gestures, it just "reveals" the underlying codename once selected (sitting in the grey box) - it would be nice to show the human name, but perhaps some might like to know the underlying command?
That would be in the Wiki in the document covering the tail protocol which does match the terminal command names to the long descriptive names (unless I goofed somewhere). I don't know that end users would need to know that info otherwise (if they weren't using the terminal line). Changing the labels from the time they're selected to display is probably a bad UI pattern tho.
Currently move references are different between the app Move List interface, and the Gear Gestures. The Move List uses the long, descriptive names (e.g. "Fast Wag"); however, the Gear Gestures use the short terminal command names (e.g. "TAIILFA"). For consistency/clarity, commands should be named consistently throughout the app UI.
The text was updated successfully, but these errors were encountered: