# Momentary Button, or similar **URL:** \ **Category:** Ignition\ **Tags:** perspective\ **Created:** [June 2, 2026, 4:54pm UTC](https://forum.inductiveautomation.com/t/momentary-button-or-similar/115806 "2026-06-02T16:54:32Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Orion\_Williams](https://avatars.discourse-cdn.com/v4/letter/o/df705f/32.png) [@Orion\_Williams](https://forum.inductiveautomation.com/u/Orion_Williams)\ **Post date:** [June 2, 2026, 4:54pm UTC](https://forum.inductiveautomation.com/t/momentary-button-or-similar/115806/1 "2026-06-02T16:54:32Z")
I'm new to Ignition, but not HMI/SCADA. I’ve created a reusable view and embedded it into another view with several Buttons that I’d like the operator to click to display different evaporators. I understand that I can use a Button component and dig into the onActionPerformed event to load a new value into my a PARAM to display that specific evaporator. But component events require too many clicks to quickly edit or view the value. A dropdown is too clunky for my liking here. Is there a way to bind a Button PROP or CUSTOM to a value that doesn’t require the component events? edit: Clarified "Button" PROP or CUSTOM. I want to do this with a Button or similar. I want to minimize events and scripts. ---
**Author:** ![dkhayes117](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dkhayes117/32/68344_2.png) [@dkhayes117](https://forum.inductiveautomation.com/u/dkhayes117)\ **Post date:** [June 2, 2026, 5:00pm UTC](https://forum.inductiveautomation.com/t/momentary-button-or-similar/115806/2 "2026-06-02T17:00:38Z")
I would use a dropdown with its value bi-directionally bound to a custom prop at the view level. Then bind your embedded view's param to the same custom prop. ---
**Author:** ![Orion\_Williams](https://avatars.discourse-cdn.com/v4/letter/o/df705f/32.png) [@Orion\_Williams](https://forum.inductiveautomation.com/u/Orion_Williams)\ **Post date:** [June 2, 2026, 5:03pm UTC](https://forum.inductiveautomation.com/t/momentary-button-or-similar/115806/3 "2026-06-02T17:03:16Z")
Unless I'm missing something, the dropdown solution would require 2 mouse clicks per selection. I'd like the operator to be able to just click the button corresponding to the evaporator they wish to select. ---
**Author:** ![dkhayes117](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dkhayes117/32/68344_2.png) [@dkhayes117](https://forum.inductiveautomation.com/u/dkhayes117)\ **Post date:** [June 2, 2026, 5:07pm UTC](https://forum.inductiveautomation.com/t/momentary-button-or-similar/115806/4 "2026-06-02T17:07:54Z")
Then you'll need a script, how else would the button do anything? A button for each evap would be far more clunkier IMO, since it will take up more UI space. If you need to add more Evaps, then add yet another button. ---
**Author:** ![dkhayes117](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dkhayes117/32/68344_2.png) [@dkhayes117](https://forum.inductiveautomation.com/u/dkhayes117)\ **Post date:** [June 2, 2026, 5:12pm UTC](https://forum.inductiveautomation.com/t/momentary-button-or-similar/115806/5 "2026-06-02T17:12:31Z")
You could use a table component where each row is a single column with your Evap ID. Then bind the embedded view's param to the selected row data on the table. This would act like a dropdown that is always expanded. ---
**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:** [June 2, 2026, 5:15pm UTC](https://forum.inductiveautomation.com/t/momentary-button-or-similar/115806/6 "2026-06-02T17:15:09Z")
~~Terrible topic title, FWIW.~~ Sadly, **not** a terrible title. ---
**Author:** ![Orion\_Williams](https://avatars.discourse-cdn.com/v4/letter/o/df705f/32.png) [@Orion\_Williams](https://forum.inductiveautomation.com/u/Orion_Williams)\ **Post date:** [June 2, 2026, 5:15pm UTC](https://forum.inductiveautomation.com/t/momentary-button-or-similar/115806/7 "2026-06-02T17:15:21Z")
Labview, AVEVA Edge, C-more HMI, CCW, etc. all manage button functions without the need to write a script. They take the "pressed" value and apply it to a boolean tag, pressed for 1, unpressed for 0. To view the assigned tag, you simply view the properties of the component, and you can rapidly click them with the properties open to view their assignments without drilling into dozens of potential events. I like your workaround idea with the table. Though I am stunned Ignition requires such ingenuity while seemingly every other HMI solution on the planet does this with simple buttons. ---
**Author:** ![Orion\_Williams](https://avatars.discourse-cdn.com/v4/letter/o/df705f/32.png) [@Orion\_Williams](https://forum.inductiveautomation.com/u/Orion_Williams)\ **Post date:** [June 2, 2026, 5:16pm UTC](https://forum.inductiveautomation.com/t/momentary-button-or-similar/115806/8 "2026-06-02T17:16:26Z")
I searched 10 topics or so using my terrible search terms and found nothing suitable. The title mattered less to me than you reading it. Job done. ---
**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:** [June 2, 2026, 5:17pm UTC](https://forum.inductiveautomation.com/t/momentary-button-or-similar/115806/9 "2026-06-02T17:17:03Z")
> [@Orion\_Williams](#): > > pressed for 1, unpressed for 0 Perspective very deliberately does not have this, as you cannot make it reliable in web browsers. (And difficult in most other cases.) Search this forum for "stuck momentary button" for many arguments and rants about the underlying causes. ---
**Author:** ![Orion\_Williams](https://avatars.discourse-cdn.com/v4/letter/o/df705f/32.png) [@Orion\_Williams](https://forum.inductiveautomation.com/u/Orion_Williams)\ **Post date:** [June 2, 2026, 5:18pm UTC](https://forum.inductiveautomation.com/t/momentary-button-or-similar/115806/10 "2026-06-02T17:18:11Z")
I would love the problem of a stuck momentary button. I can solve that. I'm just trying to figure out a regular momentary button for now. ---
**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:** [June 2, 2026, 5:18pm UTC](https://forum.inductiveautomation.com/t/momentary-button-or-similar/115806/11 "2026-06-02T17:18:53Z")
Perspective does not have one. And you won't be able to **reliably** fix it. ---
**Author:** ![lrose](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lrose/32/62724_2.png) [@lrose](https://forum.inductiveautomation.com/u/lrose)\ **Post date:** [June 2, 2026, 5:23pm UTC](https://forum.inductiveautomation.com/t/momentary-button-or-similar/115806/12 "2026-06-02T17:23:19Z")
> [@Orion\_Williams](#): > > Though I am stunned Ignition requires such ingenuity while seemingly every other HMI solution on the planet does this with simple buttons. Why not just use a Menu Tree? As long as you don't provide a Sub Menu, this is pretty much exactly what it is ment for. ---
**Author:** ![Orion\_Williams](https://avatars.discourse-cdn.com/v4/letter/o/df705f/32.png) [@Orion\_Williams](https://forum.inductiveautomation.com/u/Orion_Williams)\ **Post date:** [June 2, 2026, 5:23pm UTC](https://forum.inductiveautomation.com/t/momentary-button-or-similar/115806/13 "2026-06-02T17:23:43Z")
Got it. It's strange to me that what I'm trying to do doesn't even touch a PLC, but all the arguments against it seem to use a PLC or OPC server as the reasoning. I'm assuming also that there is no way to use a OneShotButton to accomplish this either... ---
**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:** [June 2, 2026, 5:26pm UTC](https://forum.inductiveautomation.com/t/momentary-button-or-similar/115806/14 "2026-06-02T17:26:03Z")
If you only care about setting a target tag/prop to a constant on one press, then the one-shot button is very likely exactly what you want. (I don't use it because I don't like its visuals.) ---
**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:** [June 2, 2026, 5:31pm UTC](https://forum.inductiveautomation.com/t/momentary-button-or-similar/115806/15 "2026-06-02T17:31:29Z")
> [@Orion\_Williams](#): > > doesn't even touch a PLC, but all the arguments against it seem to use a PLC or OPC server as the reasoning Ah, but the same fundamental comms problem (TCP/IP stalls/breakage) exists between the client UI and the gateway where props/tags are processed. The problem is more obvious in SCADA where there are **two** hops (client \<-\> gateway and gateway \<-\> PLC). ---
**Author:** ![smcfarlane](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/smcfarlane/32/42150_2.png) [@smcfarlane](https://forum.inductiveautomation.com/u/smcfarlane)\ **Post date:** [June 2, 2026, 6:26pm UTC](https://forum.inductiveautomation.com/t/momentary-button-or-similar/115806/16 "2026-06-02T18:26:16Z")
Perspective requires a slight shift in....perspective....when it comes to SCADA GUIs. It doesn't shine as a machine control solution. It can certainly act as one but you will have to figure out workarounds to some functions like youve discovered. What Ignition can't do compared to its competitors is a much shorter list than what it can do. If this functionality is critical for you then I would use Vision. ---
**Author:** ![jlandwerlen](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@jlandwerlen](https://forum.inductiveautomation.com/u/jlandwerlen)\ **Post date:** [June 2, 2026, 6:54pm UTC](https://forum.inductiveautomation.com/t/momentary-button-or-similar/115806/17 "2026-06-02T18:54:08Z")
You can build a momentary button, using mouse events, but be prepared for issues. ---
**Author:** ![Orion\_Williams](https://avatars.discourse-cdn.com/v4/letter/o/df705f/32.png) [@Orion\_Williams](https://forum.inductiveautomation.com/u/Orion_Williams)\ **Post date:** [June 2, 2026, 8:25pm UTC](https://forum.inductiveautomation.com/t/momentary-button-or-similar/115806/18 "2026-06-02T20:25:49Z")
IA believes in Perspective, and I'm trying to get on board. I'm also trying to learn by doing, so oftentimes, my question is not simply to find something that "works", but to figure out how things work. I'm sure Vision is more fitting for what I'm attempting to do, but I'm hoping the payoff is that I get a rapid education in Perspective. Trial by fire or something. 🙂 Thanks, all! ---
**Author:** ![Ryan\_Deardorff](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ryan_deardorff/32/63815_2.png) [@Ryan\_Deardorff](https://forum.inductiveautomation.com/u/Ryan_Deardorff)\ **Post date:** [June 2, 2026, 8:37pm UTC](https://forum.inductiveautomation.com/t/momentary-button-or-similar/115806/19 "2026-06-02T20:37:47Z")
> [@pturmel](#): > > I don't use it because I don't like its visuals I don't understand why it has the icon on the wrong side, but I fix that using CSS: ```python .psc-CSS\/OneShotButton { flex-direction: row-reverse !important; padding-left: 4px !important; padding-right: 8px !important; } ``` ---
**Author:** ![Nol](https://avatars.discourse-cdn.com/v4/letter/n/8e8cbc/32.png) [@Nol](https://forum.inductiveautomation.com/u/Nol)\ **Post date:** [June 2, 2026, 9:16pm UTC](https://forum.inductiveautomation.com/t/momentary-button-or-similar/115806/20 "2026-06-02T21:16:28Z")
> [@pturmel](#): > > Ah, but the same fundamental comms problem (TCP/IP stalls/breakage) exists between the client UI and the gateway where props/tags are processed. > > The problem is more obvious in SCADA where there are **two** hops (client \<-\> gateway and gateway \<-\> PLC). Yeah, been dealing with this recently due to a hiccup at a site. Operator writes a setpoint from tabletA but it doesn't go through because of cell network hiccup. Someone writes a different setpoint from tabletB and it goes through instantly. Later tabletA reconnects and overrides the setpoint even though it's value was sent first. In reality it's probably not a big deal as no one ever should be trying to do that but it raised a lot of questions of hypotheticals now I have to write up. [Next page](https://forum.inductiveautomation.com/t/momentary-button-or-similar/115806.md?page=2)