Jump to content
Completely agree with and share the same frustrations on this update.
The majority are more accustomed to using RGB. Supporting 16-32bit hardly seems urgent right now. Certainly not enough to introduce such a change in this manner. If I want to use RGB, I should be able to use RGB. As suggested above, it would have made perfect sense to introduce a setting for using RGB or HD color space (RGB being the Default) and leaving the methods as-is.
With regards to the V1 compatibility mode -- suggesting the use of that is hardly a solution. It's a temporary workaround to avoid breaking code because this change was not rolled out better. It'll be an expired workaround eventually. And when that happens, the expectations are for all developers to migrate to the HD color space and drop RGB altogether? Does anyone really want that?
I would like to see this revisited. I don't agree with this change being the "best decision" and seems like the majority here would agree.
Community Forum Software by IP.Board