Skip to main content

Assets Confusion



I'm utterly confused. There's an 'assets' folder in my project, but the AssetManager does not refer to this folder. So I have three questions:





First, where is the folder that AssetManager refers to?





Second, how do I put files into that folder?





Third, how do I access the files that I put into my project's 'assets' folder? (Corollary question: what is the purpose of this folder if it's not used by AssetManager?)





The docs completely fail to clarify these issues. Very frustrating.


Comments

  1. You can drag the resources you want in your project to the /assets folder and access them via code by:

    context.getAssets().open(YOUR_FILE_NAME);


    context.getAssets() will simply return an AssetManager instance for your application package, from where you can access the files.

    Hope it helps!

    ReplyDelete
  2. If you have the project file assets/foo.bar, then at runtime getAssets().open("foo.bar") will open that file.

    ReplyDelete
  3. There's an 'assets' folder in my project, but the AssetManager does not refer to this folder.


    Yes, it does.


    First, where is the folder that AssetManager refers to?


    assets/ in your project.


    Second, how do I put files into that folder?


    That depends on your operating system. Most operating systems have "file managers" which support some sort of drag-and-drop mechanism for copying files. If you are using Eclipse, though, either drag-and-drop into Eclipse or be sure to press F5 to update Eclipse for the changes you made to the Eclipse project outside of Eclipse.


    Third, how do I access the files that I put into my project's 'assets' folder?


    Using AssetManager, or sometimes via file://android_asset/ Uri values (and note that it is android_asset, singular, while the project directory is assets/, plural -- very annoying).


    So if I understand you correctly, I should not be doing: AssetManager mgr = getAssets();, which is giving me a completely different folder's contents.

    Nope, just tried it. I'm still getting the wrong folder's contents, ie, not my project's 'assets' folder.


    Then your project is seriously messed up. Many, many developers have this working perfectly fine.

    For example:


    List assets in a subdirectory using AssetManager.list
    AssetManager list not Returning anything
    http://android-pro.blogspot.com/2010/01/understanding-assets.html
    http://android.okhelp.cz/get-assets-folder-files-to-array-of-strings-android-example/

    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