Guest orcinus Posted July 14, 2004 Report Posted July 14, 2004 (Sorry if this was discussed before) It seems that Multipress Time Out setting in Accessibility doesn't have any effect at all after flashing wm2003... Key pressess in all text boxes (including message composer) remain fixed at 1 sec timeouts no matter what you set up there - even if you choose "No auto advance". Any clues? Fixes? BTW, how come 2003 doesn't do auto-caps in messages? It doesn't even make the first letter in the message capital. If i remember correctly, 2002 used to. Orcinus PS: Setting the time out "manually" in registry doesn't help either.
Guest awarner [MVP] Posted July 14, 2004 Report Posted July 14, 2004 How do you know that the keypress are 1 second? And yep it was nice having auto caps :D
Guest orcinus Posted July 14, 2004 Report Posted July 14, 2004 I can't exactly call this exact :D, but i "feel" it as one second or something close to it. If you don't believe me, try timing it with a stopwatch. Or try setting the time out to 2 seconds and check that out - it should be fairly obvious the delay isn't 2 seconds long. The reason this bugs me is i can't type text as quickly as i could with 2002 (with half a sec delay). I'm probably way off, but i have a hunch this has something to do with "tighter", improved keypress filter (the routine that filters out multiple and erranous keypresses). Orcinus
Guest orcinus Posted July 15, 2004 Report Posted July 15, 2004 Oh, just btw, long-pressing 0 for + in number entry mode doesn't work anymore either! It works when you type a number from home screen, but doesn't everywhere else. Or am i missing something here? Orcinus Posted from my SmartPhone!
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now