什么时候可以接受模态 UI? [英] When is modal UI acceptable?

问题描述

总的来说，模态界面会吸大石头.另一方面，我想不出更好的方法来处理 File Open... 或 Print...，我认为这是因为

By and large, modal interfaces suck big rocks. On the other hand, I can't think of a better way to handle File Open..., or Print... and this, I think, is because

• 它们是偶尔的动作，不频繁且重要，并且
• 它们本质上是原子的；您要么完成指定所有打印选项并完成它，要么取消整个节目.

让我们整理一些风格指南.建议对话是首选演示的任何用例以及首选的原因.对话框可以是非模态的吗?如果是，您如何标记事务边界，因为 Cancel 不再具有明确的含义.例如，您是否使用应用"按钮?

Let's put together a little style-guide. Suggest any use-cases in which a dialog is the preferred presentation and why it is preferred. Can the dialog be non-modal? If it is, how do you mark transactional boundaries, since Cancel ceases to have a clear meaning. Do you use an Apply button, for example?

推荐答案

IMO，模态界面应该只在你HAVE处理对话框正在做的事情时使用或在申请可以继续之前询问.任何其他时候，如果您使用对话框，它应该是非模态的.

IMO, modal interfaces should only be used when you HAVE to deal with whatever the dialog is doing or asking before the application can continue. Any other time, if you're using a dialog, it should be non-modal.

这篇关于什么时候可以接受模态 UI?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！