# Make "Button" and "Button Bar" interchangeable

**URL:** <https://community.glideapps.com/t/make-button-and-button-bar-interchangeable/22377>\
**Category:** Feature Requests\
**Created:** [February 7, 2021, 6:41pm UTC](https://community.glideapps.com/t/make-button-and-button-bar-interchangeable/22377 "2021-02-07T18:41:54Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![Travis](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/travis/32/4339_2.png) [@Travis](https://community.glideapps.com/u/Travis)\
**Post date:** [February 7, 2021, 6:41pm UTC](https://community.glideapps.com/t/make-button-and-button-bar-interchangeable/22377/1 "2021-02-07T18:41:54Z")

</div>

Would be amazing to turn a button into a button bar. Doing so would prompt a selection to make the current button the left or right (or if not possible to prompt, left by default).

As well as the ability to turn a button bar into a button. Ideally a prompt of which button to keep would be nice. OR it just turns the button bar into two button components (ideal).

---

<div class="post-metadata">

**Author:** ![Jacktools\_Net](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jacktools_net/32/18500_2.png) [@Jacktools\_Net](https://community.glideapps.com/u/Jacktools_Net)\
**Post date:** [February 7, 2021, 9:58pm UTC](https://community.glideapps.com/t/make-button-and-button-bar-interchangeable/22377/2 "2021-02-07T21:58:19Z")

</div>

You can do this with visibility and custom actions.

Ok you will have some buttons and button bars on your tab. But… Who cares 😉

---

<div class="post-metadata">

**Author:** ![Pablo\_books](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/pablo_books/32/2110_2.png) [@Pablo\_books](https://community.glideapps.com/u/Pablo_books)\
**Post date:** [February 7, 2021, 10:14pm UTC](https://community.glideapps.com/t/make-button-and-button-bar-interchangeable/22377/3 "2021-02-07T22:14:48Z")

</div>

@Jacktools_Net

Button and Button bar are two separate components.

@Travis  
This will be possible very soon once compound actions are resuable!

---

<div class="post-metadata">

**Author:** ![Travis](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/travis/32/4339_2.png) [@Travis](https://community.glideapps.com/u/Travis)\
**Post date:** [February 7, 2021, 10:17pm UTC](https://community.glideapps.com/t/make-button-and-button-bar-interchangeable/22377/4 "2021-02-07T22:17:13Z")

</div>

Not for the user end, for our end as developers. Example:

 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/d/2/d2626c690b7ccff87ececfa09fa2b15a4ff0101b.png)

Above I created the “Add a pokemon.” button awhile back. Its has a lot of complexity to it and would be annoying to recreate. Later on, I decided to add three more buttons. Aesthetically, it would be nice to combine “Add a pokemon.” and “View My Pokemon” into a button bar.

---

<div class="post-metadata">

**Author:** ![Travis](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/travis/32/4339_2.png) [@Travis](https://community.glideapps.com/u/Travis)\
**Post date:** [February 7, 2021, 10:19pm UTC](https://community.glideapps.com/t/make-button-and-button-bar-interchangeable/22377/5 "2021-02-07T22:19:39Z")

</div>

This will solve a lot. 🙂 Though the added functionally in case your buttons do not use a compound action would be nice. Especially in cases where you have already built a link to screen that has a lot of time invested into different components.

But yes! Moving forward with reusable compound actions it would be smarter to create those cases in compound actions.

---

<div class="post-metadata">

**Author:** ![everys](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/everys/32/10724_2.png) [@everys](https://community.glideapps.com/u/everys)\
**Post date:** [February 8, 2021, 1:20am UTC](https://community.glideapps.com/t/make-button-and-button-bar-interchangeable/22377/6 "2021-02-08T01:20:58Z")

</div>

You can do that by setting the visibility condition for those button individually.

- one can be seen when “relation to pokemon table is empty”
- other button can be seen when “relation to pokemon table is Not empty.”

I think single component with single setting concept is already perfect to get things done rather than lots of logics/switchings in one component. So i think it’s fine for how it goes around here like this at the moment.

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [February 8, 2021, 2:15am UTC](https://community.glideapps.com/t/make-button-and-button-bar-interchangeable/22377/7 "2021-02-08T02:15:13Z")

</div>

> [@Travis](#):
>
> Above I created the “Add a pokemon.” button awhile back. Its has a lot of complexity to it and would be annoying to recreate. Later on, I decided to add three more buttons. Aesthetically, it would be nice to combine “Add a pokemon.” and “View My Pokemon” into a button bar.

Yes, agreed.  
I have several similar situations where I’d like to replace two individual buttons with a single button bar, but I’ve avoided it because it’s a hassle to re-create the associated actions.

---

<div class="post-metadata">

**Author:** ![Drearystate](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/drearystate/32/49605_2.png) [@Drearystate](https://community.glideapps.com/u/Drearystate)\
**Post date:** [February 8, 2021, 7:23pm UTC](https://community.glideapps.com/t/make-button-and-button-bar-interchangeable/22377/8 "2021-02-08T19:23:58Z")

</div>

What they mean is use both and allow data to determine which is visible.

---

<div class="post-metadata">

**Author:** ![Drearystate](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/drearystate/32/49605_2.png) [@Drearystate](https://community.glideapps.com/u/Drearystate)\
**Post date:** [February 8, 2021, 7:25pm UTC](https://community.glideapps.com/t/make-button-and-button-bar-interchangeable/22377/9 "2021-02-08T19:25:51Z")

</div>

With that many buttons I would make a inline list and set every item to Independent screen configuration so I could customize the buttons, get them together and make my own custom button for each one.

 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/c/7/c72d8c7334e3ab84d142bae1dbc7c6313dbeb996.jpeg)

Kind of like this. The ondeck system in this app thats used for 3 locations has their own custom buttons and tie in well with the scheme.

---

<div class="post-metadata">

**Author:** ![Travis](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/travis/32/4339_2.png) [@Travis](https://community.glideapps.com/u/Travis)\
**Post date:** [February 9, 2021, 1:06am UTC](https://community.glideapps.com/t/make-button-and-button-bar-interchangeable/22377/10 "2021-02-09T01:06:09Z")

</div>

Your design is nice, I like the three style “buttons” with an inline line! I can see how this would be easier to manipulate into one, two, four, or more buttons. Instead of independent screen configuration, you could create an action and use if statements to make it even more versatile. It will scale really well once you can reuse actions.

This solution still does not solve what I have an issue with, though.

---

<div class="post-metadata">

**Author:** ![Robert\_Petitto](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/robert_petitto/32/25193_2.png) [@Robert\_Petitto](https://community.glideapps.com/u/Robert_Petitto)\
**Post date:** [February 9, 2021, 1:19am UTC](https://community.glideapps.com/t/make-button-and-button-bar-interchangeable/22377/11 "2021-02-09T01:19:29Z")

</div>

> [@Travis](#):
>
> Its has a lot of complexity to it and would be annoying to recreate.

> [@Travis](#):
>
> Especially in cases where you have already built a link to screen that has a lot of time invested into different components

> [@Darren\_Murphy](#):
>
> I’ve avoided it because it’s a hassle to re-create the associated actions.

Agreed!!! Know what we need? A way to save our Link to Screen layouts!

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [February 9, 2021, 1:55am UTC](https://community.glideapps.com/t/make-button-and-button-bar-interchangeable/22377/12 "2021-02-09T01:55:55Z")

</div>

@Travis I can see that some people have misunderstood your feature request. Maybe consider re-titling it for better clarity? Something like “Make Buttons & Button Bar Interchangeable” might be clearer?

---

<div class="post-metadata">

**Author:** ![Drearystate](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/drearystate/32/49605_2.png) [@Drearystate](https://community.glideapps.com/u/Drearystate)\
**Post date:** [February 9, 2021, 3:05pm UTC](https://community.glideapps.com/t/make-button-and-button-bar-interchangeable/22377/13 "2021-02-09T15:05:13Z")

</div>

Yes, if we actually had a list of saved screens and saved compound actions.
