# Pluto --- Function barrier

**URL:** <https://discourse.julialang.org/t/pluto-function-barrier/59736>\
**Category:** Tooling\
**Tags:** pluto\
**Created:** [April 21, 2021, 1:18pm UTC](https://discourse.julialang.org/t/pluto-function-barrier/59736 "2021-04-21T13:18:51Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![werpers](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/werpers/32/42610_2.png) [@werpers](https://discourse.julialang.org/u/werpers)\
**Post date:** [June 18, 2024, 7:43am UTC](https://discourse.julialang.org/t/pluto-function-barrier/59736/6 "2024-06-18T07:43:41Z")

</div>

While trying to solve a similar problem I found this thread: [PlutoUI: Trigger long computation only after user sets many parameters and confirms](https://discourse.julialang.org/t/plutoui-trigger-long-computation-only-after-user-sets-many-parameters-and-confirms/112475)

I liked the following:  
(each code block a Pluto cell)

```Julia
using PlutoUI

```

```Julia
parameters = (1,2,3)

```

```Julia
parameters; @bind trigger CheckBox(default=false)

```

```Julia
result = trigger ? sum(parameters) : nothing

```

This setup means that every time you change `parameters` the check box will be recreated unchecked, blocking the computation.

---

_[View the full topic](https://discourse.julialang.org/t/pluto-function-barrier/59736)._