David Tschumperlé

Maybe, did you activate the `cimg_use_zlib` macro when compiling your code ?

OK, thanks, that definitely helps. Still investigating...

Could you please try this : https://github.com/dtschump/CImg/commit/9a95c05805e59a4f0a65a2148a3217a9576bf891 ?

Well, here is my last attempt for today: https://github.com/dtschump/CImg/commit/766163fb864317aa9c65e5711e96fe7550011595 I don't think this will solve the problem anyway. It's hard, because I have to guess what is going on without...

Hello, back in the business :) I'd be actually interested by all the flags set by your compilation command, to reproduce the problem on my machine (then fix it more...

Well, just tried and many options seem to be not recognized by my version of the compiler (apparently it's cl 19.22.27905). At this point, I guess I need to update...

OK, some news: - I've spent some time tonight to update my version of Visual Studio 2019 (installed the Community Edition). - With it, I got the same warnings that...

I've pushed the current `develop` version to `master`, so it should be OK now. Thanks again for helping me solving this.

Hello. Your example works perfectly for me (Ubuntu 20.04). I compile with: ~~~ g++ -o foo foo.cpp -lX11 -lpthread ~~~ When you say it is generating an error, what kind...

Hello Matthijs, Indeed, we can say that the way CImgDisplay processes key events is 'rudimentary'. That's because I've never really needed to make complicated key detections so far with CImg....