afonsocraposo/buttons_tabbar

Allow ButtonsTabBar to take the whole width in case of no scroll

realitymolder opened this issue · 6 comments

realitymolder commented

Bug Report

Description

When the list is short and not scrollable, ButtonsTabBar isn't taking the whole horizontal space of the screen. I would suggest having a boolean that will help us achieve it.

Example:

image

afonsocraposo commented

Hey @realitymolder !
What do you mean? Do you mean that the buttons should expand to fill the whole horizontal space of the screen?

  • 👍1
realitymolder commented

Hey @realitymolder ! What do you mean? Do you mean that the buttons should expand to fill the whole horizontal space of the screen?

Hey there, yes! Maybe as a flag (bool) we can have this feature that as long as the list isn't scrolling (beyond the size of the screen) it should stretch each button. Like here:
as you can see there are 2 items, so it divides each item to 50% of the screen.
Sorry for the bad UI in the example! lol
telegram-cloud-photo-size-4-5864223375751233512-x

afonsocraposo commented

Hey @realitymolder! I understand now.
I'm sorry, but I won't implement this feature, since it doesn't align with the purpose of this package.
I hope you can understand 🙏🏻

dipu0 commented

there is two button and i want to fill screen width with btns but here i cannot!
@afonsocraposo there should a option for non-scroll btns to take equal space in the screens

  • 👍1
afonsocraposo commented

Hi @dipu0 !
Thank you for sharing your interest in this package. I'm sorry, but, as I mentioned above, this feature doesn't align with the purpose of this package

dipu0 commented

Hi @dipu0 !
Thank you for sharing your interest in this package. I'm sorry, but, as I mentioned above, this feature doesn't align with the purpose of this package

But when using two or three buttons and no scroll, there should be an option to expand and take the full screen width. I am using both scroll (multiple buttons with scroll) and only three with no scroll. Now I need another feature that will examine two buttons. I don't know why this isn't aligned with your purpose! And it is too disappointing that you are not willing to extend a feature that requires multiple users. And now I'm afraid of using this in the production level app.