You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ConfirmationDialog does not show a section for theme override. This is really confusing because the user would expect the internal panel of the confirmation dialog to have the color of the set theme which is not the case, as internally, the override is set anyways. Interestingly, an AcceptDialog (parent in the inhertiance chain) shows the section in the inspector properly (see screenshots below).
Steps to reproduce
Create ConfirmationDialog in editor and go to inspector, theme overrides will be missing.
The unexpected output can be seen in the remote node hierarchy. Navigate to the ConfirmationDialog and find the internal panel child. It will have a theme override applied:
Minimal reproduction project (MRP)
Not necessary
The text was updated successfully, but these errors were encountered:
Yes it is confusing. I find that add the same setting as AcceptDialog for ConfirmationDialog in default_theme.cpp can make the ui appear again, but I'm not sure whether it's the correct way of fixing this.
Tested versions
System information
Manjaro Linux (KDE)
Issue description
ConfirmationDialog
does not show a section for theme override. This is really confusing because the user would expect the internal panel of the confirmation dialog to have the color of the set theme which is not the case, as internally, the override is set anyways. Interestingly, anAcceptDialog
(parent in the inhertiance chain) shows the section in the inspector properly (see screenshots below).Steps to reproduce
Create
ConfirmationDialog
in editor and go to inspector, theme overrides will be missing.The unexpected output can be seen in the remote node hierarchy. Navigate to the ConfirmationDialog and find the internal panel child. It will have a theme override applied:
Minimal reproduction project (MRP)
Not necessary
The text was updated successfully, but these errors were encountered: