Coyote 1.0 Keyboard

I like the new keyboard so far, especially the keyboard key to turn it off/hide it. It will be a plus for me when working in word to go.... but, it brings this up.... could we get an icon on the bottom menu bar to turn the keyboard on? Then we wouldn't have to use the click and hold method on the menu button. I think it would make things much smoother and faster.

I hit that new button wondering what did, and poof, the keyboard was gone. I just stared at the blank space a moment, wondering what now, but a quick tap in the text entry field returned it. BTW- my other keyboards, Slide and ThickButtons survived intact.

The new keyboard is lightyyears ahead of the old one. Thanks to Entourage!

There is a nice "next"-button now when you need it.
btw. Is the keyboard less responsive then the old one or am I typing faster now?

The parensthesis does not work for me. The keyboard goes to the alt-mode???? Does anyone has the same problem?

I got over my initial distase for this keyboard, and it's growing on me. I can now type with both hands on the screen as if it were a physical keyboard, and using the trackball to make character-by-character movements--which unbeknownst to me was actually available with the old keyboard--is infinitely preferable to the beloved-but-doomed arrow keys.

I must say, though, that I miss not having the full compliment of keys, namely, brackets (they're used to enclose editorial comments in running body text to distinguish them from comments made by a source), though these weren't available on the old keyboard either.

I have decided that I need a physical keyboard to do anything more than type in a word or two for Google to search or something. I can't touch type on an LCD (need feedback from actual keys) and it's too frustrating to hunt-and-peck.

I prefer the original LCD keyboard because I found it slightly easier to hunt-and-peck (larger surface area for individual keys), although I'm hopeful that I'll get used to the new layout (for as little as I use it).

Originally Posted by NiaTrue

I miss not having the full compliment of keys, namely, brackets (they're used to enclose editorial comments in running body text to distinguish them from comments made by a source), though these weren't available on the old keyboard either.

The left bracket [ is under the alt-key. The right one does not work either.

Originally Posted by borisb

The problem seems to be that pressing the "]" key is instead/also pressing the ALT key to the right of it, in effect turning off the ALT mode rather than rendering a "]" keypress...

I'm going to submit a Bug report for this. It's perhaps that the detection regions aren't properly mapped in the ?123 mode.

boris and sjarel-

Good catch. I've already entered that bug with our test group.

DP

Originally Posted by borisb

The problem seems to be that pressing the "]" key is instead/also pressing the ALT key to the right of it, in effect turning off the ALT mode rather than rendering a "]" keypress...

I'm going to submit a Bug report for this. It's perhaps that the detection regions aren't properly mapped in the ?123 mode.

OK, thanks Boris. You can explain things better than I can in poor english. You did not type on the eDGe, did you?
Did you also notice that the return-key sometimes changes to an next-key of even an done-key? Alas not always when I want it to.

Originally Posted by dontpanic

boris and sjarel-

Good catch. I've already entered that bug with our test group.

DP

You were faster than I was with an replay, but sjarrel is with 2 r's, or is the second r-key not functioning either?

Originally Posted by sjarrel

Did you also notice that the return-key sometimes changes to an next-key of even an done-key? Alas not always when I want it to.

The software keyboard is context-aware of some kinds of data entry fields.
If it knows a host name/web address is expected it puts up the keyboard with the .com and the slash "/" keys.
If it knows an email address is expected it puts up the keyboard with the @ symbol.

Originally Posted by kenjennings

The software keyboard is context-aware of some kinds of data entry fields.
If it knows a host name/web address is expected it puts up the keyboard with the .com and the slash "/" keys.
If it knows an email address is expected it puts up the keyboard with the @ symbol.

Yes, but it is not aware every time. Logging in Entourage: after typing username it would be nice if the nextkey is there to go to passwordfield. Pressing the returnkey does not do the trick then. It works fine in the OI-SAFE app. Maybe there is a way that we can choose the right keyboard is comming up? -is that good english?"-
Btw I also notice that the "e" and the "r" are not always responsing.

The problem seems to be that pressing the "]" key is instead/also pressing the ALT key to the right of it, in effect turning off the ALT mode rather than rendering a "]" keypress...

I'm going to submit a Bug report for this. It's perhaps that the detection regions aren't properly mapped in the ?123 mode.

I have also noticed, when working in 'word to go', that using the 'o' key sometimes causes the cursor to jump to another area on the page.

Originally Posted by dontpanic

boris and sjarrel-

Good catch. I've already entered that bug with our test group.

DP

That was the answer on 06-18-2010 about the bug with the parenthesis on the keyboard. Do we have to wait until the major update or can this be fixed in a minor one?