Posts: 135
Joined: Feb 2009
Reputation:
0
The last couple of XBMC REVs i have found when starting XBMC the keyboard arrow keys i use for navigating does not work on Showmix, Phil65 or Hitched.
It use to be as soon as i started i could navigate directly now on Showmixi have to press DOWN key then it starts working. On Phil65 and Hitched i have to use a mouse to get it starting before returning to the keyboard.
I'm sure this is an XBMC issue. Using REV 23858 at the moment.
Any ideas?
Intel NUC Skull Canyon - Windows 10 Pro - Kodi 18
VU+ Solo2 - Canal Digital/CMore Max
Samsung UE65KS9005 Pro Calibrated
Posts: 1,251
Joined: Dec 2008
Reputation:
15
Does anyone know if there's a ticket for this bug and if so, what ticket number?
Posts: 17,418
Joined: Aug 2007
Reputation:
590
Hitcher
Team-Kodi Member
Posts: 17,418
It's because you have python scripts running at start up - something's got broken.
Posts: 1,251
Joined: Dec 2008
Reputation:
15
2009-10-23, 07:53
(This post was last modified: 2009-10-23, 08:16 by sialivi.)
I haven't added any scripts so it must be scripts that come included with both Aeon65 and Ekim232 then 'cause I have the same problem with both those.
Edit:
Looks like you're right, it's the RecentlyAdded.py scripts that's included with both these skinmods that is the culprit.
Posts: 135
Joined: Feb 2009
Reputation:
0
I have found stated in another thread that AEON only works up to REV 22516 after that XBMC have made changes that stops that script from working correcty.
I would think that as long as XBMC is evolving so should the scripts that the skinners provide. It's like having a app on Iphone that stops working because you upgraded to the latest 3.1.2, the app supplier should upgrade to make compatible.
Intel NUC Skull Canyon - Windows 10 Pro - Kodi 18
VU+ Solo2 - Canal Digital/CMore Max
Samsung UE65KS9005 Pro Calibrated
Posts: 39
Joined: Sep 2009
Reputation:
0
Phuqz
Junior Member
Posts: 39
I think we should be thankful that these people provide (what is an amazing piece of software) for free and in their own time on top of any of the other real life stuff they have to deal with.
If stuff is broken, its broken and they don't 'have' to fix it. Addons/scripts are designed all the time by people that want to achieve a certain thing and develop that against a particular build. We are lucky they release it at all. I don't think they 'should' have to do anything with it if new builds break it unless they want to.
If you can't do something yourself, you're not paying someone to do it for you and especially if you're not buying it then its all about being grateful it actually worked at all. Frankly, its up to the providors as to whether they fix it or not.
I'm sure that if everyone who used this script paid for it then the fix would be made immediately, but whilst we're not then I think we should just be patient and hope that someone will the right skills has the time and desire to sort it for us.
Posts: 135
Joined: Feb 2009
Reputation:
0
I agree Phugz patience might not be a virtue in my case :-(
Intel NUC Skull Canyon - Windows 10 Pro - Kodi 18
VU+ Solo2 - Canal Digital/CMore Max
Samsung UE65KS9005 Pro Calibrated
Posts: 135
Joined: Feb 2009
Reputation:
0
Tested now and still same issue and latest added script does not load at start.
Intel NUC Skull Canyon - Windows 10 Pro - Kodi 18
VU+ Solo2 - Canal Digital/CMore Max
Samsung UE65KS9005 Pro Calibrated
Posts: 180
Joined: Sep 2008
Reputation:
1
2009-10-30, 16:49
(This post was last modified: 2009-10-30, 16:54 by Dannydeman.)
I use the one of the latest SVN builds, 24088, but still has this issue that I can't use the keyboard with my remote (navigation does not work). I will update it to the latest available and try again.
Edit: Latest SVN, but still the same problem. Keyboard won't react to my remote or the arrow keys on my keyboard. I can only type directly through a keyboard.
Posts: 180
Joined: Sep 2008
Reputation:
1
I use LM remote, and manually mapped some buttons. The arrow buttons are mapped as "left", "right" like the keyboard (default). But not even the keyboard's arrow keys do work, so it must be something in the script?