>>21
I don't actually use CImg in my programs. I do my critical, speed-limiting processing with a few custom functions, along with high-quality libraries such as FFTW for the
ÜBER-OPTIMIZED stuff, and I use Qt and
raw OpenGL for the GUI/display. I have also used VTK and ITK for the crazier stuff like segmentation and volumetric rendering of medical data.
CImg is
slow as fuck and limited, but it's easy to use and a very quick way to get a
DQN PROGRAMMER to display his shitty image. A bit like you'd use Matlab to check out some data and validate your algorithm before spending 9001 hours on a C++ implementation.
IHBT and I feel kind of bad about it :(