debuggerx/AndroidStudioSettings
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

AI-Quail 1 | 2026.1.1 Patch 2 <debuggerx@debuggerx-PC Update yiiguxing.translation.xml

Browse Source
This commit is contained in:
debuggerx
2026-07-15 13:53:11 +08:00
parent 8d881c05c1
commit 7c8b889709
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
yiiguxing.translation.xml
+2 -2
View File
@@ -1,6 +1,6 @@
<application> <application>
<component name="Translation.Cache"> <component name="Translation.Cache">
<option name="lastTrimTime" value="1783650680308" /> <option name="lastTrimTime" value="1784094177773" />
</component> </component>
<component name="Translation.OpenAISettings"> <component name="Translation.OpenAISettings">
<option name="OPEN_AI"> <option name="OPEN_AI">
@@ -22,6 +22,7 @@
<option name="translationDialogLocationY" value="567" /> <option name="translationDialogLocationY" value="567" />
<option name="translationDialogWidth" value="1381" /> <option name="translationDialogWidth" value="1381" />
<histories> <histories>
<item value="Checks the connection status of the device. Do not use the result of this function to decide whether you can reliably make a network request, it only gives you the radio status. Instead, listen for connectivity changes via [onConnectivityChanged] stream. The returned list is never empty. In case of no connectivity, the list contains a single element of [ConnectivityResult.none]. Note also that this is the only case where [ConnectivityResult.none] is present." />
<item value="A stream of normalized gamepad events. A [GamepadNormalizer] is auto-created on first access using the current platform. Override [normalizer] before accessing this stream to use a custom normalizer. Events that cannot be normalized (unrecognized keys) are silently dropped." /> <item value="A stream of normalized gamepad events. A [GamepadNormalizer] is auto-created on first access using the current platform. Override [normalizer] before accessing this stream to use a custom normalizer. Events that cannot be normalized (unrecognized keys) are silently dropped." />
<item value="code cleanup" /> <item value="code cleanup" />
<item value="A gradient to use when filling the box. If this is specified, [color] has no effect. The [gradient] is drawn under the [image]." /> <item value="A gradient to use when filling the box. If this is specified, [color] has no effect. The [gradient] is drawn under the [image]." />
@@ -71,7 +72,6 @@
<item value="The application is not currently visible to the user, and not responding to user input. When the application is in this state, the engine will not call the [PlatformDispatcher.onBeginFrame] and [PlatformDispatcher.onDrawFrame] callbacks. This state is only entered on iOS and Android." /> <item value="The application is not currently visible to the user, and not responding to user input. When the application is in this state, the engine will not call the [PlatformDispatcher.onBeginFrame] and [PlatformDispatcher.onDrawFrame] callbacks. This state is only entered on iOS and Android." />
<item value="All views of an application are hidden, either because the application is about to be paused (on iOS and Android), or because it has been minimized or placed on a desktop that is no longer visible (on non-web desktop), or is running in a window or tab that is no longer visible (on the web). On iOS and Android, in order to keep the state machine the same on all platforms, a transition to this state is synthesized before the [paused] state is entered when coming from [inactive], and before the [inactive] state is entered when coming from [paused]. This allows cross-platform implementations that want to know when an app is conceptually &quot;hidden&quot; to only write one handler." /> <item value="All views of an application are hidden, either because the application is about to be paused (on iOS and Android), or because it has been minimized or placed on a desktop that is no longer visible (on non-web desktop), or is running in a window or tab that is no longer visible (on the web). On iOS and Android, in order to keep the state machine the same on all platforms, a transition to this state is synthesized before the [paused] state is entered when coming from [inactive], and before the [inactive] state is entered when coming from [paused]. This allows cross-platform implementations that want to know when an app is conceptually &quot;hidden&quot; to only write one handler." />
<item value="On Android and iOS, apps in this state should assume that they may be [hidden] and [paused] at any time." /> <item value="On Android and iOS, apps in this state should assume that they may be [hidden] and [paused] at any time." />
<item value="On Android, this corresponds to the Flutter host view running in Android's paused state (i.e. [`Activity.onPause`](https:developer.android.comreferenceandroidappActivityonPause()) has been called), or in Android's &quot;resumed&quot; state (i.e. [`Activity.onResume`](https:developer.android.comreferenceandroidappActivityonResume()) has been called) but does not have window focus. Examples of when apps transition to this state include when the app is partially obscured or another activity is focused, a app running in a split screen that isn't the current app, an app interrupted by a phone call, a picture-in-picture app, a system dialog, another view. It will also be inactive when the notification window shade is down, or the application switcher is visible." />
</histories> </histories>
<option name="languageScores"> <option name="languageScores">
<map> <map>