Skip to content
This repository was archived by the owner on Feb 26, 2023. It is now read-only.

Conversation

@WonderCsabo
Copy link
Member

Implements #1067.

@yDelouis i think this may be a breaking change, as clients could rely on the old behavior in their apps.

@WonderCsabo
Copy link
Member Author

@yDelouis do you agree?

@WonderCsabo WonderCsabo force-pushed the 1067_subclassCanOverrideOptionsItem branch from 537734b to f4cfed9 Compare March 22, 2015 16:26
Before this commit onOptionsItemSelected immediately returned if the
superclass handled the menu item. From now on, the super call is the
last one in the method, so subclasses can ovveride behavior.
@WonderCsabo WonderCsabo force-pushed the 1067_subclassCanOverrideOptionsItem branch from f4cfed9 to b662a2c Compare March 22, 2015 16:28
yDelouis added a commit that referenced this pull request Mar 23, 2015
…ionsItem

Allow subclasses to override @OptionsItem handling
@yDelouis yDelouis merged commit 0f65e00 into androidannotations:develop Mar 23, 2015
@yDelouis yDelouis added this to the 3.3 milestone Mar 23, 2015
@WonderCsabo WonderCsabo deleted the 1067_subclassCanOverrideOptionsItem branch March 24, 2015 13:17
@WonderCsabo
Copy link
Member Author

OK, so it is not a breaking change then. :)

@yDelouis
Copy link
Contributor

It's not mentioned in the doc. So we didn't changed the API but the internal implementation.
But we could move this to 4.0 if you think it's important.

@WonderCsabo
Copy link
Member Author

This is OK.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants