Moving Pictures is a movies plug-in for the MediaPortal media center application. The goal of the plug-in is to create a very focused and refined experience that requires minimal user interaction. The plug-in emphasizes usability and ease of use in managing a movie collection consisting of ripped DVDs, and movies reencoded in common video formats supported by MediaPortal.
12
stars
6
forks
source link
The PIN applet (Moving Pictures) does not respond to number entering by remote #873
What steps will reproduce the problem?
1. Use remote to enter parent contol PIN in PIN applet (Moving Pictures).
Result: The PIN applet does not respond to number entering by remote.
What is the expected output? What do you see instead?
The corresponding PIN digits should be entered.
What version of Moving Pictures are you using? What version of MediaPortal?
What Skin?
Moving Pictures: 1.06
MediaPortal: 1.1.0
Skin: StreamedPortal 1.1.0
Details:
I'm using Harmoney 880 to control MP via the Message plugin and Eventghost. I
have a problem of entering 4 digits PIN code to unlock Parent lock. The PIN
entering window does not respond to remote number input. Enter the number via
keyboard works. However the number keys on the remote work in all scenarios,
such as jump to time, remote filtering, etc. The settings of the Message plugin
and MediaPortal plugin in Eventghost are in thei default settings. Any idea how
to fix it? Thanks a lot.
I also tested entering pin using IRSS w/ its virtual remote. The result is the
same. The PIN applet does not respond to the number key inputs by the remote.
The log is attached. What I did are 1. run MediaPortal; 2. Go to All Movies in
Moving Pictures; 3. Filter movies to Avatar using remote filtering (to show the
number keys are working); 4. open Parent Lock applet; 5. Try to enter PIN
digits (no response); 6. Return to Home page and close MediaPortal.
Please attach a screenshot and logs if possible. When submitting log files
please submit DEBUG logs. See here for details:
http://tinyurl.com/aj65su
Original issue reported on code.google.com by shimh.e...@gmail.com on 30 Jul 2010 at 2:28
Original issue reported on code.google.com by
shimh.e...@gmail.com
on 30 Jul 2010 at 2:28Attachments: