C.Y.M schrieb: >>Why a missing case? >> >> >> > >You are right, I misread the code. It seems that one of the four context types >is not parseable. Since I only get two "Bad character data" error messages >during the initial startup of VDR, I am guessing the problem has to do with the >skin. > > > I think so too, but haven't looked into the code yet. >>>Not to change the subject about the issue above, but would it also be >>>possible >>>to add the left/right scrolling back to the new menu display items >>>(ie; current >>>recordings and next timer)? >>> >>> >>> >>> >>I don't think that is too nice to look at ... especially if you have 2 >>or more recordings which are srolling in all directions (due to the >>different length of the text). And an additional keypress to go into the >>timers-menu if it is unclear what is getting recorded seemes not too >>tiresome to me. Don't you agree? >> >> >> > >IMHO, I think that if any text on the screen is cut off, it is better to allow >scrolling. Text that is cut off just does not appear aesthetic to me. Does >scrolling increase CPU usage very much? > > Maybe I will try it and see if it looks good to me. But if I don't include it, it isn't really hard for the user to change this few lines. I don't think that there is a to big drawback if it would scroll ... I think the skin wouldn't be very much slower. But there is still some potential in the patch I added, because now the timerstatus is checked every time you hit a key in the main menu, so it slows down scrolling. I will fix that for the next realease. Talking of scrolling text: What would you think of scrolling text (in general not only in this case), if it would only scroll in one direction? I think there is no big benefit in scrolling back, as most of us only read in one direction. ;-) On the other side it would be a little more disturbing, as the text would jump back to the beginning ... Bye, Andreas
