You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The way the code is currently written, if you show a toast, it will always be completely opaque -- the alpha is always 1.
Originally, I thought passing in the alpha value might be a good way to do it, but there are some other values that might be nice to configure (basically, many of the static const values). It might be nice to add support to customize these values.
I thought of a few ways this could be done. The easiest might be to read from UserDefaults to see if there is a value to use instead of the hardcoded value. If not, it uses the original value.
The text was updated successfully, but these errors were encountered:
I've thought about doing this, but I don't like the complexity it adds. There are more robust Toast-like libraries out there if people need more runtime customization. That being said, it should be easy enough to fork and add if someone really wants these features at runtime.
The way the code is currently written, if you show a toast, it will always be completely opaque -- the alpha is always 1.
Originally, I thought passing in the alpha value might be a good way to do it, but there are some other values that might be nice to configure (basically, many of the
static const
values). It might be nice to add support to customize these values.I thought of a few ways this could be done. The easiest might be to read from UserDefaults to see if there is a value to use instead of the hardcoded value. If not, it uses the original value.
The text was updated successfully, but these errors were encountered: