Reply to thread

Message

Got it! I must be reacting slowly or my machine (computer and remote) needs more time to display the letters than yours. I need abt 0.35 sek per keystroke if I want to see the displayed number before hitting the next. By the 4th keystroke I have run out of time. So I changed the C_KeyInputTime: to 3000 and voila! - I can see all the numbers and @ as well. If you want to text "at" the wait after hitting "a" of 3 sek before you can hit the "t" must seem as an eternity to a Nokia texting champion. I can live with it, but will try to tweek it down to maybe 2.5 sek.

Had the idea of using button 1 for this squence like on my mobile phone: . , - ? ! " @ : ; / \ ( ) * 1 Probably need 5 sek, which will seem a bit long for the other keys. Maybe just include those signs that are really important for texting to search boxes type Google? Maybe include "AND" "OR" and "NOT"? Maybe spread to all the keys allowing 6 characters per button? Maybe use other buttons for the special characters? Will need to think about this.

Cheers!

<blockquote data-quote="hallergard" data-source="post: 564363" data-attributes="member: 97639">Got it!&nbsp; I must be reacting slowly or my machine (computer and remote) needs more time to display the letters than yours.&nbsp; I need abt 0.35 sek per keystroke if I want to see the displayed number before hitting the next.&nbsp; By the 4th keystroke I have run out of time.&nbsp; So I changed the C_KeyInputTime: to 3000 and voila! - I can see all the numbers and @ as well.&nbsp; If you want to text &quot;at&quot; the wait after hitting &quot;a&quot; of 3 sek before you can hit the &quot;t&quot; must seem as an eternity to a Nokia texting champion.&nbsp; I can live with it, but will try to tweek it down to maybe 2.5 sek.Had the idea of using button 1 for this squence like on my mobile phone:&nbsp; &nbsp; . , - ? ! &quot; @ : ; / \ ( ) * 1&nbsp; &nbsp; Probably need 5 sek, which will seem a bit long for the other keys.&nbsp; Maybe just include those signs that are really important for texting to search boxes type Google?&nbsp; Maybe include &quot;AND&quot; &quot;OR&quot; and &quot;NOT&quot;?&nbsp; Maybe spread to all the keys allowing 6 characters per button?&nbsp; Maybe use other buttons for the special characters?&nbsp;&nbsp; Will need to think about this.Cheers!</blockquote>

[QUOTE="hallergard, post: 564363, member: 97639"] Got it! I must be reacting slowly or my machine (computer and remote) needs more time to display the letters than yours. I need abt 0.35 sek per keystroke if I want to see the displayed number before hitting the next. By the 4th keystroke I have run out of time. So I changed the C_KeyInputTime: to 3000 and voila! - I can see all the numbers and @ as well. If you want to text "at" the wait after hitting "a" of 3 sek before you can hit the "t" must seem as an eternity to a Nokia texting champion. I can live with it, but will try to tweek it down to maybe 2.5 sek. Had the idea of using button 1 for this squence like on my mobile phone: . , - ? ! " @ : ; / \ ( ) * 1 Probably need 5 sek, which will seem a bit long for the other keys. Maybe just include those signs that are really important for texting to search boxes type Google? Maybe include "AND" "OR" and "NOT"? Maybe spread to all the keys allowing 6 characters per button? Maybe use other buttons for the special characters? Will need to think about this. Cheers! [/QUOTE]