-
Notifications
You must be signed in to change notification settings - Fork 129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TapThrough Functionality for TabBarController #118
Comments
Hello, any news to this? Checked #112 and seems that it is not fixed yet. Or would you recommend any workaround? |
Any updates? |
Husseinhj
added a commit
to Husseinhj/material-showcase-ios
that referenced
this issue
Aug 1, 2022
Created #158 pull request to support |
Hey there,
did not updated the code base so can’t really tell. Not sure if will
update any time soon as I went with different solution which is
sufficient for now.
S pozdravem / Best Regards
Petr Kahánek
On August 1, 2022, "dependabot[bot]" ***@***.***> wrote:
Any updates?
—
Reply to this email directly, view it on GitHub
<https://github.com/aromajoin/material-showcase-
ios/issues/118#issuecomment-1200759700>, or unsubscribe
<https://github.com/notifications/unsubscribe-
auth/AO3IG6E6XFTYAAKLY7RARSDVW5TXXANCNFSM4JKUPSSQ>.
You are receiving this because you commented.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am having a problem with the tapThrough functionality of the tabBar. Allowing tapThrough on a tabBar creates the following error:
"Directly modifying a tab bar managed by a tab bar controller is not allowed'
Here is the code I've used in the past to select a tabBar index:
self.tabBarController?.selectedIndex = 2
But here is the code in the MaterialShowcase.swift:
onTapThrough = { tabBar.selectedItem = tabBar.items?[itemIndex] }
I believe I need to pass the tabBarController and will need a new constructor to do so as discussed here: #112 (comment)
The text was updated successfully, but these errors were encountered: