The optimisation depth is a parameter that affects the performance of the software. It's set to a default value but can be changed in the GUI (or CLI).
Issue
Understanding the parameter requires a good understanding of the octree-based optimisation. It can be obtuse to new users, who may either feel intimidated or compelled to change it.
Proposed change
The widget should be made less accessible in the GUI, so that only users who are confident in their understanding will change the parameter. This could be done in several different ways:
by greying out the widget and adding a checkbox labelled "I know what I'm doing" or similar
by replacing the widget with a checkbox labelled "Allow changing optimisation depth" or similar, that - once checked - disappears and reveals the current widget
by adding an "Advanced Options menu". This may be overkill for a single option
by greying out the widget and making it possible to enable it from the menu bar. This may also be overkill, but a menu bar may also become useful in the future. There is a comprehensive guide for menu bars for macOS.
Improvement
This change will avoid confusion for users that do not understand the optimisation depth parameter.
Current status
The optimisation depth is a parameter that affects the performance of the software. It's set to a default value but can be changed in the GUI (or CLI).
Issue
Understanding the parameter requires a good understanding of the octree-based optimisation. It can be obtuse to new users, who may either feel intimidated or compelled to change it.
Proposed change
The widget should be made less accessible in the GUI, so that only users who are confident in their understanding will change the parameter. This could be done in several different ways:
Improvement
This change will avoid confusion for users that do not understand the optimisation depth parameter.