2015-10-28, 22:31
I'd like to request 2 features that can help custom window scriptwriters.
1). VideoFullScreen.xml spoofing - A way to falsely report the below while using a custom window.
Reason being, code that is or is not designed to run at full-screen is ignored when running a custom window. It's more sensible for the custom window coder to control this, rather then request support from each individual developer (case in point: http://forum.kodi.tv/showthread.php?tid=...pid2144909)
Something like?
2). Kodi custom window override, Kodi skin xml's take priority over plugin windows. For example if a Kodi skinner includes a custom window xml for a plugin, that plugin has no control... This is problematic when the skins included version is missing controls recently added to the plugin.
If any of the two are currently possible please forgive my naiveté , a solution would be great.
Thank You
1). VideoFullScreen.xml spoofing - A way to falsely report the below while using a custom window.
Code:
Window.IsActive(VideoFullScreen.xml)Reason being, code that is or is not designed to run at full-screen is ignored when running a custom window. It's more sensible for the custom window coder to control this, rather then request support from each individual developer (case in point: http://forum.kodi.tv/showthread.php?tid=...pid2144909)
Something like?
Code:
Window.SetBool(Window.IsActive(VideoFullScreen.xml), true)2). Kodi custom window override, Kodi skin xml's take priority over plugin windows. For example if a Kodi skinner includes a custom window xml for a plugin, that plugin has no control... This is problematic when the skins included version is missing controls recently added to the plugin.
If any of the two are currently possible please forgive my naiveté , a solution would be great.
Thank You
