Communicate_between_two_fragments_via_interface.txt

# getting-started

[ivano]

Communicate_between_two_fragments_via_interface.txt

Communicate_between_two_fragments_via_interface.txt

[marchuck]

why just use 2 regular activities instead?

[ivano]

no they are in two different activities

[ivano]

I need to call the "MainFragment" to refresh the view

[ivano]

and so i need a callback in the Second Fragment to say, hey close this fragment and activity.supportFragmentManager.popBackStack() and refresh the widget in the MainFragment

[marchuck]

you can get access to specific fragment from activity like

val fragments = activity.supportFragmentManager.fragments
for f in fragments{
if f is InterfaceSomething{
f.doThatThing()
}
}

[ivano]

I cannot use the activity, in my use case

[ivano]

communication have to be between fragments because of the architecture choice

[marchuck]

are you also using some sort of event bus or rxjava?

[ivano]

rxjava2

[marchuck]

ok, then you can easily introduce Rx based publish-subscribe pattern

https://blog.mindorks.com/implementing-eventbus-with-rxjava-rxbus-e6c940a94bd8

[ivano]

thank you

[marchuck]

one fragment can send events, and other one listens

[ivano]

looks good thanks

[marchuck]

btw, what architecture do you use? I wonder there's cleaner approach ...

[ivano]

MVVM

[ivano]

I have an overview that communicates with 3 other fragments

[marchuck]

ok, I see. so you can create singleton dependency with a RxBus structure and inject for each viewmodels

[ivano]

do you have a link?