(1) You can set datatype of the field to “float” (well, ugly name for “decimal”…) then the formatting is done automatically when leaving the field.
(2) We currently support the evnet “leaving the field” but not “every key stroke”. Remember that the event processing is done on server side, so from roundtrip perspective there needs to be a compromise… - Please also note that we support special events (e.g. key down) which call “valid value” management.
How can I send a request for each keystroke in a field? This can be done with a javascript event like “onKeyPress” but how I can register such an event with a custom control?
…by just writing it into the HTML you generate - some pseudo code:
Tralala.
Please note: the “+ID” means you append the control’s id in order to have separate event processors (in case you have the same control twice in your page).
I have a question which belongs to this topic, too.
If I submit the page after the keyPress-event for getting the input, the whole input in this field is selected. How can I set the cursor to the end of the field?
E.g.:
If I use the keyPress-event for show some input possibilities in another control, it is bad for the user to set the cursor to the end of the field manually.
Migrating from 4.1.4 to 4.2 shouldn?t be a major problem. Basically you have to install Tamino 4.2 and update kit 4.2.1.4 and then you can upgrade your databases by using the ?set version? button in the Tamino Manager. The update kit is necessary to avoid some known problems in the set version area. To learn how your applications might be affected and how to avoid migration problems you should read the Tamino migration guide beforehand. Be sure that you have created backups of your databases before you start migration!