Hal V. Engel wrote:
Since it is a compiz plug in calibration and profiling can be done by disabling the plug in before doing these operations. Disabling and enabling plug ins is a very simple operation for users. I believe that this plug in is derived from an OpenICC Google Summer of Code 2008 project. If so it does use the GPU shaders to do the work.
Right, but such a thing is poor U/I, just another thing to go wrong. The pluggin should recognise a window property (something like "_NET_WM_WINDOW_NO_CM") that the calibration application would set, so that it doesn't matter if the user forgets to disable the pluggin. Applications managing their own CM would set the same. Of course, there should also be properties that can set the source profile per window, or provide a device link per window (perhaps the pluggin already handles these.) cheers, Graeme Gill.