Opened 2 years ago
Closed 2 years ago
#1487641 closed Feature Requests (fixed)
Can the new Move confirm dialog be disabled?
| Reported by: | aberglund | Owned by: | |
|---|---|---|---|
| Priority: | 5 | Milestone: | 0.5-stable |
| Component: | User Interface | Version: | 0.5-beta |
| Severity: | normal | Keywords: | |
| Cc: |
Description
I installed today's 0.5-rc release for testing, and already have a question. One of the new features in the Changelog is "Add 'loading' message on message move/copy/delete/mark actions"
Well, I've already got three complaints on this from my testing team. While it's OK for most users, I have users who delete multiple consecutive messages by highlighting the first one, and then clicking "Delete" multiple times until the batch is gone. (They have "After message delete/move display the next message" as True.) While this method works fine in 0.4.2, the "Loading..." dialogs start to stack up quickly in 0.5-rc and after two or three clicks they cover the Delete button and the user has to wait for the dialogs to clear before proceeding.
So I'm wondering if any thought has been given to making these new dialogs a preference that could be enabled/disabled? While making it a per-user setting would be ideal, I could live with just having the ability to turn it off globally in the main.config.php if that would be easier.
Change History (5)
comment:1 Changed 2 years ago by alec
- Component changed from Core functionality to User Interface
comment:2 Changed 2 years ago by thomasb
- Milestone changed from later to 0.5-stable
It's hard to the user...
Maybe we should limit the number of concurrently displayed messages.
comment:3 Changed 2 years ago by alec
And hide the oldest without waiting for timeout? Maybe. Of course, we shouldn't hide 'loading' messages.
comment:4 Changed 2 years ago by aberglund
This is really only a problem for deletes, as the other operations require more than one click anyway. So only delete operations are an issue.
Limiting concurrent messages sounds like a possibility, as long as the delete confirmation is not modal and the user can continue to work. But if the dialog prevents the user from the next message deletion, it's not much better than the current solution. It appears to me that - since I can get at least two dialogs stacked - the current dialogs are not modal, and limiting concurrent dialogs might work.
comment:5 Changed 2 years ago by thomasb
- Resolution set to fixed
- Status changed from new to closed
The same message shall only be displayed once. Changed behavior in [b37e6987]. That should also solve this issue. However, messages (except loading) can be hidden at any time by clicking on them.
Current solution is better for performance, so it would be better when users will lern to select many messages and then do action on them. -1 from me.