[no Bug] Pin entered via numpad not accepted (1 Viewer)

[lord.warlock]

MediaPortal Version: 1.2.0b
MediaPortal Skin: StreamedMP
Windows Version: Windows 7 Ultimate x64
CPU Type: Intel i3
HDD: 1x OCZ Vertex 2 / 1x 1gb WD Green / 1x 2gb WD Green
Memory: 2x 2gb kingston
Motherboard: Gigabyte P55-UD3L
Video Card: Ati HD 5450 Silent
Video Card Driver: Latest from ati
Sound Card: HDMI trough ati
Sound Card AC3:
Sound Card Driver:
1. TV Card: Terratec Cinergy C PCI HD
1. TV Card Type: DVB-C
1. TV Card Driver: Latest from Terratec
2. TV Card: Terratec Cinergy C PCI HD
2. TV Card Type: DVB-C
2. TV Card Driver: Latest from Terratec
Satelite/CableTV Provider: Ziggo (NL)
HTPC Case: Fractal Design
Cooling: Noctua NH-D14
Power Supply: be quiet! Pure Power L7 350W
TV - HTPC Connection: HDMI

When entering a PIN I'm using the numpad on my remote. But the PIN is always rejected, when I enter it via the on screen keyboard it works without any problem.

To reproduce :

Start media portal
go to my video's
Select a folder which has a pin set.
keyboard pop's up, leave focus on the done button.
enter the pin using the numpad on youre remote.
Click done.
pin is rejected.

now reenter the pin using the keyboard.
click done.
Pin accepted !!

 

[jameson_uk]

By default the keyboard is in SMS mode. Click the standard button to switch to a standard keyboard then this will work

 

[lord.warlock]

Ok, will have a look tonight when I come home. Is there any way to set the keyboard to default to the full version ?

 

[jameson_uk]

Once changed it will remember the last used setting

Marking as no bug. If you find out different to the above then report back

(we are discussing how to make this more obvious or force the standard keyboard for PIN input as a team either way)

 

[Seidelin]

Since I am quite confident this is the cause of the problem I set this thread to no bug (edit: jameson_uk beat me to it by a few seconds). We are aware of the usability issue with SMS/Standard keyboard and trying to improve the way it works.

In the unlikely event this was not the issue, please send me a pm or create a new bug report.

Thanks for reporting, and making us (more) aware of the usability issue.