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
|
- [DUG]: Enter as Tab Neven MacEwan
- RE: [DUG]: Enter as Tab Nahum Wild
- Re: [DUG]: Enter as Tab James M Sandbrook
- RE: [DUG]: Enter as Tab Phil Dewar
- Re: [DUG]: Enter as Tab Rohit Gupta
- [DUG]: Enter as Tab Lukas Svoboda
- [DUG]: Enter as Tab Mark Derricutt