Button Meter doesn't appear when DynamicVariables=1 is added.

For instance,

[Hours] Measure=Time Format=%H

[Minutes] Measure=Time Format=%M

[MeterTest] Meter=Button X=0 Y=0 ButtonImage=button.png ButtonCommand=!Execute ["http://www.google.com/search?&q=[Hours]:[Minutes]"]

DynamicVariables=1

Environment: Rainmeter.exe v1.1 r213 32bit Windows XP SP3

This happens because meter's dimension are reset to 1. Therefore, it is necessary to set the dimension again when Dynamic Variables is enabled.

MeterImage with the same issue fixed. (attach the files of MeterImage)

Since I don't know for sure which revision you used to create this full version of MeterImage.cpp, could I get you to download the latest revision, make this change and use Tortoise to create a "patch" of the change? Then I can get it in the trunk for you without danger of a version conflict. I have stepped on Rainy once and am determined not to do it again.. ;-)

"MeterImage.patch" in MeterImage.zip is based on r214. I think maybe it's okay. ;-)

If possible, could I participate in the team as a developer? I think that maybe I can contribute several bug fixes though I am not good at English. :)

Thanks! I will get your change in today.

As to the other question, that would be up to Rainy. He reads these issue messages, so I'm sure he will reply when he gets time.

Thank you so much spx268. BTW, to solve this issue, If it is possible, could you apply this bug fix also to the Button meter?

About the matter to join in to the dev team, I will call the project owner from me later.

It's possible. Meters that have the same issue was fixed.

Includes: MeterBar, MeterBitmap, MeterButton, MeterRotator

Added...

Thanks again, spx268.

Now, I actually tested. It seems to find trouble still a little bit though there is no problem in the first sample Config.↑ For instance, it seems not to work normally for skin that shows the button when the mouse is put on a certain area. This is a problem of relating to Update perhaps, and the button shows strange behavior. Since I attached a sample, I would like you to verify it.

Comment deleted

You guessed right. "Hidden=1" is forcedly applied when the meters are updated every time. Similarly, I seem that MoveMeter, Enable/DisableMeasure etc. are ignored too.

I think that dynamic variables have a lot of potential bugs (or specifications), and it's necessary to discuss it to define about behavior.

E.g. Which is given priority to:

[MeterMenu] MouseOverAction=!Execute [!RainMeterHideMeter MeterButton1] MouseLeaveAction=!Execute [!RainmeterShowMeter MeterButton1]

[MeterButton1] DynamicVariables=1

Hidden=[MeasureButton1]

I agreed. I also have the anxiety that "dynamic variables" causes many other problems. And I'm sure that since we cannot overcome these issues, the "dynamic variables" is not real ENHANCEMENT of Rainmeter. To clear the issue, I will verify it more in detail in various tests. And I hope that you cooperate with this issue continuously. Thanks,