Isn't that more or less the same as using the #CURRENTSECTION# literal or direct inline Lua syntax (without any buffer, custom variables, and such) though?Active Colors wrote: ↑June 30th, 2021, 2:02 pmdeath.crafter,
Before this issue is fixed you can add one extra bang to MeterStyle and one extra "buffer" variable and have it working
It is currently April 20th, 2024, 2:58 am
[BUG?] in Multiple usage of #CURRENTSECTION#
-
- Rainmeter Sage
- Posts: 7128
- Joined: February 27th, 2015, 2:38 pm
- Location: Terra Yincognita
Re: [BUG?] in Multiple usage of #CURRENTSECTION#
-
- Moderator
- Posts: 1251
- Joined: February 16th, 2012, 3:32 am
- Location: Berlin, Germany
Re: [BUG?] in Multiple usage of #CURRENTSECTION#
But then death.crafter could use direct Inline Lua from the beginning?Yincognito wrote: ↑June 30th, 2021, 2:12 pm Isn't that more or less the same as using the #CURRENTSECTION# literal or direct inline Lua syntax (without any buffer, custom variables, and such) though?
It is the same thing as Inline Lua in a bang but also it is the same thing as death.crafter wanted to have it in a variable.
(And this looks much tidy in my opinion )
-
- Rainmeter Sage
- Posts: 7128
- Joined: February 27th, 2015, 2:38 pm
- Location: Terra Yincognita
Re: [BUG?] in Multiple usage of #CURRENTSECTION#
If you say so... character counting says otherwise. But anyway, it was just something I noticed, don't mind my view on it.Active Colors wrote: ↑June 30th, 2021, 2:20 pm Same thing as Inline Lua but without the Inline Lua in the bang sequence. This looks much tidy in my opinion
P.S. One other difference is that inline syntax always works, from what I could see.
-
- Rainmeter Sage
- Posts: 1399
- Joined: April 24th, 2021, 8:13 pm
Re: [BUG?] in Multiple usage of #CURRENTSECTION#
Okay now the variable parsing thing is going out of hands:
The normal variables are not even parsed. Right click to change between types.
Code: Select all
[Rainmeter]
Update=1000
AccurateText=1
[Variables]
String=Meter5
Type=0
Text00=#*CURRENTSECTION*#
Text01=[#*CURRENTSECTION*]
Text10=#*String*#
Text11=[#*String*]
[MeterStyle]
Text=[#Text0[#Type]]
Y=5R
AntiAlias=1
FontSize=14
SolidColor=00ffff
DynamicVariables=1
LeftMouseUpAction=[!Log "[#Text0[#Type]]"]
RightMouseUpAction=[!SetVariable Type "(1 - #Type#)"][!Update][!Redraw]
[MeterStyle2]
Text=[#Text1[#Type]]
Y=5R
AntiAlias=1
FontSize=14
SolidColor=00ffff
DynamicVariables=1
LeftMouseUpAction=[!Log "[#Text1[#Type]]"]
RightMouseUpAction=[!SetVariable Type "(1 - #Type#)"][!Update][!Redraw]
[Meter1]
Meter=String
MeterStyle=MeterStyle
[Meter2]
Meter=String
MeterStyle=MeterStyle2
You do not have the required permissions to view the files attached to this post.
Last edited by death.crafter on June 30th, 2021, 2:39 pm, edited 1 time in total.
from the Realm of Death
-
- Rainmeter Sage
- Posts: 1399
- Joined: April 24th, 2021, 8:13 pm
Re: [BUG?] in Multiple usage of #CURRENTSECTION#
Active Colors wrote: ↑June 30th, 2021, 2:20 pm But then death.crafter could use direct Inline Lua from the beginning?
It is the same thing as Inline Lua in a bang but also it is the same thing as death.crafter wanted to have it in a variable.
(And this looks much tidy in my opinion )
Thank you both for putting in your time and patience.Yincognito wrote: ↑June 30th, 2021, 2:12 pm Isn't that more or less the same as using the #CURRENTSECTION# literal or direct inline Lua syntax (without any buffer, custom variables, and such) though?
ActiveColors's way would be useful if I have a number of meter styles where a user wants to use a long long inline lua line as a mouse action. If you have a few and a rather short inline then you can go for literal implementation of the inline in MeterStyle.
from the Realm of Death
-
- Moderator
- Posts: 1251
- Joined: February 16th, 2012, 3:32 am
- Location: Berlin, Germany
Re: [BUG?] in Multiple usage of #CURRENTSECTION#
I understand you. For me, if you have multiple direct inline lua it will quickly become hard to read lines. It is quite subjective. For me this takes more time to work with something like this:Yincognito wrote: ↑June 30th, 2021, 2:25 pm If you say so... character counting says otherwise. But anyway, it was just something I noticed, don't mind my view on it.
You can further make my code from the previous message simpler:
Code: Select all
[Variables]
Buffer=Meter5
LMUA=([&Lua:Index('[#*Buffer*]')])
!Buffer=!SetVariable Buffer
[StyleMeter]
LeftMouseUpAction=[#!Buffer# #CURRENTSECTION#][!Update][!SetVariable Example "#LMUA#"][!Log "Example: [#Example] | LMUA: #LMUA#"]
You do not have the required permissions to view the files attached to this post.
-
- Rainmeter Sage
- Posts: 7128
- Joined: February 27th, 2015, 2:38 pm
- Location: Terra Yincognita
Re: [BUG?] in Multiple usage of #CURRENTSECTION#
It's the same issue as before: an escaped [#*CURRENTSECTION*] in a bang. Doesn't matter in how many nesting levels / variables you put it. It won't work.death.crafter wrote: ↑June 30th, 2021, 2:32 pmOkay now the variable parsing thing is going out of hands...
-
- Rainmeter Sage
- Posts: 7128
- Joined: February 27th, 2015, 2:38 pm
- Location: Terra Yincognita
Re: [BUG?] in Multiple usage of #CURRENTSECTION#
You're right. By the way, I might just use a tweaked version of your buffer variable to make the "old" direct #CURRENTSECTIONINDEX# work. Still weighing in which approach is easier.Active Colors wrote: ↑June 30th, 2021, 2:53 pmBut if you have multiple direct inline lua it will quickly become hard to read lines. It is quite subjective though. For me this takes more time to work with something like this [...]
You can further make my code from the previous message simpler [...]
-
- Rainmeter Sage
- Posts: 1399
- Joined: April 24th, 2021, 8:13 pm
Re: [BUG?] in Multiple usage of #CURRENTSECTION#
You think so? I beg to differ.Yincognito wrote: ↑June 30th, 2021, 2:56 pm It's the same issue as before: an escaped [#*CURRENTSECTION*] in a bang. Doesn't matter in how many nesting levels / variables you put it. It won't work.
While with
Code: Select all
[Variables]
Text=[#*CURRENTSECTION*]
[String]
Text=[#Text]
Code: Select all
[Variables]
Text=#*CURRENTSECTION*#
[String]
Text=[#Text]
And it's not used in a bang.
from the Realm of Death
-
- Moderator
- Posts: 1251
- Joined: February 16th, 2012, 3:32 am
- Location: Berlin, Germany
Re: [BUG?] in Multiple usage of #CURRENTSECTION#
Ah yeah, fair enough, this is unbeatableYincognito wrote: ↑June 30th, 2021, 2:25 pm P.S. One other difference is that inline syntax always works, from what I could see.
Off-topic: