[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug-gtypist] Inconsistent Errant Key Press Behavior

From: Tim Marston
Subject: Re: [bug-gtypist] Inconsistent Errant Key Press Behavior
Date: Mon, 04 Mar 2013 17:07:07 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130116 Icedove/10.0.12

Hi Richard,

On 02/03/13 22:10, Richard Edward Horner wrote:
> However, if the first key you press is 's', it will show this:
> asdf
> ^s

This behaviour is by design.  Gtypist is trying to be clever and handle
the situation where you've missed out an 'a'.  The 's' is accepted as
the next letter in sequence.  If it didn't do this, imagine what would
happen if you typed in "sdf", instead of "asdf", by accident.  All three
of those letters would be an error and you'd get something like this:


But with this behaviour, gtypist is able to show that there was only one
error (the missing 'a').  And it looks like this:


What's even *more* surprising (I think, anyway) is that if you type
"ssdf", the second 's' gets ignored!  This is because the previous
assumption (that you missed out the first character, 'a') can cause
problems if the assumption is incorrect.  If you typed 's' *instead* of
'a', then gtypist should still show that there was only one error.  If
it didn't ignore the second 's', then the second 's' and all subsequent
letters would be an error, and typing "ssdf" would look like this:


So I hope this explains what is happening.  :o)  Perhaps a good question
is whether we should provide an option to turn off this "clever" behaviour.

All the best,

Tim Marston

reply via email to

[Prev in Thread] Current Thread [Next in Thread]