The GW-Scripting list is a discussion list for information regarding the development and use of Window-Eyes scripts. Any subscriber of the GW-Scripting list has the ability to post on-topic messages.
From:
Stephen ClowerSubject:
Re:Date:
Fri, May 20, 2011 3:41:12 pmKevin,
By including an INI file with your package, you're forceably erasing any
customizations the user might have made to your app. A better approach
would be to test for a specific setting that isn't in the older INI
file, and if it doesn't exist, add it.
Regards,
Steve
On 5/20/2011 3:36 PM, Kevin Huber wrote:
--
Stephen Clower
Product support specialist
GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825
260-489-3671 * gwmicro.com
By including an INI file with your package, you're forceably erasing any
customizations the user might have made to your app. A better approach
would be to test for a specific setting that isn't in the older INI
file, and if it doesn't exist, add it.
Regards,
Steve
On 5/20/2011 3:36 PM, Kevin Huber wrote:
Hi Chip:
I just finished listening to the archive of Scripting Class 10, and I
want to comment on a point that you made when you were speaking about
packaging scripts.
You mentioned that the ".ini" file does not need to be included in the package.
I always include it when I am updating one of my scripts because if I
didn't, then someone might install the update and have an older
version of the ".ini" file in their default folder, which would not
allow the script to work properly. Am I wrong on this?
Kevin Huber
--
Stephen Clower
Product support specialist
GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825
260-489-3671 * gwmicro.com
