I believe you, but I tried the bits you posted thus far (you initial post, typo corrected) and they worked, see above. Maybe I'm missing something?
P.S. At first I thought you were right, but it was because of a mistake I made.
I believe you, but I tried the bits you posted thus far (you initial post, typo corrected) and they worked, see above. Maybe I'm missing something?
Yincognito wrote: ↑June 30th, 2021, 1:45 am I believe you, but I tried the bits you posted thus far (you initial post, typo corrected) and they worked, see above. Maybe I'm missing something?
!IgnoreActive Colors wrote: ↑June 30th, 2021, 12:22 am If it is happening with your code maybe you can pack your skin and attach here? Hopefully it will get resolved too.
Code: Select all
[Rainmeter]
Update=-1
AccurateText=1
[Lua]
Measure=Script
ScriptFile=#@#Scripts\String.lua
[Variables]
String=Meter5
LMUA=([&Lua:Index('[#*CURRENTSECTION*]')]+[&Lua:Index('[#*CURRENTSECTION*]')])
RMUA=([&Lua:Index('[#*String*]')]+[&Lua:Index('[#*String*]')])
[Meter5]
Meter=Image
H=30
W=30
SolidColor=00ffff
DynamicVariables=1
LeftMouseUpAction=[!SetVariable Example "#LMUA#"][!Log "[#Example]"]
RightMouseUpAction=[!SetVariable Example "#RMUA#"][!Log "[#Example]"]
MiddleMouseUpAction=[!SetVariable Example "#RMUA#"][!Log "#Example#"]
Code: Select all
function Index(k)
local a=string.gsub(k, '^%D+(%d+)$', '%1')
a = tonumber(a)
return a
end
First of all, the Windows version does not matter (at least I get the same behavior on Windows 7 SP1).death.crafter wrote: ↑June 30th, 2021, 6:18 am Rainmeter version info:
Rainmeter 4.4.0.3493 beta (64-bit)
Language: English (1033)
Build time: 2021-06-29 5:26:27
Windows 10[/11 preview if it matters] Home Single Language 2009 64-bit (build 22000) - English (1033)
Path: C:\Program Files\Rainmeter\
There is something going on with updating the variable. When RightMouseClickAction is triggered the log shows the right value of Example which is 10 in your skin, however, in the Skins tab of About window I don't see it declared. Maybe, because the nested variables are naturally dynamic, I suppose Rainmeter, dynamically, is able to log the value of [#Example] this way, even though I don't observe it declared in the About-Skins list of variables.
Ohh! I forgot to mention Update=-1. I guess it's not a bug then.Active Colors wrote: ↑June 30th, 2021, 9:10 am However! Your issue can be easily fixed once you, either, plug in [!Update] bang in the chain of bangs, or, set Update= to a positive integer. Then classic variable form #Example# will retrieve the "10" in the log.
Wait a second. Have you seen this message from Yincognito here? https://forum.rainmeter.net/viewtopic.php?f=14&t=37775#p192611death.crafter wrote: ↑June 30th, 2021, 9:25 am Ohh! I forgot to mention Update=-1. I guess it's not a bug then.
Anyway, did you check the real problem. The LeftMouseUpAction. It logs error for me. While RightMouseUpAction has the exact configuration and it logs right.
Screenshot 2021-06-30 145422.png
Yes I have seen it. And that works fine. But I am still getting errors when using Mouse actions. I don't exactly know why tho.Active Colors wrote: ↑June 30th, 2021, 9:33 am Wait a second. Have you seen this message from Yincognito here? https://forum.rainmeter.net/viewtopic.php?f=14&t=37775#p192611
I don't see your reply to that message.
Code: Select all
[Rainmeter]
Update=1000
AccurateText=1
[Lua]
Measure=Script
ScriptFile=#@#Scripts\String.lua
[Variables]
String=Meter5
LMUA=([&Lua:Index('[#*CURRENTSECTION*]')]*6)
RMUA=([&Lua:Index('[#*String*]')]*6)
[Meter5]
Meter=Image
H=#LMUA#
W=30
SolidColor=00ffff
DynamicVariables=1
LeftMouseUpAction=[!SetVariable Example "#LMUA#"][!Log "[#Example]"]
RightMouseUpAction=[!SetVariable Example "#RMUA#"][!Log "[#Example]"]
It reminds me that there was a problem with how bangs interpret escaped variables. I don't remember the exact thread though.death.crafter wrote: ↑June 30th, 2021, 9:45 am Yes I have seen it. And that works fine. But I am still getting errors when using Mouse actions. I don't exactly know why tho.
And I noticed it's not multiple CURRENTSECTIONs, single CURRENTSECTION doesn't work either.
When explicitly used with mouse actions.
Take this code for example. While RightMouseUpAction works right, Left doesn't. Let me change the topic of this thread.
death.crafter wrote: ↑June 30th, 2021, 9:45 am Yes I have seen it. And that works fine. But I am still getting errors when using Mouse actions. I don't exactly know why tho.
And I noticed it's not multiple CURRENTSECTIONs, single CURRENTSECTION doesn't work either.
When explicitly used with mouse actions.
Take this code for example. While RightMouseUpAction works right, Left doesn't. Let me change the topic of this thread.
ActiveColors is spot on IMHO, here is the thread that illustrates another case of this problem and Brian's answers below. That is why I said this:Active Colors wrote: ↑June 30th, 2021, 10:38 amIt reminds me that there was a problem with how bangs interpret escaped variables.
when verifying the new recent betas here. As far as I understood the matter, I'm not sure how this can be feasibly "fixed", since it's ingrained into how Rainmeter (and its parsing) works. It's not an easy horse to ride, this #CURRENTSECTION#...Yincognito wrote: ↑June 28th, 2021, 10:46 amWell, I tested it and, apart from the #*CURRENTSECTION*# quirks that already existed before and you know about, it all seems fine from my end.