Note that there are some explanatory texts on larger screens.

plurals
  1. USDiego Tori
    primarykey
    data
    text
    plurals
    1. COObviously, it's an example, so that was supposed to be imageParams. Even then when I created the LayoutParams object and passed it into the view, it still didn't work.
      singulars
    2. COSo what you're saying is that every time I call my function to fetch images, I should assign a cache state (int or enum), and based on that current state, it would reference the appropriate cache when downloading or pulling images from cache? I dunno if that will work, since I have functions that for example purge the cache after idling out for a set amount of time. If one activity calls the download function for a particular cache, and then another on top of it calls that same function, the last caller will have its cache purged since it set the current cache state.
      singulars
    3. COMy cache object is already a singleton. However, I am trying to see if I should convert the routines that download, save, cleanup, and recover my images from cache into a singleton. In other words, if ImageDownloader is a singleton, that means I would have to switch the appropriate cache objects when getting the instance. So if I had one activity using that class to download ListView thumbnails and then open out an activity on top of it to fetch an image for an ImageView, wouldn't my singletoned ImageDownloader start saving to that cache of the child activity instead of the ones for thumbnails
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload