Klaus Schmidinger schrieb: > Andreas Brugger wrote: > >> Hi Klaus! >> >> Klaus Schmidinger schrieb: >> >>> Christian Wieninger wrote: >>> >>>> or the search timer that was >>>> responsible for the timer. I think, VDRAdmin works the same way. >>>> After the recording is done this info was available til now in the >>>> recordings description. If I understood you right, this info should >>>> now be moved to the 'aux' field. Do you plan any way, to display >>>> the 'aux' value for timers and recordings in VDR's OSD? >>> >>> >>> >>> >>> The recorded channel is already stored in the 'C' record of the >>> info.vdr >>> file. If necessary, that information can be displayed in the >>> cSkin::SetRecording() function. The actual "aux" value of a timer >>> has no >>> conceivable meaning to VDR, so there's no point in displaying it, >>> I'd say. >> >> >> >> But isn't that just private information? I don't see any way to get >> that information except reading the info-File directly. >> Could you please add a function to derive this information as I think >> this could be a nice feature in a skin? > > > There will be a function to retrieve the 'aux' string from > cRecordingInfo. > However, I don't see what a skin (that doesn't know anything about what > the actual content of that string means) could reasonably do with it. > Sure, it could display it, ending up in something like > > Aux: 123blafaslhisomeinf456this789ismystring > > Meaning: the string could be *anything* (even non-printable characters). Sorry, my question wasn't written very well. I meant the channelID. Is there (or will there be) a way to retreive this ID from the info.vdr via the API? I think the aux-field would always have to be acessable via the API to use it plugins and not just scripts. But I don't know either if viewing this info in the skin makes any sense ... Bye, Andreas Brugger
