Started on: 2007-02-19
last update: 2007-02-19
Summary:
Skip Steps doesn't allow values in minutes and seconds
Area:
Config + TV/Video/Music etc
Description:
Finally there is an option in config (in svn) to allow customised skip steps. Ad breaks in the UK are usually about 4.5 minutes, so I type in 270 seconds, but I am then told values have to be in whole minutes! despite the user adding the values in seconds. It makes a good idea of little use to me, so I don't bother to use it. I'm sure this restriction wasn't in an earlier svn, are we going backwards?
Fortunately You can bypass this by manually editing the <entry name="skipsteps"> entry in MediaPortal.xml file. It won't display correctly when you actually use it (270 secs will display as 4 mins) but it DOES actually skip the right amount. I'm guessing the coder, altered it to enforce this rule rather than make the display work properly, which is a shame. Personally I wouldn't enforce any rules. If values are not in ascending order, then just re-order them before saving. For the display you can just make it 4.5 mins or 4.1 rounded to nearest 1dp, same for hours, that'll fit in the space available.
For now I'll stick to editing the xml file but unfortunately you have to set it back every time you run config or it shoves the default vals back in.
last update: 2007-02-19
Summary:
Skip Steps doesn't allow values in minutes and seconds
Area:
Config + TV/Video/Music etc
Description:
Finally there is an option in config (in svn) to allow customised skip steps. Ad breaks in the UK are usually about 4.5 minutes, so I type in 270 seconds, but I am then told values have to be in whole minutes! despite the user adding the values in seconds. It makes a good idea of little use to me, so I don't bother to use it. I'm sure this restriction wasn't in an earlier svn, are we going backwards?
Fortunately You can bypass this by manually editing the <entry name="skipsteps"> entry in MediaPortal.xml file. It won't display correctly when you actually use it (270 secs will display as 4 mins) but it DOES actually skip the right amount. I'm guessing the coder, altered it to enforce this rule rather than make the display work properly, which is a shame. Personally I wouldn't enforce any rules. If values are not in ascending order, then just re-order them before saving. For the display you can just make it 4.5 mins or 4.1 rounded to nearest 1dp, same for hours, that'll fit in the space available.
For now I'll stick to editing the xml file but unfortunately you have to set it back every time you run config or it shoves the default vals back in.