Parent WObject parameter in WTimer single shot function
There should be a parameter that should take parent WObject parameter when creating a new WTimer to take the advantage of WObject's memory management and to avoid calling the callback function on a deleted object or avoid accessing deleted objects.
Updated by Wim Dumon almost 9 years ago
- Status changed from New to Feedback
In WObject there's an undocumented class DeletionTracker (in the usage example it's demonstrated to track this, but I believe it can track any WObject).
I'm thinking of something in that direction, but then generalized for use with every functor based connect, ideally in such a way that you can specify multiple tracked objects per connection. You want to be able to express this for any signal, not just for WTimer.