only caveat on this implementation is that the IntentFilter fields will get a own copy if they have the same registerAt value. but i think that should not be a big problem.

what i have thought about is adding some kind of class extending IntentFilter that has an constructor with two arrays for actions and dataSchemes that we don't have to use those fields.

eg.

private final IntentFilter intentFilter2_ = new IntentFilter();



intentFilter2_.addAction("org.androidannotations.ACTION_1");
getActivity().registerReceiver(onActionOnAttachReceiver_, intentFilter2_);

could become

getActivity().registerReceiver(onActionOnAttachReceiver_, new ExtendedIntentFilter(new String[] {"org.androidannotations.ACTION_1"}));

// or like this, but that would make the generation code more complex.
getActivity().registerReceiver(onActionOnAttachReceiver_, new ExtendedIntentFilter("org.androidannotations.ACTION_1"));

@yDelouis @WonderCsabo thoughts?

only caveat on this implementation is that the IntentFilter fields will get a own copy if they have the same registerAt value.

Can you add an example?

first let me start with a small correction. they get an own IntentFilter if they don't have the same registerAt value (but actions and schemes are the same).

the sample:
https://github.com/excilys/androidannotations/blob/develop/AndroidAnnotations/functional-test-1-5/src/main/java/org/androidannotations/test15/receiver/FragmentWithReceiver.java

before this change there was only one IntentFilter field as all Receiver had the same actions and dataSchemes (empty)

private final IntentFilter intentFilter1_ = new IntentFilter();

but after this change, also the registerAt is taken care of and that results in 4 such fields in this sample. this could more or less easily be changed to only 2 fields by modifying the hashCode and equals of the IntentFilterData class that was introduced with the dataSchemes update. but for now i decided to keep these function with a default/non specialized behaviour.

with the suggested helper class this issue could go away and we wont have any IntentFilter fields at all.

I am not sure we should add "new" API classes for this. We should keep the generated code understandable, e.g. using only plain Android code in it.

Please rebase this.

rebased.

Can you add a test?

yeah.

FInally merged, thanks!