-
Notifications
You must be signed in to change notification settings - Fork 208
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
Using Icepick without Annotation Processing? #81
Comments
I'd love to use kotlin too, but when you have Icepick a simple class as abstract class BaseFragment : Fragment() {
override fun onCreateView(inflater: LayoutInflater?, container: ViewGroup?, savedInstanceState: Bundle?): View? {
return super.onCreateView(inflater, container, savedInstanceState)
}
} fails to compile because of icepick processor.
not really sure tough if it's the kotlin processor or icepick. |
If you're not a fan of exposing your variables and using @JvmField, I've started a simple lib that should work as Icepick: https://github.com/tinsukE/icekick |
@tinsukE your lib works great! Thanks man! |
And here's another alternative. Same API like Icepick, but works well with properties: https://github.com/evernote/android-state |
Hi,
Is it possible to use Icepick without "@State" annotations? Can I manually add the objects I want to save? I would like to use Icepick with Kotlin but I cannot get it to work.
Thanks
The text was updated successfully, but these errors were encountered: