-
Notifications
You must be signed in to change notification settings - Fork 29
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
SpeedDialMenu not showing #2
Comments
This is due to the fact that the setOnClickListener() reset the adapter for no reason. |
Thanks for raising this. There is actually a good reason that the menu adapter is reset: as per Material Design specs, the FAB is intended to work as a standard button or as an access point for the speed-dial menu, but not both. Setting one option disables the other; this is alluded to in the README.md file, but it definitely could be clearer. I'm already planning to change the onClick listener to a more flexible callback interface, so I'll make sure that includes callbacks for the speed-dial menu opening and closing. |
Hi Mark, Here is my point :
What do you think ? |
I agree, mostly, with your points, and it's one of the main reasons I'm putting together the callback layer instead of the current system. It's the way it is right now because that's what supported my use cases when it was just a personal project. The new callback should be pushed in a couple of days when I get some time off. |
Thanks 👍 :) |
Fixed in release 1.2.0 👍 |
If a ClickListener is set to the FAB, the speedDialMenu doesn't show when clicked (otherwise it shows).
Cheers
The text was updated successfully, but these errors were encountered: