Mixing
Android ViewPager don't reload after Bottom navigation replace fragments
I have Activity contains of bottom navigation bar and FrameLayout as container to replace fragments. the first fragment has View Pager of 2 fragments (Map, ListView).
the second fragment is normal layout of text views and buttons.
When I move using bottom navigation bar the fragment didn't reload the viewPager (map and List view are white pages) even the view pager tablayout is shown.
@Override
public boolean onNavigationItemSelected(@NonNull MenuItem item) {
switch (item.getItemId())
{
case R.id.action_addOffer:
FragmentTransaction ft = getSupportFragmentManager().beginTransaction();
ft.replace(R.id.container, new MyMealFragment());
ft.commit();
break;
case R.id.action_map:
FragmentTransaction ft = getSupportFragmentManager().beginTransaction();
ft.replace(R.id.container, new Map2Fragment());
ft.commit();
break;
}
return true;
}
I tried also to add, hide fragments but didn't word. I relized also that the app started to be very slow when I back to the first fragment.
Any idea ??
UPDATE(Solution)
The problem was because of nested fragments
I changed the View Pager adapter to have getChildFragmentManager() as constructor parameter
ViewPagerAdapter adapter = new ViewPagerAdapter(getChildFragmentManager());
android google-maps 
android-fragments android-activity android-viewpager asked Nov 22 '18 at 1:59
Khaled HayekKhaled Hayek
1042316
add a comment |
I have Activity contains of bottom navigation bar and FrameLayout as container to replace fragments. the first fragment has View Pager of 2 fragments (Map, ListView).
the second fragment is normal layout of text views and buttons.
When I move using bottom navigation bar the fragment didn't reload the viewPager (map and List view are white pages) even the view pager tablayout is shown.
@Override
public boolean onNavigationItemSelected(@NonNull MenuItem item) {
switch (item.getItemId())
{
case R.id.action_addOffer:
FragmentTransaction ft = getSupportFragmentManager().beginTransaction();
ft.replace(R.id.container, new MyMealFragment());
ft.commit();
break;
case R.id.action_map:
FragmentTransaction ft = getSupportFragmentManager().beginTransaction();
ft.replace(R.id.container, new Map2Fragment());
ft.commit();
break;
}
return true;
}
I tried also to add, hide fragments but didn't word. I relized also that the app started to be very slow when I back to the first fragment.
Any idea ??
UPDATE(Solution)
The problem was because of nested fragments
I changed the View Pager adapter to have getChildFragmentManager() as constructor parameter
ViewPagerAdapter adapter = new ViewPagerAdapter(getChildFragmentManager());
asked Nov 22 '18 at 1:59
Khaled HayekKhaled Hayek
1042316
1
I think the problem is whenever the fragment switched, you create a new instance of fragment. Try reusing the fragments
– Eric Marcelino
Nov 22 '18 at 2:08
add a comment |
I have Activity contains of bottom navigation bar and FrameLayout as container to replace fragments. the first fragment has View Pager of 2 fragments (Map, ListView).
the second fragment is normal layout of text views and buttons.
When I move using bottom navigation bar the fragment didn't reload the viewPager (map and List view are white pages) even the view pager tablayout is shown.
@Override
public boolean onNavigationItemSelected(@NonNull MenuItem item) {
switch (item.getItemId())
{
case R.id.action_addOffer:
FragmentTransaction ft = getSupportFragmentManager().beginTransaction();
ft.replace(R.id.container, new MyMealFragment());
ft.commit();
break;
case R.id.action_map:
FragmentTransaction ft = getSupportFragmentManager().beginTransaction();
ft.replace(R.id.container, new Map2Fragment());
ft.commit();
break;
}
return true;
}
I tried also to add, hide fragments but didn't word. I relized also that the app started to be very slow when I back to the first fragment.
Any idea ??
UPDATE(Solution)
The problem was because of nested fragments
I changed the View Pager adapter to have getChildFragmentManager() as constructor parameter
ViewPagerAdapter adapter = new ViewPagerAdapter(getChildFragmentManager());
asked Nov 22 '18 at 1:59
Khaled HayekKhaled Hayek
1042316
I have Activity contains of bottom navigation bar and FrameLayout as container to replace fragments. the first fragment has View Pager of 2 fragments (Map, ListView).
the second fragment is normal layout of text views and buttons.
When I move using bottom navigation bar the fragment didn't reload the viewPager (map and List view are white pages) even the view pager tablayout is shown.
@Override
public boolean onNavigationItemSelected(@NonNull MenuItem item) {
switch (item.getItemId())
{
case R.id.action_addOffer:
FragmentTransaction ft = getSupportFragmentManager().beginTransaction();
ft.replace(R.id.container, new MyMealFragment());
ft.commit();
break;
case R.id.action_map:
FragmentTransaction ft = getSupportFragmentManager().beginTransaction();
ft.replace(R.id.container, new Map2Fragment());
ft.commit();
break;
}
return true;
}
I tried also to add, hide fragments but didn't word. I relized also that the app started to be very slow when I back to the first fragment.
Any idea ??
UPDATE(Solution)
The problem was because of nested fragments
I changed the View Pager adapter to have getChildFragmentManager() as constructor parameter
ViewPagerAdapter adapter = new ViewPagerAdapter(getChildFragmentManager());
asked Nov 22 '18 at 1:59
Khaled HayekKhaled Hayek
1042316
asked Nov 22 '18 at 1:59
Khaled HayekKhaled Hayek
1042316
edited Nov 22 '18 at 2:38
Khaled Hayek
asked Nov 22 '18 at 1:59
Khaled HayekKhaled Hayek
1042316
asked Nov 22 '18 at 1:59
Khaled HayekKhaled Hayek
1042316
asked Nov 22 '18 at 1:59
Khaled HayekKhaled Hayek
1042316
1042316
1
I think the problem is whenever the fragment switched, you create a new instance of fragment. Try reusing the fragments
– Eric Marcelino
Nov 22 '18 at 2:08
add a comment |
1
I think the problem is whenever the fragment switched, you create a new instance of fragment. Try reusing the fragments
– Eric Marcelino
Nov 22 '18 at 2:08
1
1
I think the problem is whenever the fragment switched, you create a new instance of fragment. Try reusing the fragments
– Eric Marcelino
Nov 22 '18 at 2:08
I think the problem is whenever the fragment switched, you create a new instance of fragment. Try reusing the fragments
– Eric Marcelino
Nov 22 '18 at 2:08
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53422879%2fandroid-viewpager-dont-reload-after-bottom-navigation-replace-fragments%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53422879%2fandroid-viewpager-dont-reload-after-bottom-navigation-replace-fragments%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
I think the problem is whenever the fragment switched, you create a new instance of fragment. Try reusing the fragments
– Eric Marcelino
Nov 22 '18 at 2:08