Skip to main content

Writing an Android library - Using its own custom Application class (getApplication)



I'm writing an Android library and I wish to use a custom Application class, which will be accessible from all of the library's activities (using the getApplication method).





The problem is when I call the getApplication method from one of my library's activities, it returns the application class of the app using my library (and not the custom class I declared in the library's Android manifest).





My current guess (based on this answer and the official documentation ) is that the application using my library must also declare the custom Application class in their Android manifest - which is a problematic solution, since that application can also have its own custom class (and a single app cannot have more than one custom Application class, right?).





Can anyone offer a better solution? (or verify that this solution is accurate)





Any help will be appreciated..


Comments

  1. Nothing wrong with your custom Application implementation and AndroidManifest.xml. The correct way of using your custom Application in code is casting.

    Suppose you have a MyApplication that extends android.app.Application, to get MyApplication instead of Application:

    Boolean runInTest = ((MyApplication) getApplication()).isRunInTet();


    Hope that helps.

    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