[wpkg-users] [Bug 107] WPKG fails to check for equality of registry data

[bugzilla-daemon at bugzilla.wpkg.org]

http://bugzilla.wpkg.org/show_bug.cgi?id=107





--- Comment #1 from Rainer Meier <r.meier at wpkg.org>  2008-04-10 19:13:13 ---
Created an attachment (id=109)
 --> (http://bugzilla.wpkg.org/attachment.cgi?id=109)
Full package, fixed error en registry equality check for REG_DWORD values

I found that this error only appears if you try to read and compare the data of
REG_DWORD, REG_BINARY or REG_MULTI_SZ values. This happens due to the fact that
the used RegRead method returns string values usually - unfortunately it
returns Integer values in case of REG_DWORD and VBArray arrays in case of
REG_BINARY or REG_MULTI_SZ.

However I found a way to make use of this return values. Now it is even
possible to check for equality of REG_BINARY and REG_MULTI_SZ values. See
changes below.

Some other enhancements have been included within this update as well. Here's a
list of changes:

FIX: Fixed Bug 107. Registry equality checks throw an error in case of checked
     value is of type REG_DWORD or REG_BINARY. Now the values are converted to
     strings before comparing it to the 'value' attribute. REG_MULTI_SZ and
     REG_BINARY values are concatenated using newline characters. For
     REG_BINARY values each octett is converted to its decinal number
     representation. Examples:
     REG_MULTI_SZ = a
                    b
                    c
     value = "a
     b
     c"
     will match.
     REG_BINARY values will be converted to multiline string as well. Each
octett of the binary value
     is converted to its decimal representation.
     REG_BINARY = "11 22 33 44"
     value = "17
     34
     51
     68"
     will match.

MOD: Misleading/confusing info message about non-zero exit code (even if exit
     code was 0) changed from:
     Command '<cmd> returned non-zero exit code [<code>]. This exit code...
     to
     Command '<cmd>' returned exit code [<code>]. This exit code...
     The quoting has been fixed as well (see above).


-- 
Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.