I know it's a bit late, but I have to say something about CyberTheWorm's initial code: usually it's an extremely wrong idea to set the Update value of a skin which is using the WebParser plugin, to -1. That because a such plugin measure needs time to parse the data, but if the Update of the skin is set to -1, after the plugin measure gets the data, it can't be shown, because the skin is never updated, due to the negative Update value. Usually it's a much better idea to set the Update to the default 1000 (as FreeRaider suggested).
Yeah, I know you did this CyberTheWorm, this was just a short comment to make you to understand why a negative Update is undesired on a such skin.
balala wrote:I know it's a bit late, but I have to say something about CyberTheWorm's initial code: usually it's an extremely wrong idea to set the Update value of a skin which is using the WebParser plugin, to -1. That because a such plugin measure needs time to parse the data, but if the Update of the skin is set to -1, after the plugin measure gets the data, it can't be shown, because the skin is never updated, due to the negative Update value. Usually it's a much better idea to set the Update to the default 1000 (as FreeRaider suggested).
Yeah, I know you did this CyberTheWorm, this was just a short comment to make you to understand why a negative Update is undesired on a such skin.
Just for your knowledge, in the original code of CyberTheWorm you can use Update=-1 and add a FinishAction=[!UpdateMeter *][!Redraw] option in a "parent" measure, but it will NOT update the information captured.
FreeRaider wrote:Just for your knowledge, in the original code of CyberTheWorm you can use Update=-1 and add a FinishAction=[!UpdateMeter *][!Redraw] option in a "parent" measure.
Yes, that's right, it can be used, but it wasn't. Without a proper FinishAction, the skin which uses Update=-1 and the WebParser measure, won't never work.
balala wrote:I know it's a bit late, but I have to say something about CyberTheWorm's initial code: usually it's an extremely wrong idea to set the Update value of a skin which is using the WebParser plugin, to -1. That because a such plugin measure needs time to parse the data, but if the Update of the skin is set to -1, after the plugin measure gets the data, it can't be shown, because the skin is never updated, due to the negative Update value. Usually it's a much better idea to set the Update to the default 1000 (as FreeRaider suggested).
Yeah, I know you did this CyberTheWorm, this was just a short comment to make you to understand why a negative Update is undesired on a such skin.
Yes I figured that out after posting and seeing the initial comments. I did not want to pull data from the web site every second. FreeRaider pointing me in the correct direction with.