Quote:
Originally Posted by mdhuang
I understand Jon's concerns. It is dangerous for an average user to try the book delete hack without knowing the problem it could cause. However, I don't think removing it is a good choice since many people have found it useful. I personally don't use collections and don't know the percentage of people using it (maybe we can have a poll?).
But I do agree we should put a WARNING in the main window of the Hack Master. May be a "Dangerous!" label in red after the hack name in the checklist?
Another option is in the code, checking a book if it is in a collection before deleting it. Though I don't think that's even possible to implement.
|
My concerns are that we don't know what this hack is going to do besides get stuck in an endless loop when you try to delete a book in a collection. It's an unknown. It might do nothing and just need a cycle with the on/off switch. Might start eating other files. Who knows? Do you? Can you say it won't do something that would cause other issues? It's an unknown. That's the issue.