Walter wrote: ↑Fri Jun 24, 2022 7:21 am
You can reassign everything except [f], [g], [alpha], and [F1] through [F6].
- If and when you assign in normal (numeric) mode, you can move unshifted, f-shifted, or g-shifted labels.
- If and when you assign in AIM, you can move the respective alpha labels.
- Turning to user mode, the reassigned functionalities will become valid.
- Turning to TAM in user mode, the reassigned alpha labels will become valid.
Ah. It was the TAM [alpha] that I wanted to reassign, to keep it associated with the same key that I reassigned [alpha] and [alpha.fn] to.
On another matter:
I attempted to learn the basics of the French language across four years in high school and failed, so I have great admiration for polyglots. But polyglots--perhaps out of familiarity with different grammars or with the varying connotations of common word roots--can at times make word choices that we poor monoglots sometimes trip over. I found that happening to me in two places in this paragraph on p. 74 of the Owner's Manual:
How can you use and combine data of various types in calculations? The matrix below lists in its 1st column ten data types your WP 43S supports; and it shows what will happen when you combine various objects: an object of the DT as indicated in one of the lean columns at right (y) plus or minus an object of the DT in column 1 (x) will return an object of the DT at the intersection (thus, wherever a DT number is printed at the inter-section, the corresponding combination is legal for addition or subtraction 65 ). Grey fields point to restrictions, rose to asymmetries.
--in this context, I took "lean" to indicate anything other than narrowness: I was inspecting the table for columns in Italics, or for columns with non-perpendicular lines, or for cells that had skimpy amounts of information. (I suggest "skinny" or "narrow" for "lean".)
--"rose" caused me a different problem: (a) "grey" is a common color-describing word; "rose", less so. (b) Your elliptical sentence construct is pleasing--I appreciate writing with structural variety. But unfortunately, the more-modern less-punctuated syntax (which works well in most situations), when coupled with the rarer homonym of "rose", left me misreading the sentence. I was wondering how grey fields pointed to restrictions that rose to further asymmetries--looking back on it, I find my confusion amusing. Better wording might be . . .
(1) Grey fields point to restrictions; rose, to asymmetries.
(2) Grey fields point to restrictions, pink to asymmetries.
(3) Grey fields indicate prohibited operations; rose-colored fields, asymmetries.
I know both points are niggling, but I find it fun to see the various ways I get tripped up. And it's a Friday.
-----------
Or, rewriting the entire paragraph:
The WP43S supports ten different data types. But what happens when differing data types are used together in a calculation? The table below answers that question for addition and subtraction. Knowing the data type for the value currently in the x-register, find it in the leftmost column of the table. Do the same for the data in the y-register, using the topmost row of the table. Trace these two entries across and down respectively until you find the cell where they meet. If a number is given in that cell, that is the resulting data type. (If the cell has a grey field, then the addition/subtraction operation is prohibited; if the cell has a pink field, then the result is asymmetric--i.e., if the x- and y-register data types are reversed, a different data type results.)