Perhaps the images that don't work are incompatible in some way. Is it always the same files that work and don't work? Can you package one of the non-working images in your app package and see if you can display it from a pkg:// path?

--Mark

RokuMarkn wrote:

Perhaps the images that don't work are incompatible in some way. Is it always the same files that work and don't work? Can you package one of the non-working images in your app package and see if you can display it from a pkg:// path?

--Mark

I have put the images in the pkg and calling them from there they display with no problem. It's not always the same files, I have replaced the images I am trying to display from a server with other images, other formats, etc. to no avail. They will not display if they are being called from a URL.

I've also just now noticed something else that is weird... I have assigned the same web-based image to both HDBackgroundImageUrl and HDSmallIconUrl and their SD counterparts, and lo and behold it displays on HDSmallIconUrl! So, when the same web-based image is displayed in both HDBackgroundImageUrl and HDSmallIconUrl, all is well. However, if a different web-based image is assigned to HDSmallIconUrl, it will not display.
To clarify, when I run this it works fine:

and when I run this, the image will not display for HDSmallIconUrl:

Do the icons display if you highlight the item then un-highlight it? It sounds like it's just not downloading fast enough.
Either way, my recommendation would still be to download it to tmp: first.

I agree with TheEndless. I think your best bet is to read the image url into a tmp: file first, making sure that if you're displaying more than one image on a screen then they're each downloaded to a separate tmp: file.

I suggested that earlier and the your first attempt at coding that was flawed. You haven't showed us the code that supposedly worked (and checked the http response code), so it's possible that code may have been flawed too. Showing us the actual code you're using would be helpful.

It would also help if you could post a link to one of the image urls that doesn't appear to be working.

Another question: are any of the image urls, "https" urls, or could possibly be redirecting to "https" urls?

dratio wrote:

I've also just now noticed something else that is weird... I have assigned the same web-based image to both HDBackgroundImageUrl and HDSmallIconUrl and their SD counterparts, and lo and behold it displays on HDSmallIconUrl! So, when the same web-based image is displayed in both HDBackgroundImageUrl and HDSmallIconUrl, all is well. However, if a different web-based image is assigned to HDSmallIconUrl, it will not display.

Oh... now that you say it like that - YES!

There is a bug that causes that. Really sneaky. I ran into it when i worked with roListScreen few months ago but did not bother to mention it since i already report way too many bugs "per capita". (Somebody may think i get paid to dig dirt on B/S)

My experience was that HDSmallIconUrl / SDSmallIconUrl do not show up unless i have set the same image in HDPosterUrl / SDPosterUrl. My un-educated guess of why this is happening would be that a cache akin to roTextureManager is used internally for the images and *SmallIconUrl fetches from there but does not pre-load URLs unlike *PosterUrl and *BackgroundImageUrl

By the way, HDSmallIconUrl / SDSmallIconUrl are not documented anywhere so one may argue you are not supposed to use them

PS. And on another note, HDPosterUrl / SDPosterUrl are also undocumented for roListScreen but might be actually the ones you want to use instead of HDBackgroundImageUrl / SDBackgroundImageUrl. I was startled to discover *PosterUrl @ roListScreen.

EnTerr wrote:

dratio wrote:

I've also just now noticed something else that is weird... I have assigned the same web-based image to both HDBackgroundImageUrl and HDSmallIconUrl and their SD counterparts, and lo and behold it displays on HDSmallIconUrl! So, when the same web-based image is displayed in both HDBackgroundImageUrl and HDSmallIconUrl, all is well. However, if a different web-based image is assigned to HDSmallIconUrl, it will not display.

Oh... now that you say it like that - YES!

There is a bug that causes that. Really sneaky. I ran into it when i worked with roListScreen few months ago but did not bother to mention it since i already report way too many bugs "per capita". (Somebody may think i get paid to dig dirt on B/S)

My experience was that HDSmallIconUrl / SDSmallIconUrl do not show up unless i have set the same image in HDPosterUrl / SDPosterUrl. My un-educated guess of why this is happening would be that a cache akin to roTextureManager is used internally for the images and *SmallIconUrl fetches from there but does not pre-load URLs unlike *PosterUrl and *BackgroundImageUrl

By the way, HDSmallIconUrl / SDSmallIconUrl are not documented anywhere so one may argue you are not supposed to use them

PS. And on another note, HDPosterUrl / SDPosterUrl are also undocumented for roListScreen but might be actually the ones you want to use instead of HDBackgroundImageUrl / SDBackgroundImageUrl. I was startled to discover *PosterUrl @ roListScreen.

Interesting. Thanks for all the info I really appreciate it and I will try using the PosterUrl. Then I guess I would just set background and smallIcon to the same Url and it would display. Thanks again!

EnTerr wrote:

(Somebody may think i get paid to dig dirt on B/S)

You could:
https://www.roku.com/about/employment

- Joel