Just a few explanations on why this gone on. So let's take mak_kawa's reply:
Well, in fact [measureDisplayName] isn't even a measure. From the point of view of Rainmeter, [measureDisplayName] is nothing. In the original posted code, [measureDisplayName] looks like:
makes no sense at all, because a option should define the measure type, Calc, String or whatever. Even if the existing [measureName] measure would return the name of a valid measure type (like mentioned previously Calc, String or whatever), which I doubt, but let's just suppose it does, the option just wouldn't work. Not even would, especially not if a isn't added. has always to be set explicitly. Additionally options like Measure2, Measure3 nowhere exist. These can't be used on no measure type. Don't make too much sense. MeasureName2, MeasureName3 yes, on String measures for instance, but Measure2, Measure3 and so on, NO!
Code: Select all
[measureDisplayName] Measure=measureName Measure2=measureChargeCurrentRequest Measure3=measureChargePower IfCondition=(%3 > 0) IfTrueAction=[!SetOption meterTitle Text "%1 lädt mit %2A/%3KW"]
Secondly again doesn't make sense. In IfCondition you have to precise the name of the measure you'd like to compare. In this case theoretically , but because [measureChargePower] is a WebParser measure (also although it does work, take care that WebParser isn't anymore a plugin as it was once, but a measure) you have to make the conversion this way , which also requires to set on the dynamic variables, as mak_kawa did.