Personally I don't mind SmartSelect however I don't use it either. I perfectly understand why people want to have an option to completely shut it off. I'd think it would be fairly easy to add a shutoff option to SmartSelect. Build 4130 would be the same as 4128 except for 4130 would have that shutoff option of SmartSelect. Also, I'd think that shutoff option would be a priority of Parallels. Remember Parallels, no matter how sweet that your features are you always want to put an off option too. Because some people want to have a choice whether to use the features or not.
Stevamundo, IMHO it is not that good idea to release to public new build after each fix. When we fix most of the hot topic bugs we will prepare an update and release it to public.
And yet 3.0 was released with a lot of known bugs. Honestly, with all the bugs out there, I'd rather get a new build twice a week and go through the uninstall / reinstall hassles until the bugs all get worked out.
Yes Andrew, that's usually a good philosophy. However IMHO in this case, I think you ought to add that shutoff option to SmartSelect as soon as possible. BTW, you release 4128 after what three days of releasing 4124 for a BootCamp in Vista bug. IMHO this is more important than the BootCamp Vista bug.
