[pvr.hts] Fix dvr delete response timeout value. Must be msecs, not secs...

[ksooo]

Followup to #415.

@Jalle19: Yesterday I've learned from Kodi that deleting recordings within 30 msecs is not really working. ;-)

[Jalle19]

Good catch, thanks!

[ksooo]

Slightly improved.

[opdenkamp]

@Jalle19 no more merging in PRs here until we've got the binary add-on PR in please.

[opdenkamp]

this PR isn't right anyway, you should not be checking settings input here.

[opdenkamp]

so remove the std::max stuff

[Jalle19]

@opdenkamp what do you mean? We want to use a 30 second timeout unless the configured response timeout is larger than that.

[Jalle19]

I'll port the fix once the addons have been transitioned to their new homes, don't worry.

[opdenkamp]

so you can configure a > 30 sec timeout in settings but won't use it in this situation? why?

and no merging in new ones as discussed in the other PR. this repos is frozen now except for changes in previous branches.

edit: typo

[ksooo]

so you can configure a > 30 sec timeout in settings but won't use it in this situation? why?
For the records: The idea is exactly to use the settings value if it is > 30 secs

this PR isn't right anyway, you should not be checking settings input here.
Why? Settings are used at several places in Tvheadend class. It even has a member m_settings (which, btw I should have use instead of tvh->GetSettings()).
- std::max(30000, tvh->GetSettings().iResponseTimeout))) == NULL)
+ std::max(30000, m_settings.iResponseTimeout))) == NULL)