7.2.0 Buglist...

[AlBundy33]

Started a new thread on reg keys paths.

Ok

Args:

options="options.js"

config="config.js"

check="default"

timer=30

theme="Windows"

resolution=1200

Thanks

Quotes are only needed if there is a space. There was a quotes bug, it is fixed but not uploaded yet.

Sure - but in my batch file I call wpi.hta with

"%WINDIR%\system32\mshta.exe" "!CD!\wpi.hta" config="!CD!\WPIScripts\config.js" options="!CD!\WPIScripts\useroptions.js" %*

and therefore I need the quotes because I don't know where WPI is started from.

[GrowBigTrees]

Everything I have always gotten as a return/check value is binary. You could try RegKeyValue(...)=="0x00000019" which is 25 binary. The binary equivilant is in parenthesis (25) next to the hex value.

Don't use quotes when checking a number.

None of the following tests work for a REG_DWORD with value 1:

gcond[pn]=['RegKeyValue("HKEY_CURRENT_USER\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\Explorer\\NoRecentDocsNetHood")==0x00000001'];

gcond[pn]=['RegKeyValue("HKEY_CURRENT_USER\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\Explorer\\NoRecentDocsNetHood")=="0x00000001"'];

gcond[pn]=['RegKeyValue("HKEY_CURRENT_USER\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\Explorer\\NoRecentDocsNetHood")==1'];

[mritter]

@GrowBigTrees: It works fine for me. Your third example is how you want to do it.

Are you sure the key exists? It doesn't for me.

[GrowBigTrees]

SOLVED!

Yes it existed, but with an extra space at the end of the value name. Thanks a lot !

[Kelsenellenelvian]

7.3.0 released here...