by ZvezdanD » Sat Aug 06, 2011 5:47 am
Peke wrote:Yes it is intended behavior and you are right.
That is irrational behavior which confuses users. The enabled state of the mentioned check box should not depend of the fact how the script is previously installed. If you don't want for users to install the same script in both locations, local and global folders, you should automatically uninstall the previous version from the one folder and install the new version in another folder, but not to leave that to users to do it manually. For example, if a user has installed script in the local folder and if he/she decide to install the new version of that script in the global folder, the program should uninstall it from the local folder automatically before the installation of the new version.
By the way, I have recommended such practice in every occasion, not only when user wants to install the script in different folder then the previous version, but always, even when someone wants to install it in the same folder. For example, I have the old version of the script with some menu options and I have the new version which have different menu options - during the installation the old menu options should be removed (hidden) from the menu and the new menu options should be added. Removing of the menu options is already implemented in the Uninstall.vbs and your program should execute that file from the previously installed version before you execute Install.vbs of the new version. However, you ignored my suggestion, so I need to do that uninstall step by myself.
[quote="Peke"]Yes it is intended behavior and you are right.[/quote]
That is irrational behavior which confuses users. The enabled state of the mentioned check box should not depend of the fact how the script is previously installed. If you don't want for users to install the same script in both locations, local and global folders, you should automatically uninstall the previous version from the one folder and install the new version in another folder, but not to leave that to users to do it manually. For example, if a user has installed script in the local folder and if he/she decide to install the new version of that script in the global folder, the program should uninstall it from the local folder automatically before the installation of the new version.
By the way, I have recommended such practice in every occasion, not only when user wants to install the script in different folder then the previous version, but always, even when someone wants to install it in the same folder. For example, I have the old version of the script with some menu options and I have the new version which have different menu options - during the installation the old menu options should be removed (hidden) from the menu and the new menu options should be added. Removing of the menu options is already implemented in the Uninstall.vbs and your program should execute that file from the previously installed version before you execute Install.vbs of the new version. However, you ignored my suggestion, so I need to do that uninstall step by myself.