Android - DialogFragment 何故DialogFragmentか Android Support Packageが登場する以前のダイアログの表示の仕方は以下のようなものだった。 public class MainActivity extends Activity { @Override public void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); setContentView(R.layout.main); findViewById(R.id.button).setOnClickListener(new View.OnClickListener() { @Override public void onClick(View v) { // Activity.sho
Android Support Package の Fragment から startActivityForResult() を使うときの注意点 今回は Support Package で Fragment を使う場合の注意点です。 まず、FragmentActivity で startActivityForResult() を使う場合、requestCode は 16bit 以下にしなければなりません。 http://tools.oesf.biz/android-4.0.1_r1.0/xref/frameworks/support/v4/java/android/support/v4/app/FragmentActivity.java#654 654 /** 655 * Modifies the standard behavior to allow results to be deliv
[This post is by David Chandler, Android Developer Advocate — Tim Bray] Honeycomb introduced Fragments to support reusing portions of UI and logic across multiple activities in an app. In parallel, the showDialog / dismissDialog methods in Activity are being deprecated in favor of DialogFragments. In this post, I’ll show how to use DialogFragments with the v4 support library (for backward compatib
[This post is by Dianne Hackborn, a Software Engineer who sits very near the exact center of everything Android. — Tim Bray] An important goal for Android 3.0 is to make it easier for developers to write applications that can scale across a variety of screen sizes, beyond the facilities already available in the platform: Since the beginning, Android’s UI framework has been designed around the use
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く