Skip to main content

Difference between code before and after super()


Look at the sample codes below




@Override
protected void onPause() {
...some code here...
super.onPause();
}



and




@Override
protected void onPause() {
super.onPause();
...some code here...
}



When I asked about differences in code, I did not mean about the flow of execution, which is abvious.



So what is the real difference between these codes? When is it advised to use your code before super() call, and when to use your code after super() call? I guess there are situations when this does matter.


Source: Tips4allCCNA FINAL EXAM

Comments

  1. You should not place any of your code before super.onPause(), cause this method lets the system do what it needs to do to properly pause your application. Any code you want to execute in the onPause() callback should be placed after the call to super.onPause(). Hope this helps.

    Quote from Activities:


    Note: Your implementation of these lifecycle methods must always call the superclass implementation before doing any work, as shown in the examples above.

    ReplyDelete
  2. I've never faced any problems calling the super methods before my code and I'm pretty sure I wouldn't have faced any problems if I had called the super methods after my code. But usually super classes instances must be initialized before and deinitialized after subclasses. So ideally you should run your code after calling the super in onCreate(), onStart(), onRestart() and onResume() and before in onPause(), onStop() and onDestroy().

    But one more time. All this code is executed on the UI thread so the order of your code doesn't make great sense excluding some rare cases. But the best idea is to read the source code and to understand how it works and what really happens.

    ReplyDelete
  3. Had to chip in with this link to a thread with an identical subject:

    super.onResume() at beginning or end of method? Does it matter?

    Note the quote from Dianne Hackborn

    Yeah this is a good pattern. In most cases it probably doesn't matter, but
    it's a general rule: during any kind of initialization, let the super class
    do their work first; during any kind of finalization, you do your work
    first.

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex