Page 4 of 6
Re: Disabled option in meters
Posted: April 12th, 2018, 3:00 pm
by jsmorley
balala wrote:When I click the Click me string meter, I get in the log an Error: Cannot replace variable with itself "" message.
Huh.. I don't.
4.2.0 beta r3029 64-bit (Feb 8 2018)
Windows 10 Pro 64-bit (build 16299)
Path: C:\Program Files\Rainmeter\
IniFile: C:\Users\Jeffrey\AppData\Roaming\Rainmeter\Rainmeter.ini
SkinPath: C:\Users\Jeffrey\Documents\Rainmeter\Skins\
Skin .ini encoded as UTF-16 Little Endian.
Re: Disabled option in meters
Posted: April 12th, 2018, 3:22 pm
by balala
jsmorley wrote:Huh.. I don't.
4.2.0 beta r3029 64-bit (Feb 8 2018)
Windows 10 Pro 64-bit (build 16299)
Path: C:\Program Files\Rainmeter\
IniFile: C:\Users\Jeffrey\AppData\Roaming\Rainmeter\Rainmeter.ini
SkinPath: C:\Users\Jeffrey\Documents\Rainmeter\Skins\
Skin .ini encoded as UTF-16 Little Endian.
4.1.0 beta r2947 64-bit (Oct 18 2017)
Windows 10 Pro 64-bit (build 16299)
Path: C:\Program Files\Rainmeter\
IniFile: C:\Users\Laci\AppData\Roaming\Rainmeter\Rainmeter.ini
SkinPath: D:\Documents\Rainmeter\Skins\
The .ini file is encoded as ANSI. Have to try to re-encode. Let's see...
Re: Disabled option in meters
Posted: April 12th, 2018, 3:23 pm
by jsmorley
balala wrote:4.1.0 beta r2947 64-bit (Oct 18 2017)
Windows 10 Pro 64-bit (build 16299)
Path: C:\Program Files\Rainmeter\
IniFile: C:\Users\Laci\AppData\Roaming\Rainmeter\Rainmeter.ini
SkinPath: D:\Documents\Rainmeter\Skins\
The .ini file is encoded as ANSI. Have to try to re-encode. Let's see...
So it is something we fixed in the beta... Your version of Rainmeter is pretty old. Not even the "release" of 4.1.
Re: Disabled option in meters
Posted: April 12th, 2018, 3:26 pm
by balala
jsmorley wrote:So it is something we fixed in the beta... Your version of Rainmeter is pretty old. Not even the "release" of 4.1.
And you think updating could help? I don't update all the times, just from time to time.
Re: Disabled option in meters
Posted: April 12th, 2018, 3:27 pm
by jsmorley
balala wrote:And you think updating could help? I don't update all the times, just from time to time.
Well yeah... This issue aside, I'm not sure I can approve of staying on an earlier beta of 4.1 when there is a release of 4.1...
Re: Disabled option in meters
Posted: April 12th, 2018, 3:30 pm
by balala
jsmorley wrote:Well yeah... This issue aside, I'm not sure I can approve of staying on an earlier beta of 4.1 when there is a release of 4.1...
Right now I can't update, because some stuffs are running in the background and I'd like to wait them to finish, but a bit later I definitely will try. Made me curious...
Re: Disabled option in meters
Posted: April 12th, 2018, 3:46 pm
by balala
jsmorley wrote:Well yeah... This issue aside, I'm not sure I can approve of staying on an earlier beta of 4.1 when there is a release of 4.1...
You had right, upgrading to the latest version fixed the issue. Now everything seem to be ok.
4.2.0 beta r3029 64-bit (Feb 8 2018)
Windows 10 Pro 64-bit (build 16299)
Path: C:\Program Files\Rainmeter\
IniFile: C:\Users\Laci\AppData\Roaming\Rainmeter\Rainmeter.ini
SkinPath: D:\Documents\Rainmeter\Skins\
Re: Disabled option in meters
Posted: April 26th, 2018, 11:01 am
by Active Colors
I haven't practically tried, but in theory, if you overlay your skin with a meter that has some mouse action it should prevent other meters below from launching their actions. Thus you can place some dummy invisible meter with dummy mouse action on top of other meters which will disable launching actions from other meters. No?
Re: Disabled option in meters
Posted: April 26th, 2018, 11:12 am
by fonpaolo
I wish it could be true, or I'm probably doing something wrong, because even using "[]" to disable a mouse action, if you overlay with it on another meter, the command of the underlying meter will be executed, or in some cases both.
Re: Disabled option in meters
Posted: April 29th, 2018, 1:42 am
by Virginityrocks
Make sure the dummy meter is placed "on top" of the meter with the mouse actions by putting the dummy meter after the meter with the mouse actions in the code. If you put the dummy before the other meter, it won't work.
Won't work:
Code: Select all
[DummyMeter]
MouseAction=[]
[Meter1]
MouseAction=!THINGS
Will work:
Code: Select all
[Meter1]
MouseAction=!THINGS
[DummyMeter]
MouseAction=[]