New answers tagged notification
1
Limiting the time for undoing actions limits also the undo feature to 'oops...' functionality only/mainly. It will not let user undo some actions they performed in past after getting some more information about whatever is related to this action, or the element the action was performed on. So having an endless undo feature is a value from user experience ...
4
Case 1: You do not have a timer and the notification stays till it is manually dismissed.
There is nothing wrong what-so-ever with this approach. You display a message for undoing and it stays till the user has read and consciously dismissed it. Great persistent feedback and lesser chance of missing it even if you are distracted somewhere for a while. The ...
1
I'd say avoid using error codes like "Cannot do this stuff properly error : 321 " I don't think users really care about the error code as much as the developers do, For the expert users you can put a little
"> Show details". Next thing would be to be precise and brief about the error . Also one glance at the title should tell what the error actually is .
...
0
In the UI, maintain an additional column for the items to display Delete Status. On delete, deleted records can be marked as "Successfully Deleted" and further selection for deletion not allowed. For failed records, this column should hold the reason for Failure. Color codification also can be applied to improve visibility.
2
So if I understood you correctly User by default may delete any item but sometimes can't do so because of system failures etc.
Here are some tips how to deal with the situations like that:
If all the items were deleted successfully just remove them from the UI; no further notifications and messages are required - the fact that user can no longer see the ...
0
One approach might be: If the user does not have authorization to delete some element, do not provide any way to select it for deletion. The exact way to represent this might depend upon the specific application.
2
One solution to overcome a hindrance is to make the hindrance disappear. If the user cannot perform an action then there is no need of a partial success message of any kind because there will be no failure.
Are you familiar with the Poka-Yoke technique ? It is has been formalized for industrial purpose but I think it can be helpful in your case.
...
2
The answer depends on the amount of data a refresh would require.
Small
If a user has already selected refresh, then they have already indicated their wish to have whatever it was refresh. So it makes sense that you refresh it when you are next able to, thus saving the user an additional button press.
The catch here is that you need to make sure that ...
Top 50 recent answers are included
