【Android】SnackBar

ref:
http://stackoverflow.com/questions/30569705/android-snackbar-nullpointerexception-in-fragment
http://williammora.com/snackbar-android-library/

【Android】How to create a common class for alertDialog Box

ref:http://stackoverflow.com/a/8585364

Create a class like CustomDialog.class,

and inside of it create a static method like the one below,

 public static void ExitAppDialog(final Activity activity)
 {
     AlertDialog.Builder alertbox = new AlertDialog.Builder(activity);
     alertbox.setTitle("Warning");
     alertbox.setMessage("Exit Application?");
     alertbox.setPositiveButton("Yes", new
     DialogInterface.OnClickListener() {
     public void onClick(DialogInterface arg0, int arg1) {
         activity.finish();
     }
     });
     alertbox.setNegativeButton("No", new
     DialogInterface.OnClickListener() {
     public void onClick(DialogInterface arg0, int arg1) {

     }
     });
     alertbox.show();
 }

And in your activity's onBackPressed() call this method like this,

public void onBackPressed()
{
    CustomDialog.ExitAppDialog(myActivity.this );
}

【Android】java.lang.IllegalStateException: Fragment not attached to Activity

ref:
http://stackoverflow.com/a/22544283

Generally you get that error when you try to perform work after the Fragment is no longer attached to the Activity. In the callback that triggers the IllegalStateException add a check for isAdded:http://developer.android.com/reference/android/app/Fragment.html#isAdded()

if(!isAdded()) {
    return;
}

http://stackoverflow.com/a/10941410

I've found the very simple answer: isAdded():

Return true if the fragment is currently added to its activity.

@Override
protected void onPostExecute(Void result){
    if(isAdded()){
        getResources().getString(R.string.app_name);
    }
}

To avoid onPostExecute from being called when the Fragment is not attached to the Activity is to cancel the AsyncTask when pausing or stopping the Fragment. Then isAdded() would not be necessary anymore.

【Android】移除FragmentManager裡的BackStack entry

ref:
Is this the right way to clean-up Fragment back stack when leaving a deeply nested stack?
http://shareandopen.tumblr.com/post/35328568659/android-clear-all-back-stack

為了好的使用者體驗，希望在程式運作到某一個情境時，清除所有的back stack entry，讓使用者不要在按下back按鍵時，發生一些悲劇體驗的話，可以利用程式碼來清除back stack entry。

// In your FragmentActivity use getSupprotFragmentManager() to get the FragmentManager.

// Clear all back stack.
int backStackCount = getSupportFragmentManager().getBackStackEntryCount();
for (int i = 0; i < backStackCount; i++) {

    // Get the back stack fragment id.
    int backStackId = getSupportFragmentManager().getBackStackEntryAt(i).getId();

    fm.popBackStack(backStackId, FragmentManager.POP_BACK_STACK_INCLUSIVE);

} /* end of for */

【Android】how to open a different fragment on recyclerview OnClick

ref:
http://stackoverflow.com/a/30434250

So simplified version, here's my onbindVH:

 @Override
    public void onBindViewHolder(FeedsViewHolder holder, int position) {
        final Feed item = mFeeds.get(position);

        holder.textView1.setText(item.getText());
        holder.imageView.setImageDrawable(mContext.getResources().getDrawable(item.getImage));
        holder.imageView.setOnClickListener(new View.OnClickListener() {
            @Override
            public void onClick(View view) {
                fragmentJump(item);
            }
        });
    }

here's fragmentJump:

private void fragmentJump(Feed mItemSelected) {
    mFragment = new Fragment2();
    mBundle = new Bundle();
    mBundle.putParcelable("item_selected_key", mItemSelected);
    mFragment.setArguments(mBundle);
    switchContent(R.id.frag1, mFragment);
}

here's switchContent on the adapter:

public void switchContent(int id, Fragment fragment) {
    if (mContext == null)
        return;
    if (mContext instanceof MainActivity) {
        MainActivity mainActivity = (MainActivity) mContext;
        Fragment frag = fragment;
        mainActivity.switchContent(id, frag);
    }

}

and lastly, here's the switchContent on MainActivity:

public void switchContent(int id, Fragment fragment) {
    FragmentTransaction ft = getSupportFragmentManager().beginTransaction();
    ft.replace(id, fragment, fragment.toString());
    ft.addToBackStack(null);
    ft.commit();
}

I know it can still be simplified, but it works as is. I hope it helps. :)

【Android】Activity and Fragment's Life Cycle

複習一下，兩張圖說明一切。

ref:
http://blog.csdn.net/jewleo/article/details/8919200
http://cheng-min-i-taiwan.blogspot.tw/2012/12/android-fragments.html
http://hankyang.logdown.com/posts/220707-androidandroid-fragament-life-cycle-life-cycle
Android中保存和恢復Fragment狀態的最好方法 (20160531新增)
Activity和Fragement中onSaveInstanceState()的使用詳解  (20160531新增)

【Android Studio】如何開啟logcat

建立時間:2015-09-01
更新時間:2016-03-04
ref:

1. ref: http://stackoverflow.com/a/16817720
   按 Alt + 6
   
2. 記錄一下

1. 首先開啟Android Studio(廢話...)
2. Tools  >  Android  > Enable ADB Integration選項有勾起，沒有的話就點一下。
3. 再次確認Enable ADB Integration選項有勾起。
4. Tools  >  Android  > Android Device Monitor 點一下，需要等一下。
5. Android Device Monitor 打開後，可以double check 要模擬的device或app name，log會在右下方出現。
6. 點選綠色+號(左下角)，設定新的過濾器規則。
   
   橘黃色的log可以不用太在意，只是警告；但紅色的log就要特別注意了，是屬於嚴重錯誤。

ref:影片支援

How to get logs (logcat) with Android Studio

【轉載】單例(singleton)這種設計模式

ref:
http://droidyue.com/blog/2015/01/11/looking-into-singleton/?droid_refer=random_recommend

【轉載】譯文：Android中糟糕的AsyncTask

ref:
http://droidyue.com/blog/2014/11/08/bad-smell-of-asynctask-in-android/?droid_refer=random_recommend

值得一讀

【Android】Different Fragments using different / common menu in Action Bar

ref:
http://stackoverflow.com/a/30556508
http://stackoverflow.com/a/18714611
http://www.jcodecraeer.com/a/anzhuokaifa/androidkaifa/2014/1120/2025.html

今天想要在不同的fragment使用特定的menu item，但有些menu item是可以共用。

1.建立一個通用menu.xml

<menu xmlns:android="http://schemas.android.com/apk/res/android"
      xmlns:app="http://schemas.android.com/apk/res-auto"
      xmlns:tools="http://schemas.android.com/tools"
      tools:context=".MainActivity">
    <group
        android:id="@+id/main_menu_group">
        <item
            android:id="@+id/action_refresh"
            android:icon="@drawable/ic_refresh"
            android:orderInCategory="90"
            android:title="@string/action_refresh"
            app:showAsAction="ifRoom"/>

        <item
            android:id="@+id/action_settings"
            android:orderInCategory="100"
            android:title="@string/action_settings"
            app:showAsAction="never"/>
    </group>
</menu>

先把需要通用的menu item寫在<group>外，至於範例是想製造每個fragment呈現不同的menu item。

2.建立特定的menu - menu_f1.xml

<?xml version="1.0" encoding="utf-8"?>
<menu xmlns:android="http://schemas.android.com/apk/res/android"
      xmlns:app="http://schemas.android.com/apk/res-auto">
    <item
        android:id="@+id/action_search"
        android:icon="@drawable/ic_search"
        android:imeOptions="actionSearch"
        android:inputType="textCapWords"
        android:orderInCategory="80"
        android:title="search"
        app:actionViewClass="android.support.v7.widget.SearchView"
        app:showAsAction="ifRoom|collapseActionView"/>
</menu>

3.在需要擁有特定menu item的fragment的onCreateView
增加setHasOptionsMenu(true);
來告知這個fragment有另外的OptionsMenu(參考)

4.建立onCreateOptionsMenu(Menu menu, MenuInflater inflater) method，並在onCreateOptionsMenu  引用(inflate)特定的menu，並把通用的menu item顯示設為false。如下所示：

@Override
    public void onCreateOptionsMenu(Menu menu, MenuInflater inflater) {
        // Inflate the menu; this adds items to the action bar if it is present.
        inflater.inflate(R.menu.menu_air, menu);

        menu.setGroupVisible(R.id.main_menu_group, false);
//        menu.findItem(R.id.action_settings).setVisible(false);
//        menu.findItem(R.id.action_refresh).setVisible(false);
        
        super.onCreateOptionsMenu(menu, inflater);

    }

• 透過1.設定group的方式，將group內的menu item設為不顯示。
• 或者是用menu.findItem(R....).setVisible(false);將個別menu item設為不顯示。