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
I am using the Xceed messagebox implementation for my app. I have noticed that dark windows color setting doesn't seem to work well with the message box depending on the color choice of the user.
For example here is title of my main application window.
You can see the background is pretty dark based on my color choice in windows 10 settings. The foreground has been inverted to match.
However this invert doesn't happen in Xceed MessageBox.
I posted this issue here because I use .NET core on my open source project and I don't want to wait X number of years to see something like this potentially fixed. Any chance you could look into this? I know there are algorithms to determine what color should be used for foreground.
As an addendum, I noticed that the error icon that is supposed to show up in this error message did not show up when I changed over to this fork.
The text was updated successfully, but these errors were encountered:
I am using the Xceed messagebox implementation for my app. I have noticed that dark windows color setting doesn't seem to work well with the message box depending on the color choice of the user.
For example here is title of my main application window.
You can see the background is pretty dark based on my color choice in windows 10 settings. The foreground has been inverted to match.
However this invert doesn't happen in Xceed MessageBox.
I posted this issue here because I use .NET core on my open source project and I don't want to wait X number of years to see something like this potentially fixed. Any chance you could look into this? I know there are algorithms to determine what color should be used for foreground.
As an addendum, I noticed that the error icon that is supposed to show up in this error message did not show up when I changed over to this fork.
The text was updated successfully, but these errors were encountered: