Guest - Testers are needed for the reworked CDateTime core component. See... https://forum.kodi.tv/showthread.php?tid=378981 (September 29) x
problem with autocompletion plugin
#1
Hi!

Not sure where to post this problem in order to get some help, @Karellen please move this to a more appropriate place on the forum if Im at the wrong place. 

However, I have problem with Phils AutoCopletion plugin. It populates the search strings but when I choose a string Kodi hangs. I have tried the modded version mentioned in this thread but without luck

Debug log

Cheers
Marcus
Reply
#2
This is an add-on that would be best handled in the program add-ons thread, I note it's been a while for an update, with any luck the author might offer a tip if he pokes in.

Thread moved [PatK]
Reply
#3
I bump this thread since others have reported the same issue at Phils Githup page.
Reply
#4
It's been about a month since the last bump, hope it's okay if I bump as well. It's still broken and there doesn't seem to be movement on the github page.
Reply
#5
(2018-12-12, 22:59)macardi Wrote: Hi!

Not sure where to post this problem in order to get some help, @Karellen please move this to a more appropriate place on the forum if Im at the wrong place. 

However, I have problem with Phils AutoCopletion plugin. It populates the search strings but when I choose a string Kodi hangs. I have tried the modded version mentioned in this thread but without luck

Debug log

Cheers
Marcus
Still getting this and I am on 18.4 ....
Reply
#6
Is this fork working?
https://github.com/randomt4sk/plugin.pro...completion
Reply
#7
(2019-10-17, 10:31)malvinas2 Wrote: Is this fork working?
https://github.com/randomt4sk/plugin.pro...completion
As I said in my opening post, the version in that fork does not solve the problem.
Reply
#8
Hi, untested from my memory 
in the plugin he calls focus element 300 before sending the text. In estuary the text field is 312. Don't know if it's his bug or the skins. My quickfix was locally changin the plugin.py to focus 312.
Check the DialogKeyboard.xml of your skin and look for the edit field. The id of that edit field is what you want to put in line 47 of plugin.py
"window.setFocusId(300)" to "window.setFocusId(312)" for estuary.
Reply
#9
(2019-10-24, 00:25)Takezo36 Wrote: Hi, untested from my memory 
in the plugin he calls focus element 300 before sending the text. In estuary the text field is 312. Don't know if it's his bug or the skins. My quickfix was locally changin the plugin.py to focus 312.
Check the DialogKeyboard.xml of your skin and look for the edit field. The id of that edit field is what you want to put in line 47 of plugin.py
"window.setFocusId(300)" to "window.setFocusId(312)" for estuary.
Tested your fix, but no dice for me, other suggestions?
Reply
#10
Which skin are you using?
Reply
#11
(2019-10-24, 21:19)Takezo36 Wrote: Which skin are you using?

I use Grid and I have checked Dialogkeyboard.xml and the Edit field have id 312. However also tried with Estuary with no difference.

Also, you point at line 47, in my file its line 37. Do you use another version of the plug-in?
Reply
#12
(2019-10-24, 21:38)macardi Wrote:
(2019-10-24, 21:19)Takezo36 Wrote: Which skin are you using?

I use Grid and I have checked Dialogkeyboard.xml and the Edit field have id 312. However also tried with Estuary with no difference.

Also, you point at line 47, in my file its line 37. Do you use another version of the plug-in? 
No was a typo. 37 is correct. I was using phils version. Only other guess is he is using the jsonrpc for that. Maybe something in your remote access settings is disabled. I can maybe debug a bit properly on the weekend.
Reply
#13
Hi,
so i did a test and can't really reproduce your problem. I tried a clean 18.4 and 18 rc3 installation  on Win 10 64bit and on both phils standard version (no change on line 37)works. Tried explicitly, like in your log, in the youtube plugin on both and it worked for me.
So can't really debug this. What you could do to narrow down the problem a bit on your side is to add a few log outs in the plugin.py. From what i can see in your log the plugin is called with selectautocomplete so that seems to be ok.
I would add some logging like this
python:

xbmc.log("trying to send to " + str(params.get("id")) + " to kodi")
try:
   window = xbmcgui.Window(10103)
except Exception as e:
   xbmc.log("failed to get window")
   xbmc.log(str(e))
   return None
window.setFocusId(300)
result = get_kodi_json(method="Input.SendText", params='{"text":"%s", "done":false}' % params.get("id"))
xbmc.log("result of sending Input.SendText")
xbmc.log(str(result))
return None
Reply
#14
(2019-10-25, 10:09)Takezo36 Wrote: Hi,
so i did a test and can't really reproduce your problem. I tried a clean 18.4 and 18 rc3 installation  on Win 10 64bit and on both phils standard version (no change on line 37)works. Tried explicitly, like in your log, in the youtube plugin on both and it worked for me.
So can't really debug this. What you could do to narrow down the problem a bit on your side is to add a few log outs in the plugin.py. From what i can see in your log the plugin is called with selectautocomplete so that seems to be ok.
I would add some logging like this
python:

xbmc.log("trying to send to " + str(params.get("id")) + " to kodi")
try:
   window = xbmcgui.Window(10103)
except Exception as e:
   xbmc.log("failed to get window")
   xbmc.log(str(e))
   return None
window.setFocusId(300)
result = get_kodi_json(method="Input.SendText", params='{"text":"%s", "done":false}' % params.get("id"))
xbmc.log("result of sending Input.SendText")
xbmc.log(str(result))
return None

This issue really only occurs on Android platforms, as far as any of us can tell.
Reply
#15
(2019-10-25, 15:50)drinfernoo Wrote:
(2019-10-25, 10:09)Takezo36 Wrote: Hi,
so i did a test and can't really reproduce your problem. I tried a clean 18.4 and 18 rc3 installation  on Win 10 64bit and on both phils standard version (no change on line 37)works. Tried explicitly, like in your log, in the youtube plugin on both and it worked for me.
So can't really debug this. What you could do to narrow down the problem a bit on your side is to add a few log outs in the plugin.py. From what i can see in your log the plugin is called with selectautocomplete so that seems to be ok.
I would add some logging like this
python:

xbmc.log("trying to send to " + str(params.get("id")) + " to kodi")
try:
   window = xbmcgui.Window(10103)
except Exception as e:
   xbmc.log("failed to get window")
   xbmc.log(str(e))
   return None
window.setFocusId(300)
result = get_kodi_json(method="Input.SendText", params='{"text":"%s", "done":false}' % params.get("id"))
xbmc.log("result of sending Input.SendText")
xbmc.log(str(result))
return None

This issue really only occurs on Android platforms, as far as any of us can tell.
His initial log says win10 64bit. Thats why i tested with that. I recall having that on pi. Which i could fix with that change of the id. Having a look at that fix for Android from randomt4sk i would guess the problem is that it tries to call jsonrpc via GET which isnt supported anymore since some time.
However on android 9 also phils version works for me...
Reply

Logout Mark Read Team Forum Stats Members Help
problem with autocompletion plugin0