Klaus Schmidinger wrote: > Matthias Schniedermeyer wrote: > >> Klaus Schmidinger wrote: >> >>> Matthias Schniedermeyer wrote: >>> >>>> Klaus Schmidinger wrote: >>>> >>>> >>>>> Christian Wieninger wrote: >>>>> >>>>> >>>>>> Atleast my info about the search timer, that triggered the >>>>>> timer/recording will not be visible anymore. What about an >>>>>> additional simple submenu in the summary menu of timers/recordings, >>>>>> e.g. called with the unused key 'blue' labeled 'Aux'. >>>>> >>>>> >>>>> >>>>> The 'aux' field shall be of no concern to VDR, so I don't see why >>>>> there >>>>> should be a button wasted to display it. What's so important about >>>>> that >>>>> information, anyway? >>>> >>>> >>>> >>>> It's of no use of VDR "itself" but like the title/subitle/description >>>> (which are equaly pointless from a purely technical view. Purely >>>> technical you only need channel, time & duration, see for e.g. the >>>> good old VCR. It only needed the channel, time & duration) it can be >>>> vital for the user if s/he needs to find out the culprit who >>>> programmed a timer. >>>> >>>> I had the same question for Master-Timer years ago, because of that >>>> when Master-Timer programs a timer it also prints out which >>>> "torecord"-block (beginning on what line) was responsible for a >>>> specific timer. Then you realize that everyhing is OK, or you tune the >>>> "torecord"-block, "done" it or create a blacklist entry to get rid of >>>> the timer. >>>> >>>> So there actually is a reason for the User to see what is recorded in >>>> the AUX-field. >>>> (And to put "meaningful"-data into the AUX-field. I'm thinking about >>>> putting some more into the AUX-field, like the meantioned block-name >>>> so that you don't have to look it up elswhere. But i haven't do that >>>> in the past because i didn't want to clutter the Summary with too much >>>> data.) >>> >>> >>> What about defining a command in the reccmds.conf file that extracts >>> this info from the recording's info.vdr file? >> >> >> >> If i'm not mistaken we are discussing the "Timer is in the future" >> case, where is timer existists only in the timerlist. >> So there is no info.vdr. :-) > > Oh, I thought this was about displaying the 'aux' string in the "Recording" > menu. Well, I wouldn't mind displaying it in the "Edit timer" menu, since > I myself would never see it, anyway. Christian actually meant both cases. Whereas i was only talking about the Timer-Menu, because i think it is (more) important to be able to figure out the culprit of a timer before it records. You may want (or have to) eliminate a timer before it records for whatever reason. Bis denn -- Real Programmers consider "what you see is what you get" to be just as bad a concept in Text Editors as it is in women. No, the Real Programmer wants a "you asked for it, you got it" text editor -- complicated, cryptic, powerful, unforgiving, dangerous.
