mrwatson-de
commented
1 year ago Added field to encapsulate logic of the type of 'fix' button, _kFixButtonType =
- "" = None // FindMode
- "" = None // Title
- 1 = [(i)] // Setting, no Write = read only info setting
- 0 = None // Setting, writable, don't Test
- 0 = None // Setting, writable, Test, Pass
- 3 = [Fix] // Setting, writable, Test, Fail, Write Priv.
- 2 = [GUI] // Setting, writable, Test, Fail, no Write Priv., GUI-Button
- 0 = None // Setting, writable, Test, Fail, no Write Priv., no GUI-Button
When is sitting his read-only setting the [(i)] button is fine, but in a writable setting in no-write mode, the [←] fix button with an arrow pointing to the left is confusing, because the user expects to it to fix the setting, but it only opens the GUI dialogue.
It would make more sense, if I'm this situation the GUI button was shown in its place - maybe with a tool tip to hint that writing is currently not allowed.