问题1: clash 核心会多次并行启动 原因不明 ,希望可以再启动核心的时候做一下精准核对 当前是否不存在核心 或者做一个60s 轮询 是否存在多余的核心.
问题2:clash helper 存在安装不上的逻辑 ,比如我将它的本体 移动到回收站后, 再次进行安装。就会出现异常
需求1:当前没办法根据快速以图形化的方式去修改策略 的节点组 能包含什么节点, 希望可以改进.
需求2:切换节点自动断开连接,希望可以多一条可选项, 切换代理时 仅断开代理连接, 这样不会影响我的直连进程.
需求3:希望增加一个融合配置的gui 的操作界面. 以图形化的方式设计我们的通用规则 这样在切换每个代理都能生效
需求4:当前版本网络测试 无法指定要测速的对应域名, 有些局限, 我没办法知道哪个节点 访问我需要的目标网站会更加快
需求5:我节点太多时,无法快速通过搜索节点关键词 找到我的节点,这很不方便.
需求6:我点击右上角的clash 托盘 会有很大的延迟 大概2秒左右才会出现clash的图标, 可能是因为我的节点太多, 希望可以优化这个响应速度 ,它没必要一次性将所有信息显示出来, 或者它应该提前把该显示的信息缓存好. 这样可以降低响应速度
需求7:希望可以以gui 的方式 对clash当前配置 进行 节点筛选, 比如关键词 正则表达式, 仅显示我匹配中的节点 或者排除 我匹配中的节点.
===============================================================
Question 1: The "clash" core will start multiple times in parallel for an unknown reason. It is hoped that a precise check can be conducted when restarting the core. Is there currently no core present? Or, conduct a 60-second polling to check if there are any redundant cores.
Î
Question 2: Clash Helper has an installation issue—when I move its main file to the recycle bin and then attempt to reinstall it, an error occurs.
Requirement 1: Currently, there is no way to quickly and graphically modify which nodes a policy's node group can include. We hope this can be improved.
Requirement 2: When switching nodes, the connection is automatically disconnected. I would like an additional option to disconnect only the proxy connection when switching proxies, so that it does not affect my direct connection processes.
Requirement 3: We would like to add a GUI interface for integrated configuration, allowing us to design our general rules graphically so that changes take effect when switching between each proxy.
Requirement 4: The current version of the network test does not allow specifying the target domain for speed testing, which is somewhat limiting. I cannot determine which node will provide faster access to my intended website.
Requirement 5: When I have too many nodes, I cannot quickly locate my node by searching for keywords, which is inconvenient.
Requirement 6: When I click the Clash tray icon in the upper-right corner, there is a significant delay—about 2 seconds—before the Clash icon appears. This might be due to having too many nodes. I'd like to see this response time improved. It's not necessary to display all information at once; instead, it should cache the relevant data in advance so that the response speed can be reduced.
Requirement 7: It would be helpful to filter Clash's current configuration nodes via a GUI, for example, using keywords or regular expressions, allowing users to display only the nodes that match or exclude those that match.
问题1: clash 核心会多次并行启动 原因不明 ,希望可以再启动核心的时候做一下精准核对 当前是否不存在核心 或者做一个60s 轮询 是否存在多余的核心.
问题2:clash helper 存在安装不上的逻辑 ,比如我将它的本体 移动到回收站后, 再次进行安装。就会出现异常
需求1:当前没办法根据快速以图形化的方式去修改策略 的节点组 能包含什么节点, 希望可以改进.
需求2:切换节点自动断开连接,希望可以多一条可选项, 切换代理时 仅断开代理连接, 这样不会影响我的直连进程.
需求3:希望增加一个融合配置的gui 的操作界面. 以图形化的方式设计我们的通用规则 这样在切换每个代理都能生效
需求4:当前版本网络测试 无法指定要测速的对应域名, 有些局限, 我没办法知道哪个节点 访问我需要的目标网站会更加快
需求5:我节点太多时,无法快速通过搜索节点关键词 找到我的节点,这很不方便.
需求6:我点击右上角的clash 托盘 会有很大的延迟 大概2秒左右才会出现clash的图标, 可能是因为我的节点太多, 希望可以优化这个响应速度 ,它没必要一次性将所有信息显示出来, 或者它应该提前把该显示的信息缓存好. 这样可以降低响应速度
需求7:希望可以以gui 的方式 对clash当前配置 进行 节点筛选, 比如关键词 正则表达式, 仅显示我匹配中的节点 或者排除 我匹配中的节点.
===============================================================
Question 1: The "clash" core will start multiple times in parallel for an unknown reason. It is hoped that a precise check can be conducted when restarting the core. Is there currently no core present? Or, conduct a 60-second polling to check if there are any redundant cores.
Î
Question 2: Clash Helper has an installation issue—when I move its main file to the recycle bin and then attempt to reinstall it, an error occurs.
Requirement 1: Currently, there is no way to quickly and graphically modify which nodes a policy's node group can include. We hope this can be improved.
Requirement 2: When switching nodes, the connection is automatically disconnected. I would like an additional option to disconnect only the proxy connection when switching proxies, so that it does not affect my direct connection processes.
Requirement 3: We would like to add a GUI interface for integrated configuration, allowing us to design our general rules graphically so that changes take effect when switching between each proxy.
Requirement 4: The current version of the network test does not allow specifying the target domain for speed testing, which is somewhat limiting. I cannot determine which node will provide faster access to my intended website.
Requirement 5: When I have too many nodes, I cannot quickly locate my node by searching for keywords, which is inconvenient.
Requirement 6: When I click the Clash tray icon in the upper-right corner, there is a significant delay—about 2 seconds—before the Clash icon appears. This might be due to having too many nodes. I'd like to see this response time improved. It's not necessary to display all information at once; instead, it should cache the relevant data in advance so that the response speed can be reduced.
Requirement 7: It would be helpful to filter Clash's current configuration nodes via a GUI, for example, using keywords or regular expressions, allowing users to display only the nodes that match or exclude those that match.