…tion-declaration Which function would have been called is a guess at this point, especially in regards to wtv media (which obviously no-one is using)
Fixes #11027. Removes the "DispRecGroupAsAllProg" setting (Show filter name instead of "All Programs"), and always uses "All Programs" as the first group name. Removes the unnecessary prefix from the titles of the group entries. Fixes the (not-yet documented) "group" widget of the watchrecordings window in recordings-ui.xml to always hold the current group filter name. Themers are suggested to display the current group filter in a textarea, e.g.: <value>Watch Recordings</value> <template>Watch Recordings - %1</template>
clang++ is too smart for it's own good here. It detects that ZMQ_ASSERT's aren't using their values in the profile build. Other than these it doesn't detect any additional unused values over g++ and icpc so we suppress these in the clang build. Note: We do not suppress the "unused-result" warnings which do catch bugs the other compilers do not..
There was already a NetStream class defined in the RAOP code, the compiler would get confused and call the incorrect destructor. Rename private class to _NetStream
We weren't setting and clang++ flags so we got excessive output. clang errors out in some cases when it sees the same command line option twice. The first problem has been addressed in configure and the second in settings.pro.
By factoring out the description into a super query the performance can be greatly improved (e.g. from 2 minutes to 2 seconds) Thanks to sphery for inspiration by [d9fb218] and justinh for testing and fixing my braino with the column order. Fixes #10023
and new MytBrowser translation from Walter Cheuk Closes #11254
Some gcc specific handling of UTF-8 codes had snuck into the code. This should silence some icc warnings and also allow compilation under g++ to always produce the correct code.
If a recorder was deleted after SetNextRecording has been called it would leak a RecordingInfo and a RingBuffer. The RecordingInfo is no big deal but the RingBuffer is holding an open file descriptor and the application will start to misbehave if after we leak just a few hundred of those since select() will no longer function correctly.
AutoRecPriority is a little known and probably even less used feature that dynamically adjusts recording priorities based on the user's viewing habits. There's a small chance it could return in the future, but the implementation would be quite different.
Coverity ID 700415
This is another change in the series of changes to remove some scheduler related features and settings that the developers no longer believe are needed or want to support. Remove the Timeslot and Weekslot recording rule types. These rule types are too rigid and don't work when a broadcaster shifts the starting time of a program by a few minutes. Users should now use Channel recording rules in place of Timeslot and Weekslot rules. To approximate the old functionality, two new schedule filters have been added. In addition, the new "This time" and "This day and time" filters are less strict and match any program starting within 10 minutes of the recording rule time. Restrict the use of the FindDaily and FindWeekly recording rule types (now simply called Daily and Weekly) to search and manual recording rules. These rule types are rarely needed and limiting their use to the most powerful cases simplifies the user interface for the more common cases. Users should now use Daily and Weekly, custom search rules in place of FindDaily and FindWeekly rules. Any existing recording rules using the no longer supported or allowed types are automatically converted to the suggested alternatives.