You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First, I want to say the work on this repo is impressive. great use of clever techniques!
It would be really helpful to have a separate crate for the LibreHardwareMonitor wrapper, making it accessible for other Rust projects.
I downloaded the app and ran it, but noticed that the temperature data is missing:
Interestingly, the temperature readings are visible in LibreHardwareMonitor itself.
I’m also curious about the wrapper implementation. I see it retrieves the entire report each time. does this result in significantly higher resource usage compared to fetching individual data points, like just the temperature?
Thanks!
The text was updated successfully, but these errors were encountered:
the missing temperature data is probably related to the less than stellar logic that loads LHM sensors into the System structure. i'll blame this on the inconsistent sensor naming scheme for AMD CPUs.
for your efficiency question, i think that updating specific sensors may be more efficient in the c# code. im not actually sure that LHM supports updating a single sensor, seems like it would. less sensors in each update that goes through the wrapper would probably be more efficient, not 100% sure.
and for the idea of making a crate from this wrapper, it could definitely be done, but i don't feel this version is mature enough to be made available in that way. for example, if your system has a particularly large number of LHM sensors it will panic the wrapper and crash the application.
First, I want to say the work on this repo is impressive. great use of clever techniques!
It would be really helpful to have a separate crate for the LibreHardwareMonitor wrapper, making it accessible for other Rust projects.
I downloaded the app and ran it, but noticed that the temperature data is missing:
Interestingly, the temperature readings are visible in LibreHardwareMonitor itself.
I’m also curious about the wrapper implementation. I see it retrieves the entire report each time. does this result in significantly higher resource usage compared to fetching individual data points, like just the temperature?
Thanks!
The text was updated successfully, but these errors were encountered: