Information générale
Catégorie:
Gestionnaire d'écran & Écrans
Versions des environnements
Network:
Windows Server 2012 R2
Virtual environment:
VMWare
I think _INCSEEK might just do it - it is set by default to .5 so there's my delay. I set it to .1 and then the "odd" behaviour went away.
The help file does not say a lot (other than used in listbox or combo boxes) - if I set this on an app-wide basis, anyone know of any "untoward" behaviour that might come along with it?
Albert
>>Hi all,
>>
>>A user emailed today to say that they would like me to "fix" something that happens in a combo box - combo box that gets its rowsource from a small array (5 rows) bound to a view.
>>
>>The list has 3 rows in it that all start with "T" - these users are very keyboard centric as they like to move through the fields quickly for quotes. When they get to the combo box, some have figured out that if they press the "T" one, two or three times, they can get the choice they want. But they said it often "does not work" i.e. it does not cycle to the next item that begins with a "T".
>>
>>Checking the code, there is not much that fires off of the methods - but if try testing it by changing how fast I hit the T, it can cause it to "fail". That is, if I leave approximately 1/2 a second between key taps, it works as expected. If I hit it much faster, it then fails.
>>
>>I could not see any property that controls how fast VFP processes keystrokes - is there some other setting?
>>
>>Thanks,
>>Albert
>
>Check _INCSEEK = nTicks
>system variable in Help.
Précédent
Suivant
Répondre
Voir le fil de ce thread
Voir le fil de ce thread à partir de ce message seulement
Voir tous les messages de ce thread
Voir tous les messages de ce thread à partir de ce message seulement