[wpkg-users] [Bug 79] Major WPKG enhancements, remote logging, doc, internal restructuring

[bugzilla-daemon at bugzilla.wpkg.org]

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


Rainer Meier <skybeam at users.sourceforge.net> changed:

           What    |Removed                     |Added

  Attachment #48 is|0                           |1
           obsolete|                            |




--- Comment #15 from Rainer Meier <skybeam at users.sourceforge.net>  2007-11-06 22:07:27 ---
Created an attachment (id=50)
 --> (http://bugzilla.wpkg.org/attachment.cgi?id=50)
Fixed config.xml remote-path problem, fixed registry read

As I can see my changes might be appreciated here I went forward and fixed some
smaller issues...

This update includes the following changes:

 * FIX: Change for optional config.xml has broken config file reading in case
 *      config.xml was not stored directly within the current working folder.
 *      The code has been altered now to search for config.xml within the
 *      directory where wpkg.js is called from. So if you execute the script
 *      by using '\\server\share\wpkg.js' it looks for
 *      '\\server\share\confix.xml'. Still if it does not exist it is silently
 *      ignored and default values are used.
 * FIX: Implemented fix for Bug 12 - getRegistryValue() returns the key default
 *      value if a path to a key is specified. If the "(default)" entry is not
 *      set it returns an empty string (""). Still returns null in case no such
 *      registry entry could be located (neither key nor value).
 * MOD: Added some more debug output.

NOTE: Bug 12 reports a problem that registry keys (not values) cannot be used
within the check conditions since it always returns null (not existing). I
fixed that now. So I propose to close Bug 12 in case my re-design is accepted.

About config.xml. There is a bug within 0.9.12-test3 that config.xml is nonly
read if the script is executed within the same directory (config.xml exists
within working directory). In case of remote-execution (e.g.
\\server\share\wpkg.js) the script file cannot be found. Some people might not
have recognized this since test3 was designed to work with default values even
if config.xml does not exist (exactly like my modification). This has been
fixed now.


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


wpkg-users mailing list
wpkg-users at lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users