+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111)
+---- Forum: OS independent / Other (https://forum.kodi.tv/forumdisplay.php?fid=228)
+---- Thread: Discussion: Video view modes & zoom control changes and issues (since Kodi 18) (/showthread.php?tid=377554)
Discussion: Video view modes & zoom control changes and issues (since Kodi 18) - axbmcuser - 2024-05-16
Hi,
seems like there have been fundamental changes to video view modes, zoom control, vertical shift and pixel ratio handling introduced in Kodi 18 which are seemingly still present in latest 22 nightlies.
Maybe it's "just" an UI regression of some sort. Don't really know at this time.
Example Kodi 17:
- Setting a custom video zoom value, vertical shift and/or pixel ratio
- "View mode" changes to "Custom" while doing that
- User sets "View mode" back to "Normal", resets all 3 values to their default, which somehow feels like expected from a users point of view
Example Kodi 18-22:
- Setting a custom video zoom value, vertical shift and/or pixel ratio
- "View mode" changes to "Custom" while doing that
- User sets "View mode" back to "Normal", all 3 values (zoom/vertical shift/pixel ratio) stay on their custom values, which really feels weird from a user perspective.
See:
In fact changing "View mode" to anything else - the user set values always persist. Even when choosing special modes like "Zoom - 120% width", which especially looks weird in combination:
Bonus issue, maybe related:
On Kodi 18+, while laboriously resetting a value to it's default by hand, i encountered values like "-0.00" for vertical shift. (negative zero)
Any idea?
What were the changes introduced in Kodi 18 in this area?
Did not find a corresponding PR.
Just wanted to potentially gather some info before raising an issue on github for this.
Thanks!
RE: Discussion: Video view modes & zoom control changes and issues (since Kodi 18) - scott967 - 2024-05-17
The current implementation lets you toggle between "custom" and "normal", with "custom" retaining the user-set values. I don't see "normal" as intending a "reset to default values". I suppose a discrete "reset" option could be added as a feature request. As far as -0.00, don't see that as a functional issue?
scott s.
.