|
|
Wouldn’t using std::unique_ptr interfere with FLTK’s parent/child ownership system. If a unique_ptr fell out if scope it would call delete on the pointer and this might lead to issues.
Sent from my iPhone On 6 Jul 2022, at 18:04, Jck_01 <projektantgier@gmail.com> wrote:
I was rather hoping to dee more of your widget code and in particular
what you are doing for draw() methods, that sort of thing.
I don't use any draw() methods, just ordinary creation of controls like buttons etc. Nothing special at all.
How many threads are in your code?
Generally only one. The code in dialog windows uses one, main program thread. A new thread is created only when I call methods of network library. Could it be the reason of artefacts?
Some of what you are seeing looks a lot like it might be thread
related rendering artefacts, if the code is not thread safe (though
that's just a guess as there's not really enough here to know.)
--
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/12b02a13-f934-4f1d-bd94-6a15501de17dn%40googlegroups.com.
--
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/BF1C546B-CC5C-4B51-9DC7-3098BC3F1B16%40gmail.com.
|
[ Direct Link to Message ] | |
|
| |