AndroidStudioSettings/yiiguxing.translation.xml

<application>
  <component name="AppStorage">
    <option name="newTranslationDialogHeight" value="304" />
    <option name="newTranslationDialogWidth" value="406" />
    <option name="newTranslationDialogX" value="811" />
    <option name="newTranslationDialogY" value="447" />
    <option name="pinTranslationDialog" value="true" />
    <histories>
      <item value="Stops calling this [Ticker]'s callback. If called with the `canceled` argument set to false (the default), causes the future returned by [start] to resolve. If called with the `canceled` argument set to true, the future does not resolve, and the future obtained from [TickerFuture.orCancel], if any, resolves with a [TickerCanceled] error. Calling this sets [isActive] to false. This method does nothing if called when the ticker is inactive. By convention, this method is used by the object that receives the ticks (as opposed to the [TickerProvider] which created the ticker)." />
      <item value="The length of time this animation should last. If [reverseDuration] is specified, then [duration] is only used when going [forward]. Otherwise, it specifies the duration going in both directions." />
      <item value="Called whenever the widget configuration changes. If the parent widget rebuilds and request that this location in the tree update to display a new widget with the same [runtimeType] and [Widget.key], the framework will update the [widget] property of this [State] object to refer to the new widget and then call this method with the previous widget as an argument. Override this method to respond when the [widget] changes (e.g., to start implicit animations). The framework always calls [build] after calling [didUpdateWidget], which means any calls to [setState] in [didUpdateWidget] are redundant. {@macro flutter.widgets.State.initState} Implementations of this method should start with a call to the inherited method, as in `super.didUpdateWidget(oldWidget)`." />
      <item value="Called when a dependency of this [State] object changes. For example, if the previous call to [build] referenced an [InheritedWidget] that later changed, the framework would call this method to notify this object about the change. This method is also called immediately after [initState]. It is safe to call [BuildContext.dependOnInheritedWidgetOfExactType] from this method. Subclasses rarely override this method because the framework always calls [build] after a dependency changes. Some subclasses do override this method because they need to do some expensive work (e.g., network fetches) when their dependencies change, and that work would be too expensive to do for every build." />
      <item value="Whether to continue showing the old image (true), or briefly show nothing (false), when the image provider changes. The default value is false. Design discussion Why is the default value of [gaplessPlayback] false? Having the default value of [gaplessPlayback] be false helps prevent situations where stale or misleading information might be presented. Consider the following case: We have constructed a 'Person' widget that displays an avatar [Image] of the currently loaded person along with their name. We could request for a new person to be loaded into the widget at any time. Suppose we have a person currently loaded and the widget loads a new person. What happens if the [Image] fails to load? Option A ([gaplessPlayback] = false): The new person's name is coupled with a blank image. Option B ([gaplessPlayback] = true): The widget displays the avatar of the previous person and the name of the newly loaded person. This is why the default value is false. Most of the time, when you change the image provider you're not just changing the image, you're removing the old widget and adding a new one and not expecting them to have any relationship. With [gaplessPlayback] on you might accidentally break this expectation and re-use the old widget." />
      <item value="gapless Playback" />
      <item value="If [cacheWidth] or [cacheHeight] are provided, it indicates to the engine that the image must be decoded at the specified size. The image will be rendered to the constraints of the layout or [width] and [height] regardless of these parameters. These parameters are primarily intended to reduce the memory usage of [ImageCache]." />
      <item value="The [BuildContext] and [Size] are used to select an image configuration (see [createLocalImageConfiguration])." />
      <item value="Whether the field is serialized. Defaults to `null` which means [BuiltValue.defaultSerialize] is used. If a field is not serialized, it must either be `@nullable` or specify a default for deserialization to succeed." />
      <item value="Optionally, annotate a Built Value `Serializer` getters with this to specify settings. This is only needed for advanced use." />
      <item value="Memoized annotation for Built Value getters. Getters marked with this annotation are memoized: the result is calculated once on first access and stored in the instance." />
      <item value="Nullable annotation for Built Value fields. Fields marked with this annotation are allowed to be null." />
      <item value="Whether the generated serializer should output `null`s. By default this is `false` and nulls are omitted from the output." />
      <item value="Navigation.pushNamed() shortcut.&lt;br&gt;&lt;br&gt; Pushes a new named `page` to the stack. It has the advantage of not needing context, so you can call from your business logic. You can send any type of value to the other route in the [arguments]. [id] is for when you are using nested navigation, as explained in documentation By default, GetX will prevent you from push a route that you already in, if you want to push anyway, set [preventDuplicates] to false Note: Always put a slash on the route ('page1'), to avoid unnexpected errors" />
      <item value="Navigation.pushAndRemoveUntil() shortcut.&lt;br&gt;&lt;br&gt; Push the given `page`, and then pop several pages in the stack until [predicate] returns true [id] is for when you are using nested navigation, as explained in documentation Obs: unlike other get methods, this one you need to send a function that returns the widget to the page argument, like this: Get.offUntil(GetPageRoute(page: () =&gt; HomePage()), predicate) [predicate] can be used like this: `Get.offUntil(page, (route) =&gt; (route as GetPageRoute).routeName == 'home')` to pop routes in stack until home, or also like this: `Get.until((route) =&gt; !Get.isDialogOpen())`, to make sure the dialog is closed" />
      <item value="feat: tracking of post detail page; fix: reply to second level comment." />
      <item value="clear content of input bar after post submitted." />
      <item value="Initializes a new [FirebaseApp] instance by [name] and [options] and returns the created app. This method should be called before any usage of FlutterFire plugins. The default app instance can be initialized here simply by passing no &quot;name&quot; as an argument in both Dart &amp; manual initialization flows." />
      <item value="Notify the framework that the internal state of this object has changed. Whenever you change the internal state of a [State] object, make the change in a function that you pass to [setState]: ```dart setState(() { _myState = newValue; }); ``` The provided callback is immediately called synchronously. It must not return a future (the callback cannot be `async`), since then it would be unclear when the state was actually being set. Calling [setState] notifies the framework that the internal state of this object has changed in a way that might impact the user interface in this subtree, which causes the framework to schedule a [build] for this [State] object. If you just change the state directly without calling [setState], the framework might not schedule a [build] and the user interface for this subtree might not be updated to reflect the new state. Generally it is recommended that the `setState` method only be used to wrap the actual changes to the state, not any computation that might be associated with the change. For example, here a value used by the [build] function is incremented, and then the change is written to disk, but only the increment is wrapped in the `setState`: ```dart Future&lt;void&gt; _incrementCounter() async { setState(() { _counter++; }); Directory directory = await getApplicationDocumentsDirectory(); final String dirName = directory.path; await File('dircounter.txt').writeAsString('_counter'); } ``` It is an error to call this method after the framework calls [dispose]. You can determine whether it is legal to call this method by checking whether the [mounted] property is true." />
      <item value="Makes this Rx looks like a function so you can update a new value using `rx(someOtherValue)`. Practical to assign the Rx directly to some Widget that has a signature ::onChange( value ) Example: ``` final myText = 'GetX rocks!'.obs; in your Constructor, just to check it works :P ever( myText, print ) ; in your build(BuildContext) { TextField( onChanged: myText, )," />
      <item value="updates the value to `null` and adds it to the Stream. Even with null-safety coming, is still an important feature to support, as `call()` doesn't accept `null` values. For instance, `InputDecoration.errorText` has to be null to not show the &quot;error state&quot;. Sample: ``` final inputError = ''.obs..nil(); print('{inputError.runtimeType}: inputError'); outputs &gt; RxString: null ``` void nil() { subject.add(_value = null); }" />
      <item value="Cause the record did not support by hive cache, remove this value by now Comment reply to record, null by default, soulsRecord or usersRecord. if reply to type is soul, this value is soul record if reply to type is user, this value is user record dynamic replyToRecord;" />
      <item value="折叠" />
      <item value="update last unsenddeleted message preview for on chat list page." />
      <item value="update last message preview for unsenddeleted message on chat list page." />
      <item value="update last message preview on chat list page for unsenddeleted message." />
      <item value="permanent" />
      <item value="Creates a new map containing all of the keyvalue pairs from [parameters] except those whose value is `null`." />
      <item value="Takes a route [name] String generated by [to], [off], [offAll] (and similar context navigation methods), cleans the extra chars and accommodates the format. TODO: check for a more &quot;appealing&quot; URL naming convention. `() =&gt; MyHomeScreenView` becomes `my-home-screen-view`." />
      <item value="Navigation.push() shortcut.&lt;br&gt;&lt;br&gt; Pushes a new `page` to the stack It has the advantage of not needing context, so you can call from your business logic You can set a custom [transition], and a transition [duration]. You can send any type of value to the other route in the [arguments]. Just like native routing in Flutter, you can push a route as a [fullscreenDialog], [id] is for when you are using nested navigation, as explained in documentation If you want the same behavior of ios that pops a route when the user drag, you can set [popGesture] to true If you're using the [Bindings] api, you must define it here By default, GetX will prevent you from push a route that you already in, if you want to push anyway, set [preventDuplicates] to false" />
      <item value="prevent Duplicates" />
      <item value="make users whose 'is_group_chat_super_admin' field in 'user_flag' is true can manage any group chat." />
      <item value="使 user_flag 中 is_group_chat_super_admin 字段为 true 的用户可以管理任意群聊" />
      <item value="验收" />
      <item value="confetti" />
      <item value="skeleton for new friends page." />
      <item value="Skeleton Paragraph" />
      <item value="check user permission and jump to request page before create group chat." />
      <item value="add missing params of group chat item." />
      <item value="add missing params when create group chat item." />
      <item value="add leak params when create group chat item." />
      <item value="Controls a WebView, such as an [InAppWebView] widget instance, a [HeadlessInAppWebView] instance or [InAppBrowser] WebView instance. If you are using the [InAppWebView] widget, an [InAppWebViewController] instance can be obtained by setting the [InAppWebView.onWebViewCreated] callback. Instead, if you are using an [InAppBrowser] instance, you can get it through the [InAppBrowser.webViewController] attribute." />
      <item value="A scrolling container that animates items when they are inserted or removed. This widget's [AnimatedListState] can be used to dynamically insert or remove items. To refer to the [AnimatedListState] either provide a [GlobalKey] or use the static [of] method from an item's input callback. This widget is similar to one created by [ListView.builder]. {@youtube 560 315 https:www.youtube.comwatch?v=ZtfItHwFlZ8} {@tool dartpad} This sample application uses an [AnimatedList] to create an effect when items are removed or added to the list. See code in examplesapilibwidgetsanimated_listanimated_list.0.dart {@end-tool} See also: [SliverAnimatedList], a sliver that animates items when they are inserted or removed from a list." />
      <item value="{@template flutter.widgets.animatedList.initialItemCount} The number of items the list will start with. The appearance of the initial items is not animated. They are created, as needed, by [itemBuilder] with an animation parameter of [kAlwaysCompleteAnimation]. {@endtemplate}" />
      <item value="Insert the given entry into the overlay. If `below` is non-null, the entry is inserted just below `below`. If `above` is non-null, the entry is inserted just above `above`. Otherwise, the entry is inserted on top. It is an error to specify both `above` and `below`." />
      <item value="Obs: unlike other get methods, this one you need to send a function that returns the widget to the page argument, like this: Get.offUntil(GetPageRoute(page: () =&gt; HomePage()), predicate)" />
      <item value="confetti Controller" />
      <item value="blast Direction" />
      <item value="number Of Particles" />
      <item value="emission Frequency" />
    </histories>
    <option name="languageScores">
      <map>
        <entry key="CHINESE" value="377" />
        <entry key="ENGLISH" value="378" />
        <entry key="GERMAN" value="1" />
        <entry key="FRENCH" value="1" />
      </map>
    </option>
  </component>
  <component name="Cache">
    <option name="lastTrimTime" value="1665200758411" />
  </component>
  <component name="Settings">
    <option name="phoneticFontFamily" value="DejaVu Sans Mono" />
    <option name="primaryFontFamily" value="Noto Sans CJK SC Regular" />
    <option name="showActionsInContextMenuOnlyWithSelection" value="false" />
    <option name="translateDocumentation" value="true" />
  </component>
</application>