Gelldur
Java doesn't have destructor so when fragment/activity is on the stack it doesn't receive notifications but it still live. Sometimes fragment is only a component without any view.
Of course i can unregister there but as i sad. When activity is in background it doesnt receive events. I use API calls for EventBus so when user exits activity...
Thanks if something isn't straight forward then there is issue in design (bad design). If now I understand correctly your case. You want add this 'perk' to `eventBus` to pass...
As you describe. EventBus is just single bus. You can use "perks" to achieve something else like passing events from bus1 to bus2. You may just create your own wrapper...
Yes sure. It could be done.
@shenfumin I'm going to add: (brief example) ``` if(bus.wait()) { bus.consume(); } ``` So it will wait until event come in. Also can be `waitFor(10s)` as timeout
Hello For now there is no possibility to handle event per thread. As EventBus 3.0 you may only handle events on specific thread calling `EventBus::process()` but you shouldn't call process...
@geiseri yes you are right that was intention of `PassEverythingPerk` to have for example 2 event loops e.g. for logic and UI and pass events between those EventBus. I nned...
Hey, not sure now because everything what is on `development` branch I try to move to C++17. Sorry fot this inconsistency.