craigbrett17
commented
6 years ago craigbrett17[CodePlex]
Yes, if you could submit these as separate issues, that would be very much appreciated as we can then track each issue and assign it and such like.
I can comment on each issue individually once this has happend. Or I can put it here, but if you're going to split it out for us, it might be more tidy to have the comments relating to each issue with their issue.
Some great spots here though. Thanks!
tristandb[CodePlex]
This is an array of issues, so if you'd like it I submitted each as it's own, I'd be glad to.
As noted previously, CPU is an immense problem. Running BlindSpot, regardless of playing or not playing eats through my CPU until my fan is extremely loud. I'm running this on a MacBook with a VM, so I am not by all means on a low-end machine. Installing new versions of blind spot over older ones corrupts the user data that's stored in local/BlindSpot. You then have to delete all user files, delete the program folder and reinstall. BlindSpot does not create a registry entry to make it show up in windows installed programs. Thus, I have to manually go to program files and delete the BlindSpot directory, a process that isn't exactly friendly for a novice user. BlindSpot stores passwords in plaintext inside the user data directory. This is a huge security risk.
The following is more of a list of pet peeves I have with the program, and could maybe directed elsewhere: If you clear out the user information, blindspot does not regenerate your settings and user files. Thus, you get a libspotify error upon login, or the process launches but is entirely silent (have to kill in TaskMGR). There's no way to delete playlists or follow/unfollow artists. In the quotQubeyquot keyboard format, volume up and down still use alt+shift, not ctrl+windows. For JAWS users, this is potentially problematic since JFW utilizes this keystroke for table navigation.