+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Discussions (https://forum.kodi.tv/forumdisplay.php?fid=222)
+--- Forum: Feature Requests (https://forum.kodi.tv/forumdisplay.php?fid=9)
+--- Thread: Solved Move Autohide OSD from System Settings to Skin (Estuary) Settings (/showthread.php?tid=367983)
Move Autohide OSD from System Settings to Skin (Estuary) Settings - _BJ1 - 2022-04-23
This setting has to be skin related - not system related. Some skins open additional (custom) windows when users take some action on OSD buttons (e.g. extended Info or PVR plot and more). These windows will be stayed on screen when video OSD is auto hide by system.
Some skins take care of those additional windows when autoclosing player osd (e.g. Arctic Zephyr or Estuary >Mod V2). An example for this is the custom window 1110 (Custom_1110_CloseVideoOSD.xml) of Estuary ModV2: https://github.com/b-jesch/skin.estuary.modv2/blob/Nexus/xml/Custom_1110_CloseVideoOSD.xml
RE: Move Autohide OSD from System Settings to Skin (Estuary) Settings - Hitcher - 2022-04-23
It is in Skin settings.
RE: Move Autohide OSD from System Settings to Skin (Estuary) Settings - _BJ1 - 2022-04-23
This has to be a setting of the skin itself, not a setting of the interface. For now these setting affects to all skins and violates there own settings.
RE: Move Autohide OSD from System Settings to Skin (Estuary) Settings - Hitcher - 2022-04-23
Ah I see what you mean now. I guess it should really close all open dialogs as well.
RE: Move Autohide OSD from System Settings to Skin (Estuary) Settings - enen92 - 2022-04-24
I got to the same conclusion as the OP short after the PR went in. Issued a new PR to revert that change (https://github.com/xbmc/xbmc/pull/21308) and will try to come up with an alternative before nexus is final.
Thanks for the heads up.
Move Autohide OSD from System Settings to Skin (Estuary) Settings - enen92 - 2022-05-05
This is being now proposed as an alternative implemented in estuary: https://github.com/xbmc/xbmc/pull/21355
Might take a bit of time to go in due to the other PRs it depends on. Also, the main underlying feature is still WIP while use cases just like this one are stress testing and validating the implementation.