|
|
Hello, I have found the code which makes the artefacts on the screen. There is a callback method which is called when the button is pressed. In this callback I call the network function of a boost/asio library. This function writes data to the server. It is just boost::asio::async_write call. When I commented out this call, everything was OK - no artefacts at all. So the artefacts are generated by boost::asio::async_write. It's strange since my network library doesn't use FLTK at all!
--
You received this message because you are subscribed to the Google Groups "fltk.general" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkgeneral+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkgeneral/3d535d57-440a-40ab-a48c-607093feedd8n%40googlegroups.com.
[ Direct Link to Message ] | |
|
| |