-
Notifications
You must be signed in to change notification settings - Fork 12
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
InflateException with 0.1.7 using AboutFragment #69
Comments
Yep, I can reproduce this - I failed to actually test the fragment functionality before releasing :P I have a hunch that this is caused by missing theme attrs - #62 could potentially resolve this by using a default theme in the fragment instead of inheriting the activity's. |
Alright, |
Yes, fixed now. But I noticed something else: attribouterFragment is scoped to ContextWrapper - any specific reason why? I think Context should be enough |
Evidently not, or this bug wouldn't have occurred. The ContextWrapper allows the fragment to inflate layouts with their own theme attrs, e.g. If you wish to change this, you can use |
But for the fragment use case you are not actually using the provided Context instance anywhere from what I can see in the Attribouter class. It is only used for the activity to start the activity. |
Oh, are you talking about the extension functions used to configure it? Yes, those could be rewritten; it ultimately has little impact on the usage, though. If you wanted to, you could just construct I'm not sure why |
Yes, was talking about the extension functions. I'm currently using the Attribouter(context) because of that. |
After updating from 0.1.6 I'm getting the following error:
Usage is like this (in another fragment):
The text was updated successfully, but these errors were encountered: