by Mizery_Made » Fri Feb 19, 2010 9:01 pm
That warning doesn't really protect from this potential data loss however. As if someone is dragging 50 files to the tree, they should know that it's going to modify them. The issue here was, the user forgot to hold CTRL, so they overwrote the data instead of appending. If CTRL isn't held down, a warning could be provided specifying "This action will replace (field) on # files. Do you want to continue?" so that someone has the opportunity to realize it will replace the genre for instance, instead of adding it. Maybe?
That warning doesn't really protect from this potential data loss however. As if someone is dragging 50 files to the tree, they should know that it's going to modify them. The issue here was, the user forgot to hold CTRL, so they overwrote the data instead of appending. If CTRL isn't held down, a warning could be provided specifying "This action will replace (field) on # files. Do you want to continue?" so that someone has the opportunity to realize it will [i]replace[/i] the genre for instance, instead of adding it. Maybe?