Jake Wharton
Jake Wharton
They don't need to be in new modules. The Kotlin dependency can be marked as optional and we can hide the enclosing class from Java callers.
I would call `ButterKnife.bind` in both cases so that the extension is still usable for code generation from locations where you only have an `Activity` reference.
Seems like the solution is to create the listener as a local and then pass it to every view. This optimization would work for any listener.
Go for it On Thu, Sep 13, 2018 at 2:52 PM MONIKA-KUMAR-JETHANI < [email protected]> wrote: > @JakeWharton can I work on this? > > — > You are receiving this...
Can you provide a test case where this happens? On Tue, Oct 4, 2016 at 5:54 PM vimal-lamiv [email protected] wrote: > The post to enable again and set enabled to...
Without a supplied test case that I can use to apply a fix I have to investigate writing one myself which I'm not eager to do. Unless someone supplies a...
Only if you promise me you'll stop using Hungarian notation!
My biggest objection is that this would require specialization of a mechanism which is currently general. The reason those other listeners allow receiving the view is because their associated callback...
Each listener isn't implemented manually such that we can just magically add a parameter to just one of them. There's a generic listener annotation system where only the available arguments...
Is there a newer version that fixes this? Otherwise you should file a bug in the JavaParser project.