On Sunday 06 November 2005 15:04, Bruce Markey wrote: > Joseph A. Caputo wrote: > > Kevin Kuphal wrote: > > > >> Bruce Markey wrote: > ... > >>> This was absolutely deliberate. Later means 'the scheduler > >>> decided it may be best to postpone this so hit "Record anyway" > >>> if you'd rather have this ASAP'. Earlier means 'who gives a rats > >>> ass, it's going to record earlier anyway'. > >>> > >>> States like rsInactive, rsLowDiskSpace, rsLaterShowing, etc. > >>> are active font to tell the users that it coudda, shouldda, > >>> wouldda record and the user may want to do something about. > >>> rsPreviousRecording, rsEarlierShowing, rsRepeat, etc. is > >>> just trivial crap. The show has been or will be recorded > >>> and this is all just 'oh, by the way...'. It could be said > >>> that a Later is going to record eventually but I actively > >>> look for Laters to see if things shuffled around the I'd > >>> most prefer. > ... > > Thing thing is here, we're not trying to draw the user's attention. > > Dunno where the "we" came from
Heh :-) That's "we" as in... the entire Myth development community. Sorry if I made it sound like I'd ever contributed anything to this particular featre. > but as I said, I am absolutely trying > to draw attention to things where the user may want to respond to the > situation. > > > This *is* supposed to be an "oh, by the way". You told the scheduler to > > "Supposed to"? ;-) I created the status column in viewschedule, > the idea of mnemonic letters to show the 'rs' status, the coloring > of fonts based on the recstatus, specifying rsLaterShowing and > rsEarlierShowing in place of rsOtherShowing (for this exact issue, > mind you) and collaborated with gigem on the issues surrounding the > "Reschedule Higher Priorities" feature. I can tell you with absolute > certainty that the very existence of an "L" state is because it is > supposed to inform the users that a recording will be postponed and > the user may want to reconsider that decision. > > > "record one showing", > > I also invented FindOne which is entirely original work unique to > MythTV. No other DVR had anything like this but I'd expect that, in > the future, this will become a standard feature that users expect > to find on anything calling it's self a DVR. > > > or some other similar rule that gives the > > scheduler the freedom to choose between multiple showings. All > > showings > > except the one that will actually get recorded are shown in an > > inactive > > Huh, no they are not. The statuses where the user needs to be informed > that they may want to respond are shown in the active font. This > includes things like rsTunerBusy, rsLowDiskSpace, rsTooManyRecordings > for max episodes, rsInactive to remind that the inactive flag is > still on and needs to be cleared for this rule to continue recording, > and rsLaterShowing which says that this could be recorded in this time > slot rather than allowing it to be postponed. I even added a new type > recently, rsNotListed to point out that the listings changed and a > Single will not record. I also recently changed rsDontRecord to the > active font. This is useful if a showing is marked rsDontRecord a > few days ahead of time but then things changed. You can see that > you may want to remove this override if things will fit nicely now. > > > font, purely for informational purposes, regardless of whether they > > are > > earlier showing or later showings. Oops, sorry... I was unclear there. Of course I neglected to mention the items that show up very clearly in other fonts, such as conflicts or lack of a resource, where an program will not be recorded at all because of some condition the user may want to resolve. > > I appreciate your opinion and understand exactly what you are saying > but your assumption that Later and Earlier are equally important > should > be reconsidered for your sake (I've resolved this for myself a couple > years ago ;-). The Celebrity Poker Showdown you are recording tonight > will be shown three times next Wed. and four more times next Thur. > Big whoop. Tonight's season finale of "Battlestar Galactica" is being > put off until next Thur. because tonight is the only time slot to > record -10 "Bowling for Dollars" starring Wink Martindale. What!!! > > Part of the deal with "Reschedule Higher Priorities" is that the > user needs to be informed that the scheduler has made this logical > but blind decision. Whether a Later is caused by SMH, input preference > to choose a later time to fit on the preferred card, or losing a > conflict for a time slot but there is a later showing, the fact that > the user could choose to record this earlier showing should not be > hidden. Yes, I can see that you're right... "L" is of more significance to the user than "P". My overall point (betcha didn't think I had one :-) is that whatever the behavior has been lo these past months (and I've got myself so mixed up now reading back over this thread that I don't even know what that is) has been working great for me, so don't change it! :-) -JAC _______________________________________________ mythtv-dev mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
