303 replies to this topic

[mirakels]

Ja en dan ook zonder hoofdletter

Actually this is just a translation error. I guess the po file for nl is not up to date.

[mirakels]

Also caching of event data also prevents if your data in the future has changed then you would have strange behaviour, the event in the list would show one thing while the selected data would show another. Granted that is not something that may happen very often and less often for the user to notice it, but it is something that should be taken into account.

I for one would like to know when event data changes. But I do not know how this change will be visible on screen. I guess the eventid will change so I would expect that the event description 'suddenly' dissappers'. If eventid's are reused the you may see a strange description in relation to the event title (assuming a diffferent program starts).
(if you do a page left and page right all should be fine again though

About the caching in general. I still don't like to do that in GraphMultiEPG. The epgcache already is there to cache. So introducing a second cache seems pointless. Saving the long event descriptions for long service list can take quite some memory. And AFAIK the performance is quit good as it is now. I cannot see any delay between pressing a cursor key and the update of the event description.

[awx]

Also caching of event data also prevents if your data in the future has changed then you would have strange behaviour, the event in the list would show one thing while the selected data would show another. Granted that is not something that may happen very often and less often for the user to notice it, but it is something that should be taken into account.

I for one would like to know when event data changes. But I do not know how this change will be visible on screen. I guess the eventid will change so I would expect that the event description 'suddenly' dissappers'. If eventid's are reused the you may see a strange description in relation to the event title (assuming a diffferent program starts).
(if you do a page left and page right all should be fine again though

About the caching in general. I still don't like to do that in GraphMultiEPG. The epgcache already is there to cache. So introducing a second cache seems pointless. Saving the long event descriptions for long service list can take quite some memory. And AFAIK the performance is quit good as it is now. I cannot see any delay between pressing a cursor key and the update of the event description.

epgcache is not really a cache but more of a database then anything else (from the looks of it).

Its up to you if you want to cache the data or not, I run my own version so I am not really affect by this decision. There is minimal memory usage for caching the current page of data. I dont like to display things incorrectly so my vote is for caching instead of presenting the user with incorrect results from time to time. This may be especially confusing for users who do not have underlying knowledge of the situation and will just think there is a bug in the software.

Yes, paging fixes the issue but thats a hack solution to work around an actual problem.
The real solution would have to have some sort of async notification that underlying data has changed, but that is not a trivial task.

[lasa]

Where can I change the colors for the current program? I am not fond of the green background.