Posts: 3,532
Joined: Oct 2013
Reputation:
357
That's a info label and no runscript command. Read the embuary info wiki how to do a call
Main: Lancool II Mesh - Ryzen 9 5900x - MSI x570 Unify - Zotac RTX 3080 AMP HOLO - 32GB Trident Z Neo 3600 CL16 - EVO 960 M.2 250GB / EVO 940 250GB / MX100 512GB / Crucial P1 2TB / WD Blue 3D Nand 2TB
Sound: Saxx AS30 DSP - Beyer Dynamic Custom One Pro
TV: Nvidia Shield 2019 Pro- Adalight 114x LEDs - Sony 65XG9505 - Kodi / Emby - Yamaha RX-V683 - Heco Victa 700/101/251a + Dynavoice Magic FX-4
Server: i3 Skylake - 8GB - OMV4 - 22TB Storage
Posts: 3,532
Joined: Oct 2013
Reputation:
357
2021-07-10, 16:30
(This post was last modified: 2021-07-10, 16:33 by sualfred.)
The video info dialog action is a kodi builtin feature, that's why there is no onclick command. The Kodi core knows what to do with it because of it's in core defined ID and it's action. That's not the case for your custom window. A custom window is a custom window with no core relation. All actions in there have to be assigned by yourself. That also applies to features to other availabe core windows which have no included action.
If you want to call for tmdb info of one of the directors -> use the embuary info script
For searching -> use the globalsearch script
For more information about the skinning engine works, please take a look at the official Kodi wiki or - like I learned it - study other skins how they achieve something. Learning with a working example always worked best for me in the beginning stage.
Main: Lancool II Mesh - Ryzen 9 5900x - MSI x570 Unify - Zotac RTX 3080 AMP HOLO - 32GB Trident Z Neo 3600 CL16 - EVO 960 M.2 250GB / EVO 940 250GB / MX100 512GB / Crucial P1 2TB / WD Blue 3D Nand 2TB
Sound: Saxx AS30 DSP - Beyer Dynamic Custom One Pro
TV: Nvidia Shield 2019 Pro- Adalight 114x LEDs - Sony 65XG9505 - Kodi / Emby - Yamaha RX-V683 - Heco Victa 700/101/251a + Dynavoice Magic FX-4
Server: i3 Skylake - 8GB - OMV4 - 22TB Storage