Skip to content

feat(墨迹识别): 添加激进优化模式选项#484

Draft
doudou0720 wants to merge 2 commits into
net6from
fix/InkAnalyse
Draft

feat(墨迹识别): 添加激进优化模式选项#484
doudou0720 wants to merge 2 commits into
net6from
fix/InkAnalyse

Conversation

@doudou0720
Copy link
Copy Markdown
Member

未经实际测试

在墨迹转形状功能中新增激进优化模式开关,当启用时跳过积压的识别任务直接处理最新笔画,避免快速书写时程序卡顿甚至误判假死。


我们的电脑用的32位WPS导致卡死了,墨迹闪烁甚至误判假死

这个会把积压的任务直接丢弃,所以加了设置项

我觉得画图频率应该不是很快,对跑的动的用户也无感

在墨迹转形状功能中新增激进优化模式开关,当启用时跳过积压的识别任务直接处理最新笔画,避免快速书写时程序卡顿甚至误判假死。

Signed-off-by: doudou0720 <98651603+doudou0720@users.noreply.github.com>
@doudou0720 doudou0720 marked this pull request as draft May 9, 2026 11:03
Signed-off-by: doudou0720 <98651603+doudou0720@users.noreply.github.com>
@doudou0720 doudou0720 marked this pull request as ready for review May 9, 2026 15:20
@CJKmkp
Copy link
Copy Markdown
Member

CJKmkp commented May 10, 2026

hyw

@CJKmkp
Copy link
Copy Markdown
Member

CJKmkp commented May 10, 2026

什么垃圾设备

@CJKmkp
Copy link
Copy Markdown
Member

CJKmkp commented May 10, 2026

我觉得此功能是不必要的,因为4120不会出现此问题并且相关优化已经做过了

@CJKmkp
Copy link
Copy Markdown
Member

CJKmkp commented May 10, 2026

4120都能处理,而且多指书写的并行多墨迹纠正都没有任何问题

@CJKmkp
Copy link
Copy Markdown
Member

CJKmkp commented May 10, 2026

响应速度非常快,不存在积压

@CJKmkp CJKmkp marked this pull request as draft May 10, 2026 04:16
@CJKmkp
Copy link
Copy Markdown
Member

CJKmkp commented May 10, 2026

针对性能不足用户我的建议是不开墨迹纠正

@CJKmkp
Copy link
Copy Markdown
Member

CJKmkp commented May 10, 2026

我觉得我的测试书写速度应该远超正常使用的书写速度

@doudou0720
Copy link
Copy Markdown
Member Author

doudou0720 commented May 10, 2026 via email

@doudou0720
Copy link
Copy Markdown
Member Author

这个又不影响现有使用怕啥)

@CJKmkp
Copy link
Copy Markdown
Member

CJKmkp commented May 10, 2026

我觉得你还是先测了再说吧

@CJKmkp
Copy link
Copy Markdown
Member

CJKmkp commented May 13, 2026

我认为理论上墨迹识别不区分PPT软件

@doudou0720
Copy link
Copy Markdown
Member Author

我觉得你还是先测了再说吧

这两天期中,要等会

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants