On 12/1/05, Benji Mouse <benji.the.mouse@xxxxxxxxx> wrote: <snip> > > I wonder what's different between the input handling of the remote > configuration step, and the input handling of the running program, and > what I could've done to make them behave differently. > > Any suggestions on where to go from here? > Sorry I didn't mention this before. If I had noticed it, I would have. It just now occurred to me that something else is wrong. And, I think it shows that the problem that I'm dealing with isn't an input problem at all - it's just a symptom. When starting VDR, the info banner showing the channel, what's on, etc. is normally displayed for a few seconds. Well it just occurred to me that it's not being displayed at all. When I start VDR, I get the video playing, and that's it - no interface. I've also discovered that SVDRP isn't working. The log says that it's running on port 2001, but netstat doesn't show anything listening on 2001. I started looking through the code, and it looks like the input routines and the SVDRP socket construction are all tied to the interface class. This leads me to believe that fixing whatever is causing the interface not to show up may fix the input and SVDRP problems. Another interesting thing - If I don't load ANY plugins, SVDRP will start (netstat shows it listening on 2001). Of course it won't accept any input, but at least the socket is there. If I load a plugin (remote, for example, but I've verified it with others, also) the socket doesn't show up. I'm going to keep digging around on my own, but if anyone has any suggestions, I would greatly appreciate them. Thanks, Benj.
