Yincognito wrote: ↑March 23rd, 2019, 12:02 am
The null character is indeed supported in a regex expression, but it is treated by many programming languages (including the C programming language that Rainmeter is written into, according to
this) as the end of the string. So it might not be a subject to a Rainmeter regex substitute, since it won't be a part of the actual string, but rather a string array separator in the
REG_MULTI_SZ type.
Yes.. what we don't know (maybe you've already tried it and
do know) is whether Rainmeter (or, more specifically, the Win32 API Rainmeter uses) will read the registry entry up to the first null and stop, or will it read in the entire buffer into memory, nulls and all. If the latter, then you won't be able to
see the strings after the first null, but they will be there and could be made available with a substitute to get rid of embedded nulls.
Either way, you CAN read a REG_MULTI_SZ registry entry using Rainmeter. It requires Powershell and a little command-line kung fu, but you could easily do it with a Command measure. One example:
Code: Select all
PS> Get-ItemProperty -Path "HKCU:\Software\Binary Fortress Software\DisplayFusion\Wallpaper\c01c88eb-b1af-446a-ba4c-d714a2c45fdd" | Select-Object -ExpandProperty Wallpaper_0_RotatePaths
That will dump out a list of strings you could then grab and parse however you like. With a little creativity, you can probably alternatively format the text as a single string joined together with a separator of your choice (e.g., "string1;string2;string3")