mirror of
https://github.com/1Remote/1Remote.git
synced 2026-04-25 21:46:00 +03:00
[GH-ISSUE #623] 串口功能最新版彻底不能使用了 #1467
Labels
No labels
area-configuration
area-ct-app
area-ct-rdp
area-ct-remoteapp
area-ct-ssh
area-ct-vnc
area-launcher
area-list
area-tags
area-teamwork
bug
chore
dependencies
general-build/ci
general-performance
general-refactor
general-security
general-supportive
general-ux
meta-documentation
meta-enhancement
meta-enhancement
meta-feature
meta-help-wanted
meta-unknown-error
priority-hi
priority-low
pull-request
question
resolution-duplicate
resolution-invalid
resolution-wontfix
stale
task-put-off
task-still-considering
task-working-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/1Remote#1467
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Hi-360 on GitHub (Mar 11, 2024).
Original GitHub issue: https://github.com/1Remote/1Remote/issues/623
Originally assigned to: @VShawn on GitHub.
2024.02.20串口功能还能使用,现在最新更新的已经不能使用了 。我的系统环境是win10 在win11上一直都不能使用串口功能· 希望楼主能够尽快修复 现在1remote已经是主力工具了

@VShawn commented on GitHub (Mar 15, 2024):
奇怪了,今年以来串口协议相关的代码完全没有动过。
不过事实上我正在考虑移除串口协议,以后所有串口协议需求用户可以通过APP协议自行实现。
@Hi-360 commented on GitHub (Mar 15, 2024):
我也觉得很奇怪
@Hi-360 commented on GitHub (Mar 18, 2024):
这个问题 最近更新的版本中修复了吗?
@VShawn commented on GitHub (Mar 18, 2024):
没有改,没有调试环境,无法修复。
@Hi-360 commented on GitHub (Mar 27, 2024):
已经好了 串口也能正常使用了 感谢作者
| |
njfb1029
|
|
@.***
|
---- 回复的原邮件 ----
| 发件人 | @.> |
| 发送日期 | 2024年3月27日 14:58 |
| 收件人 | @.> |
| 抄送人 | Wu @.>,
@.> |
| 主题 | Re: [1Remote/1Remote] 串口功能最新版彻底不能使用了 (Issue #623) |
Closed #623 as completed via
b183078.—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>