Details
-
User Story
-
Resolution: Unresolved
-
P2: Important
-
None
-
QDS Berlin - 2023 Week 11/12, QDS Berlin - 2023 Week 15/16, QDS Berlin - 2023 Week 17/18, QDS Berlin - 2023 Week 19/20
Description
- The current theme ignores drawing toolbar separators (It just keeps the space). Is it the right behavior? If not, a color and display width should be considered for that.
- There are some unhandled push buttons. e.g. QMessageBox buttons. Should we leave them to be painted by the native style? If not, how should they look like? I think they should be different from prominent buttons.
- Scrollbars are also left to be painted by the native style.
- Should we force QWidget + buttons to be the same as Qml + buttons? They look different, in font and style.
- A standard palette is considered for unhandled situations in the style. In special cases, some mid-level colors are required. I put something there, but it would be nice to have the exact colors for them. These color roles are as follows:
-
- Control – Light Color: This should be lighter than the button color.
- Control – Dark Color: This should be darker than the button color.
- Control – Mid Color: This should be something between the control light color and the control dark color. Maybe keeping this the same as the button color is not a bad Idea.
- It's good to update theme colors so that we can use the correct names in the style. e.g. I used DStoolbarIcon_blocked for the standard palette to get the base and window color in the disabled state, and DStoolbarBackground for the active state.
- DStextColorDisabled is used for disabled text color on the Qml side. Should we use this color in the studioStyle as well? Because this color is not used on the QWidget side yet. But we can use it.
- A backspace icon/iconFont is required because we draw that in the code, and it's not a good idea to keep it there.