bcoder

UniApp Flex布局教程

分类：Others, Others 阅读 (318) 已关闭评论

3月 042025

一、Flex布局基础

Flex布局由 容器（父元素） 和 项目（子元素） 构成。通过 display: flex 声明容器。

<template>
  <view class="container">
    <view class="item">1</view>
    <view class="item">2</view>
  </view>
</template>

<style>
.container {
  display: flex; /* 启用 Flex 布局 */
}
</style>

</view>

</template>

<style>

.container {

display: flex; /* 启用 Flex 布局 */

}

</style>

二、（父）容器属性详解

1. flex-direction

定义主轴方向（项目的排列方向）

值	描述
row (默认)	水平排列（左→右）
row-reverse	水平反向（右→左）
column	垂直排列（上→下）
column-reverse	垂直反向（下→上）

<view class="container column">
  <view class="item">1</view>
  <view class="item">2</view>
</view>

<style>
.column {
  flex-direction: column; /* 垂直排列 */
  height: 300rpx; /* 需要指定高度 */
}
</style>

</view>

<style>

.column {

flex-direction: column; /* 垂直排列 */

height: 300rpx; /* 需要指定高度 */

}

</style>

2. justify-content

定义主轴对齐方式

值	描述
flex-start	向主轴起点对齐（默认）
flex-end	向主轴终点对齐
center	居中对齐
space-between	两端对齐，间隔相等
space-around	每个项目两侧间隔相等

3. align-items

定义交叉轴对齐方式

值	描述
stretch	拉伸填满容器（默认）
flex-start	向交叉轴起点对齐
flex-end	向交叉轴终点对齐
center	居中对齐

4. flex-wrap

定义是否换行

值	描述
nowrap	不换行（默认）
wrap	换行
wrap-reverse	反向换行

5. align-content

多行项目的交叉轴对齐方式

值	描述
stretch	拉伸填满容器（默认）
flex-start	向交叉轴起点对齐
center	居中对齐
space-between	两端对齐

三、项目属性

1. flex-grow

定义项目的放大比例（默认0）

结果：剩余空间按1:2分配

2. flex-shrink

定义项目的缩小比例（默认1）

<view class="container">
  <view class="item shrink0">1（不缩小）</view>
  <view class="item">2</view>
</view>
<style>
.shrink0 { flex-shrink: 0; }
.item { width: 400rpx; } /* 故意超出容器宽度 */
</style>

</view>

<style>

.shrink0 { flex-shrink: 0; }

.item { width: 400rpx; } /* 故意超出容器宽度 */

</style>

结果：第一个元素保持宽度，第二个被压缩

3. align-self

单个项目的交叉轴对齐方式

<view class="container">
  <view class="item self-center">居中对齐</view>
  <view class="item">默认对齐</view>
</view>
<style>
.self-center {
  align-self: center;
}
</style>

</view>

<style>

.self-center {

align-self: center;

}

</style>

四、综合示例

<template>
    <view class="container">
        <view class="item header">Header</view>
        <view class="item main">Main Content</view>
        <view class="item footer">Footer</view>
    </view>
</template>

<style>
.container {
    display: flex;
    flex-direction: column;
    height: 100vh;
}

.header, .footer {
    height: 100rpx;
    background: #eee;
}

.main {
    flex: 1;
    background: #f0f0f0;
}
</style>

<view class="item header">Header</view>

<view class="item main">Main Content</view>

<view class="item footer">Footer</view>

</view>

</template>

<style>

.container {

display: flex;

flex-direction: column;

height: 100vh;

}

.header, .footer {

height: 100rpx;

background: #eee;

}

.main {

flex: 1;

background: #f0f0f0;

}

</style>

结果：经典的头-主体-底布局

五、注意事项

在微信小程序中需添加 overflow: hidden 解决兼容性问题
使用 rpx 单位保证多端适配
推荐配合 box-sizing: border-box 使用

在Android Studio中查看app的keystore信息

分类：Android, Java 阅读 (221) 已关闭评论

2月 172025

　　在我们使用第三方平台服务的时候，经常需要输入应用的包名和keystore对应的SHA1、SHA-256信息，正常情况下都是使用java的keytool来获取这些信息，其他在Android Studio中使用gradle任务同样可以获取这些信息。

　　在Android Studio中打开Gradle选项卡，选择选项卡左上角的”Exec Gradle Task”按钮，在弹出的窗口中输入gradle signingReport命令，执行，就可以在输出结果窗口中看到keystore路径、SHA1、SHA-256等信息了。操作过程如下图：

输出结果如下：

Executing tasks: [signingReport] in project E:\ZLZLProject\PosCollectorApp


> Task :app:signingReport
Variant: debug
Config: debug
Store: E:\AndroidAVD\.android\debug.keystore
Alias: AndroidDebugKey
MD5: C2:AE:BC:4D:3B:2A:ED:88:C1:B1:42:7F:36:25:B3:FB
SHA1: AA:F5:92:38:65:9F:B0:D5:95:90:38:5E:DA:78:3F:E2:76:01:15:99
SHA-256: FC:8E:3C:E0:80:78:3F:A1:C6:4B:1D:AC:6C:7B:24:58:BC:9E:4E:8D:92:DA:31:E8:67:ED:32:34:DE:23:41:82
Valid until: 2051��12��13��������
----------
Variant: release
Config: null
Store: null
Alias: null
----------
Variant: debugAndroidTest
Config: debug
Store: E:\AndroidAVD\.android\debug.keystore
Alias: AndroidDebugKey
MD5: C2:AE:BC:4D:3B:2A:ED:88:C1:B1:42:7F:36:25:B3:FB
SHA1: AA:F5:92:38:65:9F:B0:D5:95:90:38:5E:DA:78:3F:E2:76:01:15:99
SHA-256: FC:8E:3C:E0:80:78:3F:A1:C6:4B:1D:AC:6C:7B:24:58:BC:9E:4E:8D:92:DA:31:E8:67:ED:32:34:DE:23:41:82
Valid until: 2051��12��13��������
----------

BUILD SUCCESSFUL in 795ms
1 actionable task: 1 executed

Build Analyzer results available
14:36:24: Execution finished 'signingReport'.

Executing tasks: [signingReport] in project E:\ZLZLProject\PosCollectorApp

> Task :app:signingReport

Variant: debug

Config: debug

Store: E:\AndroidAVD\.android\debug.keystore

Alias: AndroidDebugKey

MD5: C2:AE:BC:4D:3B:2A:ED:88:C1:B1:42:7F:36:25:B3:FB

SHA1: AA:F5:92:38:65:9F:B0:D5:95:90:38:5E:DA:78:3F:E2:76:01:15:99

SHA-256: FC:8E:3C:E0:80:78:3F:A1:C6:4B:1D:AC:6C:7B:24:58:BC:9E:4E:8D:92:DA:31:E8:67:ED:32:34:DE:23:41:82

Valid until: 2051��12��13��

----------

Variant: release

Config: null

Store: null

Alias: null

----------

Variant: debugAndroidTest

Config: debug

Store: E:\AndroidAVD\.android\debug.keystore

Alias: AndroidDebugKey

MD5: C2:AE:BC:4D:3B:2A:ED:88:C1:B1:42:7F:36:25:B3:FB

SHA1: AA:F5:92:38:65:9F:B0:D5:95:90:38:5E:DA:78:3F:E2:76:01:15:99

SHA-256: FC:8E:3C:E0:80:78:3F:A1:C6:4B:1D:AC:6C:7B:24:58:BC:9E:4E:8D:92:DA:31:E8:67:ED:32:34:DE:23:41:82

Valid until: 2051��12��13��

----------

BUILD SUCCESSFUL in 795ms

1 actionable task: 1 executed

Build Analyzer results available

14:36:24: Execution finished 'signingReport'.

Flutter记录之GridView

分类：Uncategorized 阅读 (775) 已关闭评论

1月 092024

GridView继承自BoxScrollView，BoxScrollView继承自ScrollView

GridView有多种构建函数

GridView

GridView.builder

GridView.count

GridView.custom

GridView.extent

Sqlite中将时间戳转换为带秒或者秒的时间

分类：Database, Sqlite 阅读 (1,902) 已关闭评论

3月 302023

将长度为10位的时间戳（秒级）转换为时间：

select cast(datetime(logtime, 'unixepoch', 'localtime') as text),logcontent from
logs

1 2	select cast(datetime(logtime, 'unixepoch', 'localtime') as text),logcontent from logs

将长度为13位的时间戳（毫秒级）转换为时间(秒级)：

select cast(datetime(logtime/1000, 'unixepoch', 'localtime') as text),logcontent from
logs

1 2	select cast(datetime(logtime/1000, 'unixepoch', 'localtime') as text),logcontent from logs

将长度为13位的时间戳（毫秒级）转换为时间（毫秒级）：

select cast(datetime(logtime/1000, 'unixepoch', 'localtime') as text)||'.'||cast(logtime%1000 as text),logcontent from
logs

1 2	select cast(datetime(logtime/1000, 'unixepoch', 'localtime') as text)\|\|'.'\|\|cast(logtime%1000 as text),logcontent from logs

yarn : 无法加载文件 d:\nodejs\yarn.ps1，因为在此系统上禁止运行脚本。

分类：Android, Java, Others, Others 阅读 (1,120) 已关闭评论

1月 122023

执行yarn android出现如下错误

yarn : 无法加载文件 d:\nodejs\yarn.ps1，因为在此系统上禁止运行脚本。有关详细信息，请参阅 https:/go.microsoft.com/fwlink/?LinkID=135170 中的 about_Execution_Policies。
所在位置 行:1 字符: 1
+ yarn android
+ ~~~~
    + CategoryInfo          : SecurityError: (:) []，PSSecurityException
    + FullyQualifiedErrorId : UnauthorizedAccess

yarn : 无法加载文件 d:\nodejs\yarn.ps1，因为在此系统上禁止运行脚本。有关详细信息，请参阅 https:/go.microsoft.com/fwlink/?LinkID=135170 中的 about_Execution_Policies。

所在位置行:1 字符: 1

+ yarn android

+ ~~~~

+ CategoryInfo : SecurityError: (:) []，PSSecurityException

+ FullyQualifiedErrorId : UnauthorizedAccess

解决办法：

打开“开始”菜单，搜索powershell，在powershell菜单上右键，点击“以管理员身份运行”
在打开的powershell命令行窗口中输入get-ExecutionPolicy，可以查看返回的是Restricted，这个意思是管理员权限是禁用的
在命令行窗口中输入set-ExecutionPolicy remotesigned，按照提示输入y，回车，就可以执行yarn相关命令了

Android Studio编译报:app:checkDebugManifest错误的解决办法

分类：Uncategorized 阅读 (1,854) 已关闭评论

1月 112023

将项目的原来的gradle版本由5.1.1升级到7.2版本后再编译就报如下错误

FAILURE: Build completed with 5 failures.

1: Task failed with an exception.
-----------
* What went wrong:
A problem was found with the configuration of task ':app:checkDebugManifest' (type 'CheckManifest').
  - In plugin 'com.android.build.gradle.api.AndroidBasePlugin' type 'com.android.build.gradle.internal.tasks.CheckManifest' property 'manifest' has @Input annotation used on property of type 'File'.
    
    Reason: A property of type 'File' annotated with @Input cannot determine how to interpret the file.
    
    Possible solutions:
      1. Annotate with @InputFile for regular files.
      2. Annotate with @InputDirectory for directories.
      3. If you want to track the path, return File.absolutePath as a String and keep @Input.
    
    Please refer to https://docs.gradle.org/7.2/userguide/validation_problems.html#incorrect_use_of_input_annotation for more details about this problem.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
==============================================================================

2: Task failed with an exception.
-----------
* What went wrong:
A problem was found with the configuration of task ':app:createDebugCompatibleScreenManifests' (type 'CompatibleScreensManifest').
  - In plugin 'com.android.build.gradle.api.AndroidBasePlugin' type 'com.android.build.gradle.tasks.CompatibleScreensManifest' property 'outputScope' is missing an input or output annotation.
    
    Reason: A property without annotation isn't considered during up-to-date checking.
    
    Possible solutions:
      1. Add an input or output annotation.
      2. Mark it as @Internal.
    
    Please refer to https://docs.gradle.org/7.2/userguide/validation_problems.html#missing_annotation for more details about this problem.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
==============================================================================

3: Task failed with an exception.
-----------
* What went wrong:
A problem was found with the configuration of task ':app:compileDebugShaders' (type 'ShaderCompile').
  - In plugin 'com.android.build.gradle.api.AndroidBasePlugin' type 'com.android.build.gradle.tasks.ShaderCompile' property 'sourceDir' is annotated with @InputFiles but missing a normalization strategy.
    
    Reason: If you don't declare the normalization, outputs can't be re-used between machines or locations on the same machine, therefore caching efficiency drops significantly.
    
    Possible solution: Declare the normalization strategy by annotating the property with either @PathSensitive, @Classpath or @CompileClasspath.
    
    Please refer to https://docs.gradle.org/7.2/userguide/validation_problems.html#missing_normalization_annotation for more details about this problem.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
==============================================================================

4: Task failed with an exception.
-----------
* What went wrong:
Some problems were found with the configuration of task ':app:signingConfigWriterDebug' (type 'SigningConfigWriterTask').
  - In plugin 'com.android.build.gradle.api.AndroidBasePlugin' type 'com.android.build.gradle.internal.tasks.SigningConfigWriterTask' property 'signingConfig.name' is missing an input or output annotation.
    
    Reason: A property without annotation isn't considered during up-to-date checking.
    
    Possible solutions:
      1. Add an input or output annotation.
      2. Mark it as @Internal.
    
    Please refer to https://docs.gradle.org/7.2/userguide/validation_problems.html#missing_annotation for more details about this problem.
  - In plugin 'com.android.build.gradle.api.AndroidBasePlugin' type 'com.android.build.gradle.internal.tasks.SigningConfigWriterTask' property 'signingConfig.signingReady' is missing an input or output annotation.
    
    Reason: A property without annotation isn't considered during up-to-date checking.
    
    Possible solutions:
      1. Add an input or output annotation.
      2. Mark it as @Internal.
    
    Please refer to https://docs.gradle.org/7.2/userguide/validation_problems.html#missing_annotation for more details about this problem.
  - In plugin 'com.android.build.gradle.api.AndroidBasePlugin' type 'com.android.build.gradle.internal.tasks.SigningConfigWriterTask' property 'signingConfig.storeFile' is annotated with @InputFile but missing a normalization strategy.
    
    Reason: If you don't declare the normalization, outputs can't be re-used between machines or locations on the same machine, therefore caching efficiency drops significantly.
    
    Possible solution: Declare the normalization strategy by annotating the property with either @PathSensitive, @Classpath or @CompileClasspath.
    
    Please refer to https://docs.gradle.org/7.2/userguide/validation_problems.html#missing_normalization_annotation for more details about this problem.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
==============================================================================

5: Task failed with an exception.
-----------
* What went wrong:
Some problems were found with the configuration of task ':app:transformNativeLibsWithMergeJniLibsForDebug' (type 'TransformTask').
  - In plugin 'com.android.build.gradle.api.AndroidBasePlugin' type 'com.android.build.gradle.internal.pipeline.TransformTask' property 'allSecondaryInputs' is private and annotated with @Internal.
    
    Reason: Annotations on private getters are ignored.
    
    Possible solutions:
      1. Make the getter public.
      2. Annotate the public version of the getter.
    
    Please refer to https://docs.gradle.org/7.2/userguide/validation_problems.html#private_getter_must_not_be_annotated for more details about this problem.
  - In plugin 'com.android.build.gradle.api.AndroidBasePlugin' type 'com.android.build.gradle.internal.pipeline.TransformTask' property 'logging' is missing an input or output annotation.
    
    Reason: A property without annotation isn't considered during up-to-date checking.
    
    Possible solutions:
      1. Add an input or output annotation.
      2. Mark it as @Internal.
    
    Please refer to https://docs.gradle.org/7.2/userguide/validation_problems.html#missing_annotation for more details about this problem.
  - In plugin 'com.android.build.gradle.api.AndroidBasePlugin' type 'com.android.build.gradle.internal.pipeline.TransformTask' property 'oldSecondaryInputs' is annotated with @InputFiles but missing a normalization strategy.
    
    Reason: If you don't declare the normalization, outputs can't be re-used between machines or locations on the same machine, therefore caching efficiency drops significantly.
    
    Possible solution: Declare the normalization strategy by annotating the property with either @PathSensitive, @Classpath or @CompileClasspath.
    
    Please refer to https://docs.gradle.org/7.2/userguide/validation_problems.html#missing_normalization_annotation for more details about this problem.
  - In plugin 'com.android.build.gradle.api.AndroidBasePlugin' type 'com.android.build.gradle.internal.pipeline.TransformTask' property 'path' is missing an input or output annotation.
    
    Reason: A property without annotation isn't considered during up-to-date checking.
    
    Possible solutions:
      1. Add an input or output annotation.
      2. Mark it as @Internal.
    
    Please refer to https://docs.gradle.org/7.2/userguide/validation_problems.html#missing_annotation for more details about this problem.
  - In plugin 'com.android.build.gradle.api.AndroidBasePlugin' type 'com.android.build.gradle.internal.pipeline.TransformTask' property 'temporaryDir' is missing an input or output annotation.
    
    Reason: A property without annotation isn't considered during up-to-date checking.
    
    Possible solutions:
      1. Add an input or output annotation.
      2. Mark it as @Internal.
    
    Please refer to https://docs.gradle.org/7.2/userguide/validation_problems.html#missing_annotation for more details about this problem.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
==============================================================================

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

See https://docs.gradle.org/7.2/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 7s

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

139

140

141

142

143

144

145

146

147

148

149

150

FAILURE: Build completed with 5 failures.

1: Task failed with an exception.

-----------

* What went wrong:

A problem was found with the configuration of task ':app:checkDebugManifest' (type 'CheckManifest').

- In plugin 'com.android.build.gradle.api.AndroidBasePlugin' type 'com.android.build.gradle.internal.tasks.CheckManifest' property 'manifest' has @Input annotation used on property of type 'File'.

Reason: A property of type 'File' annotated with @Input cannot determine how to interpret the file.

Possible solutions:

1. Annotate with @InputFile for regular files.

2. Annotate with @InputDirectory for directories.

3. If you want to track the path, return File.absolutePath as a String and keep @Input.

Please refer to https://docs.gradle.org/7.2/userguide/validation_problems.html#incorrect_use_of_input_annotation for more details about this problem.

* Try:

Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

==============================================================================

2: Task failed with an exception.

-----------

* What went wrong:

A problem was found with the configuration of task ':app:createDebugCompatibleScreenManifests' (type 'CompatibleScreensManifest').

- In plugin 'com.android.build.gradle.api.AndroidBasePlugin' type 'com.android.build.gradle.tasks.CompatibleScreensManifest' property 'outputScope' is missing an input or output annotation.

Reason: A property without annotation isn't considered during up-to-date checking.

Possible solutions:

1. Add an input or output annotation.

2. Mark it as @Internal.

Please refer to https://docs.gradle.org/7.2/userguide/validation_problems.html#missing_annotation for more details about this problem.

* Try:

Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

==============================================================================

3: Task failed with an exception.

-----------

* What went wrong:

A problem was found with the configuration of task ':app:compileDebugShaders' (type 'ShaderCompile').

- In plugin 'com.android.build.gradle.api.AndroidBasePlugin' type 'com.android.build.gradle.tasks.ShaderCompile' property 'sourceDir' is annotated with @InputFiles but missing a normalization strategy.

Reason: If you don't declare the normalization, outputs can't be re-used between machines or locations on the same machine, therefore caching efficiency drops significantly.

Possible solution: Declare the normalization strategy by annotating the property with either @PathSensitive, @Classpath or @CompileClasspath.

Please refer to https://docs.gradle.org/7.2/userguide/validation_problems.html#missing_normalization_annotation for more details about this problem.

* Try:

Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

==============================================================================

4: Task failed with an exception.

-----------

* What went wrong:

Some problems were found with the configuration of task ':app:signingConfigWriterDebug' (type 'SigningConfigWriterTask').

- In plugin 'com.android.build.gradle.api.AndroidBasePlugin' type 'com.android.build.gradle.internal.tasks.SigningConfigWriterTask' property 'signingConfig.name' is missing an input or output annotation.

Reason: A property without annotation isn't considered during up-to-date checking.

Possible solutions:

1. Add an input or output annotation.

2. Mark it as @Internal.

Please refer to https://docs.gradle.org/7.2/userguide/validation_problems.html#missing_annotation for more details about this problem.

- In plugin 'com.android.build.gradle.api.AndroidBasePlugin' type 'com.android.build.gradle.internal.tasks.SigningConfigWriterTask' property 'signingConfig.signingReady' is missing an input or output annotation.

Reason: A property without annotation isn't considered during up-to-date checking.

Possible solutions:

1. Add an input or output annotation.

2. Mark it as @Internal.

Please refer to https://docs.gradle.org/7.2/userguide/validation_problems.html#missing_annotation for more details about this problem.

- In plugin 'com.android.build.gradle.api.AndroidBasePlugin' type 'com.android.build.gradle.internal.tasks.SigningConfigWriterTask' property 'signingConfig.storeFile' is annotated with @InputFile but missing a normalization strategy.

Reason: If you don't declare the normalization, outputs can't be re-used between machines or locations on the same machine, therefore caching efficiency drops significantly.

Possible solution: Declare the normalization strategy by annotating the property with either @PathSensitive, @Classpath or @CompileClasspath.

Please refer to https://docs.gradle.org/7.2/userguide/validation_problems.html#missing_normalization_annotation for more details about this problem.

* Try:

Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

==============================================================================

5: Task failed with an exception.

-----------

* What went wrong:

Some problems were found with the configuration of task ':app:transformNativeLibsWithMergeJniLibsForDebug' (type 'TransformTask').

- In plugin 'com.android.build.gradle.api.AndroidBasePlugin' type 'com.android.build.gradle.internal.pipeline.TransformTask' property 'allSecondaryInputs' is private and annotated with @Internal.

Reason: Annotations on private getters are ignored.

Possible solutions:

1. Make the getter public.

2. Annotate the public version of the getter.

Please refer to https://docs.gradle.org/7.2/userguide/validation_problems.html#private_getter_must_not_be_annotated for more details about this problem.

- In plugin 'com.android.build.gradle.api.AndroidBasePlugin' type 'com.android.build.gradle.internal.pipeline.TransformTask' property 'logging' is missing an input or output annotation.

Reason: A property without annotation isn't considered during up-to-date checking.

Possible solutions:

1. Add an input or output annotation.

2. Mark it as @Internal.

Please refer to https://docs.gradle.org/7.2/userguide/validation_problems.html#missing_annotation for more details about this problem.

- In plugin 'com.android.build.gradle.api.AndroidBasePlugin' type 'com.android.build.gradle.internal.pipeline.TransformTask' property 'oldSecondaryInputs' is annotated with @InputFiles but missing a normalization strategy.

Reason: If you don't declare the normalization, outputs can't be re-used between machines or locations on the same machine, therefore caching efficiency drops significantly.

Possible solution: Declare the normalization strategy by annotating the property with either @PathSensitive, @Classpath or @CompileClasspath.

Please refer to https://docs.gradle.org/7.2/userguide/validation_problems.html#missing_normalization_annotation for more details about this problem.

- In plugin 'com.android.build.gradle.api.AndroidBasePlugin' type 'com.android.build.gradle.internal.pipeline.TransformTask' property 'path' is missing an input or output annotation.

Reason: A property without annotation isn't considered during up-to-date checking.

Possible solutions:

1. Add an input or output annotation.

2. Mark it as @Internal.

Please refer to https://docs.gradle.org/7.2/userguide/validation_problems.html#missing_annotation for more details about this problem.

- In plugin 'com.android.build.gradle.api.AndroidBasePlugin' type 'com.android.build.gradle.internal.pipeline.TransformTask' property 'temporaryDir' is missing an input or output annotation.

Reason: A property without annotation isn't considered during up-to-date checking.

Possible solutions:

1. Add an input or output annotation.

2. Mark it as @Internal.

Please refer to https://docs.gradle.org/7.2/userguide/validation_problems.html#missing_annotation for more details about this problem.

* Try:

Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

==============================================================================

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

See https://docs.gradle.org/7.2/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 7s

网上搜索大部分说是把使用的gradle的版本降到原来的版本，但是因为ide升级原因？版本不能降

后来搜索到一个方法是把项目里的build.gradle中的gradle插件的版本升级一下，由原来的3.4.1版本升级到4.2.0再编译就好了

buildscript {
    repositories {
        google()
        jcenter()
        
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:4.2.0' //原来是3.4.1
    }
}

allprojects {
    repositories {
        google()
        jcenter()
        
    }
}

task clean(type: Delete) {
    delete rootProject.buildDir
}

buildscript {

repositories {

google()

jcenter()

}

dependencies {

classpath 'com.android.tools.build:gradle:4.2.0' //原来是3.4.1

}

allprojects {

repositories {

google()

jcenter()

}

task clean(type: Delete) {

delete rootProject.buildDir

}

General error: 1267 Illegal mix of collations (utf8_general_ci,IMPLICIT) and (utf8_unicode_ci,IMPLICIT) for operation ‘=’

分类：Database, MySQL 阅读 (1,188) 已关闭评论

11月 162022

出现这个问题的原因是两个表的字符集不一致

解决方法有两个：

1. 在select的时候对字段进行转码，如下：

select os.*, ob.obulatitude, ob.obulongtitude from OBU_status os left join obudevices as ob on CONVERT(os.device_ID USING utf8) COLLATE utf8_unicode_ci=ob.obuhardware

其中CONVERT(os.device_ID USING utf8) COLLATE utf8_unicode_ci使用convert函数对字段进行了转码

2. 修改表的字符集

这个比较麻烦，如果是新项目没有问题，如果是已经在运行的项目，要考虑对其他地方是不是有影响

复习一些几何知识

分类：Others, Others 阅读 (1,473) 已关闭评论

11月 112022

1. 已知三角形三边长度，计算面积

三边长度：a, b, c

半周长：p = (a + b + c) / 2

三角形面积：S = √[p(p-a)(p-b)(p-c)] =（1/4）√[(a+b+c)(a+b-c)(a+c-b)(b+c-a)]

2. 已知三角形各边长度，求其中某个顶点到对边的距离

三边长度：a, b, c，求a到bc边的距离ad

根据上面公式得出三角形面积，

由公式S = 1/2 (底 x 高)，则ad = 2*S / bc

3. 设三角形三边分别为a、b、c，内切圆半径为r，则三角形面积=(a+b+c)r/2

4. 已知三角形两边a，b，这两边夹角C，则S＝1/2 * absinC

Python中使用subprocess创建的进程杀不掉的问题

分类：Others, Python 阅读 (2,421) 已关闭评论

8月 232022

使用subprocess的Popen函数创建了一个进程

使用Popen的kill和terminate函数都杀不掉这个进程

后来发现是因为Popen的时候使用了shell=True参数，如果不使用这个参数可以杀掉

后来百度找到了其他方法

import psutil

def kill(proc_pid):
    process = psutil.Process(proc_pid)
    for proc in process.children(recursive=True):
        proc.kill()
        process.kill()

import psutil

def kill(proc_pid):

process = psutil.Process(proc_pid)

for proc in process.children(recursive=True):

proc.kill()

process.kill()

想要杀掉进程的时候使用这个kill参数并传入子进程的pid就可以了

            child = subprocess.Popen(['ping 192.168.1.10 -t'], shell=True, stdout=fileno, stderr=fileno)
            kill(child.pid)

1 2	child = subprocess.Popen(['ping 192.168.1.10 -t'], shell=True, stdout=fileno, stderr=fileno) kill(child.pid)

参考链接：http://www.dovov.com/shell-truepythonsubprocess.html

Page 1 of 40 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 Older Entries