Does the Android ICS API have a native equivalent to ViewPager support lib? No. I know about ViewPager and all the support libs for earlier version but i don’t get why I should use a support library consider the fact that I use the lastest version of the api and don’t plan to support earlier … Read more
There are 3 ways to pass objects to a fragment They are: Passing the object through a setter is the fastest way, but state will not be restored automatically. setArguments with Serializable objects is the slowest way (but okay for small objects, I think) and you have automatic state restoration. Passing as Parcelable is a … Read more
I saw this when I was having similar problems and just thought Id drop a quick note. Rather than creating a dummy fragment in order to replace the existing one I think you should animate the current fragments view. When the animation finishes you can simply remove the fragment. This is how i did it: … Read more
I suggest that this is the correct behaviour. The 302 and 307 status codes indicate that the resource is to be found elsewhere. #bookmark is a location within the resource. Once the resource (html document) has been located it is for the browser to locate the #bookmark within the document. The analogy is this: You … Read more
IMHO I do not agree with this answer. You may want to replace your fragment or you may want to add it. For example let’s say that you are in a fragment that is a list retrieved by a network request, if you replace the fragment with let’s say the detailFragment and you add it … Read more
Aromero, Don’t forget to override the onCreateOptionsMenu using the fragment version of the method, similar to this: @Override public void onCreateOptionsMenu (Menu menu, MenuInflater inflater) { inflater.inflate(R.menu.queue_options, menu); super.onCreateOptionsMenu(menu, inflater); } This goes in the fragment, by the way, and adds to the inflated menu of the Activity, if there is one. Had the same … Read more
If I understand correctly you mean : Is there any reason NOT to indiscriminately do this without re-evaluating each individual case where I use a fragment? The answer is Yes – you should not do this without carefully re-evaluating each individual case where you use a fragment. Of course, by preventing restarts due to config … Read more
If I understand correctly you mean : Is there any reason NOT to indiscriminately do this without re-evaluating each individual case where I use a fragment? The answer is Yes – you should not do this without carefully re-evaluating each individual case where you use a fragment. Of course, by preventing restarts due to config … Read more
To solve this, if you are using android.app.DialogFragment, then use getFragmentManager(): mDateButton.setOnClickListener(new View.OnClickListener() { public void onClick(View v) { FragmentManager fm = getActivity().getFragmentManager(); DatePickerFragment dialog = new DatePickerFragment(); dialog.show(fm, DIALOG_DATE); } }); to use getSupportFragmentManager(), must extend from: android.support.v4.app.DialogFragment. check your import: import android.support.v4.app.DialogFragment;
Since version 25.2.0 of Android support library, the class FragmentManager.FragmentLifecycleCallbacks is static and accessible to all. We can now use an instance of that class and register it in the supportFragmentManager of the Activity. public class ExampleActivity extends AppCompatActivity { public void onCreate(Bundle savedInstaceState) { // initialization code getSupportFragmentManager() .registerFragmentLifecycleCallbacks(new FragmentManager.FragmentLifecycleCallbacks() { @Override public void … Read more