Are the test sources included in the plugin? And if so, how do i execute the
tests?
Am 06.08.2010 02:00 schrieb "Tobi" :
Rainer Blickle wrote:
> How do you (everyone subscribed to this list) test your developed code ?
In the Vodcatcher plugin I used CxxTest:
http://projects.vdr-developer.org/gi
Why don't you move it later in your boot sequence or simply add a
wait-til-the-IR-is-ready to your tv script? I don't use runvdr but It
should be very simple to do.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
On 6 August 2010 08:41, Peter Odéus wrote:
> The problem remains. In 9 times out of 10 vdr will fail to start due
> to USB IR not being loaded by the time the script "runvdr" chmods the
> permissions on input devices.
>
> /dev/input/event[1-4] are being loaded in time, but as I wrote,
> /dev/input
Am 06.08.2010 10:12, schrieb Rainer Blickle:
Are the test sources included in the plugin?
Yes
And if so, how do i execute the tests?
For the vodcatcher plugin:
make runtests
Tobias
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cg
> Running an external commad after a download is finished sounds like a
> good idea. I'll implement it in the next version.
Great, thanks. Those who have their tv still connected to FF-card tv
output will have to transcode sooner (with the external command) or
later (mplayer plugin, etc) anyway.
Ideally, I'd like a way to "ask vdr" the status of the CAM from a script.
I know this is available on the OSD by going into the "SETUP > CAM" menu
where the CAM is displayed as "CAM Ready", "CAM Present" or "Alhpacrypt"
but I need to do this outside the OSD.
Anyone have any ideas how to do thi
