Im trying to add a button so it only appears on one specific tab, and that tab is also a hidden tab.
ANy suggestion to go about this, or try something different to reach the same objective.
thank you all!
Tabs are individually designed already, so I’m not quite understanding how you are getting duplicate buttons on every tab.
Also, tabs that are hidden are not accessible through the app. How are you getting to a hidden tab in the first place?
Screenshots might help.
1 Like
than k you for ur reply.
I am trying to add a button to screen ‘A’ for it to appear only on that specific screen A. The button is linked to tab M (which is hidden).
What happens now is that when i add the button it appears across all the related screens.
I’m still not clear. Are we talking about screens or tabs?
im sending u a picture of what im trying to say:
im tryng to link on the go button with ‘mareas’ but only that this buttong shows on this specific screen ‘camaron’.
thank u for your help.
I could be wrong, but I’m almost positive that you can’t use the ‘Navigate to Tab’ action to navigate to a tab that is marked as hidden. You would be better off using a ‘Show New Screen’ action.
1 Like
ok will try with show new tab. thank u
although if i use ‘show new scree’ how would i go about for it only to show on this ‘camaron’ specific screen?
How do you get to that screen? If it’s at the top level of a tab, then it should only be on that tab as each tab is designed independently. If you are navigating through an inline list, then you have a couple of options, but first I want to understand how to got to that Camaron screen.
1 Like
You can turn on ‘Independent Screen Configuration’ for your list, which will allow you to design the details for each list item independently…but you will have to do it for each and every list item, including new list items if any are added. If most of your screens are similar except for the button, then I’d suggest the option below.
There is another option to just set the visibility conditions on the button itself. You can can set the condition to only show the button if a column in your table IS Camaron.
3 Likes
option 2 makes total sense! thank u will try it
1 Like
Detail screen layouts become attached to the table when navigating through a list, so that they remain consistent throughout the app. The exceptions are when you are at the top level of a tab or a ‘show new screen’…or if you use independent screen configuration.
1 Like
thank you so verrrrry much, it worked! been weeks trying to figure this out. great work
1 Like
But wouldn’t that be neat!?
I’m pretty neutral on it I guess. I think I’d prefer re-using Screens as opposed to trying to use hidden Tabs. I understand that it may be convenient for those that may have put the work into building a tab, only to hide it, with no way to navigate to it. It seems counterintuitive to put the work into building a tab, only to click on the hide button.
For myself, I don’t build tabs that I don’t plan to use. I build screens instead. Kind of a hard concept to grasp for new glide users who are still learning the ins and outs of Glide, but I feel that ‘Show New Screen’ is better in the long run. Tabs are purpose driven to be visible tabs accessible via the tab bar or the side menu. Screens are purpose driven to be called as an action, and virtually unlimited as far as the number of screens you can create.
3 Likes
Well, yes, if you think of tabs as menu options. Re-using screens is probably what everyone who’s ever tried that hack is trying to do. It’s weird (in my opinion), that when you create a new screen using an action, you can’t ever re-use it, not even on the same table, and if the tie is accidentally broken for some reason (yes, I’ve had it happen), you have to re-build the screen from scratch.
1 Like