Right, you just don't have enough color control with Qt native widgets. What I did with iv (a Qt app) is make the main image canvas an OpenGL widget (I forget what that's called in Qt land, just look at the source), and just the image as a single texture-mapped quadrilateral. I could tell OpenGL whether the buffer was linear or sRGB, and use a GLSL program to transform the colors if not already in one of those spaces.
In a future enhancement hopefully this summer, we'll make OIIO (and iv in particular) OpenColorIO-aware, and that should do an even more careful job with color space management. On Jul 14, 2011, at 7:01 PM, Will Rosecrans wrote: > > Yeah, basically, Qt is completely ignorant of color spaces. If you > have some sort of really weird display color space other than sRGB, > you'll need to worry about that yourself. Most people draw images in > "basically sRGB" without knowing it isn't really linear, so if you > draw sRGB, you will almost always be consistent with other > applications. (Excepting something like Nuke where a user has > explicit control over the color space of a viewer. Then the user > might explicitly choose Rec.709 or whatever for display.) > _______________________________________________ > Oiio-dev mailing list > [email protected] > http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org -- Larry Gritz [email protected] _______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
