Why are you using a TabbedComponent if you don’t want Tabs?
You can just add multiple components to your window (addChildComponent), and just set one visibile at time (setVisible) through whatever means of selection you want to use.
It was a suggestion by me on a previous thread in order to make a pages like UX flow.
TabbedComponent already implements switching of the tabs and the resizing.
Of course you are right, with a little bit of experience in JUCE it is trivial to roll your own without the TabbedButtonBar.
But for a head start simply set the tab bar to zero size:
tabbedComponent.setTabBarDepth (0);
I’m new, and it seemed like the right way…
you are correct about using a component this is exactly what im currently doing
Tnx, I have decided to use compenents and switch between them when needed. just to make sure im on the right path, I have a function that swaps between components in my editor, and im giving a pointer to that function for each compennt so each component can switch if a button is clicked inside of it. is there a better way
?
Looks good from a distance. Just make sure to use owning pointers if you decide to create the current tab on the spot or plain members if you have them all available in parallel.
1 Like