Menu

#348 Problem with EnumRegValue

2.0 Series
closed-fixed
nobody
Scripting (211)
5
2005-04-08
2005-04-07
No

Please correct me if I'm wrong:

EnumRegValue maybe has an error by design. The example
in NSIS documentation (2.06) shows that comparing the
result to "" can be used as abort criteria for the
loop. In reality those empty "registry variable names"
are allowed and regularly used. So a key where such a
"default value" is set will not be traversed by that
EnumRegValue-loop.

I don't know whether the empty variable name is always
the first one (last EnumRegValue parameter=0) in the loop.

I know that there probably is a workaround using
ReadRegStr and checking the error flag.

Discussion

  • Amir Szekely

    Amir Szekely - 2005-04-08
    • status: open --> closed-fixed
     
  • Amir Szekely

    Amir Szekely - 2005-04-08

    Logged In: YES
    user_id=584402

    Thanks, fixed. EnumRegValue now sets the error flag if the
    enumeration index is out of range. The documentation
    examples was updated to match the new stop criteria. The
    change is backward compatible because the output variable is
    still set to an empty string if there the enumeration index
    is out of range.

     

Log in to post a comment.