•   
  • 1
  • 7
  • 8
  • 9
  • 10(current)
  • 11
  •   
Release script.toolbox
I can confirm there is an issue with script.toolbox on Android (maybe specific to Amazon Fire TV). See my ticket here: http://trac.kodi.tv/ticket/16092

Quote:0 ERROR: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<--
331 - NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
332 Error Type: <type 'exceptions.ImportError'>
333 Error Contents: The _imaging C module is not installed
334 Traceback (most recent call last):
335 File "/storage/emulated/0/Android/data/org.xbmc.kodi/files/.kodi/addons/script.toolbox/default.py", line 230, in <module>
336 Main()
337 File "/storage/emulated/0/Android/data/org.xbmc.kodi/files/.kodi/addons/script.toolbox/default.py", line 37, in __init__
338 image, imagecolor = Filter_Image(self.image_now, self.radius)
339 File "/storage/emulated/0/Android/data/org.xbmc.kodi/files/.kodi/addons/script.toolbox/resources/lib/Utils.py", line 169, in Filter_Image
340 imagecolor = Get_Colors(img)
341 File "/storage/emulated/0/Android/data/org.xbmc.kodi/files/.kodi/addons/script.toolbox/resources/lib/Utils.py", line 175, in Get_Colors
342 pixels = img.load()
343 File "/data/data/org.xbmc.kodi/cache/apk/assets/addons/script.module.pil/lib/PIL/ImageFile.py", line 164, in load
344 self.load_prepare()
345 File "/data/data/org.xbmc.kodi/cache/apk/assets/addons/script.module.pil/lib/PIL/PngImagePlugin.py", line 381, in load_prepare
346 ImageFile.ImageFile.load_prepare(self)
347 File "/data/data/org.xbmc.kodi/cache/apk/assets/addons/script.module.pil/lib/PIL/ImageFile.py", line 231, in load_prepare
348 self.im = Image.core.new(self.mode, self.size)
349 File "/data/data/org.xbmc.kodi/cache/apk/assets/addons/script.module.pil/lib/PIL/Image.py", line 37, in __getattr__
350 raise ImportError("The _imaging C module is not installed")
351 ImportError: The _imaging C module is not installed
352 -->End of Python script error report<--
Reply
(2015-07-28, 18:11)phil65 Wrote: It´s already included since some months, Window(home).Property(imagecolor).
Gets filled after using info=blur.

Very cool, thanks
Reply
(2015-07-29, 15:45)janeczku Wrote: I can confirm there is an issue with script.toolbox on Android (maybe specific to Amazon Fire TV). See my ticket here: http://trac.kodi.tv/ticket/16092

Yeah, same here on FireTV, it throws an error every time I show movie info.
Using Isengard 15 but also tried Helix which also failed. Using Arctic Zephyr skin.
Reply
(2015-07-29, 15:45)janeczku Wrote: I can confirm there is an issue with script.toolbox on Android (maybe specific to Amazon Fire TV). See my ticket here: http://trac.kodi.tv/ticket/16092

But you closed the ticket saying it was fixed. Could you please reopen it?

Thanks
Reply
The closest I can offer to a workaround, with Mimic at least, is to disable Script Toolbox in add ons. Before you can do that you have to edit out the dependency line from the skin's addon.xml file. I presume that will be undone if Mimic updates.

It would be nice to know something more.
Reply
I think you'll need to reopen this as a new bug. Even though you edited it, your old one is still marked as closed, and it's clearly not.

I think that's how these things work.
Reply
(2015-07-29, 08:23)Fist Wrote: Phil, still waiting for an answer on this bug, that I've now reproduced three Amazon Fire TVs:

http://xbmclogs.com/pmxjvawbu

Skin is Mimic (Script Toolbox is a dependency). Build is Isengard final.

Thanks

Updating the Fire TV to OS 5 (for developers) fixes it.
Reply
Hi Phil,

Is there anyway to apply the blur against the focused item in a list? I'd like to use the blur to create backgrounds in connection to the focused item if possible?

Thanks,

Mike.
SKIN: Aeon Madnox
RIP Schimi2k, we miss you.
When I grow up I want to be a skilled skinner
Thank me by ⬇ adding to my + reputation
Reply
Hi

Just used this script in Aeon Nox to add extra fanart to the DB, however there was only an option for adding Movies & TV Shows extrafanart to the DB, not an option for Music extrafanart.

Is this possible? And how would i do it?
Reply
Kodi 16 / export settings

So in Jarvis I suppose not as big a deal to save skin settings, but I'm thinking it would still be of value to have a simple user option that retains script.toolbox functionality, or maybe there is a better way to backup settings now?

scott s.
.
maintainer of skin  Aeon MQ5 mods for post-Gotham Kodi releases:
Matrix see: Aeon MQ5 Mod Martix release thread
Leia see: Aeon MQ5 Mod Leia release thread
Reply
(2015-09-08, 22:37)scott967 Wrote: Kodi 16 / export settings

So in Jarvis I suppose not as big a deal to save skin settings, but I'm thinking it would still be of value to have a simple user option that retains script.toolbox functionality, or maybe there is a better way to backup settings now?

scott s.
.
Concerning backup / export settings, please note that there is right now an issue in Jarvis because of the new guisettings.xml moved into the addon_data folder. Not sure that Phil is aware / fixed this since it comes from KODI. guisettings.xml update is triggered at KODI closing, that means all modifications made during session and exported without having closed KODI first won't be up to date.

http://forum.kodi.tv/showthread.php?tid=237583
[Skin] KOver - V1.1.0 Stable (Repo version)
[WIP] ReKOver - Skinning tool project

If I've been helpful or you like my work, hit "THANK USER" button ;) ...
Reply
(2015-09-08, 23:53)Jayz2K Wrote:
(2015-09-08, 22:37)scott967 Wrote: Kodi 16 / export settings

So in Jarvis I suppose not as big a deal to save skin settings, but I'm thinking it would still be of value to have a simple user option that retains script.toolbox functionality, or maybe there is a better way to backup settings now?

scott s.
.
Concerning backup / export settings, please note that there is right now an issue in Jarvis because of the new guisettings.xml moved into the addon_data folder. Not sure that Phil is aware / fixed this since it comes from KODI. guisettings.xml update is triggered at KODI closing, that means all modifications made during session and exported without having closed KODI first won't be up to date.

http://forum.kodi.tv/showthread.php?tid=237583

you could try this: https://github.com/phil65/script.toolbox...4320c4b5d7
Works in jarvis and should also give you real-time string / bool values.
Donate: https://kodi.tv/contribute/donate (foundation), 146Gr48FqHM7TPB9q33HHv6uWpgQqdz1yk (BTC personal)
Estuary: Kodis new default skin - ExtendedInfo Script - KodiDevKit
Reply
(2015-09-09, 01:44)phil65 Wrote:
(2015-09-08, 23:53)Jayz2K Wrote:
(2015-09-08, 22:37)scott967 Wrote: Kodi 16 / export settings

So in Jarvis I suppose not as big a deal to save skin settings, but I'm thinking it would still be of value to have a simple user option that retains script.toolbox functionality, or maybe there is a better way to backup settings now?

scott s.
.
Concerning backup / export settings, please note that there is right now an issue in Jarvis because of the new guisettings.xml moved into the addon_data folder. Not sure that Phil is aware / fixed this since it comes from KODI. guisettings.xml update is triggered at KODI closing, that means all modifications made during session and exported without having closed KODI first won't be up to date.

http://forum.kodi.tv/showthread.php?tid=237583

you could try this: https://github.com/phil65/script.toolbox...4320c4b5d7
Works in jarvis and should also give you real-time string / bool values.

Thanks I will look at it. Meanwhile I forked your repo and did my own fix here:

https://github.com/scott967/script.toolb...943400e831

but I have to look at what if any difference I did.

I did see in some initial testing that I could export settings from Isengard and they seem to import and work in Jarvis using unmodified code, so in my commit I created "pre-Jarvis"-style backup file in the export (that is, it is in format skin_name.setting) and left import as-is. The idea is user could then move from Isengard to Jarvis with a clean jarvis install.

But I only tested in the skin I maintain.

scott s.
.
maintainer of skin  Aeon MQ5 mods for post-Gotham Kodi releases:
Matrix see: Aeon MQ5 Mod Martix release thread
Leia see: Aeon MQ5 Mod Leia release thread
Reply
I didnt pay attention to backwards compat for the exported files, that´s true. Can fix that in a proper way in case that is wanted.
Donate: https://kodi.tv/contribute/donate (foundation), 146Gr48FqHM7TPB9q33HHv6uWpgQqdz1yk (BTC personal)
Estuary: Kodis new default skin - ExtendedInfo Script - KodiDevKit
Reply
Hello i'm using script toolbox but when running the script i get al ot of these errors:

16:57:34 T:6032 ERROR: Failed to open(//Movies/The Croods (2013)/extrafanart) opendir call failed with "NFS: Lookup of //Movies failed with NFS3ERR_NOENT(-2)"
16:57:34 T:6032 ERROR: XFILE::CDirectory::GetDirectory - Error getting nfs://***.***.***.**/media/movies/Movies/The Croods (2013)/extrafanart
16:57:34 T:6032 ERROR: Failed to open(//Movies/The Dark Knight (2008)/extrafanart) opendir call failed with "NFS: Lookup of //Movies failed with NFS3ERR_NOENT(-2)"
16:57:34 T:6032 ERROR: XFILE::CDirectory::GetDirectory - Error getting nfs://***.***.***.**/media/seagate/Movies/The Dark Knight (2008)/extrafanart
16:57:34 T:6032 ERROR: Failed to open(//Movies/The Equalizer (2014)/extrafanart) opendir call failed with "NFS: Lookup of //Movies failed with NFS3ERR_NOENT(-2)"

And a lot more of these errors.

Maybe someone can help me with this?

Thanks!
Reply
  •   
  • 1
  • 7
  • 8
  • 9
  • 10(current)
  • 11
  •   



Logout Mark Read Team Forum Stats Members Help
script.toolbox2
This forum uses Lukasz Tkacz MyBB addons.