Bugzilla – Bug 11431
Problems with entering encryption with the remote.
Last modified: 2009-09-08 09:31:31 UTC
When trying to enter encryption key with the Fab4 remote there a few issues. 1. You cannot tell what letter/number you are choosing. 2. If you try to use the logical 'cell phone text messaging' way with the key pad you get very strange behaviors.
Which firmware version are you testing?
Sorry r4864
Sorry i did a reset to get back to setup ...then when I reconnected it upgraded to r4864 and same problem with that one..is there a certain firmware that I should test? r4875?
Same result with r4875
Remote only operation needs to work for MP. I think that the only issue here is that the selection color went from green (ok) to almost black (bad). probably just needs to be a lighter grey until we have the full remote skin working.
There are 2 issues, as I see it: 1. The highlight color is black, meaning you can't see the char. 2. The order that characters are selected in is using the Jive mechanic. That is, when I press UP it selects '9'. When I press UP the second time for the second character it selects '8'. This makes sense if you have a wheel for input, but makes no sense for Up/Down arrows. Pressing UP should provide consistent input.
Noah: this file: /Users/dean/squeezeplay/assets/Fab4Skin/images/Text_Entry/Keyboard_Touch/tch_cursor.png needs to be grey and not black so that the cursor is distinguished from the text being drawn on top of it. This needs to be fixed for MP, so please prioritize appropriately
Is the text rendered on top of the cursor (i.e. cursor becomes highlighted bkground) on remote?
yes, the text is rendered on top of the cursor.
Created attachment 4967 [details] Cursor color comparison (teal vs. mono selection) We are going to fight a contrast battle the more black or white we add to the gray cursor. In this instance the addition of color would be appropriate. It accomplishes a higher level of readability/contrast. By extension, all items that are selected or "highlighted" would use a teal accent color...
IMO the teal looks great!
Asset updated to gray version in snv. 3/24/09 - 6:04pm as seen in attached comparison. *The cursor color treatment should be flagged as an area to review at a later date.*
What's the purpose of the block cursor? Without a way to toggle between insert/overwrite modes it doesn't make any sense. IMO, you should always be in insert mode using the bar cursor and then use the back(space) key to erase the character to the left of the cursor and insert a new characters at the cursor. I'm talking about exactly the way an HTML form's text input box works in most (all?) browsers. There is no overwrite mode. If the intention is to use the block cursor and overwrite mode when someone touches within an existing string, that doesn't work because there's no way to insert a forgotten character without some way to toggle out of overwrite mode.
Jim: if you use the remote to enter text, then there is an overwrite mode. Try this by using your IR remote and scroll up/down when on the text entry screen. Also, if we decide to add drag-to-select text (like on a computer gui), then the cursor becomes a highlight.
Tom, once Noah's finished this is yours to fix.
I think this is ready for you, right tom?
(In reply to comment #16) > I think this is ready for you, right tom? It's unclear to me what the issue is for this bug. Can you clarify?
Based on my conversation with Richard today, I think he's working on this.
(In reply to comment #14) > Jim: if you use the remote to enter text, then there is an overwrite mode. Try > this by using your IR remote and scroll up/down when on the text entry screen. I'm not sure I see this. As with the SB2/3 remote, if you use up/down when the cursor is over a character then it cycles through characters. I just did a factory reset and ran through the entire setup using the IR. The biggest issue I found is that when entering text the "auto-move to next character" behavior is too fast - much faster than with previous IR interfaces - making it difficult if you pause for a split second while going through the characters on a remote button. It also makes it difficult to use the up/down cycling when entering a special character on the '1' key and you overshoot the one you're looking for.
I think this is working great, but we still need to revert to the teal cursor. Noah: can you check in the old asset?
This should be resolved. Feel free to reopen after review of current build.