NetSpeedTray

C

Camel1965

Bardzo aktywny
Zasłużony
Dołączył
8 Wrzesień 2010
Posty
55549
Reakcje/Polubienia
40839

NetSpeedTray 2.1.3​

NetSpeedTray v2.1.3: the app finally speaks your language​


A patch release built almost entirely from a month of your bug reports. The headline is a bug that has been in every version NetSpeedTray has ever shipped: the app never actually detected your system language. Alongside it, three real hardware-readout fixes - including one where the widget was showing you your graphics card's temperature under a CPU label.


⚠️ Please read if you have never picked a language manually. NetSpeedTray may now start in your Windows display language instead of English, because auto-detect finally works. For Hebrew that also means the whole interface mirrors right-to-left. If you preferred it in English, choose English (US) in Settings → General → Language - the choice sticks. Everything else carries over untouched.
Kliknij aby rozwinąć...

Bug Fixes​


"Auto-detect (system)" never detected anything. (
Zaloguj lub Zarejestruj się aby zobaczyć!
) NetSpeedTray asked Windows for your system language, but on Windows that call returns a name like Korean_Korea rather than the ko_KR code our language files use. The lookup missed every time and quietly fell back to English. German, Spanish and French happened to work purely by accident; Korean, Japanese, Russian, Polish, Dutch, Slovenian, Hebrew and both Chinese variants never did - in any release. If you ever installed NetSpeedTray, found it in English despite your system being set otherwise, and assumed it simply wasn't translated: it was, and I'm sorry. Reported by
Zaloguj lub Zarejestruj się aby zobaczyć!
, who translated the app into Korean and then had to report that she couldn't see her own work.


  • The Language card now shows what auto-detect resolved to, so this can never fail silently again.
  • Choosing "Auto-detect (system)" now correctly prompts you to restart. It previously stayed silent.
  • If your Windows display language is English but your regional format is German, Spanish or French, you keep the localized app you had before.

The widget showed your GPU's temperature as your CPU's. (
Zaloguj lub Zarejestruj się aby zobaczyć!
) When a machine has no sensor named exactly "CPU Package", NetSpeedTray falls back to matching sensor names - and one of the words it matched on was "Core". NVIDIA's sensor is called "GPU Core". On laptops whose CPU publishes no temperature at all, that was the only sensor in the running, so your graphics card's temperature appeared under a CPU label. A sensor's identity now decides. Thanks to
Zaloguj lub Zarejestruj się aby zobaczyć!
, whose sensor report made this visible.


GPU usage ignored every app you started after NetSpeedTray. (
Zaloguj lub Zarejestruj się aby zobaczyć!
) Windows reports GPU load per process, and NetSpeedTray built its list of processes to watch once, at startup - so any program launched afterwards was never counted. On a single-GPU PC this hid; on a laptop with both an integrated and a discrete GPU it meant the discrete card was never measured at all. Thanks to
Zaloguj lub Zarejestruj się aby zobaczyć!
, who filed it as a feature request and turned out to have found a bug.


The widget could show "GPU 0%" without ever having measured the GPU. Over a Remote Desktop connection NetSpeedTray deliberately skips GPU polling, but the readout still displayed a confident 0% - which was really just the value it starts up with. An unmeasured CPU or GPU reading now shows N/A. A genuine 0% on an idle GPU is still shown as 0%.


VRAM read 0.0 GB after every sleep/wake until you opened Settings and clicked Save. (
Zaloguj lub Zarejestruj się aby zobaczyć!
) The GPU counters don't survive a suspend cycle, and nothing rebuilt them. They are now rebuilt when your PC wakes.


The taskbar and the Monitor window disagreed about the temperature. (
Zaloguj lub Zarejestruj się aby zobaczyć!
) The widget cut the decimal off while the Monitor rounded it, so the same 27.9 °C reading showed as "27" in one place and "28" in the other.


Dragging the widget more than ~500 px from the tray snapped it back. (
Zaloguj lub Zarejestruj się aby zobaczyć!
) The saved position is a distance from the edge of your screen, and anything past 500 was rejected and reset on the next launch - so on a 4K taskbar almost any real drag silently undid itself.


The language list only showed the first 10 languages. (
Zaloguj lub Zarejestruj się aby zobaczyć!
) Chinese, Traditional Chinese and Hebrew sat below the fold with no way to scroll to them by mouse. The list now sizes itself, so it will keep fitting as languages are added.


The Monitor's Hardware graph was drawing an empty grid. (
Zaloguj lub Zarejestruj się aby zobaczyć!
) The CPU, GPU and RAM tab showed a blank chart with a 0-1 scale instead of your history - and had done since 2.1.0. The two data sources behind it disagree on how they stamp time, and the hardware one tripped a conversion that was caught and logged rather than shown, so the tab failed quietly and looked merely empty. The Network graph on the next tab was never affected. Found by opening the tab while smoke-testing this release.


The app never told Windows what version it was. (
Zaloguj lub Zarejestruj się aby zobaczyć!
) Right-clicking NetSpeedTray.exe and opening Properties showed a blank Details tab - no version, no publisher, no copyright - in every release ever shipped. The version resource was being written in a form Windows could not read back. Beyond the Properties dialog, installers, update tools and antivirus reputation checks all read that metadata, so this is worth more than it looks.


✨ Added​


Optional colours for the upload and download arrows. (
Zaloguj lub Zarejestruj się aby zobaczyć!
) The arrows have always taken their colour from the speed text beside them, so with colour coding on, the whole line changes together. That is still the default and nothing moves on upgrade. Turn on Settings → Appearance → Custom arrow colors to give each direction its own fixed colour instead. Requested by
Zaloguj lub Zarejestruj się aby zobaczyć!
.


Keep the Settings and Monitor windows on top. (
Zaloguj lub Zarejestruj się aby zobaczyć!
) A new toggle in Settings → Advanced → Behavior pins both windows above everything else, so the Monitor can sit over a full-screen app while you watch a transfer. Requested by
Zaloguj lub Zarejestruj się aby zobaczyć!
.


Localization​


Turkish is the 14th language, contributed by
Zaloguj lub Zarejestruj się aby zobaczyć!
- a complete, careful translation that landed with full key parity on the first try.


Translation updates from
Zaloguj lub Zarejestruj się aby zobaczyć!
(Japanese) and
Zaloguj lub Zarejestruj się aby zobaczyć!
(Russian), plus a fill-in pass across the remaining languages. Several strings that were still shipping in English - the free-float label and the portable-update messages - are now translated.


Zaloguj lub Zarejestruj się aby zobaczyć!
also caught a mistake in the English source: the Monitor window was still being called "the dashboard", a name the app dropped in 2.0, which every locale had been faithfully translating.


Native-speaker review is still very welcome - see
Zaloguj lub Zarejestruj się aby zobaczyć!
. Some of this release's strings are my own drafts, and corrections are genuinely wanted.


Security​


Pillow updated to 12.3.0, closing thirteen advisories in the image library matplotlib uses to draw the history graph. To be straight about it: none of them were reachable here - NetSpeedTray never opens an image, it only writes its own graph - so this is housekeeping rather than a fix for anything that put you at risk. The dependency is current again either way.


Quality Assurance​


1141 unit tests pass - up from 865 in 2.1.2. Every fix in this release was verified against the pre-fix code to confirm its tests actually fail without it.


This release was also smoke-tested as a real build - installed, clicked through every Monitor tab, and run in Turkish - which is how the two fixes above were found. Neither was reachable by a unit test: one lives in the packaged executable, the other behind an exception handler.


New this release: a locale is now checked for more than key parity. Turkish arrived as a complete file that the app could not actually reach, because a language also has to be registered in code - and every existing test passed. That gap is closed.
Kliknij aby rozwinąć...
Zaloguj lub Zarejestruj się aby zobaczyć!
 
Musisz się zalogować lub zarejestrować aby odpowiedzieć
Do góry