[
{
"path": ".github/ISSUE_TEMPLATE/BugReport_en.yaml",
"content": "name: Bug Report\ndescription: File a bug report\nbody:\n - type: checkboxes\n attributes: \n label: Prerequisites\n options:\n - label: I have searched for related issues in the [issues](https://github.com/halo-dev/halo/issues) list.\n required: true\n - label: I have read the [FAQ](https://github.com/zhongyang219/TrafficMonitor/blob/master/Help_en-us.md) in detail and searched for related issues in FAQ list.\n required: true\n - type: input\n attributes:\n label: Current TrafficMonitor Version\n description: Right-click the TrafficMonitor tray icon, select `Help` → `About`.\n validations: \n required: true\n - type: input\n attributes:\n label: Current Operating System Version\n validations: \n required: true\n - type: textarea\n attributes:\n label: What happened?\n description: \"For ease of management, please do not report multiple unrelated issues under the same issue.\"\n validations:\n required: true\n - type: textarea\n attributes:\n label: Log Output\n description: \"Error logs can be found in the TrafficMonitor root directory. This will be automatically formatted as code, so no backticks are needed.\"\n render: shell\n - type: textarea\n attributes:\n label: Additional Information\n description: \"If you have other information to note, you can fill it in here.\"\n"
},
{
"path": ".github/ISSUE_TEMPLATE/BugReport_zh.yaml",
"content": "name: Bug反馈\ndescription: 提交Bug反馈\nbody:\n - type: checkboxes\n attributes: \n label: 前置条件\n options:\n - label: 已经在[issue](https://github.com/zhongyang219/TrafficMonitor/issues)列表中搜索了相关问题。\n required: true\n - label: 已详细阅读了[常见问题](https://github.com/zhongyang219/TrafficMonitor/blob/master/Help.md)并在常见问题列表中搜索了相关问题。\n required: true\n - type: input\n attributes:\n label: 您当前使用的TrafficMonitor版本\n description: 右键TrafficMonitor托盘图标，选择`帮助` → `关于`。\n validations: \n required: true\n - type: input\n attributes:\n label: 您当前使用的操作系统版本\n validations: \n required: true\n - type: textarea\n attributes:\n label: 发生了什么?\n description: \"为了方便我们管理，请不要在同一个issue下报告多个不相关的问题。\"\n validations:\n required: true\n - type: textarea\n attributes:\n label: 日志输出\n description: \"错误日志可在TrafficMonitor根目录中找到。 这将自动格式化为代码,因此无需反引号。\"\n render: shell\n - type: textarea\n attributes:\n label: 附加信息\n description: \"如果你还有其他需要提供的信息，可以在这里填写。\"\n"
},
{
"path": ".github/ISSUE_TEMPLATE/FeatureRequest_en.yaml",
"content": "name: Feature Request\ndescription: File a feature request\nbody:\n - type: checkboxes\n attributes: \n label: Prerequisites\n options:\n - label: I have searched for related issues in the [issues](https://github.com/zhongyang219/TrafficMonitor/issues) list.\n required: true\n - label: I have read the [wiki](https://github.com/zhongyang219/TrafficMonitor/wiki/Home_en) page and make sure that the current version of TrafficMonitor does not provide this feature.\n required: true\n - type: input\n attributes:\n label: Current TrafficMonitor Version\n description: \"Right-click the TrafficMonitor tray icon, select `Help` → `About`.\"\n validations: \n required: true\n - type: textarea\n attributes: \n label: Describe the feature\n description: \"For ease of management, please do not report multiple unrelated issues under the same issue.\"\n validations:\n required: true\n - type: textarea\n attributes:\n label: Additional Information\n description: \"If you have other information to note, you can fill it in here.\"\n"
},
{
"path": ".github/ISSUE_TEMPLATE/FeatureRequest_zh.yaml",
"content": "name: 功能请求\ndescription: 请求一个新功能\nbody:\n - type: checkboxes\n attributes: \n label: 前置条件\n options:\n - label: 已经在[issue](https://github.com/zhongyang219/TrafficMonitor/issues)列表中搜索了相关问题。\n required: true\n - label: 已经阅读了[wiki](https://github.com/zhongyang219/TrafficMonitor/wiki)页面并确保当前版本TrafficMonitor没有提供此功能。\n required: true\n - type: input\n attributes:\n label: 您当前使用的TrafficMonitor版本\n description: 右键TrafficMonitor托盘图标，选择`帮助` → `关于`。\n validations: \n required: true\n - type: textarea\n attributes: \n label: 描述一下该功能\n description: \"为了方便我们管理，请不要在同一个issue下提交多个没有相关性的特性。\"\n validations:\n required: true\n - type: textarea\n attributes:\n label: 附加信息\n description: \"如果你还有其他需要提供的信息，可以在这里填写。\"\n"
},
{
"path": ".github/ISSUE_TEMPLATE/config.yml",
"content": "blank_issues_enabled: false\n"
},
{
"path": ".github/workflows/main.yml",
"content": "name: Release CI\non: push\njobs:\n\n x64_build:\n runs-on: windows-latest\n\n steps:\n - uses: actions/checkout@v3\n \n - name: Add msbuild to PATH\n uses: microsoft/setup-msbuild@v2\n \n - name: Run msbuild\n run: msbuild -p:configuration=release -p:platform=x64 -p:platformToolset=v143\n \n - name: Get current time\n uses: josStorer/get-current-time@v2.0.2\n id: current-time\n with:\n format: YYYYMMDD_HHmmss\n utcOffset: \"+08:00\"\n \n - name : Upload artifact\n uses: actions/upload-artifact@v4\n with:\n name: x64_${{ steps.current-time.outputs.formattedTime }}_TrafficMonitor\n path: |\n Bin/x64/Release/TrafficMonitor.exe\n Bin/x64/Release/*.dll\n\n - name : Upload pdb files\n uses: actions/upload-artifact@v4\n with:\n name: x64_${{ steps.current-time.outputs.formattedTime }}_pdb\n path: Bin/x64/Release/*.pdb\n\n x86_build:\n runs-on: windows-latest\n\n steps:\n - uses: actions/checkout@v3\n \n - name: Add msbuild to PATH\n uses: microsoft/setup-msbuild@v2\n \n - name: Run msbuild\n run: msbuild -p:configuration=release -p:platform=x86 -p:platformToolset=v143\n \n - name: Get current time\n uses: josStorer/get-current-time@v2.0.2\n id: current-time\n with:\n format: YYYYMMDD_HHmmss\n utcOffset: \"+08:00\"\n \n - name : Upload artifact\n uses: actions/upload-artifact@v4\n with:\n name: x86_${{ steps.current-time.outputs.formattedTime }}_TrafficMonitor\n path: |\n Bin/Release/TrafficMonitor.exe\n Bin/Release/*.dll\n \n - name : Upload pdb files\n uses: actions/upload-artifact@v4\n with:\n name: x86_${{ steps.current-time.outputs.formattedTime }}_pdb\n path: Bin/Release/*.pdb\n\n arm64ec_build:\n runs-on: windows-latest\n\n steps:\n - uses: actions/checkout@v3\n \n - name: Add msbuild to PATH\n uses: microsoft/setup-msbuild@v2\n \n - name: Run msbuild\n run: msbuild -p:configuration=release -p:platform=ARM64EC -p:platformToolset=v143\n \n - name: Get current time\n uses: josStorer/get-current-time@v2.0.2\n id: current-time\n with:\n format: YYYYMMDD_HHmmss\n utcOffset: \"+08:00\"\n\n - name: Move dll file path \n run: mv Bin/x64/Release/*.dll Bin/ARM64EC/Release/\n\n - name : Upload artifact\n uses: actions/upload-artifact@v4\n with:\n name: arm64EC_${{ steps.current-time.outputs.formattedTime }}_TrafficMonitor\n path: |\n Bin/ARM64EC/Release/TrafficMonitor.exe\n Bin/ARM64EC/Release/*.dll\n\n - name : Upload pdb files\n uses: actions/upload-artifact@v4\n with:\n name: arm64EC_${{ steps.current-time.outputs.formattedTime }}_pdb\n path: Bin/ARM64EC/Release/*.pdb\n # winXP_build:\n # runs-on: windows-latest\n\n # steps:\n # - uses: actions/checkout@v3\n \n # - name: Add msbuild to PATH\n # uses: microsoft/setup-msbuild@v1.1.3\n \n # - name: Run msbuild\n # run: |\n # set ExternalCompilerOptions=/DCOMPILE_FOR_WINXP\n # msbuild -p:configuration=release -p:platform=x86 -p:platformToolset=v140_xp\n # shell: cmd\n \n # - name: Get current time\n # uses: josStorer/get-current-time@v2.0.2\n # id: current-time\n # with:\n # format: YYYYMMDD_HHmmss\n # utcOffset: \"+08:00\"\n \n # - name : Upload artifact\n # uses: actions/upload-artifact@v3\n # with:\n # name: winXP_${{ steps.current-time.outputs.formattedTime }}_TrafficMonitor\n # path: Bin/Release/TrafficMonitor.exe\n"
},
{
"path": ".gitignore",
"content": "## Ignore Visual Studio temporary files, build results, and\n## files generated by popular Visual Studio add-ons.\n##\n## Get latest from https://github.com/github/gitignore/blob/master/VisualStudio.gitignore\n\n# User-specific files\n*.suo\n*.user\n*.userosscache\n*.sln.docstates\n\n# User-specific files (MonoDevelop/Xamarin Studio)\n*.userprefs\n\n# Build results\n[Dd]ebug/\n[Dd]ebugPublic/\n[Rr]elease/\n[Rr]eleases/\nx64/\nx86/\nbld/\n[Bb]in/\n[Oo]bj/\n[Ll]og/\n\n# Visual Studio 2015 cache/options directory\n.vs/\n# Uncomment if you have tasks that create the project's static files in wwwroot\n#wwwroot/\n\n# MSTest test Results\n[Tt]est[Rr]esult*/\n[Bb]uild[Ll]og.*\n\n# NUNIT\n*.VisualState.xml\nTestResult.xml\n\n# Build Results of an ATL Project\n[Dd]ebugPS/\n[Rr]eleasePS/\ndlldata.c\n\n# .NET Core\nproject.lock.json\nproject.fragment.lock.json\nartifacts/\n**/Properties/launchSettings.json\n\n*_i.c\n*_p.c\n*_i.h\n*.ilk\n*.meta\n*.obj\n*.pch\n*.pdb\n*.pgc\n*.pgd\n*.rsp\n*.sbr\n*.tlb\n*.tli\n*.tlh\n*.tmp\n*.tmp_proj\n*.log\n*.vspscc\n*.vssscc\n.builds\n*.pidb\n*.svclog\n*.scc\n\n# Chutzpah Test files\n_Chutzpah*\n\n# Visual C++ cache files\nipch/\n*.aps\n*.ncb\n*.opendb\n*.opensdf\n*.sdf\n*.cachefile\n*.VC.db\n*.VC.VC.opendb\n\n# Visual Studio profiler\n*.psess\n*.vsp\n*.vspx\n*.sap\n\n# TFS 2012 Local Workspace\n$tf/\n\n# Guidance Automation Toolkit\n*.gpState\n\n# ReSharper is a .NET coding add-in\n_ReSharper*/\n*.[Rr]e[Ss]harper\n*.DotSettings.user\n\n# JustCode is a .NET coding add-in\n.JustCode\n\n# TeamCity is a build add-in\n_TeamCity*\n\n# DotCover is a Code Coverage Tool\n*.dotCover\n\n# Visual Studio code coverage results\n*.coverage\n*.coveragexml\n\n# NCrunch\n_NCrunch_*\n.*crunch*.local.xml\nnCrunchTemp_*\n\n# MightyMoose\n*.mm.*\nAutoTest.Net/\n\n# Web workbench (sass)\n.sass-cache/\n\n# Installshield output folder\n[Ee]xpress/\n\n# DocProject is a documentation generator add-in\nDocProject/buildhelp/\nDocProject/Help/*.HxT\nDocProject/Help/*.HxC\nDocProject/Help/*.hhc\nDocProject/Help/*.hhk\nDocProject/Help/*.hhp\nDocProject/Help/Html2\nDocProject/Help/html\n\n# Click-Once directory\npublish/\n\n# Publish Web Output\n*.[Pp]ublish.xml\n*.azurePubxml\n# TODO: Comment the next line if you want to checkin your web deploy settings\n# but database connection strings (with potential passwords) will be unencrypted\n*.pubxml\n*.publishproj\n\n# Microsoft Azure Web App publish settings. Comment the next line if you want to\n# checkin your Azure Web App publish settings, but sensitive information contained\n# in these scripts will be unencrypted\nPublishScripts/\n\n# NuGet Packages\n*.nupkg\n# The packages folder can be ignored because of Package Restore\n**/packages/*\n# except build/, which is used as an MSBuild target.\n!**/packages/build/\n# Uncomment if necessary however generally it will be regenerated when needed\n#!**/packages/repositories.config\n# NuGet v3's project.json files produces more ignorable files\n*.nuget.props\n*.nuget.targets\n\n# Microsoft Azure Build Output\ncsx/\n*.build.csdef\n\n# Microsoft Azure Emulator\necf/\nrcf/\n\n# Windows Store app package directories and files\nAppPackages/\nBundleArtifacts/\nPackage.StoreAssociation.xml\n_pkginfo.txt\n\n# Visual Studio cache files\n# files ending in .cache can be ignored\n*.[Cc]ache\n# but keep track of directories ending in .cache\n!*.[Cc]ache/\n\n# Others\nClientBin/\n~$*\n*~\n*.dbmdl\n*.dbproj.schemaview\n*.jfm\n*.pfx\n*.publishsettings\norleans.codegen.cs\n\n# Since there are multiple workflows, uncomment next line to ignore bower_components\n# (https://github.com/github/gitignore/pull/1529#issuecomment-104372622)\n#bower_components/\n\n# RIA/Silverlight projects\nGenerated_Code/\n\n# Backup & report files from converting an old project file\n# to a newer Visual Studio version. Backup files are not needed,\n# because we have git ;-)\n_UpgradeReport_Files/\nBackup*/\nUpgradeLog*.XML\nUpgradeLog*.htm\n\n# SQL Server files\n*.mdf\n*.ldf\n*.ndf\n\n# Business Intelligence projects\n*.rdl.data\n*.bim.layout\n*.bim_*.settings\n\n# Microsoft Fakes\nFakesAssemblies/\n\n# GhostDoc plugin setting file\n*.GhostDoc.xml\n\n# Node.js Tools for Visual Studio\n.ntvs_analysis.dat\nnode_modules/\n\n# Typescript v1 declaration files\ntypings/\n\n# Visual Studio 6 build log\n*.plg\n\n# Visual Studio 6 workspace options file\n*.opt\n\n# Visual Studio 6 auto-generated workspace file (contains which files were open etc.)\n*.vbw\n\n# Visual Studio LightSwitch build output\n**/*.HTMLClient/GeneratedArtifacts\n**/*.DesktopClient/GeneratedArtifacts\n**/*.DesktopClient/ModelManifest.xml\n**/*.Server/GeneratedArtifacts\n**/*.Server/ModelManifest.xml\n_Pvt_Extensions\n\n# Paket dependency manager\n.paket/paket.exe\npaket-files/\n\n# FAKE - F# Make\n.fake/\n\n# JetBrains Rider\n.idea/\n*.sln.iml\n\n# CodeRush\n.cr/\n\n# Python Tools for Visual Studio (PTVS)\n__pycache__/\n*.pyc\n\n# Cake - Uncomment if you are using it\n# tools/**\n# !tools/packages.config\n\n# Telerik's JustMock configuration file\n*.jmconfig\n\n# BizTalk build output\n*.btp.cs\n*.btm.cs\n*.odx.cs\n*.xsd.cs\n\n*.ini\n!skin.ini\n*.dat\n*.bak\n/TrafficMonitor/skins/test*\n[Dd]ebug (without temperature)/\n[Rr]elease (without temperature)/\n[Dd]ebug (lite)/\n[Rr]elease (lite)/\n/TrafficMonitor/compile_time.txt\n!/TrafficMonitor/language/*.ini\n*.diagsession\n"
},
{
"path": "Help.md",
"content": "**简体中文 | [English](./Help_en-us.md)**\n\n## TrafficMonitor 常见问题\n这里是关于TrafficMonitor常见问题的页面，如果你想查看关于TrafficMonitor的各项功能和使用方法的详细介绍，请[点击这里](https://github.com/zhongyang219/TrafficMonitor/wiki)转到TraffinMonitor Wiki页面。\n\n### Windows11下任务栏窗口和系统小组件重叠\n\n在Windows11下，可以通过以下步骤解决此问题：\n\n打开“选项设置”——“任务栏设置”，点击“Windows11相关设置”按钮，勾选“避免与右侧小组件重叠”选项，如下图所示。\n\n\n\n如果你的任务栏中没有显示“小组件”，则此选项是灰色不可用状态。\n\n### Windows11下“任务栏窗口显示在任务栏左侧”是灰色不可用状态\n\n在Windows11，只有在任务栏居中的情况下，此选项才可用。\n\n因为当任务栏靠左显示时，左侧没有给TrafficMonitor显示的空间。 \n\n### Windows11下，当任务栏被占满时，TrafficMonitor的任务栏窗口和任务栏图标重叠\n\n\n\n这个问题目前无法解决，建议尽量不要让任务栏被占满，或者在系统设置中将“合并任务栏按钮和标签”改为“始终”。\n\n请不要向我反馈此问题。\n\n### 如何显示CPU和内存利用率？\n\n在主窗口点击右弹出键菜单，勾选“显示更多信息”。如果需要在任务栏窗口中也显示CPU和内存利用率，则在任务栏窗口中点击右键弹出菜单，选择“显示设置”，在弹出对话框中勾选“CPU和内存利用率”即可。\n\n### 如何更改任务栏中“CPU”、“内存”等文本\n\n任务栏窗口中的标签文本是可以自定义的。点击鼠标右键，在右键菜单中选择“选项”，点击“任务栏窗口设置”，点击“显示文本设置”，双击项目右侧的文本即可更改，然后点击两次“确定”即可。\n\n\n\n由于这些文本是可以自定义的，因此切换语言时不会自动更改。在切换语言后，你可以点击“显示文本”对话框中的“恢复默认”按钮。\n\n### 网速一直显示为0KB\n\n这种情况可能是因为你电脑中正在使用的网卡发生了切换导致的。\n\n点击右键菜单“选择网络连接”下面的“刷新网络连接列表”也许可以解决这个问题。\n\n\n\n如果问题仍然存在，请尝试在“选择网络连接”的子菜单下选择你要监控的网络连接，而不是选择“自动选择”。\n\n如果问题仍然存在，请尝试在“选项设置”>“常规设置”>“高级”中点击“选择要监控的网络连接”按钮，在弹出的对话框中只勾选你想监控的网络连接，去掉其他项目的勾选，点击两次“确定”按钮即可。\n\n\n\n### 如何单独设置任务栏窗口中每个项目的颜色？\n在右键菜单中选择“选项”，切换到“任务栏窗口设置”，勾选“指定每个项目的颜色”，此时再点击“文本颜色”右边的颜色块，就会弹出“任务栏窗口颜色设置”的对话框了。\n\n如果不勾选“指定每个项目的颜色”，则只能为文本设置统一的颜色。\n\n### 设置了开机自动运行仍然无法开机自启。\n从1.80版本开始，标准版和Lite版采用了不同的方式来实现开机自启动。\n\n* Lite版和1.80以前的版本：\n\n Lite版和1.80以前的版本的开机启动功能是通过在注册表“计算机\\HKEY_CURRENT_USER\\Software\\Microsoft\\Windows\\CurrentVersion\\Run”中创建“TrafficMonitor”的注册表项来实现的，如果你遇到无法开机启动的问题，请先检查该注册表项是否存在，再检查程序的路径是否正确。如果你移动了程序的位置，则会因为路径无效导致开机自启动失效，此时只需要在选项设置中取消“开机自动运行”的勾选，再将其勾选上就可以了。\n\n 注意，某些第三方安全软件可能会阻止TrafficMonitor的开机自启动，请尝试在安全软件中允许TrafficMonitor开机自启动。\n\n 如果设置了以管理员身份运行也会出现开机无法自启动的问题，请尝试去掉以管理员身份运行。\n\n* 标准版：\n\n 标准版是通过创建任务计划来实现开机自启动的。可以通过`控制面板\\系统和安全\\管理工具`来打开任务计划程序。\n\n 如下图所示：\n\n \n\n 如果你遇到无法开机自启动的情况，请到“任务计划程序”中检查TrafficMonitor的计划任务是否正常创建，exe文件的路径是否正确。\n\n开机无法自启动的一个常见原因是你可能移动了TrafficMonitor主程序的位置。如果你为TrafficMonitor设置好了开机自动运行，但是你将TrafficMonitor移动到了其他位置，那么开机自启动肯定就失效了。你需要打开TrafficMonitor的“选项设置”——“常规设置”，如果“开机时自动运行”处于勾选状态，先去掉勾选，然后再次打开“选项设置”——“常规设置”，重新勾选“开机时自动运行”即可。\n\n需要注意的是，如果你使用不含温度监控的版本在注册表中创建了开机自启动项，然后再使用包含温度监控的版本开启开机自启动功能，它会自动将注册表中的开机自启动项删除，再在任务计划中创建开机自启动项。反之亦然。\n\n### 程序弹出“无法保存设置”的对话框。\n如果遇到这种情况，说明程序没有向其所在目录下写入数据的权限，导致设置数据无法保存。尝试将程序移动到其他有写入权限的文件夹中可以解决这个问题。\n\n你也可以通过以下步骤将配置文件的保存路径改为C:\\Users\\\\<用户名\\>\\AppData\\Roaming\\TrafficMonitor目录。\n\n* 退出TrafficMonitor，以管理员身份重新启动TrafficMonitor。\n* 在右键菜单中选择“选项”，切换到“常规设置”选项卡，在“数据和配置文件”中选择“保存到Appdata目录”。\n\n如果此时仍然提示“无法保存设置”，请打开应用程序所在目录，打开`global_cfg.ini`文件，如果不存在请新建一个，在里面添加如下内容：\n\n```\n[config]\nportable_mode = false\n```\n\n如果无法新建，可以在其他位置（比如桌面）新建该文件，然后移动到程序所在目录。\n\n如果`global_cfg.ini`文件已存在，就把`portable_mode `的值改成`false`，保存后重新启动TrafficMonitor。\n\n如果`global_cfg.ini`没有写入权限，可以尝试把该文件复制到桌面，改好后复制回原来的路径将原文件覆盖。\n\n执行以上步骤后理论上应该不会出现这种问题了。如果这个问题仍然出现，请尝试把C:\\Users\\\\<用户名\\>\\AppData\\Roaming\\TrafficMonitor\\config.ini删除，该文件会在删除后重新生成。\n\n在1.79以后的版本中，如果程序所在目录无法写入数据，会自动将配置和数据文件保存到C:\\Users\\\\<用户名\\>\\AppData\\Roaming\\TrafficMonitor目录，此时，“选项”——“常规设置”——“数据和配置文件”中“保存到程序所在目录”将不可用。\n\n### 更改设置后下次开机时设置丢失\n\n如果你没有看到“无法保存设置”的对话框，则说明程序的配置文件是能正常保存的。因此这个问题的原因可能是你的电脑中存在了多个TrafficMonitor的程序文件，并且配置文件保存在了程序所在目录下。\n\n例如，你打开了“D:\\software\\TrafficMonitor\\TrafficMonitor.exe”，并且更改了选项设置，但是下次开机时启动的却是“D:\\software1\\TrafficMonitor\\TrafficMonitor.exe”，而你之前修改的配置被保存在了“D:\\software\\TrafficMonitor\\”目录下。\n\n解决这个问题的方法是：\n\n1. 在“选项设置”>“常规设置”>“配置和数据文件”中，将配置文件的保存位置更改为Appdata目录。\n2. 删除你电脑中不需要的TrafficMonitor的程序文件，启动TrafficMonitor后，打开“选项设置”>“常规设置”，点击“重新设置开机自动运行”按钮。\n\n### 网速数值显示不全。\n由于不同字体每个字符的宽度并不一样，在某些情况下，确实会出现网速数值显示不全的问题。如果出现了这样的问题，请打开“选项”——“任务栏窗口设置”，在“数据位数”下拉列表中选择一个更大的值。\n### 设置了鼠标穿透后如何取消？\n在通知区的TrafficMonitor的图标上点击鼠标右键，去掉“鼠标穿透”的勾选即可。\n\n设置了鼠标穿透后，悬浮窗将无法响应任何鼠标消息，也无法弹出右键菜单，但是可以通过通知区图标来弹出右键菜单。主窗口的右键菜单和通知区图标的右键是完全一样的。\n\n另外，即使你之前设置了隐藏通知区图标，开启鼠标穿透后，通知区图标也会自动显示出来，防止无法弹出右键菜单。\n\n说明：以下几种情况下通知区图标会自动显示出来：\n\n* 开启鼠标穿透后；\n* 不显示任务栏窗口的情况下隐藏主窗口后；\n* 隐藏主窗口的情况下关闭任务栏窗口后；\n* 开启鼠标穿透的情况下关闭任务栏窗口后。\n### Windows 10 白色任务栏主题时任务栏窗口颜色的问题\n\n在使用白色任务栏主题时，你可以在在“任务栏窗口设置”点击“预设方案”按钮，选择“浅色模式”，可以一键设置浅色模式任务栏颜色。如图所示：\n\n\n\n同时，你还可能勾选“自动适应Windows10深色/浅色主题”，程序会在Windows10深色/浅色主题更换时自动切换颜色方案。你可以点击“自动适应设置”按钮来配置在深色和浅色主题时分别使用哪个颜色预设。\n\n### 在Windows7/Windows8/8.1下任务栏窗口有个背景色，无法完全透明\n这个问题确实存在，但是在Win10下是正常的。这个问题暂时无法解决。\n\n在1.79以后的版本中，Windows8/8.1下可以在“选项”——“任务栏窗口设置”中勾选“背景色透明”，再勾选“根据任务栏颜色自动设置背景色”即可获得较好的显示效果。\n\n### 任务栏窗口有时会显示不全，比如单位被覆盖了\n这确实是一个BUG，但是我目前还没有找到一个好的解决方法，这个问题通常出现在任务栏右侧通知区域宽度变化的时候，主要在在切换输入法的时候，如果出现了这个问题，可以将通知区任意一个图标向上拖动将其隐藏，再将其拖下来即可恢复正常。\n出现这个问题原因在于，由于系统任务栏通知区的图标数量可能会发生变化，导致通知区的宽度也会时常变化，当通知区的宽度发生变化时，TrafficMonitor的任务栏窗口需要实时调整其位置。但是由于我无法知道通知区的宽度在什么时候变化，因此只能每隔一段时间判断是否需要调整位置，如果任务栏通知区域的宽度变化得太快，就会导致TrafficMonitor的任务栏无法及时调整其位置，从而导致了这个BUG。\n\n**以下步骤或许可以解决这个问题：**\n\n* 打开“设置”\n* 点击“时间和语言”——“区域和语言”\n* 点击右侧“高级键盘设置”\n* 勾选“使用桌面语言栏”\n* 右键点击任务栏，选择“任务栏设置”\n* 点击“打开或关闭系统图标”，关闭“输入指示”\n方法来自知乎 [win10的任务栏为何一点击就乱动？](https://www.zhihu.com/question/312032145/answer/627965084)\n\n### Windows10中开启HDR后任务栏窗口无法显示\n\n部分用户反馈，在Windows10中开始HDR功能会导致任务栏窗口无法显示。如果遇到这个问题，可以尝试在[“选项设置”——“任务栏窗口设置”](https://github.com/zhongyang219/TrafficMonitor/wiki/选项设置#任务栏窗口设置)中关闭“背景透明”选项的勾选。\n\n在1.85版本以后，可以通过在“选项设置”——“任务栏窗口设置”——“渲染设置”中改成Direct2D渲染来解决这个问题。\n\n### CPU利用率显示和任务管理器不一致\n\n在Windows10及以上操作系统中，如果你需要让TrafficMonitor显示的CPU利用率和任务管理器一致，请到[“选项设置”——“常规设置”——“高级”](https://github.com/zhongyang219/TrafficMonitor/wiki/选项设置#高级)——“CPU使用率获取方式”中选择“使用性能计数器”。\n\n由于Windows10以上操作系统中任务管理器获取CPU利用率的方式发生了改变，因此选择“基于CPU使用时间”的方式获取到的CPU利用率会和任务管理器中显示的不一致。\n\n### 关于TrafficMonitor温度监控的问题\n\n由于温度监控功能在某些电脑中存在一些问题，因此温度监控功能默认是关闭的，如果你要使用TrafficMonitor的温度监控功能，请到[“选项设置”-“常规设置”-“硬件监控”](https://github.com/zhongyang219/TrafficMonitor/wiki/选项设置#硬件监控)中开启。开启后，任务栏右键菜单中的“显示设置”子菜单下才会出现温度相关的项目。\n\nTrafficMonitor的温度监控功能依赖第三方开源库[LibreHardwareMonitor](https://github.com/LibreHardwareMonitor/LibreHardwareMonitor)。如果你遇到硬件温度无法显示，或者显示的温度异常的问题，请先下载LibreHardwareMonitor，并查看LibreHardwareMonitor是否能正常显示对应的温度。如果下载的最新版LibreHardwareMonitor可以正常监控到硬件温度，则将下载的LibreHardwareMonitor文件夹中的LibreHardwareMonitorLib.dll替换掉TrafficMonitor文件夹下的LibreHardwareMonitorLib.dll文件，即可解决温度无法检测的问题。\n\n请不要向我反馈诸如温度显示不准确、显卡利用率不准确之类的问题，此类问题我无法解决。TrafficMonitor不是专业的硬件监控软件，无法保证硬件监控的数据在所有设备上的准确性。\n\n**注意：硬件监控功能（包括温度监控和显卡使用率监控）可能存在一些问题，它可能会占用更多的CPU和内存。据部分用户反馈，开启温度功能后会导致程序崩溃和系统死机等问题，请在知晓以上风险后再决定开启硬件监控功能。否则，请不要使用硬件监控功能。**\n\n### 程序启动时提示找不到“MSVC\\*.dll”、“mfc\\*.dll”、“vc*.dll”\n\n点击以下链接下载并安装Microsoft Visual C++ 运行环境。\n\n[最新支持的 Visual C++ 可再发行程序包下载 | Microsoft Docs](https://docs.microsoft.com/zh-CN/cpp/windows/latest-supported-vc-redist?view=msvc-170)\n\n### 我希望在任务栏上显示更多硬件信息，比如风扇转速、功率等\n\n现在推出了硬件监控插件，可以显示LibreHardwareMonitor中所有监控项目。\n\n\n\n使用说明和下载链接请点下方链接转到插件下载页面：\n\n[TrafficMonitorPlugins/download/plugin_download.md at main · zhongyang219/TrafficMonitorPlugins](https://github.com/zhongyang219/TrafficMonitorPlugins/blob/main/download/plugin_download.md)\n\n### 关于程序崩溃问题\n\n如果遇到程序崩溃的问题，重新启动程序后，请先到“选项”——“常规设置”——“硬件监控”中关闭所有项目的硬件监控，因为基于用户提供的dmp文件发现，大多数崩溃问题都和硬件监控功能有关。和硬件监控功能相关的崩溃问题我无法解决，请不要向我发送邮件反馈。如果你排除了硬件监控的问题，但是崩溃问题仍然存在，请先到“选项”——“常规设置”——“高级”——“插件管理”中禁用所有插件，再重新启动程序（如果程序无法启动，请删除TrafficMonitor所在目录下plugins里面的所有dll文件）。如果排除了插件的问题，但是崩溃问题仍然存在，请根据崩溃弹窗中的提示向我发送电子邮件。\n\n如果还遇到其他问题，也可以点击“关于”对话框中的“联系作者”，或者直接[点击此处](mailto:zhongyang219@hotmail.com)向我发送电子邮件。但我由于作者的能力有限，我并不能保证可以解决所有问题，但是你的反馈也许可以帮助我更好的改进这个软件。\n请在邮件中尽可能详细地描述你遇到的问题，出现了什么错误提示，你尝试过哪些操作等，最好能够附上截图和配置文件（“选项”——“常规设置”——“打开配置文件所在路径”）。\n注意，发送前请先确认一下你发送时使用的电子邮件地址，如果你的邮件地址是形如“outlook_随机字符串@outlook.com”的格式，那么这样的邮箱地址是无法回复的。\n这可能是由于你使用了第三方邮箱地址作为Microsoft账号登录Windows导致的。如果有这样的情况，请务必在邮件中附上正确的电子邮件地址。\n"
},
{
"path": "Help_en-us.md",
"content": "**[简体中文](./Help.md) | English**\n\n# TrafficMonitor Frequently Asked Questions\nThis is the page about the Frequently Asked Questions of TrafficMonitor. If you want to view the detailed introduction of the functions and usage of TrafficMonitor, please [click here](https://github.com/zhongyang219/TrafficMonitor/wiki) to go the the TraffinMonitor Wiki page.\n\n### In Windows 11, the taskbar window overlapped with the windows Widgets\n\nIn Windows 11, this issue can be fixed with the following steps:\n\nOpen \"Option Settings\"-\"Taskbar Window Settings\", click the \"Settings related to Windows 11\" button, and check \"Avoid overlapping with right Widgets\" option. As shown in the picture bellow.\n\n\n\nIf the Widgets is not showing on the taskbar, this option is grayed.\n\n### In Windows 11, \"The taskbar window appears to the left of the taskbar\" is grayed\n\nIn Windows 11, this option is only available when the taskbar is align centered.\n\nBecause when the taskbar is displayed on the left, there is no space on the left side for TrafficMonitor to display.\n\n### In Windows 11, the taskbar window of TrafficMonitor overlaps with the taskbar icons when taskbar is full\n\n\n\nThis problem cannot be fixed at present. It is recommended to try not to fill the taskbar, or change \"Merge taskbar buttons and tabs\" to \"Always\" in the system settings.\n\nPlease do not send feedback to me on this issue.\n\n### How to show the CPU and memory usage?\n\nRight click the main window and check \"Show More Info\". If you also need to display the CPU and memory usage in the taskbar window, right click the taskbar window and select \"Display Settings\", check \"CPU and Memory Usage\" in the pop-up dialog box.\n\n### How do I change the text such as \"CPU\" and \"MEM\" in the taskbar\n\nThe label text in the taskbar window can be customized. Right click on the taskbar window, select \"Options\", click \"Taskbar Windows Settings\", click \"Display Text settings\" button, the text on the right side of the item can be modified by double click. After modified, click \"OK\" button twice.\n\n\n\nBecause the text is customizable, it does not automatically change when you switch the language. After you swatch the language, you can click \"Restore default\" button in the \"Display Text settings\" dialog box.\n\n### The net speed is always displayed as 0KB\n\nThis may caused by the switch of the network you are using on your computer.\n\nClick \"Refresh connection list\" under \"Select network connections\" in the context menu may solve this problem.\n\n\n\nIf this problem still exists, please try to select the network connection you want to monitored in the \"Select network connections\" submenu instead of select \"Auto select\".\n\nIf this problem still exists, please try to click the \"Select the connection to monitor\" button in \"Options Settings\" > \"General Settings\" > \"Advanced\", check the network you want to monitored, uncheck other items, and click \"OK\" button twice.\n\n\n\n### How do I set the color of each item in the taskbar window individually?\n\nSelect \"Options\" In the right-click menu, switch to \"Taskbar Window Settings\" tab, check \"Specify colors for each item\", and then click the color block on the right side of \"Text Color \" to pop up the dialog box for taskbar window color settings. \n\nIf you do not check \"Specify colors for each item\", you can only set the uniform color for the text.\n\n### \"Auto run when Windows start\" dose not work\nStarting from version 1.80, the version with temperature monitoring and the version without temperature monitoring have adopted different methods to realize \"auto run when Windows start\".\n\n* Versions without temperature monitoring and versions before 1.80:\n\n The auto run function of the versions without temperature monitoring and versions before 1.80 is achieved by creating the \"TrafficMonitor\" key in the registry path of \"Computer\\HKEY_CURRENT_USER\\Software\\Microsoft\\Windows\\CurrentVersion\\Run\".\n If you encounter the problem of auto run dose not work, please check that the registry exists, and then check the program path is correct. If you move the location of the program, the auto run will be invalid because of the program location being invalid. In this case, you only need to uncheck \"Auto run when Windows start\" in the option settings, and then check it on.\n\n Note that some third-party security software may prevent TrafficMonitor from booting up automatically. Please try to allow TrafficMonitor to boot up automatically in the security software.\n\n If you set the program to run as an administrator, the auto run function will also not work. Please try to remove running as an administrator.\n\n* Version with temperature monitoring:\n\n The version that includes temperature monitoring implements auto run function by creating a task plan. The task scheduler can be opened through `Control Panel\\System and Security\\Administrative Tools`. As shown below:\n\n \n\n If you encounter that situation that the program cannot be started automatically after booting, please go to \"Task Scheduler\" to check whether the scheduled task of TrafficMonitor is created normally and the path of the exe file is correct.\n\nA common reason why the \"Auto run when Windows start\" dose not work is that you may have moved the location of the TrafficMonitor main program. If you have set up TrafficMonitor to run automatically at startup, but you move TrafficMonitor to another location, then the auto run at startup will definitely fail. You need to open \"Option Settings\"-\"General Settings\" of TrafficMonitor, if \"Auto run when Windows start\" is checked, remove the check, then open \"Option Settings\"-\"General Settings\" again, and check again \"Auto run when Windows start\" will be fine.\n\nIt should be noted that if you use the version without temperature monitoring to create a auto-start item in the registry, and then use the version that with temperature monitoring to turn on the \"Auto run when Windows start\" function, it will automatically delete the auto-start item in the registry, and then create a auto-start item in the task plan. vice versa.\n\n### The program pops up the \"Unable to Save Settings\" message box.\nIf you encountered this problem, that means the program does not have permission to write data to its directory, causing the settings data cannot be saved. Try to move the program to another folder that has write permissions will save this problem. \nYou can also change the save path of the configuration and data file to the C:\\Users\\\\\\AppData\\Roaming\\TrafficMonitor directory by the following steps. \n\n* Exit TrafficMonitor and restart TrafficMonitor as an administrator.\n* Select \"Options\" in the right-click menu, switch to the \"General Settings\" tab, and select \"Save to AppData Directory\" in \"Configuration and data files\".\n\nIf it still pops up the \"Unable to Save Settings\" message box, open the directory where the application is located, open the `global_cfg.ini` file. If it doesn't exist, create a new one, adding the following:\n\n```\n[config]\nportable_mode = false\n```\n\nIf the file cannot be created, you can create the file in a different location, such as the desktop, and then move to the directory where the program is located.\n\nIf the `global_cfg.ini` file already exists, change the value of `portable_mode` to `false` and save, then restart TrafficMonitor.\n\nIf `global_cfg.ini` does not have write permission, you can try copying the file to the desktop, and then copying it back to the original path to overwrite the original file after modified.\n\nAfter these steps, this problem should not theoretically occur. If this problem still occurs, try to delete the file C:\\Users\\\\\\AppData\\Roaming\\TrafficMonitor\\config.ini. This file will be regenerated after it is deleted. \n\nIn version 1.79 and later, if the directory where the program located is not writable, the configuration and data files will be automatically saved to the \"C:\\Users\\\\\\AppData\\Roaming\\TrafficMonitor\" directory. At this time, \"Options\" -“General Settings”-“Save to the program directory” in “Configuration and data files” will not be available.\n\n### The configuration is lost after next start up\n\nIf you do not see the \"Unable to Save Settings\" message box, that means the configuration file can be saved normally. The cause of this problem may be that you have multiple TrafficMonitor application files on your computer and the configuration files are saved in the application directory.\n\nFor example, you have open \"D:\\software\\TrafficMonitor\\TrafficMonitor.exe\", and modified the configuration, but next time you start your computer, \"D:\\software1\\TrafficMonitor\\TrafficMonitor.exe\" is started, while the configuration files you modified before is saved in \"D:\\software\\TrafficMonitor\\\\\".\n\nThe method to solve this problem is:\n\n1. Change the save location of the configuration files to AppData directory in \"Option Settings\" > \"General Settings\" > \"Configuration and data file\".\n2. Delete the TrafficMonitor application files you don't need on your computer, start TrafficMonitor, open \"Option Settings\" > \"General Settings\", click \"Reset autorun\" button. \n\n### The net speed value is not fully displayed.\nBecause the width of each character in different fonts is not the same, in some cases, it does appear the problem of the net speed value is not fully displayed. If this problem occurs, open \"Options\"-\"Taskbar Window Settings\", and select a larger value in the \"Number of digits\" drop down list.\n### How to cancel after setting the mouse penetrate?\nRight click the TrafficMonitor icon in the notification area, uncheck the \"Mouse Penetrate\".\nAfter the mouse penetrate is set, the suspension window will not be able to respond to any mouse messages, or pop-up right-click menu. But the menu can be popped up by right click the icon in notification area. The right-click menu of the main window and which of the notification area icon is exactly the same.\nIn addition, even if you have previously set the hidden notify icon, when the \"mouse penetrate\" is set, the notify icon will also automatically appear to prevent the right-click menu cannot be displayed. \nNote: The notification area icon will be automatically displayed in the following situations: \n\n* After the \"Mouse Penetrate\" is set;\n* Hide the main window without displaying the taskbar window;\n* Close the taskbar window when the main window is hidden;\n* Close the taskbar window when the \"Mouse Penetrate\" is set.\n### Problems with the taskbar window color in Windows 10 white taskbar theme\nWhen using the white taskbar theme, you can click the \"Preset\" button in the \"Taskbar Window Settings\" and select \"Light Mode\" to set the taskbar color in light mode. As the picture shows:\n\n\n\nAt the same time, you may also check \"Auto adapt to Windows 10 dark/light theme\", the program will automatically switch the color preset when Windows 10 dark/light theme is changed. You can click the \"Auto Adapt settings\" button to configure which color preset to use for dark and light themes.\n\n### The taskbar windows cannot be displayed when the HDR is turned on in Windows 10\n\nSome users have reported that turning on the HDR function in Windows 10 will cause the taskbar window to fail to display. If you encounter this problem, you can try turning off the \"Background Transparent\" option in [\"Option Settings\" - \"Taskbar Window Settings\"](https://github.com/zhongyang219/TrafficMonitor/wiki/选项设置#任务栏窗口设置).\n\nSince version 1.85, this can be fixed by changing to Direct2D rendering in \"Options Settings\" - \"Taskbar Window Settings\" - \"Rendering Settings\".\n\n### The CPU usage displayed is inconsistent with Task Manager\n\nSince Windows 10, if you want to make the CPU usage shown by TrafficMonitor consistent with Task Manager, please go to \"Option Settings\"-\"General Settings\"-\"Advanced\"-\"CPU usage acquisition method\", and select \"Use the performance counter\".\n\n### About the temperature monitoring of TrafficMonitor\n\nDue to some problems occurred in some computers caused by the temperature monitoring function, the temperature monitoring function is turned off by default. If you want to use the temperature monitoring function of TrafficMonitor, please go to [\"Option Settings\"-\"General Settings\"-\"Hardware Monitoring\"](https://github.com/zhongyang219/TrafficMonitor/wiki/选项设置#硬件监控) to enable it. After it is turned on, temperature-related items will appear under the \"Display Settings\" submenu in the taskbar right-click menu.\n\nThe temperature monitoring function of TrafficMonitor relies on a third-party open source library [LibreHardwareMonitor](https://github.com/LibreHardwareMonitor/LibreHardwareMonitor). If you encounter the problem that the hardware temperature cannot be displayed, or the displayed temperature is incorrect, then please download LibreHardwareMonitor first, and check whether LibreHardwareMonitor can display the corresponding temperature normally.\n\nIf LibreHardwareMonitor cannot display the temperature of the corresponding hardware, then I cannot solve this problem. You can report your problem to the author of LibreHardwareMonitor.\n\nIf the latest version of LibreHardwareMonitor can display the hardware temperature normally, replace the LibreHardwareMonitorLib.dll files in the TrafficMonitor folder with the downloaded the LibreHardwareMonitorLib.dll files may solve this problem.\n\n**Note: The hardware monitoring function (including temperature monitoring and GPU usage monitoring) may have some problems, which may cause more CPU and memory usage. According to feedback from some users, turning on the temperature function will cause problems such as program crashes and system crashes. Please decide to turn on the hardware monitoring function after you are aware of the above risks. Otherwise, please do not use the hardware monitoring function.**\n\n## The program prompts that \"MSVC\\*.dll\" or \"mfc\\*.dll\" cannot be found when the program starts\n\nClick the link below to download and install the Microsoft Visual C++ runtime environment.\n\n[Latest supported Visual C++ Redistributable downloads | Microsoft Docs](https://docs.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170)\n\n### I want to have more hardware information on the taskbar, such an fan speed, power, etc\n\nThe Hardware Monitor plug in is now available. It can display all the monitoring items in LibreHardwareMonitor.\n\n\n\nFor instructions and download links, please click the link below to go to the plug-in download page:\n\n[TrafficMonitorPlugins/download/plugin_download.md at main · zhongyang219/TrafficMonitorPlugins](https://github.com/zhongyang219/TrafficMonitorPlugins/blob/main/download/plugin_download.md)\n\n### About the crash issue\n\nIf you encounter the problem of program crash, please turn off all the items in \"Options\" - \"General Settings\" - \"Hardware Monitoring\" after restarting the program, because based on the DMP file provided by the user, most crash problems are related to the hardware monitoring function. I cannot solve the crash problem related to the hardware monitoring function, please do not send me email feedback. If you have excluded the hardware monitoring problem, but the crash problem still exists, please go to \"Options\" - \"General Settings\" - \"Advanced\" - \"Plug-in Management\" to disable all plugins, and then restart the program. (If the program fails to start, please delete all the `dll` files in the `plugins` in the directory where TrafficMonitor is located). If you have excluded the plugin problem, but the crash problem still exists, please send me the email according to the prompts in the crash window.\n\nIf you have encountered any other problems, you can also click \"Contact Author\" in the \"About\" dialog box, or directly [click here](mailto:zhongyang219@hotmail.com) to send me an email.\nPlease describe the problems you have encountered in detail, the error prompts, what operations you have tried, it is better to attach the screenshots and configuration files (\"Options\"-\"General Settings\"-\"Open configuration file path\"). \nNote: Please confirm the email address that you used before sending the email. If your email address is form like \"Outlook_\\@outlook.com\", then such email address is unable to reply.\nThis may be due to the fact that you are using a third-party e-mail address as the Microsoft account to log on to Windows. If this is the case, be sure to enclose the correct email address in the message.\n"
},
{
"path": "LICENSE",
"content": "Copyright (c) <2019> \n\n\"Anti 996\" License Version 1.0 (Draft)\n\nPermission is hereby granted to any individual or legal entity\nobtaining a copy of this licensed work (including the source code,\ndocumentation and/or related items, hereinafter collectively referred\nto as the \"licensed work\"), free of charge, to deal with the licensed\nwork for any purpose, including without limitation, the rights to use,\nreproduce, modify, prepare derivative works of, distribute, publish\nand sublicense the licensed work, subject to the following conditions:\n\n1. The individual or the legal entity must conspicuously display,\nwithout modification, this License and the notice on each redistributed\nor derivative copy of the Licensed Work.\n\n2. The individual or the legal entity must strictly comply with all\napplicable laws, regulations, rules and standards of the jurisdiction\nrelating to labor and employment where the individual is physically\nlocated or where the individual was born or naturalized; or where the\nlegal entity is registered or is operating (whichever is stricter). In\ncase that the jurisdiction has no such laws, regulations, rules and\nstandards or its laws, regulations, rules and standards are\nunenforceable, the individual or the legal entity are required to\ncomply with Core International Labor Standards.\n\n3. The individual or the legal entity shall not induce, suggest or force\nits employee(s), whether full-time or part-time, or its independent\ncontractor(s), in any methods, to agree in oral or written form, to\ndirectly or indirectly restrict, weaken or relinquish his or her\nrights or remedies under such laws, regulations, rules and standards\nrelating to labor and employment as mentioned above, no matter whether\nsuch written or oral agreements are enforceable under the laws of the\nsaid jurisdiction, nor shall such individual or the legal entity\nlimit, in any methods, the rights of its employee(s) or independent\ncontractor(s) from reporting or complaining to the copyright holder or\nrelevant authorities monitoring the compliance of the license about\nits violation(s) of the said license.\n\nTHE LICENSED WORK IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND,\nEXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF\nMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.\nIN NO EVENT SHALL THE COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM,\nDAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR\nOTHERWISE, ARISING FROM, OUT OF OR IN ANY WAY CONNECTION WITH THE\nLICENSED WORK OR THE USE OR OTHER DEALINGS IN THE LICENSED WORK.\n"
},
{
"path": "LICENSE_CN",
"content": "版权所有（c）<2019> \n\n反996许可证版本1.0\n\n在符合下列条件的情况下，特此免费向任何得到本授权作品的副本（包括源代码、文件和/或相关内容，以\n下统称为“授权作品”）的个人和法人实体授权：被授权个人或法人实体有权以任何目的处置授权作品，包括\n但不限于使用、复制，修改，衍生利用、散布，发布和再许可：\n\n1. 个人或法人实体必须在许可作品的每个再散布或衍生副本上包含以上版权声明和本许可证，不得自行修\n改。\n2. 个人或法人实体必须严格遵守与个人实际所在地或个人出生地或归化地、或法人实体注册地或经营地（\n以较严格者为准）的司法管辖区所有适用的与劳动和就业相关法律、法规、规则和标准。如果该司法管辖区\n没有此类法律、法规、规章和标准或其法律、法规、规章和标准不可执行，则个人或法人实体必须遵守国际\n劳工标准的核心公约。\n3. 个人或法人不得以任何方式诱导、暗示或强迫其全职或兼职员工或其独立承包人以口头或书面形式同意\n直接或间接限制、削弱或放弃其所拥有的，受相关与劳动和就业有关的法律、法规、规则和标准保护的权利\n或补救措施，无论该等书面或口头协议是否被该司法管辖区的法律所承认，该等个人或法人实体也不得以任\n何方法限制其雇员或独立承包人向版权持有人或监督许可证合规情况的有关当局报告或投诉上述违反许可证\n的行为的权利。\n\n该授权作品是\"按原样\"提供，不做任何明示或暗示的保证，包括但不限于对适销性、特定用途适用性和非侵\n权性的保证。在任何情况下，无论是在合同诉讼、侵权诉讼或其他诉讼中，版权持有人均不承担因本软件或\n本软件的使用或其他交易而产生、引起或与之相关的任何索赔、损害或其他责任。\n"
},
{
"path": "OpenHardwareMonitorApi/LibreHardwareMonitorLib.xml",
"content": "\n\n \n LibreHardwareMonitorLib\n \n \n \n \n \n \n \n \n \n \n \n \n \n Stores all hardware groups and decides which devices should be enabled and updated.\n \n \n \n \n Creates a new instance with basic initial .\n \n \n \n \n Creates a new instance with additional .\n \n Computer settings that will be transferred to each .\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n Contains computer information table read in accordance with System Management BIOS (SMBIOS) Reference Specification.\n \n \n \n \n Triggers the method for the given observer.\n \n Observer who call to devices.\n \n \n \n Triggers the method with the given visitor for each device in each group.\n \n Observer who call to devices.\n \n \n \n If hasn't been opened before, opens , , and triggers the private method depending on which categories are\n enabled.\n \n \n \n \n If opened before, removes all and triggers , and .\n \n \n \n \n If opened before, removes all and recreates it.\n \n \n \n \n specific additional settings passed to its .\n \n \n \n Support for the Kraken X3 devices from NZXT\n \n \n \n Initializes a new instance of the class.\n \n The group.\n The thread.\n The affinity.\n \n \n \n Gets the specified .\n \n The group.\n The thread.\n .\n \n \n \n Gets the CPUID.\n \n \n \n \n Gets the CPU index.\n \n \n \n \n \n \n \n Sets the default fan speed.\n \n \n \n \n Gets the OverdriveN temperature.\n \n The type.\n The sensor.\n The minimum temperature.\n The scale.\n If set to true, resets the sensor value to null.\n \n \n \n Gets a PMLog sensor value.\n \n The data.\n Type of the sensor.\n The sensor.\n The factor.\n \n \n \n Gets the Overdrive6 power.\n \n The type.\n The sensor.\n \n \n \n Initializes a new instance of the class.\n \n Component name.\n Identifier that will be assigned to the device. Based on \n Additional settings passed by the .\n \n \n \n Gets the device identifier.\n \n \n \n \n \n \n \n \n \n \n This structure describes a group-specific affinity.\n \n \n \n \n Initializes a new instance of the struct.\n \n The group.\n The mask.\n \n \n \n Gets a single group affinity.\n \n The group.\n The index.\n .\n \n \n \n Gets the group.\n \n \n \n \n Gets the mask.\n \n \n \n \n Determines whether the specified is equal to this instance.\n \n The to compare with this instance.\n true if the specified is equal to this instance; otherwise, false.\n \n \n \n Returns a hash code for this instance.\n \n A hash code for this instance, suitable for use in hashing algorithms and data structures like a hash table.\n \n \n \n Implements the == operator.\n \n The a1.\n The a2.\n The result of the operator.\n \n \n \n Implements the != operator.\n \n The a1.\n The a2.\n The result of the operator.\n \n \n \n Object representing a component of the computer.\n \n Individual information can be read from the .\n \n \n \n \n \n Creates a new instance based on the data provided.\n \n Component name.\n Identifier that will be assigned to the device. Based on \n Additional settings passed by the .\n \n \n \n Event triggered when is closing.\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n Collection of identifiers representing the purpose of the hardware.\n \n \n \n \n Handler that will trigger the actions assigned to it when the event occurs.\n \n Component returned to the assigned action(s).\n \n \n \n Basic abstract with methods for the class which can store all hardware and decides which devices are to be checked and updated.\n \n \n \n \n Triggered when a new is registered.\n \n \n \n \n Triggered when a is removed.\n \n \n \n \n Gets a list of all known .\n Can be updated by .\n \n List of all enabled devices.\n \n \n \n Gets or sets a value indicating whether collecting information about devices should be enabled and updated.\n \n if a given category of devices is already enabled.\n \n \n \n Gets or sets a value indicating whether collecting information about:\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n devices should be enabled and updated.\n \n if a given category of devices is already enabled.\n \n \n \n Gets or sets a value indicating whether collecting information about devices should be enabled and updated.\n \n if a given category of devices is already enabled.\n \n \n \n Gets or sets a value indicating whether collecting information about or devices should be enabled and updated.\n \n if a given category of devices is already enabled.\n \n \n \n Gets or sets a value indicating whether collecting information about devices should be enabled and updated.\n \n if a given category of devices is already enabled.\n \n \n \n Gets or sets a value indicating whether collecting information about devices should be enabled and updated.\n \n if a given category of devices is already enabled.\n \n \n \n Gets or sets a value indicating whether collecting information about devices should be enabled and updated.\n \n if a given category of devices is already enabled.\n \n \n \n Gets or sets a value indicating whether collecting information about devices should be enabled and updated.\n \n if a given category of devices is already enabled.\n \n \n \n Gets or sets a value indicating whether collecting information about devices should be enabled and updated.\n \n if a given category of devices is already enabled.\n \n \n \n Generates full LibreHardwareMonitor report for devices that have been enabled.\n \n A formatted text string with library, OS and hardware information.\n \n \n \n Represents a unique / identifier in text format with a / separator.\n \n \n \n \n Creates a new identifier instance based on the base and additional elements.\n \n Base identifier being the beginning of the new one.\n Additional parts by which the base will be extended.\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n Abstract parent with logic for the abstract class that stores data.\n \n \n \n \n Accepts the observer for this instance.\n \n Computer observer making the calls.\n \n \n \n Call the method for all child instances (called only from visitors).\n \n Computer observer making the calls.\n \n \n \n A group of devices from one category in one list.\n \n \n \n \n Gets a list that stores information about in a given group.\n \n \n \n \n Report containing most of the known information about all in this .\n \n A formatted text string with hardware information.\n \n \n \n Stop updating this group in the future.\n \n \n \n \n Handler that will trigger the actions assigned to it when the event occurs.\n \n Component returned to the assigned action(s).\n \n \n \n Abstract object that stores information about a device. All sensors are available as an array of .\n \n Can contain .\n Type specified in .\n \n \n \n \n \n \n \n \n \n \n Gets a unique hardware ID that represents its location.\n \n \n \n \n Gets or sets device name.\n \n \n \n \n Gets the device that is the parent of the current hardware. For example, the motherboard is the parent of SuperIO.\n \n \n \n \n Gets an array of all sensors such as , , etc.\n \n \n \n \n Gets child devices, e.g. of the .\n \n \n \n \n Report containing most of the known information about the current device.\n \n A formatted text string with hardware information.\n \n \n \n Refreshes the information stored in array.\n \n \n \n \n An that will be triggered when a new sensor appears.\n \n \n \n \n An that will be triggered when one of the sensors is removed.\n \n \n \n \n Gets rarely changed hardware properties that can't be represented as sensors.\n \n \n \n \n Abstract object that represents additional parameters included in .\n \n \n \n \n Gets a parameter default value defined by library.\n \n \n \n \n Gets a parameter description defined by library.\n \n \n \n \n Gets a unique parameter ID that represents its location.\n \n \n \n \n Gets or sets information whether the given is the default for .\n \n \n \n \n Gets a parameter name defined by library.\n \n \n \n \n Gets the sensor that is the data container for the given parameter.\n \n \n \n \n Gets or sets the current value.\n \n \n \n \n Category of what type the selected sensor is.\n \n \n \n \n Stores the readed value and the time in which it was recorded.\n \n \n \n of the sensor.\n The time code during which the was recorded.\n \n \n \n Gets the value of the sensor\n \n \n \n \n Gets the time code during which the was recorded.\n \n \n \n \n Stores information about the readed values and the time in which they were collected.\n \n \n \n \n \n \n \n \n \n Gets the unique identifier of this sensor for a given .\n \n \n \n \n Gets a maximum value recorded for the given sensor.\n \n \n \n \n Gets a minimum value recorded for the given sensor.\n \n \n \n \n Gets or sets a sensor name.\n By default determined by the library.\n \n \n \n \n \n \n \n \n \n Gets the last recorded value for the given sensor.\n \n \n \n \n Gets a list of recorded values for the given sensor.\n \n \n \n \n Resets a value stored in .\n \n \n \n \n Resets a value stored in .\n \n \n \n \n Abstract object that stores information about the limits of .\n \n \n \n \n Upper limit of value.\n \n \n \n \n Lower limit of value.\n \n \n \n \n Abstract object that stores information about the critical limits of .\n \n \n \n \n Critical upper limit of value.\n \n \n \n \n Critical lower limit of value.\n \n \n \n \n Abstract object that stores settings passed to , and .\n \n \n \n \n Returns information whether the given collection of settings contains a value assigned to the given key.\n \n Key to which the setting value is assigned.\n \n \n \n Assigns a setting option to a given key.\n \n Key to which the setting value is assigned.\n Text setting value.\n \n \n \n Gets a setting option assigned to the given key.\n \n Key to which the setting value is assigned.\n Default value.\n \n \n \n Removes a setting with the specified key from the settings collection.\n \n Key to which the setting value is assigned.\n \n \n \n Base interface for creating observers who call to devices.\n \n \n \n \n Refreshes the values of all in all on selected .\n \n Instance of the computer to be revisited.\n \n \n \n Refreshes the values of all on selected .\n \n Instance of the hardware to be revisited.\n \n \n \n Refreshes the values on selected .\n \n Instance of the sensor to be revisited.\n \n \n \n Refreshes the values on selected .\n \n Instance of the parameter to be revisited.\n \n \n Chipset temperature [℃]\n \n \n CPU temperature [℃]\n \n \n motherboard temperature [℃]\n \n \n \"T_Sensor\" temperature sensor reading [℃]\n \n \n VRM temperature [℃]\n \n \n CPU Core voltage [mV]\n \n \n CPU_Opt fan [RPM]\n \n \n VRM heat sink fan [RPM]\n \n \n Chipset fan [RPM]\n \n \n Water Pump [RPM]\n \n \n Water flow sensor reading [RPM]\n \n \n CPU current [A]\n \n \n \"Water_In\" temperature sensor reading [℃]\n \n \n \"Water_Out\" temperature sensor reading [℃]\n \n \n Water block temperature sensor reading [℃]\n \n \n \n An unsafe but universal implementation for the ACPI Embedded Controller IO interface for Windows\n \n \n It is unsafe because of possible race condition between this application and the PC firmware when\n writing to the EC registers. For a safe approach ACPI/WMI methods have to be used, but those are\n different for each motherboard model.\n \n \n \n \n Selects another bank. Memory from 0x10-0xAF swaps to data from new bank.\n Beware to select the default bank 0 after changing.\n Bank selection is reset after power cycle.\n \n New bank index. Can be a value of 0-3.\n \n \n \n Represents the motherboard of a computer with its and as .\n \n \n \n \n Creates motherboard instance by retrieving information from and creates a new based on data from and .\n \n table containing motherboard data.\n Additional settings passed by .\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n Gets the name obtained from .\n \n \n \n \n Always \n \n \n \n \n \n \n \n \n \n Gets the information.\n \n \n \n \n \n \n \n \n \n \n Motherboard itself cannot be updated. Update instead.\n \n \n \n \n \n \n \n \n \n \n Closes using .\n \n \n \n \n Composite class containing information about the selected .\n \n \n \n \n Creates a new instance and assigns values.\n \n Name of the selected component.\n Description of the selected component.\n Default value of the selected component.\n \n \n \n Gets a name of the parent .\n \n \n \n \n Gets a description of the parent .\n \n \n \n \n Gets a default value of the parent .\n \n \n \n \n Observer making calls to selected component 's.\n \n \n \n \n Creates a new observer instance.\n \n Instance of the that triggers events during visiting the .\n \n \n \n Goes through all the components of the specified with its .\n \n Computer class instance that is derived from the interface.\n \n \n \n Goes through all the components of the specified with its .\n \n Hardware class instance that is derived from the interface.\n \n \n \n Goes through all the components of the specified using .\n \n Sensor class instance that is derived from the interface.\n \n \n \n Goes through all the components of the specified .\n \n \n \n \n Parameter class instance that is derived from the interface.\n \n \n \n System enclosure security status based on DMTF SMBIOS Reference Specification v.3.3.0, Chapter 7.4.3.\n \n \n \n \n System enclosure state based on DMTF SMBIOS Reference Specification v.3.3.0, Chapter 7.4.2.\n \n \n \n \n System enclosure type based on DMTF SMBIOS Reference Specification v.3.3.0, Chapter 7.4.1.\n \n \n \n \n Processor family based on DMTF SMBIOS Reference Specification v.3.3.0, Chapter 7.5.2.\n \n \n \n \n Processor characteristics based on DMTF SMBIOS Reference Specification v.3.3.0, Chapter 7.5.9.\n \n \n \n \n Processor type based on DMTF SMBIOS Reference Specification v.3.3.0, Chapter 7.5.1.\n \n \n \n \n Processor socket based on DMTF SMBIOS Reference Specification v.3.3.0, Chapter 7.5.5.\n \n \n \n \n System wake-up type based on DMTF SMBIOS Reference Specification v.3.3.0, Chapter 7.2.2.\n \n \n \n \n Cache associativity based on DMTF SMBIOS Reference Specification v.3.3.0, Chapter 7.8.5.\n \n \n \n \n Processor cache level.\n \n \n \n \n Memory type.\n \n \n \n \n Initializes a new instance of the class.\n \n The data.\n The strings.\n \n \n \n Gets the byte.\n \n The offset.\n .\n \n \n \n Gets the word.\n \n The offset.\n .\n \n \n \n Gets the dword.\n \n The offset.\n .\n \n \n \n Gets the qword.\n \n The offset.\n .\n \n \n \n Gets the string.\n \n The offset.\n .\n \n \n \n Motherboard BIOS information obtained from the SMBIOS table.\n \n \n \n \n Gets the BIOS release date.\n \n \n \n \n Gets the size of the physical device containing the BIOS.\n \n \n \n \n Gets the string number of the BIOS Vendor’s Name.\n \n \n \n \n Gets the string number of the BIOS Version. This value is a free-form string that may contain Core and OEM version information.\n \n \n \n \n Gets the size.\n \n .\n \n \n \n Gets the date.\n \n The bios date.\n .\n \n \n \n System information obtained from the SMBIOS table.\n \n \n \n \n Gets the family associated with system.\n \n This text string identifies the family to which a particular computer belongs. A family refers to a set of computers that are similar but not identical from a hardware or software point of\n view. Typically, a family is composed of different computer models, which have different configurations and pricing points. Computers in the same family often have similar branding and cosmetic\n features.\n \n \n \n \n \n Gets the manufacturer name associated with system.\n \n \n \n \n Gets the product name associated with system.\n \n \n \n \n Gets the serial number string associated with system.\n \n \n \n \n Gets the version string associated with system.\n \n \n \n \n Gets \n \n \n \n \n System enclosure obtained from the SMBIOS table.\n \n \n \n \n Gets the asset tag associated with the enclosure or chassis.\n \n \n \n \n Gets \n \n \n \n \n Gets or sets the system enclosure lock.\n \n System enclosure lock is present if . Otherwise, either a lock is not present or it is unknown if the enclosure has a lock.\n \n \n \n Gets the string describing the chassis or enclosure manufacturer name.\n \n \n \n \n Gets the number of power cords associated with the enclosure or chassis.\n \n \n \n \n Gets the state of the enclosure’s power supply (or supplies) when last booted.\n \n \n \n \n Gets the height of the enclosure, in 'U's. A U is a standard unit of measure for the height of a rack or rack-mountable component and is equal to 1.75 inches or 4.445 cm. A value of 0\n indicates that the enclosure height is unspecified.\n \n \n \n \n Gets the physical security status of the enclosure when last booted.\n \n \n \n \n Gets the string describing the chassis or enclosure serial number.\n \n \n \n \n Gets the string describing the chassis or enclosure SKU number.\n \n \n \n \n Gets the thermal state of the enclosure when last booted.\n \n \n \n \n Gets \n \n \n \n \n Gets the number of null-terminated string representing the chassis or enclosure version.\n \n \n \n \n Motherboard information obtained from the SMBIOS table.\n \n \n \n \n Gets the value that represents the manufacturer's name.\n \n \n \n \n Gets the value that represents the motherboard's name.\n \n \n \n \n Gets the value that represents the motherboard's serial number.\n \n \n \n \n Gets the value that represents the motherboard's revision number.\n \n \n \n \n Processor information obtained from the SMBIOS table.\n \n \n \n \n Gets the characteristics of the processor.\n \n \n \n \n Gets the value that represents the number of cores per processor socket.\n \n \n \n \n Gets the value that represents the number of enabled cores per processor socket.\n \n \n \n \n Gets the value that represents the current processor speed (in MHz).\n \n \n \n \n Gets the external Clock Frequency, in MHz. If the value is unknown, the field is set to 0.\n \n \n \n \n Gets \n \n \n \n \n Gets the handle.\n \n The handle.\n \n \n \n Gets the identifier.\n \n \n \n \n Gets the L1 cache handle.\n \n \n \n \n Gets the L2 cache handle.\n \n \n \n \n Gets the L3 cache handle.\n \n \n \n \n Gets the string number of Processor Manufacturer.\n \n \n \n \n Gets the value that represents the maximum processor speed (in MHz) supported by the system for this processor socket.\n \n \n \n \n Gets \n \n \n \n \n Gets the value that represents the string number for the serial number of this processor.\n This value is set by the manufacturer and normally not changeable.\n \n \n \n \n Gets \n \n \n \n \n Gets the string number for Reference Designation.\n \n \n \n \n Gets the value that represents the number of threads per processor socket.\n \n \n \n \n Gets the value that represents the string number describing the Processor.\n \n \n \n \n Cache information obtained from the SMBIOS table.\n \n \n \n \n Gets \n \n \n \n \n Gets \n \n \n \n \n Gets the handle.\n \n \n \n \n Gets the value that represents the installed cache size.\n \n \n \n \n Gets the cache designation.\n \n .\n \n \n \n Memory information obtained from the SMBIOS table.\n \n \n \n \n Gets the string number of the string that identifies the physically labeled bank where the memory device is located.\n \n \n \n \n Gets the string number of the string that identifies the physically-labeled socket or board position where the memory device is located.\n \n \n \n \n Gets the string number for the manufacturer of this memory device.\n \n \n \n \n Gets the string number for the part number of this memory device.\n \n \n \n \n Gets the string number for the serial number of this memory device.\n \n \n \n \n Gets the size of the memory device. If the value is 0, no memory device is installed in the socket.\n \n \n \n \n Gets the value that identifies the maximum capable speed of the device, in mega transfers per second (MT/s).\n \n \n \n \n Gets the type of this memory device.\n \n The type.\n \n \n \n Reads and processes information encoded in an SMBIOS table.\n \n \n \n \n Initializes a new instance of the class.\n \n \n \n \n Gets \n \n \n \n \n Gets \n \n \n \n \n Gets \n \n \n \n \n Gets \n \n \n \n \n Gets \n \n \n \n \n Gets \n \n \n \n \n Gets \n \n \n \n \n Report containing most of the information that could be read from the SMBIOS table.\n \n A formatted text string with computer information and the entire SMBIOS table.\n \n \n \n Helper to calculate the disk performance with base timestamps\n https://docs.microsoft.com/en-us/windows/win32/cimwin32prov/win32-perfrawdata\n \n \n \n \n Gets the SMART data.\n \n \n \n \n Gets the SMART attributes.\n \n \n \n \n Gets the SMART data.\n \n \n \n \n Initializes a new instance of the class.\n \n The SMART id of the attribute.\n The name of the attribute.\n \n \n \n Initializes a new instance of the class.\n \n The SMART id of the attribute.\n The name of the attribute.\n \n A delegate for converting the raw byte\n array into a value (or null to use the attribute value).\n \n \n \n \n Initializes a new instance of the class.\n \n The SMART id of the attribute.\n The name of the attribute.\n \n A delegate for converting the raw byte\n array into a value (or null to use the attribute value).\n \n \n Type of the sensor or null if no sensor is to\n be created.\n \n \n If there exists more than one attribute with\n the same sensor channel and type, then a sensor is created only for the\n first attribute.\n \n \n The name to be used for the sensor, or null if\n no sensor is created.\n \n True to hide the sensor initially.\n \n Description for the parameters of the sensor\n (or null).\n \n \n \n \n Gets the SMART identifier.\n \n \n \n \n Localization class for SMART attribute names.\n \n \n \n \n \n \n \n Reads Smart health status of the drive\n \n True, if drive is healthy; False, if unhealthy; Null, if it cannot be read\n \n \n \n Initializes static members of the class.\n \n \n \n \n Gets the processor group count.\n \n \n \n \n Returns true if the is valid.\n \n The affinity.\n true if the specified affinity is valid; otherwise, false.\n \n \n \n Sets the processor group affinity for the current thread.\n \n The processor group affinity.\n The previous processor group affinity.\n \n \n \n All OK, but need to wait.\n \n \n \n \n All OK, but need restart.\n \n \n \n \n All OK but need mode change.\n \n \n \n \n All OK, but with warning.\n \n \n \n \n ADL function completed successfully.\n \n \n \n \n Generic Error. Most likely one or more of the Escape calls to the driver\n failed!\n \n \n \n \n ADL not initialized.\n \n \n \n \n One of the parameter passed is invalid.\n \n \n \n \n One of the parameter size is invalid.\n \n \n \n \n Invalid ADL index passed.\n \n \n \n \n Invalid controller index passed.\n \n \n \n \n Invalid display index passed.\n \n \n \n \n Function not supported by the driver.\n \n \n \n \n Null Pointer error.\n \n \n \n \n Call can't be made due to disabled adapter.\n \n \n \n \n Invalid Callback.\n \n \n \n \n Display Resource conflict.\n \n \n \n \n Failed to update some of the values. Can be returned by set request that\n include multiple values if not all values were successfully committed.\n \n \n \n \n There's no Linux XDisplay in Linux Console environment.\n \n \n \n \n If set to 1, then the available spare space has fallen below the threshold.\n \n \n \n \n If set to 1, then a temperature is above an over temperature threshold or below an under temperature threshold.\n \n \n \n \n If set to 1, then the device reliability has been degraded due to significant media related errors or any internal error that degrades device reliability.\n \n \n \n \n If set to 1, then the media has been placed in read only mode\n \n \n \n \n If set to 1, then the volatile memory backup device has failed. This field is only valid if the controller has a volatile memory backup solution.\n \n \n \n \n Create a instance from a struct with zero initialized memory arrays\n no need to init every inner array with the correct sizes\n \n type of struct that is needed\n \n \n \n \n SMART data requested.\n \n \n \n \n Identify data is requested.\n \n \n \n \n Read SMART data.\n \n \n \n \n Read SMART thresholds.\n obsolete\n \n \n \n \n Autosave SMART data.\n \n \n \n \n Save SMART attributes.\n \n \n \n \n Set SMART to offline immediately.\n \n \n \n \n Read SMART log.\n \n \n \n \n Write SMART log.\n \n \n \n \n Write SMART thresholds.\n obsolete\n \n \n \n \n Enable SMART.\n \n \n \n \n Disable SMART.\n \n \n \n \n Get SMART status.\n \n \n \n \n Set SMART to offline automatically.\n \n \n \n \n bit 0:15 Maximum Power (MP) in centiwatts\n \n \n \n \n bit 16:23\n \n \n \n \n bit 24 Max Power Scale (MPS), bit 25 Non-Operational State (NOPS)\n \n \n \n \n bit 32:63 Entry Latency (ENLAT) in microseconds\n \n \n \n \n bit 64:95 Exit Latency (EXLAT) in microseconds\n \n \n \n \n bit 96:100 Relative Read Throughput (RRT)\n \n \n \n \n bit 104:108 Relative Read Latency (RRL)\n \n \n \n \n bit 112:116 Relative Write Throughput (RWT)\n \n \n \n \n bit 120:124 Relative Write Latency (RWL)\n \n \n \n \n bit 128:143 Idle Power (IDLP)\n \n \n \n \n bit 150:151 Idle Power Scale (IPS)\n \n \n \n \n bit 152:159\n \n \n \n \n bit 160:175 Active Power (ACTP)\n \n \n \n \n bit 176:178 Active Power Workload (APW), bit 182:183 Active Power Scale (APS)\n \n \n \n \n bit 184:255.\n \n \n \n \n byte 0:1 M - PCI Vendor ID (VID)\n \n \n \n \n byte 2:3 M - PCI Subsystem Vendor ID (SSVID)\n \n \n \n \n byte 4: 23 M - Serial Number (SN)\n \n \n \n \n byte 24:63 M - Model Number (MN)\n \n \n \n \n byte 64:71 M - Firmware Revision (FR)\n \n \n \n \n byte 72 M - Recommended Arbitration Burst (RAB)\n \n \n \n \n byte 73:75 M - IEEE OUI Identifier (IEEE). Controller Vendor code.\n \n \n \n \n byte 76 O - Controller Multi-Path I/O and Namespace Sharing Capabilities (CMIC)\n \n \n \n \n byte 77 M - Maximum Data Transfer Size (MDTS)\n \n \n \n \n byte 78:79 M - Controller ID (CNTLID)\n \n \n \n \n byte 80:83 M - Version (VER)\n \n \n \n \n byte 84:87 M - RTD3 Resume Latency (RTD3R)\n \n \n \n \n byte 88:91 M - RTD3 Entry Latency (RTD3E)\n \n \n \n \n byte 92:95 M - Optional Asynchronous Events Supported (OAES)\n \n \n \n \n byte 96:239.\n \n \n \n \n byte 240:255. Refer to the NVMe Management Interface Specification for definition.\n \n \n \n \n byte 256:257 M - Optional Admin Command Support (OACS)\n \n \n \n \n byte 258 M - Abort Command Limit (ACL)\n \n \n \n \n byte 259 M - Asynchronous Event Request Limit (AERL)\n \n \n \n \n byte 260 M - Firmware Updates (FRMW)\n \n \n \n \n byte 261 M - Log Page Attributes (LPA)\n \n \n \n \n byte 262 M - Error Log Page Entries (ELPE)\n \n \n \n \n byte 263 M - Number of Power States Support (NPSS)\n \n \n \n \n byte 264 M - Admin Vendor Specific Command Configuration (AVSCC)\n \n \n \n \n byte 265 O - Autonomous Power State Transition Attributes (APSTA)\n \n \n \n \n byte 266:267 M - Warning Composite Temperature Threshold (WCTEMP)\n \n \n \n \n byte 268:269 M - Critical Composite Temperature Threshold (CCTEMP)\n \n \n \n \n byte 270:271 O - Maximum Time for Firmware Activation (MTFA)\n \n \n \n \n byte 272:275 O - Host Memory Buffer Preferred Size (HMPRE)\n \n \n \n \n byte 276:279 O - Host Memory Buffer Minimum Size (HMMIN)\n \n \n \n \n byte 280:295 O - Total NVM Capacity (TNVMCAP)\n \n \n \n \n byte 296:311 O - Unallocated NVM Capacity (UNVMCAP)\n \n \n \n \n byte 312:315 O - Replay Protected Memory Block Support (RPMBS)\n \n \n \n \n byte 316:511\n \n \n \n \n byte 512 M - Submission Queue Entry Size (SQES)\n \n \n \n \n byte 513 M - Completion Queue Entry Size (CQES)\n \n \n \n \n byte 514:515\n \n \n \n \n byte 516:519 M - Number of Namespaces (NN)\n \n \n \n \n byte 520:521 M - Optional NVM Command Support (ONCS)\n \n \n \n \n byte 522:523 M - Fused Operation Support (FUSES)\n \n \n \n \n byte 524 M - Format NVM Attributes (FNA)\n \n \n \n \n byte 525 M - Volatile Write Cache (VWC)\n \n \n \n \n byte 526:527 M - Atomic Write Unit Normal (AWUN)\n \n \n \n \n byte 528:529 M - Atomic Write Unit Power Fail (AWUPF)\n \n \n \n \n byte 530 M - NVM Vendor Specific Command Configuration (NVSCC)\n \n \n \n \n byte 531\n \n \n \n \n byte 532:533 O - Atomic Compare and Write Unit (ACWU)\n \n \n \n \n byte 534:535\n \n \n \n \n byte 536:539 O - SGL Support (SGLS)\n \n \n \n \n byte 540:703\n \n \n \n \n byte 704:2047\n \n \n \n \n byte 2048:3071 Power State Descriptors\n \n \n \n \n byte 3072:4095 Vendor Specific\n \n \n \n \n This field indicates critical warnings for the state of the controller.\n Each bit corresponds to a critical warning type; multiple bits may be set.\n \n \n \n \n Composite Temperature: Contains the temperature of the overall device (controller and NVM included) in units of Kelvin.\n \n \n \n \n Available Spare: Contains a normalized percentage (0 to 100%) of the remaining spare capacity available\n \n \n \n \n Available Spare Threshold: When the Available Spare falls below the threshold indicated in this field,\n an asynchronous event completion may occur. The value is indicated as a normalized percentage (0 to 100%).\n \n \n \n \n Percentage Used: Contains a vendor specific estimate of the percentage of NVM subsystem life used based on\n the actual usage and the manufacturer’s prediction of NVM life. A value of 100 indicates that the estimated endurance of\n the NVM in the NVM subsystem has been consumed, but may not indicate an NVM subsystem failure. The value is allowed to exceed 100.\n \n \n \n \n Data Units Read: Contains the number of 512 byte data units the host has read from the controller;\n this value does not include metadata. This value is reported in thousands\n (i.e., a value of 1 corresponds to 1000 units of 512 bytes read) and is rounded up.\n \n \n \n \n Data Units Written: Contains the number of 512 byte data units the host has written to the controller;\n this value does not include metadata. This value is reported in thousands\n (i.e., a value of 1 corresponds to 1000 units of 512 bytes written) and is rounded up.\n \n \n \n \n Host Read Commands: Contains the number of read commands completed by the controller.\n For the NVM command set, this is the number of Compare and Read commands.\n \n \n \n \n Host Write Commands: Contains the number of write commands completed by the controller.\n For the NVM command set, this is the number of Write commands.\n \n \n \n \n Controller Busy Time: Contains the amount of time the controller is busy with I/O commands.\n \n \n \n \n Power Cycles: Contains the number of power cycles.\n \n \n \n \n Power On Hours: Contains the number of power-on hours.\n This does not include time that the controller was powered and in a low power state condition.\n \n \n \n \n Unsafe Shutdowns: Contains the number of unsafe shutdowns.\n This count is incremented when a shutdown notification is not received prior to loss of power.\n \n \n \n \n Media Errors: Contains the number of occurrences where the controller detected an unrecoverable data integrity error.\n Errors such as uncorrectable ECC, CRC checksum failure, or LBA tag mismatch are included in this field.\n \n \n \n \n Number of Error Information Log Entries: Contains the number of Error Information log entries over the life of the controller\n \n \n \n \n Warning Composite Temperature Time: Contains the amount of time in minutes that the controller is operational and the Composite Temperature is greater than or equal to the Warning Composite\n Temperature Threshold.\n \n \n \n \n Critical Composite Temperature Time: Contains the amount of time in minutes that the controller is operational and the Composite Temperature is greater than the Critical Composite Temperature\n Threshold.\n \n \n \n \n Contains the current temperature reported by temperature sensor 1-8.\n \n \n \n \n Gets the resulting IO control code.\n \n \n \n \n Initializes a new instance of the struct.\n \n Type of the device.\n The function.\n The access.\n \n \n \n Initializes a new instance of the struct.\n \n Type of the device.\n The function.\n The method.\n The access.\n \n \n \n The operation was successful\n \n \n \n \n NvidiaML was not first initialized with nvmlInit()\n \n \n \n \n A supplied argument is invalid\n \n \n \n \n The requested operation is not available on target device\n \n \n \n \n The current user does not have permission for operation\n \n \n \n \n A query to find an object was unsuccessful\n \n \n \n \n An input argument is not large enough\n \n \n \n \n A device's external power cables are not properly attached\n \n \n \n \n NVIDIA driver is not loaded\n \n \n \n \n User provided timeout passed\n \n \n \n \n NVIDIA Kernel detected an interrupt issue with a GPU\n \n \n \n \n NvidiaML Shared Library couldn't be found or loaded\n \n \n \n \n Local version of NvidiaML doesn't implement this function\n \n \n \n \n infoROM is corrupted\n \n \n \n \n The GPU has fallen off the bus or has otherwise become inaccessible\n \n \n \n \n The GPU requires a reset before it can be used again\n \n \n \n \n The GPU control device has been blocked by the operating system/cgroups\n \n \n \n \n RM detects a driver/library version mismatch\n \n \n \n \n An operation cannot be performed because the GPU is currently in use\n \n \n \n \n An public driver error occurred\n \n \n \n \n Driver with access at kernel level.\n \n \n \n \n Contains Win32 definitions for Windows NT.\n \n \n \n \n Describes a local identifier for an adapter.\n \n \n \n \n Represents a 64-bit signed integer value.\n \n \n \n \n Contains basic information about the operating system.\n \n \n \n \n Statically checks if the current system and .\n \n \n \n \n Gets information about whether the current system is 64 bit.\n \n \n \n \n Gets information about whether the current system is Unix based.\n \n \n \n\n"
},
{
"path": "OpenHardwareMonitorApi/OpenHardwareMonitorApi.vcxproj",
"content": "\n\n \n \n Debug\n ARM64EC\n \n \n Debug\n Win32\n \n \n Release\n ARM64EC\n \n \n Release\n Win32\n \n \n Debug\n x64\n \n \n Release\n x64\n \n \n \n {C0A42F4A-ABB3-4575-B4D5-CEDD8379AC26}\n v4.7.2\n ManagedCProj\n OpenHardwareMonitorApi\n 10.0\n \n \n \n DynamicLibrary\n true\n v143\n true\n Unicode\n \n \n DynamicLibrary\n false\n v143\n true\n Unicode\n \n \n DynamicLibrary\n true\n v143\n true\n Unicode\n \n \n DynamicLibrary\n true\n v143\n true\n Unicode\n \n \n DynamicLibrary\n false\n v143\n true\n Unicode\n \n \n DynamicLibrary\n false\n v143\n true\n Unicode\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n true\n $(ProjectDir)..\\include;$(IncludePath)\n $(SolutionDir)Bin\\$(Configuration)\\\n \n \n true\n $(ProjectDir)..\\include;$(IncludePath)\n $(SolutionDir)Bin\\$(Platform)\\$(Configuration)\\\n \n \n true\n $(ProjectDir)..\\include;$(IncludePath)\n $(SolutionDir)Bin\\$(Platform)\\$(Configuration)\\\n \n \n false\n $(ProjectDir)..\\include;$(IncludePath)\n $(SolutionDir)Bin\\$(Configuration)\\\n \n \n false\n $(ProjectDir)..\\include;$(IncludePath)\n $(SolutionDir)Bin\\$(Platform)\\$(Configuration)\\\n \n \n false\n $(ProjectDir)..\\include;$(IncludePath)\n $(SolutionDir)Bin\\$(Platform)\\$(Configuration)\\\n \n \n \n Level3\n Disabled\n WIN32;_DEBUG;%(PreprocessorDefinitions);OPENHARDWAREMONITOR_EXPORTS\n Use\n \n \n \n \n \n \n \n Level3\n Disabled\n _DEBUG;%(PreprocessorDefinitions);OPENHARDWAREMONITOR_EXPORTS\n Use\n \n \n \n \n \n \n \n Level3\n Disabled\n _DEBUG;%(PreprocessorDefinitions);OPENHARDWAREMONITOR_EXPORTS\n Use\n \n \n \n \n \n \n \n \n Level3\n WIN32;NDEBUG;%(PreprocessorDefinitions);OPENHARDWAREMONITOR_EXPORTS\n Use\n \n \n \n \n \n \n \n Level3\n NDEBUG;%(PreprocessorDefinitions);OPENHARDWAREMONITOR_EXPORTS\n Use\n \n \n \n \n \n \n \n Level3\n NDEBUG;%(PreprocessorDefinitions);OPENHARDWAREMONITOR_EXPORTS\n Use\n \n \n \n \n \n \n \n \n LibreHardwareMonitorLib.dll\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n Create\n Create\n Create\n Create\n Create\n Create\n \n \n \n \n \n \n \n \n \n \n \n \n"
},
{
"path": "OpenHardwareMonitorApi/OpenHardwareMonitorApi.vcxproj.filters",
"content": "\n\n \n \n {4FC737F1-C7A5-4376-A066-2A32D752A2FF}\n cpp;c;cc;cxx;def;odl;idl;hpj;bat;asm;asmx\n \n \n {93995380-89BD-4b04-88EB-625FBE52EBFB}\n h;hh;hpp;hxx;hm;inl;inc;xsd\n \n \n {67DA6AB6-F800-4c08-8B7A-83BB121AAD01}\n rc;ico;cur;bmp;dlg;rc2;rct;bin;rgs;gif;jpg;jpeg;jpe;resx;tiff;tif;png;wav;mfcribbon-ms\n \n \n \n \n 头文件\n \n \n 头文件\n \n \n 头文件\n \n \n 头文件\n \n \n 头文件\n \n \n 头文件\n \n \n \n \n 源文件\n \n \n 源文件\n \n \n 源文件\n \n \n \n \n \n \n \n 资源文件\n \n \n"
},
{
"path": "OpenHardwareMonitorApi/OpenHardwareMonitorImp.cpp",
"content": "// 这是主 DLL 文件。\n\n#include \"stdafx.h\"\n\n#include \"OpenHardwareMonitorImp.h\"\n#include \n\nnamespace OpenHardwareMonitorApi\n{\n static std::wstring error_message;\n\n //将CRL的String类型转换成C++的std::wstring类型\n static std::wstring ClrStringToStdWstring(System::String^ str)\n {\n if (str == nullptr)\n {\n return std::wstring();\n }\n else\n {\n const wchar_t* chars = (const wchar_t*)(Runtime::InteropServices::Marshal::StringToHGlobalUni(str)).ToPointer();\n std::wstring os = chars;\n Runtime::InteropServices::Marshal::FreeHGlobal(IntPtr((void*)chars));\n return os;\n }\n }\n\n\n std::shared_ptr CreateInstance()\n {\n std::shared_ptr pMonitor;\n try\n {\n MonitorGlobal::Instance()->Init();\n pMonitor = std::make_shared();\n }\n catch (System::Exception^ e)\n {\n error_message = ClrStringToStdWstring(e->Message);\n }\n return pMonitor;\n }\n\n std::wstring GetErrorMessage()\n {\n return error_message;\n }\n\n float COpenHardwareMonitor::CpuTemperature()\n {\n return m_cpu_temperature;\n }\n\n float COpenHardwareMonitor::GpuTemperature()\n {\n if (m_gpu_nvidia_temperature >= 0)\n return m_gpu_nvidia_temperature;\n else if (m_gpu_ati_temperature >= 0)\n return m_gpu_ati_temperature;\n else\n return m_gpu_intel_temperature;\n }\n\n float COpenHardwareMonitor::HDDTemperature()\n {\n return m_hdd_temperature;\n }\n\n float COpenHardwareMonitor::MainboardTemperature()\n {\n return m_main_board_temperature;\n }\n\n float COpenHardwareMonitor::GpuUsage()\n {\n if (m_gpu_nvidia_usage >= 0)\n return m_gpu_nvidia_usage;\n else if (m_gpu_ati_usage >= 0)\n return m_gpu_ati_usage;\n else\n return m_gpu_intel_usage;\n }\n\n float COpenHardwareMonitor::CpuFreq()\n {\n return m_cpu_freq;\n }\n\n float COpenHardwareMonitor::CpuUsage()\n {\n return m_cpu_usage;\n }\n\n const std::map& COpenHardwareMonitor::AllHDDTemperature()\n {\n return m_all_hdd_temperature;\n }\n\n const std::map& COpenHardwareMonitor::AllCpuTemperature()\n {\n return m_all_cpu_temperature;\n }\n\n const std::map& COpenHardwareMonitor::AllHDDUsage()\n {\n return m_all_hdd_usage;\n }\n\n void COpenHardwareMonitor::SetCpuEnable(bool enable)\n {\n MonitorGlobal::Instance()->computer->IsCpuEnabled = enable;\n }\n\n void COpenHardwareMonitor::SetGpuEnable(bool enable)\n {\n MonitorGlobal::Instance()->computer->IsGpuEnabled = enable;\n }\n\n void COpenHardwareMonitor::SetHddEnable(bool enable)\n {\n MonitorGlobal::Instance()->computer->IsStorageEnabled = enable;\n }\n\n void COpenHardwareMonitor::SetMainboardEnable(bool enable)\n {\n MonitorGlobal::Instance()->computer->IsMotherboardEnabled = enable;\n }\n\n bool COpenHardwareMonitor::GetCPUFreq(IHardware^ hardware, float& freq) {\n for (int i = 0; i < hardware->Sensors->Length; i++)\n {\n if (hardware->Sensors[i]->SensorType == SensorType::Clock)\n {\n String^ name = hardware->Sensors[i]->Name;\n if (name != L\"Bus Speed\")\n m_all_cpu_clock[ClrStringToStdWstring(name)] = Convert::ToDouble(hardware->Sensors[i]->Value);\n }\n }\n float sum{};\n for (auto i : m_all_cpu_clock)\n sum += i.second;\n freq = sum / m_all_cpu_clock.size() / 1000.0;\n return true;\n }\n\n bool COpenHardwareMonitor::GetCpuUsage(IHardware^ hardware, float& cpu_usage)\n {\n for (int i = 0; i < hardware->Sensors->Length; i++)\n {\n if (hardware->Sensors[i]->SensorType == SensorType::Load)\n {\n String^ name = hardware->Sensors[i]->Name;\n if (name != L\"CPU Total\")\n {\n cpu_usage = Convert::ToDouble(hardware->Sensors[i]->Value);\n return true;\n }\n }\n }\n return false;\n }\n\n bool COpenHardwareMonitor::GetHardwareTemperature(IHardware^ hardware, float& temperature)\n {\n temperature = -1;\n std::vector all_temperature;\n float core_temperature{ -1 };\n System::String^ temperature_name;\n switch (hardware->HardwareType)\n {\n case HardwareType::Cpu:\n temperature_name = L\"Core Average\";\n break;\n case HardwareType::GpuNvidia: case HardwareType::GpuAmd: case HardwareType::GpuIntel:\n temperature_name = L\"GPU Core\";\n break;\n default:\n break;\n }\n for (int i = 0; i < hardware->Sensors->Length; i++)\n {\n //找到温度传感器\n if (hardware->Sensors[i]->SensorType == SensorType::Temperature)\n {\n float cur_temperture = Convert::ToDouble(hardware->Sensors[i]->Value);\n all_temperature.push_back(cur_temperture);\n if (hardware->Sensors[i]->Name == temperature_name) //如果找到了名称为temperature_name的温度传感器，则将温度保存到core_temperature里\n core_temperature = cur_temperture;\n }\n }\n if (core_temperature >= 0)\n {\n temperature = core_temperature;\n return true;\n }\n if (!all_temperature.empty())\n {\n //如果有多个温度传感器，则取平均值\n float sum{};\n for (auto i : all_temperature)\n sum += i;\n temperature = sum / all_temperature.size();\n return true;\n }\n //如果没有找到温度传感器，则在SubHardware中寻找\n for (int i = 0; i < hardware->SubHardware->Length; i++)\n {\n if (GetHardwareTemperature(hardware->SubHardware[i], temperature))\n return true;\n }\n return false;\n }\n\n bool COpenHardwareMonitor::GetCpuTemperature(IHardware^ hardware, float& temperature)\n {\n temperature = -1;\n m_all_cpu_temperature.clear();\n for (int i = 0; i < hardware->Sensors->Length; i++)\n {\n //找到温度传感器\n if (hardware->Sensors[i]->SensorType == SensorType::Temperature)\n {\n String^ name = hardware->Sensors[i]->Name;\n //保存每个CPU传感器的温度\n m_all_cpu_temperature[ClrStringToStdWstring(name)] = Convert::ToDouble(hardware->Sensors[i]->Value);\n }\n }\n //计算平均温度\n if (!m_all_cpu_temperature.empty())\n {\n float sum{};\n for (const auto& item : m_all_cpu_temperature)\n sum += item.second;\n temperature = sum / m_all_cpu_temperature.size();\n }\n return temperature > 0;\n }\n\n bool COpenHardwareMonitor::GetGpuUsage(IHardware^ hardware, float& gpu_usage)\n {\n float usage_max = 0;\n for (int i = 0; i < hardware->Sensors->Length; i++)\n {\n //找到负载\n if (hardware->Sensors[i]->SensorType == SensorType::Load)\n {\n float cur_gpu_usage = Convert::ToDouble(hardware->Sensors[i]->Value);\n if (hardware->Sensors[i]->Name == L\"GPU Core\")\n {\n gpu_usage = cur_gpu_usage;\n return true;\n }\n\n //计算最大值\n if (cur_gpu_usage > usage_max)\n usage_max = cur_gpu_usage;\n }\n }\n gpu_usage = usage_max;\n return true;\n }\n\n bool COpenHardwareMonitor::GetHddUsage(IHardware^ hardware, float& hdd_usage)\n {\n for (int i = 0; i < hardware->Sensors->Length; i++)\n {\n //找到负载\n if (hardware->Sensors[i]->SensorType == SensorType::Load)\n {\n if (hardware->Sensors[i]->Name == L\"Total Activity\")\n {\n hdd_usage = Convert::ToDouble(hardware->Sensors[i]->Value);\n return true;\n }\n }\n }\n return false;\n }\n\n COpenHardwareMonitor::COpenHardwareMonitor()\n {\n ResetAllValues();\n }\n\n COpenHardwareMonitor::~COpenHardwareMonitor()\n {\n MonitorGlobal::Instance()->UnInit();\n }\n\n void COpenHardwareMonitor::ResetAllValues()\n {\n m_cpu_temperature = -1;\n m_gpu_nvidia_temperature = -1;\n m_gpu_ati_temperature = -1;\n m_gpu_intel_temperature = -1;\n m_hdd_temperature = -1;\n m_main_board_temperature = -1;\n m_gpu_nvidia_usage = -1;\n m_gpu_ati_usage = -1;\n m_gpu_intel_usage = -1;\n m_all_hdd_temperature.clear();\n m_all_hdd_usage.clear();\n m_cpu_freq = -1;\n m_cpu_usage = -1;\n }\n\n void COpenHardwareMonitor::InsertValueToMap(std::map& value_map, const std::wstring& key, float value)\n {\n auto iter = value_map.find(key);\n if (iter == value_map.end())\n {\n value_map[key] = value;\n }\n else\n {\n std::wstring key_exist = iter->first;\n size_t index = key_exist.rfind(L'#'); //查找字符串是否含有#号\n if (index != std::wstring::npos)\n {\n //取到#号后面的数字，将其加1\n int num = _wtoi(key_exist.substr(index + 1).c_str());\n num++;\n key_exist = key_exist.substr(0, index + 1);\n key_exist += std::to_wstring(num);\n }\n else //没有#号则在末尾添加\" #1\"\n {\n key_exist += L\" #1\";\n }\n value_map[key_exist] = value;\n }\n }\n\n void COpenHardwareMonitor::GetHardwareInfo()\n {\n ResetAllValues();\n error_message.clear();\n try\n {\n auto computer = MonitorGlobal::Instance()->computer;\n computer->Accept(MonitorGlobal::Instance()->updateVisitor);\n for (int i = 0; i < computer->Hardware->Count; i++)\n {\n //查找硬件类型\n switch (computer->Hardware[i]->HardwareType)\n {\n case HardwareType::Cpu:\n if (m_cpu_temperature < 0)\n GetCpuTemperature(computer->Hardware[i], m_cpu_temperature);\n if (m_cpu_freq < 0)\n GetCPUFreq(computer->Hardware[i], m_cpu_freq);\n if (m_cpu_usage < 0)\n GetCpuUsage(computer->Hardware[i], m_cpu_usage);\n break;\n case HardwareType::GpuNvidia:\n if (m_gpu_nvidia_temperature < 0)\n GetHardwareTemperature(computer->Hardware[i], m_gpu_nvidia_temperature);\n if (m_gpu_nvidia_usage < 0)\n GetGpuUsage(computer->Hardware[i], m_gpu_nvidia_usage);\n break;\n case HardwareType::GpuAmd:\n if (m_gpu_ati_temperature < 0)\n GetHardwareTemperature(computer->Hardware[i], m_gpu_ati_temperature);\n if (m_gpu_ati_usage < 0)\n GetGpuUsage(computer->Hardware[i], m_gpu_ati_usage);\n break;\n case HardwareType::GpuIntel:\n if (m_gpu_intel_temperature < 0)\n GetHardwareTemperature(computer->Hardware[i], m_gpu_intel_temperature);\n if (m_gpu_intel_usage < 0)\n GetGpuUsage(computer->Hardware[i], m_gpu_intel_usage);\n break;\n case HardwareType::Storage:\n {\n float cur_hdd_temperature = -1;\n GetHardwareTemperature(computer->Hardware[i], cur_hdd_temperature);\n //m_all_hdd_temperature[ClrStringToStdWstring(computer->Hardware[i]->Name)] = cur_hdd_temperature;\n InsertValueToMap(m_all_hdd_temperature, ClrStringToStdWstring(computer->Hardware[i]->Name), cur_hdd_temperature);\n float cur_hdd_usage = -1;\n GetHddUsage(computer->Hardware[i], cur_hdd_usage);\n //m_all_hdd_usage[ClrStringToStdWstring(computer->Hardware[i]->Name)] = cur_hdd_usage;\n InsertValueToMap(m_all_hdd_usage, ClrStringToStdWstring(computer->Hardware[i]->Name), cur_hdd_usage);\n if (m_hdd_temperature < 0)\n m_hdd_temperature = cur_hdd_temperature;\n }\n break;\n case HardwareType::Motherboard:\n if (m_main_board_temperature < 0)\n GetHardwareTemperature(computer->Hardware[i], m_main_board_temperature);\n break;\n default:\n break;\n }\n }\n }\n catch (System::Exception^ e)\n {\n error_message = ClrStringToStdWstring(e->Message);\n }\n }\n\n ////////////////////////////////////////////////////////////////////////////////////\n MonitorGlobal::MonitorGlobal()\n {\n\n }\n\n MonitorGlobal::~MonitorGlobal()\n {\n\n }\n\n void MonitorGlobal::Init()\n {\n updateVisitor = gcnew UpdateVisitor();\n computer = gcnew Computer();\n computer->Open();\n }\n\n void MonitorGlobal::UnInit()\n {\n computer->Close();\n }\n\n}\n"
},
{
"path": "OpenHardwareMonitorApi/OpenHardwareMonitorImp.h",
"content": "// OpenHardwareMonitorApi.h\n\n#pragma once\n#include \n#include \"OpenHardwareMonitor/OpenHardwareMonitorApi.h\"\n#include \"UpdateVisitor.h\"\n#include
![\"image-20250310121048889\"](\"Screenshots/image-20250310121048889.png\")
\n\n如果你的任务栏中没有显示“小组件”，则此选项是灰色不可用状态。\n\n### Windows11下“任务栏窗口显示在任务栏左侧”是灰色不可用状态\n\n在Windows11，只有在任务栏居中的情况下，此选项才可用。\n\n因为当任务栏靠左显示时，左侧没有给TrafficMonitor显示的空间。 \n\n### Windows11下，当任务栏被占满时，TrafficMonitor的任务栏窗口和任务栏图标重叠\n\n![\"image-20250310173257156\"](\"images/image-20250310173257156.png\")
\n\n这个问题目前无法解决，建议尽量不要让任务栏被占满，或者在系统设置中将“合并任务栏按钮和标签”改为“始终”。\n\n请不要向我反馈此问题。\n\n### 如何显示CPU和内存利用率？\n\n在主窗口点击右弹出键菜单，勾选“显示更多信息”。如果需要在任务栏窗口中也显示CPU和内存利用率，则在任务栏窗口中点击右键弹出菜单，选择“显示设置![](\"./Screenshots/images/item.png\")
”，在弹出对话框中勾选“CPU和内存利用率”即可。\n\n### 如何更改任务栏中“CPU”、“内存”等文本\n\n任务栏窗口中的标签文本是可以自定义的。点击鼠标右键，在右键菜单中选择“选项”，点击“任务栏窗口设置”，点击“显示文本设置”，双击项目右侧的文本即可更改，然后点击两次“确定”即可。\n\n![\"image-20221119093547649\"](\"Screenshots/images/image-20221119093547649.png\")
\n\n由于这些文本是可以自定义的，因此切换语言时不会自动更改。在切换语言后，你可以点击“显示文本”对话框中的“恢复默认”按钮。\n\n### 网速一直显示为0KB\n\n这种情况可能是因为你电脑中正在使用的网卡发生了切换导致的。\n\n点击右键菜单“选择网络连接”下面的“刷新网络连接列表”也许可以解决这个问题。\n\n![\"image-20221119094324759\"](\"Screenshots/images/image-20221119094324759.png\")
\n\n如果问题仍然存在，请尝试在“选择网络连接”的子菜单下选择你要监控的网络连接，而不是选择“自动选择”。\n\n如果问题仍然存在，请尝试在“选项设置”>“常规设置”>“高级”中点击“选择要监控的网络连接”按钮，在弹出的对话框中只勾选你想监控的网络连接，去掉其他项目的勾选，点击两次“确定”按钮即可。\n\n![\"image-20221119094501312\"](\"Screenshots/images/image-20221119094501312.png\")
\n\n### 如何单独设置任务栏窗口中每个项目的颜色？\n在右键菜单中选择“选项”，切换到“任务栏窗口设置”，勾选“指定每个项目的颜色”，此时再点击“文本颜色”右边的颜色块，就会弹出“任务栏窗口颜色设置”的对话框了。\n\n如果不勾选“指定每个项目的颜色”，则只能为文本设置统一的颜色。\n\n### 设置了开机自动运行仍然无法开机自启。\n从1.80版本开始，标准版和Lite版采用了不同的方式来实现开机自启动。\n\n* Lite版和1.80以前的版本：\n\n Lite版和1.80以前的版本的开机启动功能是通过在注册表“计算机\\HKEY_CURRENT_USER\\Software\\Microsoft\\Windows\\CurrentVersion\\Run”中创建“TrafficMonitor”的注册表项来实现的，如果你遇到无法开机启动的问题，请先检查该注册表项是否存在，再检查程序的路径是否正确。如果你移动了程序的位置，则会因为路径无效导致开机自启动失效，此时只需要在选项设置中取消“开机自动运行”的勾选，再将其勾选上就可以了。\n\n 注意，某些第三方安全软件可能会阻止TrafficMonitor的开机自启动，请尝试在安全软件中允许TrafficMonitor开机自启动。\n\n 如果设置了以管理员身份运行也会出现开机无法自启动的问题，请尝试去掉以管理员身份运行。\n\n* 标准版：\n\n 标准版是通过创建任务计划来实现开机自启动的。可以通过`控制面板\\系统和安全\\管理工具`来打开任务计划程序。\n\n 如下图所示：\n\n ![](\"./Screenshots/images/image3.jpg\"/)
\n\n 如果你遇到无法开机自启动的情况，请到“任务计划程序”中检查TrafficMonitor的计划任务是否正常创建，exe文件的路径是否正确。\n\n开机无法自启动的一个常见原因是你可能移动了TrafficMonitor主程序的位置。如果你为TrafficMonitor设置好了开机自动运行，但是你将TrafficMonitor移动到了其他位置，那么开机自启动肯定就失效了。你需要打开TrafficMonitor的“选项设置”——“常规设置”，如果“开机时自动运行”处于勾选状态，先去掉勾选，然后再次打开“选项设置”——“常规设置”，重新勾选“开机时自动运行”即可。\n\n需要注意的是，如果你使用不含温度监控的版本在注册表中创建了开机自启动项，然后再使用包含温度监控的版本开启开机自启动功能，它会自动将注册表中的开机自启动项删除，再在任务计划中创建开机自启动项。反之亦然。\n\n### 程序弹出“无法保存设置”的对话框。\n如果遇到这种情况，说明程序没有向其所在目录下写入数据的权限，导致设置数据无法保存。尝试将程序移动到其他有写入权限的文件夹中可以解决这个问题。\n\n你也可以通过以下步骤将配置文件的保存路径改为C:\\Users\\\\<用户名\\>\\AppData\\Roaming\\TrafficMonitor目录。\n\n* 退出TrafficMonitor，以管理员身份重新启动TrafficMonitor。\n* 在右键菜单中选择“选项”，切换到“常规设置”选项卡，在“数据和配置文件”中选择“保存到Appdata目录”。\n\n如果此时仍然提示“无法保存设置”，请打开应用程序所在目录，打开`global_cfg.ini`文件，如果不存在请新建一个，在里面添加如下内容：\n\n```\n[config]\nportable_mode = false\n```\n\n如果无法新建，可以在其他位置（比如桌面）新建该文件，然后移动到程序所在目录。\n\n如果`global_cfg.ini`文件已存在，就把`portable_mode `的值改成`false`，保存后重新启动TrafficMonitor。\n\n如果`global_cfg.ini`没有写入权限，可以尝试把该文件复制到桌面，改好后复制回原来的路径将原文件覆盖。\n\n执行以上步骤后理论上应该不会出现这种问题了。如果这个问题仍然出现，请尝试把C:\\Users\\\\<用户名\\>\\AppData\\Roaming\\TrafficMonitor\\config.ini删除，该文件会在删除后重新生成。\n\n在1.79以后的版本中，如果程序所在目录无法写入数据，会自动将配置和数据文件保存到C:\\Users\\\\<用户名\\>\\AppData\\Roaming\\TrafficMonitor目录，此时，“选项”——“常规设置”——“数据和配置文件”中“保存到程序所在目录”将不可用。\n\n### 更改设置后下次开机时设置丢失\n\n如果你没有看到“无法保存设置”的对话框，则说明程序的配置文件是能正常保存的。因此这个问题的原因可能是你的电脑中存在了多个TrafficMonitor的程序文件，并且配置文件保存在了程序所在目录下。\n\n例如，你打开了“D:\\software\\TrafficMonitor\\TrafficMonitor.exe”，并且更改了选项设置，但是下次开机时启动的却是“D:\\software1\\TrafficMonitor\\TrafficMonitor.exe”，而你之前修改的配置被保存在了“D:\\software\\TrafficMonitor\\”目录下。\n\n解决这个问题的方法是：\n\n1. 在“选项设置”>“常规设置”>“配置和数据文件”中，将配置文件的保存位置更改为Appdata目录。\n2. 删除你电脑中不需要的TrafficMonitor的程序文件，启动TrafficMonitor后，打开“选项设置”>“常规设置”，点击“重新设置开机自动运行”按钮。\n\n### 网速数值显示不全。\n由于不同字体每个字符的宽度并不一样，在某些情况下，确实会出现网速数值显示不全的问题。如果出现了这样的问题，请打开“选项”——“任务栏窗口设置”，在“数据位数”下拉列表中选择一个更大的值。\n### 设置了鼠标穿透后如何取消？\n在通知区的TrafficMonitor的图标上点击鼠标右键，去掉“鼠标穿透”的勾选即可。\n\n设置了鼠标穿透后，悬浮窗将无法响应任何鼠标消息，也无法弹出右键菜单，但是可以通过通知区图标来弹出右键菜单。主窗口的右键菜单和通知区图标的右键是完全一样的。\n\n另外，即使你之前设置了隐藏通知区图标，开启鼠标穿透后，通知区图标也会自动显示出来，防止无法弹出右键菜单。\n\n说明：以下几种情况下通知区图标会自动显示出来：\n\n* 开启鼠标穿透后；\n* 不显示任务栏窗口的情况下隐藏主窗口后；\n* 隐藏主窗口的情况下关闭任务栏窗口后；\n* 开启鼠标穿透的情况下关闭任务栏窗口后。\n### Windows 10 白色任务栏主题时任务栏窗口颜色的问题\n\n在使用白色任务栏主题时，你可以在在“任务栏窗口设置”点击“预设方案”按钮，选择“浅色模式”，可以一键设置浅色模式任务栏颜色。如图所示：\n\n![](\"./Screenshots/images/image2.jpg\")
\n\nAt the same time, you may also check \"Auto adapt to Windows 10 dark/light theme\", the program will automatically switch the color preset when Windows 10 dark/light theme is changed. You can click the \"Auto Adapt settings\" button to configure which color preset to use for dark and light themes.\n\n### The taskbar windows cannot be displayed when the HDR is turned on in Windows 10\n\nSome users have reported that turning on the HDR function in Windows 10 will cause the taskbar window to fail to display. If you encounter this problem, you can try turning off the \"Background Transparent\" option in [\"Option Settings\" - \"Taskbar Window Settings\"](https://github.com/zhongyang219/TrafficMonitor/wiki/选项设置#任务栏窗口设置).\n\nSince version 1.85, this can be fixed by changing to Direct2D rendering in \"Options Settings\" - \"Taskbar Window Settings\" - \"Rendering Settings\".\n\n### The CPU usage displayed is inconsistent with Task Manager\n\nSince Windows 10, if you want to make the CPU usage shown by TrafficMonitor consistent with Task Manager, please go to \"Option Settings\"-\"General Settings\"-\"Advanced\"-\"CPU usage acquisition method\", and select \"Use the performance counter\".\n\n### About the temperature monitoring of TrafficMonitor\n\nDue to some problems occurred in some computers caused by the temperature monitoring function, the temperature monitoring function is turned off by default. If you want to use the temperature monitoring function of TrafficMonitor, please go to [\"Option Settings\"-\"General Settings\"-\"Hardware Monitoring\"](https://github.com/zhongyang219/TrafficMonitor/wiki/选项设置#硬件监控) to enable it. After it is turned on, temperature-related items will appear under the \"Display Settings\" submenu in the taskbar right-click menu.\n\nThe temperature monitoring function of TrafficMonitor relies on a third-party open source library [LibreHardwareMonitor](https://github.com/LibreHardwareMonitor/LibreHardwareMonitor). If you encounter the problem that the hardware temperature cannot be displayed, or the displayed temperature is incorrect, then please download LibreHardwareMonitor first, and check whether LibreHardwareMonitor can display the corresponding temperature normally.\n\nIf LibreHardwareMonitor cannot display the temperature of the corresponding hardware, then I cannot solve this problem. You can report your problem to the author of LibreHardwareMonitor.\n\nIf the latest version of LibreHardwareMonitor can display the hardware temperature normally, replace the LibreHardwareMonitorLib.dll files in the TrafficMonitor folder with the downloaded the LibreHardwareMonitorLib.dll files may solve this problem.\n\n**Note: The hardware monitoring function (including temperature monitoring and GPU usage monitoring) may have some problems, which may cause more CPU and memory usage. According to feedback from some users, turning on the temperature function will cause problems such as program crashes and system crashes. Please decide to turn on the hardware monitoring function after you are aware of the above risks. Otherwise, please do not use the hardware monitoring function.**\n\n## The program prompts that \"MSVC\\*.dll\" or \"mfc\\*.dll\" cannot be found when the program starts\n\nClick the link below to download and install the Microsoft Visual C++ runtime environment.\n\n[Latest supported Visual C++ Redistributable downloads | Microsoft Docs](https://docs.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170)\n\n### I want to have more hardware information on the taskbar, such an fan speed, power, etc\n\nThe Hardware Monitor plug in is now available. It can display all the monitoring items in LibreHardwareMonitor.\n\n\n\nFor instructions and download links, please click the link below to go to the plug-in download page:\n\n[TrafficMonitorPlugins/download/plugin_download.md at main · zhongyang219/TrafficMonitorPlugins](https://github.com/zhongyang219/TrafficMonitorPlugins/blob/main/download/plugin_download.md)\n\n### About the crash issue\n\nIf you encounter the problem of program crash, please turn off all the items in \"Options\" - \"General Settings\" - \"Hardware Monitoring\" after restarting the program, because based on the DMP file provided by the user, most crash problems are related to the hardware monitoring function. I cannot solve the crash problem related to the hardware monitoring function, please do not send me email feedback. If you have excluded the hardware monitoring problem, but the crash problem still exists, please go to \"Options\" - \"General Settings\" - \"Advanced\" - \"Plug-in Management\" to disable all plugins, and then restart the program. (If the program fails to start, please delete all the `dll` files in the `plugins` in the directory where TrafficMonitor is located). If you have excluded the plugin problem, but the crash problem still exists, please send me the email according to the prompts in the crash window.\n\nIf you have encountered any other problems, you can also click \"Contact Author\" in the \"About\" dialog box, or directly [click here](mailto:zhongyang219@hotmail.com) to send me an email.\nPlease describe the problems you have encountered in detail, the error prompts, what operations you have tried, it is better to attach the screenshots and configuration files (\"Options\"-\"General Settings\"-\"Open configuration file path\"). \nNote: Please confirm the email address that you used before sending the email. If your email address is form like \"Outlook_\\