Long button names like ¡°write to the decoder those variable values that are showing here as changes on this screen now, but not those that are showing as changed when you select a different one of the tabs at the top¡± can be helpful for beginners, but they¡¯re a pain once people have read them once or twice: You have to look hard at long sentences to figure out how it differs from some other one, like "write to the decoder all variable values that are showing here on this screen now, but not those that are show when you select a different one of the tabs at the top"
Short messages like ¡°Do!¡± or an emoji are an over-reaction to that, clearly, but there is some value in having short button names.
Luckily for beginners, we¡¯ve got pretty extensive help pages that people have been writing & indexing over time. So, for example, if one went to and put ¡°write sheets¡± in the search block, you¡¯d find:
which explains exactly what¡¯s going on with those buttons. (Lots of other search strings get there too)
If people want to propose clearer _and_ short terminology, that¡¯s great. Particularly if they put a bit of time into understand what the buttons do first.
Bob
Could I just say that as a relative newcomer I still find the term "sheet" confusing. You obviously know what you mean but at best the word seems superfluous and at worst confusing. If you mean "read decoder", why not say so? And for "write changes", why not something like "write changes to file". If I recall correctly "sheet" is mentioned four times with what seem to be four different meanings.
Not that I don't appreciate what you do for us, just saying that from this user's perspective the terminology is not helpful.
--
Bob Jacobsen
jacobsen@... +1-510-708-5988 AIM, Skype JacobsenRG
Bob Jacobsen