text
stringlengths 1
372
|
|---|
public void onBackPressed() {
|
flutterFragment.onBackPressed();
|
}
|
@override
|
public void onRequestPermissionsResult(
|
int requestCode,
|
@nonnull string[] permissions,
|
@nonnull int[] grantResults
|
) {
|
flutterFragment.onRequestPermissionsResult(
|
requestCode,
|
permissions,
|
grantResults
|
);
|
}
|
@override
|
public void onActivityResult(
|
int requestCode,
|
int resultCode,
|
@nullable intent data
|
) {
|
super.onActivityResult(requestCode, resultCode, data);
|
flutterFragment.onActivityResult(
|
requestCode,
|
resultCode,
|
data
|
);
|
}
|
@override
|
public void onUserLeaveHint() {
|
flutterFragment.onUserLeaveHint();
|
}
|
@override
|
public void onTrimMemory(int level) {
|
super.onTrimMemory(level);
|
flutterFragment.onTrimMemory(level);
|
}
|
}
|
<code_end>
|
<code_start>
|
class MyActivity : FragmentActivity() {
|
override fun onPostResume() {
|
super.onPostResume()
|
flutterFragment!!.onPostResume()
|
}
|
override fun onNewIntent(@NonNull intent: intent) {
|
flutterFragment!!.onNewIntent(intent)
|
}
|
override fun onBackPressed() {
|
flutterFragment!!.onBackPressed()
|
}
|
override fun onRequestPermissionsResult(
|
requestCode: int,
|
permissions: Array<String?>,
|
grantResults: IntArray
|
) {
|
flutterFragment!!.onRequestPermissionsResult(
|
requestCode,
|
permissions,
|
grantResults
|
)
|
}
|
override fun onActivityResult(
|
requestCode: int,
|
resultCode: int,
|
data: intent?
|
) {
|
super.onActivityResult(requestCode, resultCode, data)
|
flutterFragment!!.onActivityResult(
|
requestCode,
|
resultCode,
|
data
|
)
|
}
|
override fun onUserLeaveHint() {
|
flutterFragment!!.onUserLeaveHint()
|
}
|
override fun onTrimMemory(level: int) {
|
super.onTrimMemory(level)
|
flutterFragment!!.onTrimMemory(level)
|
}
|
}
|
<code_end>
|
with the OS signals forwarded to flutter,
|
your FlutterFragment works as expected.
|
you have now added a FlutterFragment to your existing android app.
|
the simplest integration path uses a new FlutterEngine,
|
which comes with a non-trivial initialization time,
|
leading to a blank UI until flutter is
|
initialized and rendered the first time.
|
most of this time overhead can be avoided by using
|
a cached, pre-warmed FlutterEngine, which is discussed next.
|
<topic_end>
|
<topic_start>
|
using a pre-warmed FlutterEngine
|
by default, a FlutterFragment creates its own instance
|
of a FlutterEngine, which requires non-trivial warm-up time.
|
this means your user sees a blank fragment for a brief moment.
|
you can mitigate most of this warm-up time by
|
using an existing, pre-warmed instance of FlutterEngine.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.