Reply to thread

Message

It's not a bug report nor a skin issue. But it might be design related and could be a discussion for a possible feature request.

When the input of the user is needed, currently a full keyboard is displayed.
[ATTACH=full]116545[/ATTACH]

While this is good in case of textural input, only a part of the the keyboard is needed if the expected value is an integer or single data type. Nevertheless it is possible to type a non-numbering character.
[ATTACH=full]116546[/ATTACH]

Not sure how much changes are needed, but if it would be possible to tell the on-screen-keyboard the expected data type, it could be the full keyboard, if text is expected or a simplified and slimmed down numpad if only single or double values are expected. If the data type is an integer, even the comma (,) could be disabled or hidden.
[ATTACH=full]116548[/ATTACH]

<blockquote data-quote="chefkoch" data-source="post: 942084" data-attributes="member: 10438">It's not a bug report nor a skin issue. But it might be design related and could be a discussion for a possible feature request.&nbsp;When the input of the user is needed, currently a full keyboard is displayed.[ATTACH=full]116545[/ATTACH]&nbsp; &nbsp;While this is good in case of textural input, only a part of the the keyboard is needed if the expected value is an integer or single data type. Nevertheless it is possible to type a non-numbering character.[ATTACH=full]116546[/ATTACH]&nbsp;Not sure how much changes are needed, but if it would be possible to tell the on-screen-keyboard the expected data type, it could be the full keyboard, if text is expected or a simplified and slimmed down numpad if only single or double values are expected. If the data type is an integer, even the comma (,) could be disabled or hidden.[ATTACH=full]116548[/ATTACH]</blockquote>

[QUOTE="chefkoch, post: 942084, member: 10438"] It's not a bug report nor a skin issue. But it might be design related and could be a discussion for a possible feature request. When the input of the user is needed, currently a full keyboard is displayed. [ATTACH=full]116545[/ATTACH] While this is good in case of textural input, only a part of the the keyboard is needed if the expected value is an integer or single data type. Nevertheless it is possible to type a non-numbering character. [ATTACH=full]116546[/ATTACH] Not sure how much changes are needed, but if it would be possible to tell the on-screen-keyboard the expected data type, it could be the full keyboard, if text is expected or a simplified and slimmed down numpad if only single or double values are expected. If the data type is an integer, even the comma (,) could be disabled or hidden. [ATTACH=full]116548[/ATTACH] [/QUOTE]