Question concerning v1.7.0.x

[Gripweed]

2) Add the option to disable automatic image deletion by epg123,
and allow users to delete files manually.

The image cache could get quite large, but I for one would be OK with it
taking up an 8TB SSD.

I really don't have any direct comment on your suggestion. I'll go along with you in that for some, they could possibly have their image cache grow quite large. I don't think I would be one of them because as I wrote previously I rarely deal with WMC as anything other than a PVR. In any event, I think it would be advantageous if the storage location could be made user configurable. As it stands now, my image cache is located on my C drive under epg123/images. My C drive is very small, about 100 gigs with 20 gigs free and meant mainly for System and Program files. Data files are stored on other drives or servers which are much bigger. I'd like to see the image cache go on one of those data drives.

edit: damn spell checker!

[garyan2]

Released a new version. I'm not going to go through all the improvement I've done since last entry, but here are the highlights.

• not using amazon expire dates
• handles unknown user and exceeded download limit errors
• handles If-Modified-Since queries and responses
• works offline
• cache works great locally and on network
• settable cache image retention

One of the changes that will be noticeable is that station logos are now links and no longer embedded in the mxf file. This we reduce the size of the mxf quite a bit for large lineups. Initial load of the guide will show no logos until WMC requests them from the service and it transfers them over.