[redglory]

Is still see no usecase for it because you can use the library node editor or directly the xsp method for it. Why would you even need to filter by path? Noone is using its Kodi library like that, or at least should not. Thats what tags, genres etc. are for.

Don't get me wrong, but adding little things without a real benefit makes something hard to maintain somewhere in the future. And this script is still mainly created for Embuary.

I understand [emoji6]

Will take a look if nodes respond to what i need [emoji106]

[sualfred]

test.txt: Won 3 Oscars

Code:

RunScript(script.embuary.helper,action=txtfile,path='"D:\test.txt"',property=Awards)

Result

Code:


[KodiDevKit] 2019-07-23 21:07:44: Got result:
[KodiDevKit] 2019-07-23 21:07:44: Won 3 Oscars


Are you sure you don't use $ESCINFO[Window(home).Property(Awards)] ? Because otherwise it's not possible.

[chrissix666]

EDIT: Solved

Are you sure you don't use $ESCINFO[Window(home).Property(Awards)] ? Because otherwise it's not possible.

Code:

$ESCINFO[Window(home).Property(Awards)]

Copied direct out of the code, i am more than sure 

[chrissix666]

EDIT: Solved

Real InfoLabel vs my fake InfoLabel:
    

Code:

<onload>RunScript(script.embuary.helper,action=txtfile,path=$INFO[ListItem.Path]$INFO[ListItem.FolderName]-awards.txt,property=Awards)</onload>    

[sualfred]

Try the github version and let me know if this makes a difference.

Edit:
And show me your code via pastbin or similar site please.

[chrissix666]

EDIT: Solved

Edit:
And show me your code via pastbin or similar site please.

New version unfortunately makes no difference.
Code in pastebin at beginning and fake InfoLabel 1386
It's equal the code 1342 with the real InfoLabel
->  https://pastebin.com/Hb2uNRLT

[sualfred]

Code:


<label>$ESCINFO[Window(home).Property(Awards)]</label>


Are you sure you DON'T use $ESCINFO[Window(home).Property(Awards)] ? Because otherwise it's not possible.

$ESCINFO = Wraps the string in " " to escape it. That's required if you provide a string with a comma or other special character to something else. Otherwise the $INFO[] string is cutted off at this point. Never use $ESCINFO in the output of a window if you don't want " ".

[chrissix666]

Code:


<label>$ESCINFO[Window(home).Property(Awards)]</label>


Are you sure you DON'T use $ESCINFO[Window(home).Property(Awards)] ? Because otherwise it's not possible.

$ESCINFO = Wraps the string in " " to escape it. That's required if you provide a string with a comma or other special character to something else. Otherwise the $INFO[] string is cutted off at this point. Never use $ESCINFO in the output of a window if you don't want " ". 

Sry, Sry! I've read over that! Shame on my english exam! It's working fine with $INFO! Sorry again wasting your time, really time for another Pp Bier!

[sualfred]

Everything is fine. Just relax, look at your code and bookmark the skinning manual

[bsoriano]

@sualfred,

I have been asked if I could open the info dialog for a specific movie or tv show from an onclick. I don’t think this is possible without using extendedinfo. Is this something you would consider adding to your script?

Here is my use case: In Amber, I use script.grab.fanart to grab random movie fanart or tv show fanart and show that as the background for a menu item, autoscrolling every x seconds. I provide the option of showing the title of the movie/tv show that is being shown. The request I received is if I could make that name clickable and open the info dialog for that movie or tv show. This as a way of answering the audience question of “what movie is that?”

script.grab.fanart does not provide me the DBID of the movie or tv show, but I guess even with my very limited knowledge of Python I could mod it to do that, unless you could provide me with a different idea.

So what do you think? Is this something that you think you would consider adding to your script?

Thanks for considering my request.

Regards,

Bart

[sualfred]

There is no way to call the info dialog like that. Only if you get rid of the script and use a dynamic container for it. One for tvshows and one for movies. Just make it fullsize, add nothing to itemlayout and add autoscroll to the container. So the focuseditem changes by itself as long it's not in focus by your cursor. As soon as you focus it somehow you can use the regular action(info) for it.

[bsoriano]

There is no way to call the info dialog like that. Only if you get rid of the script and use a dynamic container for it. One for tvshows and one for movies. Just make it fullsize, add nothing to itemlayout and add autoscroll to the container. So the focuseditem changes by itself as long it's not in focus by your cursor. As soon as you focus it somehow you can use the regular action(info) for it.

@sualfred , thanks! I think that is too much work for that particular use case. 

Regards,

Bart

[redglory]

Is still see no usecase for it because you can use the library node editor or directly the xsp method for it. Why would you even need to filter by path? Noone is using its Kodi library like that, or at least should not. Thats what tags, genres etc. are for.

Don't get me wrong, but adding little things without a real benefit makes something hard to maintain somewhere in the future. And this script is still mainly created for Embuary.

Just to clarify.

I had to use script.skin.helper.widgets filtered by path because my skin didn't give me the option to use a smartplaylist as a widget.

since I'm going to change skin It's an easy task

[sualfred]

Ok.

Anyway: https://github.com/sualfred/script.embua...the-script

If you ever feel the need to parse your own json requests to get custom results that are not possible with library nodes/smart playlists (like multiple AND/OR stacked filters).

[redglory]

Ok.

Anyway: https://github.com/sualfred/script.embua...the-script

If you ever feel the need to parse your own json requests to get custom results that are not possible with library nodes/smart playlists (like multiple AND/OR stacked filters).

Thanks for your support and attention