<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - UI: field for SMTP server port number is spin button" href="https://bugs.documentfoundation.org/show_bug.cgi?id=104825#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - UI: field for SMTP server port number is spin button" href="https://bugs.documentfoundation.org/show_bug.cgi?id=104825">bug 104825</a> from <a class="email" href="mailto:tietze.heiko@gmail.com" title="Heiko Tietze <tietze.heiko@gmail.com>"> Heiko Tietze</a> <pre>Wrote on the KDE HIG: * Use spin boxes for numerical input only. Use a list or option menu when you need the user to select from fixed data sets of other types. * Use a spin box if the numerical value is meaningful or useful for the user to know, and the valid input range is unlimited or fixed at one end only. For example, a control for specifying the number of iterations of some action, or a time-out value. * If the range is fixed at both ends, or the numerical values are arbitrary (for example, a volume control), use a Slider control instead. * For cases where the values are constrained at both ends and there large ranges of integers (more than about 20) or floating-point values that require precise control, consider providing both a Slider and Spin Box. This allows the user to quickly set or fine-tune the setting more easily than they could with the slider control alone. The pure edit is not better as it gives no clue about numerical and constrained input. So odd yes, but better than ordinary edit.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>