Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Check boxes...
Message
De
14/12/2001 12:24:37
 
 
À
14/12/2001 11:57:12
Hilmar Zonneveld
Independent Consultant
Cochabamba, Bolivie
Information générale
Forum:
Visual FoxPro
Catégorie:
Problèmes
Titre:
Divers
Thread ID:
00594287
Message ID:
00594501
Vues:
25
Hilmar,

I try to take care of it in the class code of each control. I also do other things in the textbox class, like prevent backspace from exiting the control.

For buttons, I try to always have a key associated with them (so the user can hit alt-a, to add a line, for example). I prefer for buttons not to have a tab stop, to prevent enter key problems (someone here may slap me around for this *grin*, but oh well).

Also, when a user clicks a button (or hot-keys it), I set focus back to the data entry item on the form, or back to the control that previously had focus (depending on situation).

>OK, I must admit you are right. My users here had the same argument.
>
>How about globally intercepting ENTER in your forms (method Form.KeyPress; you will also need to set Form.KeyPreview = .T.), and change all ENTERs to TABs?
>
>I think I will try this myself, one of these days.
>
>I am not sure whether this is a good idea; ENTER might be needed for other things. Of course, users can still activate a button with Spacebar.
>
>Hilmar.
>
>>Hilmar,
>>
>>I suppose it depends on what you mean by "works fine". In some data entry cases, it is less than ideal. For fast data-entry folks using an accounting application, it can be a beating, because a lot of the information is keyed with the 10-key pad, and using that ENTER key.
>>
>>So, I go to the trouble... :)
Steve Gibson
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform