Title: Order of calling @AfterViews annotated methods from super classes · Issue #810 · androidannotations/androidannotations · GitHub
Open Graph Title: Order of calling @AfterViews annotated methods from super classes · Issue #810 · androidannotations/androidannotations
X Title: Order of calling @AfterViews annotated methods from super classes · Issue #810 · androidannotations/androidannotations
Description: I have such inheritance hierarchy: A -> B -> C (both A and B are abstract activities/fragments). All classes have methods with @Afterviews annotations - lets say initA, initB and initC What I have noticed, if I just compile project (I'm ...
Open Graph Description: I have such inheritance hierarchy: A -> B -> C (both A and B are abstract activities/fragments). All classes have methods with @Afterviews annotations - lets say initA, initB and initC What I have ...
X Description: I have such inheritance hierarchy: A -> B -> C (both A and B are abstract activities/fragments). All classes have methods with @Afterviews annotations - lets say initA, initB and initC What I...
Opengraph URL: https://github.com/androidannotations/androidannotations/issues/810
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Order of calling @AfterViews annotated methods from super classes ","articleBody":"I have such inheritance hierarchy: \nA -\u003e B -\u003e C (both A and B are abstract activities/fragments). \nAll classes have methods with @AfterViews annotations - lets say initA, initB and initC \n\nWhat I have noticed, if I just compile project (I'm using AndroidStudio, but as I remember I had similar problem in Eclipse), after changing something in class B, methods will be called in order:\ninitB, initA, initC \nAfter clean rebuild i get the correct order: \ninitA, initB, initC - until I change again something in B \n\nI think they should always be called in order consistent with inheritance hierarchy, otherwise it causes lots of unexpected bugs if i forget to do clean rebuild \n","author":{"url":"https://github.com/AntekM","@type":"Person","name":"AntekM"},"datePublished":"2013-12-12T02:52:02.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":13},"url":"https://github.com/810/androidannotations/issues/810"}| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:52106932-6bec-46bf-696d-e1c5ccec916c |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | B256:338161:668890:892178:6A5FFB9E |
| html-safe-nonce | be649b878cfed6d4b396b5dce12ce11ebdadcd885ed6a8129cc10850d0bfd1fd |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJCMjU2OjMzODE2MTo2Njg4OTA6ODkyMTc4OjZBNUZGQjlFIiwidmlzaXRvcl9pZCI6IjM4MjMwODI4NDAxNTU3NDkyNzgiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | c86c3abe482978b97ad05dda5914f1863a0ef932a0a93813bbe181a1bb518cb8 |
| hovercard-subject-tag | issue:24154834 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/androidannotations/androidannotations/810/issue_layout |
| twitter:image | https://opengraph.githubassets.com/76eb8a929058c89f18ce74e2a5b82e832acdc9697075db83fdb8d0fb1f3e7c31/androidannotations/androidannotations/issues/810 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/76eb8a929058c89f18ce74e2a5b82e832acdc9697075db83fdb8d0fb1f3e7c31/androidannotations/androidannotations/issues/810 |
| og:image:alt | I have such inheritance hierarchy: A -> B -> C (both A and B are abstract activities/fragments). All classes have methods with @Afterviews annotations - lets say initA, initB and initC What I have ... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | AntekM |
| hostname | github.com |
| expected-hostname | github.com |
| None | 79522f2cee5c5409f33a714312a1a68d41ad77a807626020d980fb1eb81def07 |
| turbo-cache-control | no-preview |
| go-import | github.com/androidannotations/androidannotations git https://github.com/androidannotations/androidannotations.git |
| octolytics-dimension-user_id | 1315313 |
| octolytics-dimension-user_login | androidannotations |
| octolytics-dimension-repository_id | 3116751 |
| octolytics-dimension-repository_nwo | androidannotations/androidannotations |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 3116751 |
| octolytics-dimension-repository_network_root_nwo | androidannotations/androidannotations |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 3df4fbea9b6b5ead5c6724a99dc5f5b62caa864b |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width