# \[FEATURE-6423\] 'Confirm?' prop for the Perspective Multi-State Button

**URL:** <https://forum.inductiveautomation.com/t/feature-6423-confirm-prop-for-the-perspective-multi-state-button/62125>\
**Category:** Ignition\
**Tags:** perspective, vision\
**Created:** [July 20, 2022, 2:44pm UTC](https://forum.inductiveautomation.com/t/feature-6423-confirm-prop-for-the-perspective-multi-state-button/62125 "2022-07-20T14:44:37Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [August 5, 2022, 12:46am UTC](https://forum.inductiveautomation.com/t/feature-6423-confirm-prop-for-the-perspective-multi-state-button/62125/4 "2022-08-05T00:46:53Z")

</div>

Oy! I hope not. Confirmation popups are an anti-pattern. See this recent discussion (among many):

> [@Create Text Confirmation Instead of Click Confirmation](https://forum.inductiveautomation.com/t/create-text-confirmation-instead-of-click-confirmation/62423/2):
>
> You are battling human nature. You will lose. Consider not using a popup, instead using a time-limited “command mode” of some kind, specific to each screen that needs it. The command mode would enable the other relevant buttons, and would time out after a short idle period. This approach satisfies requirements for avoiding accidental button presses, without using a popup that becomes a rote action.

---

_[View the full topic](https://forum.inductiveautomation.com/t/feature-6423-confirm-prop-for-the-perspective-multi-state-button/62125)._