- DietPi-Display | The tool does now always show those settings previously applied, and reads the sysfs API only for settings which were not explicitly saved earlier. Previously, to faster detect non-functional settings and inconsistencies, even if settings were previously stored to the kernel command-line, the tool always read all values for enabled and connected displays from the sysfs API. This however means that when applying settings, exiting and restarting the tool, the previously applied settings are not shown anymore, and more importantly, all shown possibly different values were applied when changing only one setting. In the meantime, we know about inconsistencies when managing multiple displays, that e.g. on Raspberry Pi the rotation applied to one display, applies to all onboard display ports, and that the list of nodes from the sysfs API is neither consistently sorted, nor complete, entries can miss parameters, leading to duplicates, and on Raspberry Pi all modes with resolutions above the current one are simply missing. It makes more sense to consequently show those settings explicitly applied, and it can be seen on the display(s) whether/in how far they work or not. Many thanks to @adshrc again for the follow-up report.
0 commit comments