I had the same "problem" as you, but obviously concerning other things:
https://forum.rainmeter.net/viewtopic.php?t=42367#p214984
So yep, as Brian said, this "problem" is normal, and the behavior is the expected one. RunCommand will only get the STDOUT output once the program you ran terminates.
In your case, I see 3 potential solutions:
- try to make the observer write to a .csv log file instead, which you could then periodically parse with WebParser (assuming it's not locked into a write only state and such by the observer; if by any chance you can make the observer only write the last event, then the parsing would probably be a little faster)
- try to direct data to an AutoIt / AutoHotKey (compiled or not) script, because both these tools can actually send bangs to a Rainmeter skin periodically (like, say, setting a variable with the current data received from the observer) at a very low performance cost, given that they use window messages
- try to use the plugin you mentioned, because if it's made well and you figure out exactly how to use it, it represents by far the easiest, most comfortable and most practical choice for an efficient retrieval of your MQTT data
https://forum.rainmeter.net/viewtopic.php?t=42367#p214984
So yep, as Brian said, this "problem" is normal, and the behavior is the expected one. RunCommand will only get the STDOUT output once the program you ran terminates.
In your case, I see 3 potential solutions:
- try to make the observer write to a .csv log file instead, which you could then periodically parse with WebParser (assuming it's not locked into a write only state and such by the observer; if by any chance you can make the observer only write the last event, then the parsing would probably be a little faster)
- try to direct data to an AutoIt / AutoHotKey (compiled or not) script, because both these tools can actually send bangs to a Rainmeter skin periodically (like, say, setting a variable with the current data received from the observer) at a very low performance cost, given that they use window messages
- try to use the plugin you mentioned, because if it's made well and you figure out exactly how to use it, it represents by far the easiest, most comfortable and most practical choice for an efficient retrieval of your MQTT data
Statistics: Posted by Yincognito — Yesterday, 8:26 pm