Open Aytackydln opened 1 year ago
This is an intended behavior - throwExceptions primarily meant as a debug-feature. If you want to listen to exceptions without them being thrown you should use the Exception
event instead. (You can also selectively throw using this event.)
Well using Exception event is the idea, actually. When initialized with throwExceptions Exception event isn't triggered. Maybe this should be a public property intead?
When initialized with throwExceptions Exception event isn't triggered.
this would be a bug, but i just checked everything and I don't see any reason why it should be fired. Are you sure that's the case?
Oh wait, it does but app crash is the problem but you only mean it to be used for debugging.
Using throwExceptions true makes my code cleaner, though.
Problem: When provider is initialized with throwExceptions = true, UpdateQueue throws exceptions in thread-pool and crashes application
Hopefully this is an acceptable solution.