![]() But - this assumes that once you start OHM up, the set of sensors and the order it reports them is fixed. Clearly this is where your problem appears as they aren't fixed. I think the best solution which will fix the problem and still be efficient is to have the plugin see if it gets a different number of sensor values than it expects in 2) and if that occurs, trigger a "reset" and go back to mode 1) to refresh the sensor list. I can also put valid ranges on the sensor values (Load should never be above 100, Temperatures should never be above 500, etc) and if those are violated (which would indicate the wrong sensor is being read), also trigger a mode 1) refresh. Looks like there are some issues that need looking into. The skins made with the plugin seem to work fine in and of themselves. Everything displays as it should and it's very nice. If any skin using it is running, then Rainmeter becomes a bit weird and unstable. Rmskin file, I either get a crash of Rainmeter (if the new skin has a Lua script) or a behavior where the new skin is loaded but does not display unless I refresh the skin. Rainmeter open hardware monitor plugin skin#.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |