Reply to thread

Message: <blockquote data-quote="CyberSimian" data-source="post: 1253698" data-attributes="member: 141969"><img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite3" alt=":(" title="Frown    :(" loading="lazy" data-shortname=":(" /> <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite3" alt=":(" title="Frown    :(" loading="lazy" data-shortname=":(" /> <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite3" alt=":(" title="Frown    :(" loading="lazy" data-shortname=":(" />My choice (in decreasing order of preference) would be:(1) To have the red-dot function part of the MP base product.  In this way, the function is available to all MP users without having to install any plugins.  But we must be realistic; with so few developers, this may never happen.(2) To have the red-dot function part of an official MP plugin.  In this way, the function is available to every MP user who wants to use it.  [USER=68833]@ajs[/USER] 's changes to LMH seem to provide this. (I need to do more testing, to see if I can reproduce the problem that [USER=54906]@catavolt[/USER] found.)(3) To have the red-dot function part of a new plugin that implements only the red-dot function. This keeps the function self-contained, but means that the user has yet another plugin to install and worry about. To me, this does not seem to have any advantages over (2). Also, LMH was already providing info about active recordings, so LMH seems like a natural fit for the red-dot function (and [USER=68833]@ajs[/USER] 's changes seem to have made it work correctly, whereas previously it did not).(4) To have the red-dot function part of a single-user's private build of the MP source. I suspect that this occurs when a user wants a particular facility, but the view of the development team is that it does not fit in with MP conventions (either internally or externally), or "TV Server" is in the universally-despised code freeze, or that it is a low priority change that is unlikely ever to be implemented. The problem is that this solution is available only to the author, or to the few who might find a relevant zip file in a thread.  And there is the ongoing problem of maintenance, with these private builds becoming incompatible with new releases of MP. The "Sky EPG" build of MP is like this -- it seems to stop working with every new release of MP, and the author has long since moved on to other things, inconveniencing those users who were relying on that build.Of the choices presented, I think that (2) is the best compromise, provided that it can be made to work correctly in all cases (still testing that).  Or, to put that another way, I think that (2) is the "least-worst" compromise.-- from CyberSimian in the UK</blockquote>

Verification