Kay J.

I think `@IgnoreWhen` is a good idea. this allows to be used on other methods than `@UiThread` too. e.g. networking callbacks

While I see the goal - knowing if an Activity or Fragment is newly created or recreated - as a valid request. I'm not sure if `@AfterViews` is a good...

There are like two kinds of annotations: - Those who tell AA that it should enhance a class (EActivity, EBean, EView, etc) - Those who tell AA HOW it should...

From what i have seen we either need a new annotation or a parameter to toggle usage of the RadioGroup listener as there is no way to detect the correct...

After an [attempt to support](https://github.com/androidannotations/androidannotations/pull/1937) both `RadioGroup` and `CompoundButton` with `@CheckedChange` we decided that it is better to create a new annotation for `RadioGroup`

@WonderCsabo think we should simply put a `@SuppressWarning` on the generated method. What do you think?

okay, have fun. :)

Not sure, but maybe we could just remove the cast for appcompat. iirc the cast is only there as appcompat required it when we implemented the `internalFindViewById` stuff.

As far as i know there is currently no (public) build-in method for checking this. and i'm not sure if making `BackgroundExecutor.hasSerialRunning(String serial)` public instead of private is a good...

Hey @Goutte, from reading the test it looks okay i think... but I'm not that deep into the multithreading "behind the scenes"... :D May @WonderCsabo and possibly even @rom1v (he...