Entry cursor visibility

[TravisE]

Thanks, Tim.

I actually happened to be using either the medium or small fonts, as it seems that I have no problem reading the fonts themselves (and prefer being able to fit a bit more on screen). The large font might slightly improve things, though it may still take me a moment to find the cursor.

Interestingly, I hadn't thought of the desktop computer issue. The cursor in GTK programs indeed also seems one pixel thick, though I've seen at least one GUI toolkit use a thicker one. However, sometimes, on a large, busy screen, I do indeed have trouble finding it if I don't initially know where it is. A lot of my work is in either a text terminal or a text editor set up for a full character-cell-sized block cursor, though, and the problem seems better there. (Though even in that case, there have been times where even a blinking cursor has been difficult for me to find. So maybe it's just me to some extent. Hmm.)

However, on the computer, there is also often the option of using Shift+arrows to easily see where the cursor is (by extending a selection starting from the cursor). It's possible I unconsciously do this to locate it. On the Prime, I have not been able to find a particularly quick way for starting a selection at the cursor (as on the TI-89).

I don't recall experiencing much of a problem on monochrome calculators (TI-89, HP 50g). I'm guessing this could be due to either a larger cursor (on the TI-89, it is two pixels wide, plus it inverts the pixels underneath; on the 50g it's a full character) and/or the much lower DPI display.

Another problem I noticed on the Prime: When the cursor is inside a selected block of text (with Begin and End on the Copy menu) it's practically invisible because it's rendered black on black. Using a different selection background color or having the cursor pixels inverted might help. (Although many computer toolkits don't seem to invert it, either, it's also uncommon to have a persistent selection as on the Prime and 50g series; also the selection background is usually a color other than the cursor itself.)

On a final note, I've now noticed that the Check option, if the error isn't already on screen, usually seems to place the cursor either on the top or bottom line of the screen depending on scroll direction. I don't know yet if this is 100% consistent, but if it is, remembering that will help a lot simply by significantly reducing the possible regions to search for it.

Hope that helps in some way!