An even better way in my opinion is to write a component that you can plonk onto any form and it will automatically setup new on-key events (preserving the old events) which then trap key strokes and move to the next field on enter. That way you can add this functionality to any existing or new form without having to change all fields to subclassed fields.
 
If anyone wants a component that does this then let me know.
 
Cheers,
Lukas
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Rohit Gupta
Sent: Saturday, 8 July 2000 20:07
To: Multiple recipients of list delphi
Subject: Re: [DUG]: Enter as Tab

I am afraid the best solution (that works for all components sensibly) is to subclass all components and implement it in each component.
-----Original Message-----
From: Neven MacEwan <[EMAIL PROTECTED]>
To: Multiple recipients of list delphi <[EMAIL PROTECTED]>
Date: Saturday, 8 July 2000 12:57
Subject: [DUG]: Enter as Tab

Hiya All
 
I've had a client ask me to treat enter as Tab (yes that again)
 
Can anyone give me a few pointers
 
1/ How to do it
2/ pitfalls
 
TIA
Neven

Reply via email to