Compare commits

..

7 Commits

2 changed files with 14 additions and 13 deletions
+1
View File
@@ -8,6 +8,7 @@
</component> </component>
<component name="Registry"> <component name="Registry">
<entry key="ide.instant.shutdown" value="false" /> <entry key="ide.instant.shutdown" value="false" />
<entry key="ide.images.show.chessboard" value="true" />
<entry key="ide.experimental.ui" value="false" /> <entry key="ide.experimental.ui" value="false" />
<entry key="ide.experimental.ui.inter.font" value="false" /> <entry key="ide.experimental.ui.inter.font" value="false" />
<entry key="debugger.new.tool.window.layout" value="false" /> <entry key="debugger.new.tool.window.layout" value="false" />
+13 -13
View File
@@ -1,12 +1,22 @@
<application> <application>
<component name="Translation.Cache"> <component name="Translation.Cache">
<option name="lastTrimTime" value="1711514243410" /> <option name="lastTrimTime" value="1712047345174" />
</component> </component>
<component name="Translation.Settings"> <component name="Translation.Settings">
<option name="primaryLanguage" value="CHINESE" /> <option name="primaryLanguage" value="CHINESE" />
</component> </component>
<component name="Translation.States"> <component name="Translation.States">
<histories> <histories>
<item value="The stroke weight for drawing the icon. Requires the underlying icon font to support the `wght` [FontVariation] axis, otherwise has no effect. Variable font filenames often indicate the supported axes. Must be greater than 0. Defaults to nearest [IconTheme]'s [IconThemeData.weight]. See also: [fill], for controlling fill. [grade], for controlling stroke weight in a more granular way. [opticalSize], for controlling optical size. https:fonts.google.comknowledgeglossaryweight_axis" />
<item value="By default, the placeholder is sized to fit its container. If the placeholder is in an unbounded space, it will size itself according to the given [fallbackWidth] and [fallbackHeight]." />
<item value="Sliver Grid Delegate With Max Cross Axis Extent" />
<item value="max Cross Axis Extent" />
<item value="[SliverGridDelegateWithMaxCrossAxisExtent], which creates a layout with tiles that have a maximum cross-axis extent." />
<item value="[SliverGridDelegateWithFixedCrossAxisCount], which creates a layout with a fixed number of tiles in the cross axis." />
<item value="This contains the response message from a connection. It tells you whether your connection was successful or a failure, in which case will tell you where the failure occurred" />
<item value="This is the bluetooth device that we get when we have a successful connection. If our bluetooth connection wasn't successful, then null will be returned" />
<item value="This is likely a mistake, as Provider will not automatically update dependents when AMDHomePageViewModel is updated. Instead, consider changing Provider for more specific implementation that handles the update mechanism, such as:" />
<item value="Tried to use Provider with a subtype of ListenableStream (AMDHomePageViewModel)." />
<item value="inflate" /> <item value="inflate" />
<item value="The number of device pixels for each logical pixel for the screen this view is displayed on. This number might not be a power of two. Indeed, it might not even be an integer. For example, the Nexus 6 has a device pixel ratio of 3.5. Device pixels are also referred to as physical pixels. Logical pixels are also referred to as device-independent or resolution-independent pixels. By definition, there are roughly 38 logical pixels per centimeter, or about 96 logical pixels per inch, of the physical display. The value returned by [devicePixelRatio] is ultimately obtained either from the hardware itself, the device drivers, or a hard-coded value stored in the operating system or firmware, and may be inaccurate, sometimes by a significant margin. The Flutter framework operates in logical pixels, so it is rarely necessary to directly deal with this property. When this changes, [PlatformDispatcher.onMetricsChanged] is called. When using the Flutter framework, using [MediaQuery.of] to obtain the device pixel ratio (via [MediaQueryData.devicePixelRatio]), instead of directly obtaining the [devicePixelRatio] from a [FlutterView], will automatically cause any widgets dependent on this value to rebuild when it changes, without having to listen to [PlatformDispatcher.onMetricsChanged]. See also: [WidgetsBindingObserver], for a mechanism at the widgets layer to observe when this value changes. [Display.devicePixelRatio], which reports the DPR of the display. The value here is equal to the value exposed on [display]." /> <item value="The number of device pixels for each logical pixel for the screen this view is displayed on. This number might not be a power of two. Indeed, it might not even be an integer. For example, the Nexus 6 has a device pixel ratio of 3.5. Device pixels are also referred to as physical pixels. Logical pixels are also referred to as device-independent or resolution-independent pixels. By definition, there are roughly 38 logical pixels per centimeter, or about 96 logical pixels per inch, of the physical display. The value returned by [devicePixelRatio] is ultimately obtained either from the hardware itself, the device drivers, or a hard-coded value stored in the operating system or firmware, and may be inaccurate, sometimes by a significant margin. The Flutter framework operates in logical pixels, so it is rarely necessary to directly deal with this property. When this changes, [PlatformDispatcher.onMetricsChanged] is called. When using the Flutter framework, using [MediaQuery.of] to obtain the device pixel ratio (via [MediaQueryData.devicePixelRatio]), instead of directly obtaining the [devicePixelRatio] from a [FlutterView], will automatically cause any widgets dependent on this value to rebuild when it changes, without having to listen to [PlatformDispatcher.onMetricsChanged]. See also: [WidgetsBindingObserver], for a mechanism at the widgets layer to observe when this value changes. [Display.devicePixelRatio], which reports the DPR of the display. The value here is equal to the value exposed on [display]." />
<item value="Subsequent version, remove this deprecated member. ignore: deprecated_member_use" /> <item value="Subsequent version, remove this deprecated member. ignore: deprecated_member_use" />
@@ -47,21 +57,11 @@
<item value="No clip at all. This is the default option for most widgets: if the content does not overflow the widget boundary, don't pay any performance cost for clipping. If the content does overflow, please explicitly specify the following [Clip] options: [hardEdge], which is the fastest clipping, but with lower fidelity. [antiAlias], which is a little slower than [hardEdge], but with smoothed edges. [antiAliasWithSaveLayer], which is much slower than [antiAlias], and should rarely be used." /> <item value="No clip at all. This is the default option for most widgets: if the content does not overflow the widget boundary, don't pay any performance cost for clipping. If the content does overflow, please explicitly specify the following [Clip] options: [hardEdge], which is the fastest clipping, but with lower fidelity. [antiAlias], which is a little slower than [hardEdge], but with smoothed edges. [antiAliasWithSaveLayer], which is much slower than [antiAlias], and should rarely be used." />
<item value="Whether the start of this range precedes the end." /> <item value="Whether the start of this range precedes the end." />
<item value="Whether this range represents a valid position in the text." /> <item value="Whether this range represents a valid position in the text." />
<item value="The range of text that is still being composed. Composing regions are created by input methods (IMEs) to indicate the text within a certain range is provisional. For instance, the Android Gboard app's English keyboard puts the current word under the caret into a composing region to indicate the word is subject to autocorrect or prediction changes. Composing regions can also be used for performing multistage input, which is typically used by IMEs designed for phonetic keyboard to enter ideographic symbols. As an example, many CJK keyboards require the user to enter a Latin alphabet sequence and then convert it to CJK characters. On iOS, the default software keyboards do not have a dedicated view to show the unfinished Latin sequence, so it's displayed directly in the text field, inside of a composing region. The composing region should typically only be changed by the IME, or the user via interacting with the IME. If the range represented by this property is [TextRange.empty], then the text is not currently being composed." />
<item value="various" />
<item value="transparency" />
<item value="feat: reduce loading timeout of webview." />
<item value="feat: update spar pack page; set cache mode of webview to LOAD_CACHE_ELSE_NETWORK only when not connected to network." />
<item value="Overrides the way the cache is used. The way the cache is used is based on the navigation type. For a normal page load, the cache is checked and content is re-validated as needed. When navigating back, content is not revalidated, instead the content is just retrieved from the cache. This method allows the client to override this behavior by specifying one of LOAD_DEFAULT, LOAD_CACHE_ELSE_NETWORK, LOAD_NO_CACHE or LOAD_CACHE_ONLY. The default value is LOAD_DEFAULT." />
<item value="in Premultiplied" />
<item value="PDF 417_COMPACT" />
<item value="MARGIN" />
<item value="MAX SIZE" />
</histories> </histories>
<option name="languageScores"> <option name="languageScores">
<map> <map>
<entry key="CHINESE" value="322" /> <entry key="CHINESE" value="332" />
<entry key="ENGLISH" value="323" /> <entry key="ENGLISH" value="333" />
<entry key="HAWAIIAN" value="1" /> <entry key="HAWAIIAN" value="1" />
<entry key="POLISH" value="1" /> <entry key="POLISH" value="1" />
<entry key="ROMANIAN" value="1" /> <entry key="ROMANIAN" value="1" />