Page MenuHome

Asher (mindsize)
User

Projects

User does not belong to any projects.

User Details

User Since
Tue, May 4, 3:49 AM (1 w, 13 h)

Recent Activity

Wed, May 5

Asher (mindsize) added a comment to D10955: UI Experiment: Operator Confirmation.

@Asher (mindsize) - It's always a struggle leading with design and the existing infrastructure. Thank you for the context.

No worries, and don't take my comment as negative. If we really needed to we could add an operator callback specifically to override or customize the text used in confirmations. So we could get "Delete Selected Lights?" if desired. But I doubt I would get far with that since confirmations aren't used often and we generally design to avoid them.

Wed, May 5, 5:42 AM · User Interface

Tue, May 4

Asher (mindsize) added a comment to D10955: UI Experiment: Operator Confirmation.

@Asher (mindsize), generally the issue is dealing with the hand you are dealt. Operators only have two text descriptions, one long and the other short. The short one can quite often be too long for a button, not be phrased correctly, or otherwise cannot be used as button text. A confirmation like this one has to be generic, meant to optionally confirm any operator so there just isn’t the option to hand-craft it.

Tue, May 4, 3:13 PM · User Interface
Asher (mindsize) added a watcher for User Interface: Asher (mindsize).
Tue, May 4, 4:28 AM
Asher (mindsize) added a comment to D10955: UI Experiment: Operator Confirmation.

To me it seems important to have this rather harmless confirmation prompt look drastically different from ones like the quit confirmation prompt, where you might not be able to undo (e.g. auto save turned off or not working because of sculpt mode, or using Linux where the quit.blend is stored in /tmp/- which is another stupid thing...). This is a popup that may often appear during normal work and should be small and unobtrusive (if there is one at all), confirmation prompts to avoid data-loss -- or even just the moment where the user thinks there was some data-loss -- can well be intrusive. They interrupt the user intentionally and want to make them think.

While I think a better visual design for this would be good, I'd not suggest going the proposed direction.

Tue, May 4, 4:23 AM · User Interface