On 07/06/05, Stuart Morgan <stuart at tase.co.uk> wrote:
> On Tue 7 June 2005 10:11, John Pullan wrote:
> > TBH the update code is probably correct in principal but in practice
> > stuff goes wrong. I do believe that it should update the channel table
> > automatically in the same way as STBs. However we have issues at the
> > moment when people change the "channel idents" etc.
>> The major issue is that the 'updates' overwrite current channel configurations
> including icon paths, xmltvids, visible flags and as you've said customised
> channel callsigns etc It also breaks scheduled recording because the channel
> number is changed too
>> The code simply needs to update the necessary fields instead of overwriting
> everything.
> --
Err yes in principal but harder in practice :) . As I understand it
it's identifying the service (channel) which is the hard bit. In the
uk this is a no-brainer because our service id's stay fixed. However,
Taylor tells me that we're unusual in this regard and that the only
thing which stays the same is the channel ident. (Same issue as with
the xmltvid discussion)
At the moment the code IMHO is too aggressive and ends up deleting and
then adding channels. The offending code is around line 739 in
siscan.cpp but until we have a way of uniquely identify the channels
it's probably going to be hard. Taylor has but forward the suggestion
of adding another field to the channel table with a read only copy of
the channel ident in it.
--
John