|
|
On 7 Jul 2022, at 15:10, Jck_01 wrote:
>
> 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!
That sounds most curious - if the async call is not interacting with fltk at all, I’d expect it to be “safe”, so this is unexpected. Does it (the async method) interact with the GUI context in some way, or something?
It might be useful if you could show us the code for the callback, in case something useful occurs to anyone on seeing it...
--
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/0EC5AAF2-9053-44C6-B19D-3778EF42A7A2%40gmail.com.
[ Direct Link to Message ] | |
|
| |