Scott

The example code captures the while monitor, parts of the monitor. I try to run through a couple of scenarios. The base case https://github.com/smasherprog/screen_capture_lite/blob/47defa25fd20048874f78b230a2bed17777eade2/Example_CPP/Screen_Capture_Example.cpp#L408 Should get you the whole monitor

Yes thats correct. The mouse image is separate. Otherwise you would need to receive and handle an entire image of everything just because the mouse moved. So your application should...

Perfect so thats correct. There are 3 callbacks })->onFrameChanged([&](const SL::Screen_Capture::Image& img, const SL::Screen_Capture::Monitor& monitor) { })->onNewFrame([&](const SL::Screen_Capture::Image& img, const SL::Screen_Capture::Monitor& monitor) { })->onMouseChanged([&](const SL::Screen_Capture::Image* img, const SL::Screen_Capture::MousePoint &mousepoint) { })->start_capturing();...

onFrameChanged WIll always start with the FULL IMAGE, then call you back sending only CHANGES. So, in theory, you can just use that for your purposes

The idea with the pieces is that you send only those and you can stitch them together on the other side. If you know that you are going to send...

Sending a 4k res pic on at a decent framerate will generate significant network throughput even with good compression. So, be carefull

Gonna close this as working as expected unless you have some additional info?

I might be able to do this. For android it would be more of an example because the capturing has to happen in java. For ios, i am unsure and...

I agree. there was a weird state where some compilers didnt support the new c++ version so i left it. If you want to give a stab at a PR,...

Ill keep the PR until the other compilers catch up to Visual studio..... Never thought I'd say that..