Kevin,
In the same routine which checks for your special version indicator, add
the default hot key assignment to the INI file. Once done, it should be
safe to register the hot keys.
Steve
On 5/20/2011 4:49 PM, Kevin Huber wrote:
Hi Steve:
I see your point, But, , if I have changed a hotkey in my script,
because, for instance, it conflicts with an existing Window-eyes
hotkey, then if someone downloaded and installed the script, that
change wouldn't take effect because the hotkey would already exist in
there version of the ".ini" file, so how would you get that new
hotkey to take effect?
Kevin Huber
On 5/20/11, Stephen Clower<[email protected]> wrote:
Kevin,
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
--
Stephen Clower
Product support specialist
GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825
260-489-3671 * gwmicro.com
