I wanted to prompt another SdAskOptions dialog before the one i have currently in my installer and the problem I faced was the two options on the first dialog was added onto the second dialog. I scoured the web for an answer. A solution i found is to uncheck and unhide the feature items of the first SdAskOptions before showing the second options dialog. It worked but I am not satisfied. I wanted a more elegant solution. It turns out the problem is the way i created the script created feature set was not correct.
So how should a script-created feature set be properly created? Simple. Declare a string variable and initialize it.
STRING szREGION_SET;
.
.
szMyCustomFeature = “my_feature_set”;
Or declare a constant if the feature set scope is global.
#define szMyCustomFeature “CTFeatureSet”
Each feature set should be unique.
So what did i do wrong? On both instances of SdAskoptions initialization, my script created feature set is a string variable without value. My deduction might be wrong. I think since i did not initialize a string value for my feature set variable, I am actually creating a null string feature set and when I added items in the second function, i am actually adding it to this null string feature set.
