TLDR: No fix forthcoming, at least for now.
Here's the reply I got:
I wrote back and asked if I could post this e-mail to the forum, and got this reply.Hi,
I guess you are referring to the plugin I have created based on the sources by LeoDavidson and uploaded in this thread?
To be honest, there are 179 Downloads of this in well over one year and maintaining this plugin that was relying on our internal data structure is not very high on our priority list.
As you most likely know: making Argus Monitor is something we (2 HW/SW engineers) do in our spare time, as a hobby, next to full time jobs and families. So the time for it is very limited (I am writing this after having picked up my 2 kids from Kindergarden and before I have to prepare dinner for us ) and we have to focus on what most users benefit from. So, I personally can't keeping this up to date myself (if Leo wants he can contact us and I will give him the modified sources back, together with the information required to make it work for the current release).
There is a silver lining for those of you that were relying on this plugin though (which should basically still work, maybe with the exception of some values like GPU load). I am currently working on a new API that should be able to provide a stable interface to our data and that will be:
a) based on shared memory,
b) documented, so anyone with some knowledge of programming can access the information and
c) should be stable and not change frequently, even if the internal data structures inside Argus might required changing
Right now, the PlugIn you use is relying on the data we exchange with the sidebar gadget and as users request changes to this part of Argus, we might have to update this which in turn requires updates to the Rainmeter plugin. Not good, but currently the only way to go.
I can't tell when the new 'official' API is ready and we are working on some other major refactoring for 5.3 that will keep us busy, so it will not be in 5.3.01, but maybe in 5.3.02 (we are two guys working on this project, so we have to discuss and align when we can bring this and what the priorities of other tasks are).
Sorry for not being able to be of more direct help here, but this is as good as it gets for now.
sure, please quote/post my response. Also, if Leo (the OP of the thread) wants to, he can contact us again and I will provide the information he needs to adapt the current plugin to the new data structure.
In theory, it would have been possible to make this structure publicly available, but what prevented us from doing so was that this would have tie us to external dependencies as soon as someone would rely on this and we could not freely change it as soon as this would be required.
The release of an 'official' API will free us from that and would also help other use cases if someone wants to get to the data for any means she can think of.