Shoutbox

While I am trying to apply registry settings about colors, I think I found a bug. Because the registry entries for colors doesn't use RGB colorref values but it uses BGR (!) values. For example yellow's hex value must be FFFF00, however in registry we have to use 00FFFF to apply yellow. Because if we write FFFF00 in the registry, it is aquamarine color, not yellow. Even, if we set yellow from prefences panel, for example for floating desktop contacts windows' background, then that color's value is registered as 00FFFF in registry. If you say this is intended behaviour then there is a problem with TabChatFlashColor entry. Because it uses the true RGB values, I mean, the problem I mentioned above isn't valid  for that value. If we write the correct RGB value FFFF00 for yellow, then tabs flash with yellow color. Please fix the first problem, if it is not a problem, then fix the second problem with TabChatFlashColor.

Do you use an RTL version of MP!L? That could be one explination (I think)

It is stored as a COLORREF, which is in BGR format. This is completely normal and not a bug. Most applications use this as their color format.

quote:

---

Originally posted by SpunkyLoveMuff
Do you use an RTL version of MP!L? That could be one explination (I think)

---

No, I use LTR Plus! and I don't think it is related to Windows registry in any way.

quote:

---

Originally posted by deAd
It is stored as a COLORREF, which is in BGR format. This is completely normal and not a bug. Most applications use this as their color format.

---

I checked Windows Live Messenger's registry entry "IM Color" after setting my font color to yellow and I saw it is stored as RGB in it too (FFFF00). So I decided to post this thread however I am still not that sure of it.

In fact there would be no that big problem if Plus! didn't offer registry settings. However while setting these settings in registry people must know they must use BGR values.

If your statement is true, then TabChatFlashColor must use BGR values too in terms of consistency I think we both agree on this.

I'll correct the documentation for the registry entries... the reason for this is that ARGB is encoded the opposite way to RGB and some values are ARGB, some others are not .

Thanks for reporting.

*Reminder bump*

Still not corrected