Input data: Any TV tuner card (i have DVB-S), some channels mapped to that tuner. One channel in transponder changes its name. We start scan in TVConfig.
Current situation: tvserver scans that transponder, sees that one channel has changed its name, and changes TuningDetails name in our DB. MP channel name will not be changed (for various reasons, listed below).
Desired situation: the channel in MP changes its name according to changed name in TuningDetails for this channel.
Reasons for current behavior as i understand them:
1. A channel can be renamed, and i don't want to loose my custom name after changing transponder channel name.
2. One MP channel can have several TuningDetails, so channel name can be ambiguous (unclear, name from what TuningDetails should be used for MP channel name).
3. Any other reason i'm currently not aware of.
So i suggest to :
either do some automatic renaming for the cases when only one changed TuningDetail is configured for MP channel (or the old name of TuningDetails was the same as MP channel name, and this TuningDetails was the first one in the TuningDetails list for that channel),
or possbility to do that at later time (via button press).
Both solutions will overwrite my custom names, so to avoid this we have to mark the channels that were renamed by user. Another boolean DB Field "IsCustomName"? Does it worth it? how many users rename their channels?
First solution should be default active with checkbox that deactivates this function for those who doesn't need that feature (for whatever reason, don't know any atm).
@mm1352000 Correct me if i'm wrong.
So before i implement it, I want to clear all pros/contras and choose the solution most comfortable for the majority of users.
Current situation: tvserver scans that transponder, sees that one channel has changed its name, and changes TuningDetails name in our DB. MP channel name will not be changed (for various reasons, listed below).
Desired situation: the channel in MP changes its name according to changed name in TuningDetails for this channel.
Reasons for current behavior as i understand them:
1. A channel can be renamed, and i don't want to loose my custom name after changing transponder channel name.
2. One MP channel can have several TuningDetails, so channel name can be ambiguous (unclear, name from what TuningDetails should be used for MP channel name).
3. Any other reason i'm currently not aware of.
So i suggest to :
either do some automatic renaming for the cases when only one changed TuningDetail is configured for MP channel (or the old name of TuningDetails was the same as MP channel name, and this TuningDetails was the first one in the TuningDetails list for that channel),
or possbility to do that at later time (via button press).
Both solutions will overwrite my custom names, so to avoid this we have to mark the channels that were renamed by user. Another boolean DB Field "IsCustomName"? Does it worth it? how many users rename their channels?
First solution should be default active with checkbox that deactivates this function for those who doesn't need that feature (for whatever reason, don't know any atm).
@mm1352000 Correct me if i'm wrong.
So before i implement it, I want to clear all pros/contras and choose the solution most comfortable for the majority of users.
Last edited: