First of all I would like to say thx for this great piece of software.
Now the question
Since I got my hands on Rainmeter I had the idea of creating a Profile skin for my G19 Keyboard. I have tons of profiles and is not that easy to remeber what goes where, so I messed around with the app and did some skins to get used to it.
Since I had no clue about lua I used your links to manuals, lua skins, etc.
Now i'm stuck on something quite stupid but just cant figure how to solve it.
Code: Select all
[MeasureProfiles]
Measure=Plugin
Plugin=Plugins\WebParser.dll
Url="file://C:\Users\caronte\AppData\Local\Logitech\G-series Software\Keyboard\Profiles\{F1584FF0-AC67-40D5-B1BC-3F0347083B4D}.lgp"
RegExp="(.*)"
Debug=2
Debug2File=#CURRENTPATH#profiles.txt
UpdateRate=55
FinishAction=!RainmeterEnableMeasure g19ProfilesXML #CURRENTCONFIG#
[g19ProfilesXML]
Measure=Script
ScriptFile="#CURRENTPATH#g19_profiles.lua"
TableName=g19_LUA_PROFILES
FileToParse="#CURRENTPATH#profiles.txt"
ShiftState=#MKey#
UpdateDivider=60
Disabled=1
DinamycVariables=1
[M3_key]
Meter=Image
ImageName=#M3_img#
X=250
Y=0
DinamycVariables=1
LeftMouseUpAction=!Execute [!RainmeterHideMeter M1_key_on][!RainmeterShowMeter M1_key][!RainmeterHideMeter M2_key_on][!RainmeterShowMeter M2_key][!RainmeterHideMeter M3_key][!RainmeterShowMeter M3_key_on][!RainmeterSetVariable Mkey 3][!RainmeterUpdateMeasure g19ProfilesXML #CURRENTCONFIG#][!RainmeterUpdateMeter Macro0 #CURRENTCONFIG#]
The first measure parses the whole xml profile and enables the lua script. There i grab the parts i need and show them (so far works perfectly), but since there are 3 posible configurations for the same keys on each profile (the key binding switches when u select the M1, M2 or M3 configuration) i want to be able to see the assigned keys for those Mkeys.
The variable update works like a charm but the Macros don't update.
I used a string meter to verfy that the Mkey variable updates and it does.
Either the lua script doesn't update or the Macros string don't do it.
PS: Just tryed with RainmeterUpdateMeterGroup but to no avail either.