2023-02-28, 01:24
@Hitcher - Your syntax is wrong for query. It is just
https://github.com/jurialmunkey/plugin.v...parameters
https://github.com/jurialmunkey/plugin.v...ons-Dialog
Also, if you're passing a label instead of an ID you might run into issues if the names of your actors have unusual unicode characters.
You can get around this by using the $WINPROP method with single quotes around $ESCINFO of the label:
ALTERNATIVE METHOD:
Note that you don't need to use the scripted recommendations window. You can use a native Kodi custom dialog instead and then simply add normal containers of items to it.
e.g. Say you create a custom dialog with ID 1120 to act as a recommendations dialog for people. You can open from info (or anywhere) by setting the path you want as a window property and then using it as content in the custom dialog:
Then you can use this method of replacing window manager for extended info instead. This approach is where add_query/add_path are used.
https://github.com/jurialmunkey/plugin.v...ended-Info
Advantage of this "native" method is that has no scripted windows. The only script running is the window manager which keeps track of info dialog history for the purpose of backtracking (back from info dialog opens previous info dialog in history) but you only need to use that if you want that "extendedinfo" type experience where you can navigate "through" the recommendations to new info dialogs.
The individual lists take a bit longer to load initially if you're loading several but everything functions exactly how you expect a normal custom dialog to function which is a huge advantage. Basically the "native" version sacrifices speed for a more flexible and a straightforward approach; whereas the "scripted" version is fast but less flexible and more complex.
query= not add_query=https://github.com/jurialmunkey/plugin.v...parameters
https://github.com/jurialmunkey/plugin.v...ons-Dialog
Also, if you're passing a label instead of an ID you might run into issues if the names of your actors have unusual unicode characters.
You can get around this by using the $WINPROP method with single quotes around $ESCINFO of the label:
xml:
<ondown>SetProperty(TMDbHelper.WinProp.Title,'$ESCINFO[Container(50).ListItem.Label]',Home)</ondown>
<ondown>Runscript(plugin.video.themoviedb.helper,recommendations=10052|info=stars_in_movies|true|info,query=$WINPROP[Title],tmdb_type=person,window_id=1113)</ondown>
ALTERNATIVE METHOD:
Note that you don't need to use the scripted recommendations window. You can use a native Kodi custom dialog instead and then simply add normal containers of items to it.
e.g. Say you create a custom dialog with ID 1120 to act as a recommendations dialog for people. You can open from info (or anywhere) by setting the path you want as a window property and then using it as content in the custom dialog:
xml:
<!-- From Info Dialog -->
<ondown>SetProperty(TMDbHelper.StarsInMovies,plugin://plugin.video.themoviedb.helper/?info=stars_in_movies&tmdb_type=person&query=$INFO[Container(50).ListItem.Label],Home)</ondown>
<ondown>ActivateWindow(1120)</ondown>
<!-- In Container in Dialog 1120 -->
<control type="list" id="1234">
<content>$INFO[Window(Home).Property(TMDbHelper.StarsInMovies)]</content>
<!-- Optional onclick for opening a new info dialog -->
<!-- Note this is where "add_query" comes into play -->
<onclick>Close</onclick>
<onclick>RunScript(plugin.video.themoviedb.helper,add_path=$INFO[Container(1234).ListItem.FolderPath],call_auto=1190)</onclick>
</control>
Then you can use this method of replacing window manager for extended info instead. This approach is where add_query/add_path are used.
https://github.com/jurialmunkey/plugin.v...ended-Info
Advantage of this "native" method is that has no scripted windows. The only script running is the window manager which keeps track of info dialog history for the purpose of backtracking (back from info dialog opens previous info dialog in history) but you only need to use that if you want that "extendedinfo" type experience where you can navigate "through" the recommendations to new info dialogs.
The individual lists take a bit longer to load initially if you're loading several but everything functions exactly how you expect a normal custom dialog to function which is a huge advantage. Basically the "native" version sacrifices speed for a more flexible and a straightforward approach; whereas the "scripted" version is fast but less flexible and more complex.