Hans Meine <[EMAIL PROTECTED]> schrieb am 31.03.05 13:37:06: > > You suggested to register all jobs to the recordserver, right? > Yes and no - I dislike the idea that my Freevo shuts down if I do not use it > (the idletimer method). I think the user should always initiate the > shutdown. Of course, if he/she shuts down the system, there should not be > "active jobs" (which could be recordings, transcodings, CD/DVD ripping, ...). > > I propose a "waiting for XXX to finish..." dialog in that case, where one can > press cancel if one decides that one wants to listen to music again / > similar. >
Okay, I guess this is a question of taste, but probably one can have both. Georg already wrote that idletimer plugin and added a solution to pause/resume it. I would prefer a automatic shutdown, if it is implemeted correctly. Especially I would like to have this for the nights and the mornings, where noone is using freevo. But as I said the user should be able to choose... > When Freevo boots up, I would add a check whether this is within a small time > window after the programmed bootup, and then directly start that shutdown > wait screen. If that happens in the middle of the night, Freevo will just > shutdown after the recording, but if you happen to see it and want to use > your Freevo box, you could press "Cancel". > > > I agree totally in this. Will something like that be implemented in > > freevo2.0? For the moment I am just looking for a fast and easy solution. > I think this wait-dialog shouldn't be much more difficult than the idletimer, > but one needs to know the Freevo UI internals (which [un]fortunately changed > between 1.3.x and 2.0, so I am not sure if it's worth implementing ATM). > This is why I always thought it is not worth to look in that thing now, but who knows when freevo2.0 will be ready. After looking at your work I have the feeling that I have all the pieces I need, I just have to puzzle them together, that is why I decided to do it now, even if everything will have to be chanced again for 2.0... > > Moreover I understood from your postings that your patches are not able to > > shut down freevo automatically after a recording? > Right. > > > The idletimer plugin would solve that problem. > ..I'd prefer the word "work around".. ;-)) Work around is good enough for the moment :-) > > A helper script which is callable from inside and outside freevo, has the > > advantage, that you can make it the preferred shutdown methode of your > > system. Moreover it is usable for the automatic shutdown and the shutdown > > form the menu. > You're right; actually that's something I've been thinking about already. > (How to cope with external shutdowns.) An even more reliable method would be > to call nvram-wakeup from within the recordserver as soon as the program > schedule changes; as long as no reboot is needed, this allows even an > external halt, even a power outage at any time.) > Right, that would be ideal solution, but that would have to wait for 2.0. > > Thanks again, I hope it is okay for you, if I am messing around with it a > > little bit? > Of course! Thanks, if I get my PC working again (it seems the motherboard is broken), I will work on this on the weekend. Greetings from K�ln Tanja ______________________________________________________________ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193 ------------------------------------------------------- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/Info/Sentarus/hamr30 _______________________________________________ Freevo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freevo-devel
