There are some things, which should be exposed through user-specific settings. This is an additional feature beyond the core functions of the application, thus, it is not part of the v2 milestone.
This issue tracks the places, where a user-specific setting is beneficial / desired.
[ ] the inputDebounceDelay of the ColorFormInputMethod class
[ ] which method is used to display the colors
This will be a major effort, possibly worth a dedicated issue!
Idea: All elements that are created to display a color have a dedicated class. Somewhere in the beginning of the DOM hierarchy, a class is set, controlling the method and setting the color is then handled in CSS by custom properties.
[ ] precision: Several input methods can operate on decimal numbers / floats. Should this be exposed? Should this be a dynamic thing, meaning that the the precision may be adjusted while using the application?
[ ] all rounding operations should be performed as late as possible (when the value is actually displayed!)
[ ] see roundToPrecision() in src/script/utility/index.ts
There are some things, which should be exposed through user-specific settings. This is an additional feature beyond the core functions of the application, thus, it is not part of the v2 milestone.
This issue tracks the places, where a user-specific setting is beneficial / desired.
inputDebounceDelay
of theColorFormInputMethod
class[ ] which method is used to display the colors
precision
: Several input methods can operate on decimal numbers / floats. Should this be exposed? Should this be a dynamic thing, meaning that the the precision may be adjusted while using the application?roundToPrecision()
insrc/script/utility/index.ts