# The missing Apply button press "trap"

**URL:** https://discourse.paraview.org/t/the-missing-apply-button-press-trap/15650
**Category:** Development
**Tags:** proposal
**Created:** [October 28, 2024, 4:42pm UTC](https://discourse.paraview.org/t/the-missing-apply-button-press-trap/15650 "2024-10-28T16:42:02Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![cobo](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/c/f17d59/32.png) [@cobo](https://discourse.paraview.org/u/cobo)
#### Post date: [October 28, 2024, 4:42pm UTC](https://discourse.paraview.org/t/the-missing-apply-button-press-trap/15650/1 "2024-10-28T16:42:02Z")

</div>

As an experienced user of ParaView, I press `Apply` in order to load a data file after choosing the proper reader - automatically. However, I had once more a support case with a less experienced customer - like I had it already several times before: You have some geometric object visible on the screen that was loaded from a file, but no way to attach any “filter” to it, like `Transform` or `Clip` or any other!

And only after some struggling also from my side I realized: The customer had not pressed the `Apply` button, but only the “eye” in the pipeline brower. With that it is possible to trigger loading the file as well and view the geometric object, only that it somehow is not “completed” yet - internally.

Since I do not know how all this is working internally, I cannot propose a proper solution. But somehow I assume that there must be one, and I could imagine many from a user’s point of view:

- Disable the “eye” as long as `Apply` was not pressed. Not really “friendly”, but at least a way to enforce pressing that button
- Or else, automatically trigger the `Apply` actions if the user presses the “eye”
- Or issue some message if the user presses the “eye” for an “unfinished” object
- Or whatever…

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [October 28, 2024, 4:47pm UTC](https://discourse.paraview.org/t/the-missing-apply-button-press-trap/15650/2 "2024-10-28T16:47:50Z")

</div>

All good suggestions.

[https://gitlab.kitware.com/paraview/paraview/-/issues/19476](https://gitlab.kitware.com/paraview/paraview/-/issues/19476)

---

<div class="post-metadata">

### Author: ![jpmorr](https://discourse.paraview.org/user_avatar/discourse.paraview.org/jpmorr/32/8745_2.png) [@jpmorr](https://discourse.paraview.org/u/jpmorr)
#### Post date: [October 29, 2024, 9:43am UTC](https://discourse.paraview.org/t/the-missing-apply-button-press-trap/15650/3 "2024-10-29T09:43:19Z")

</div>

As a relatively new user to paraview I’ve been caught out by this many times already where I couldn’t figure out how to apply a filter to some data I had loaded and set data variables for display already. Then accidentally clicking apply suddenly allowed access to the filters.

I’ve now mostly defaulted to hitting apply first but still occasionally forget and switch on data with the eye first. A little red exclamation beside the eye would help remind users filters are not yet available if the apply button has not been pressed.

Good that there is at least an issue tracking this!
