Thanks for the reply Sander.
The TCP/IP control feature could become very useful. It is a good method of controlling CdC from other programs that have a scripting capability. I will certainly take a look at chartlist.pl. Any interesting results or discoveries will be posted here. Thanks Robin -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Sander Pool Sent: 16 March 2007 15:47 To: [email protected] Subject: Re: [skychart-discussion] TCP/IP and CdC v3.0.1.3svn Hi Robin, I'm glad I'm not the only one who cares about the TCP/IP interface! I posted some questions a few weeks ago and got no responses. The biggest problem I have is that I can't reproduce good behavior with scripts that Patrick says should work. I created my own version of chartlist.pl that fixes a few Perl related issues but still doesn't work right. Give that one a try and see if you can make it work. It's in the 'Sander's files' folder under the files section. http://tinyurl. <http://tinyurl.com/yulc7h> com/yulc7h Sander Robin Lauryssen-Mitchell wrote: > > > Hi folks, > > Just starting to play around with TCP/IP control of CdC on Windows XP (SP2). > So highly likely that I am missing something! > > Connected to CdC via telnet (also tried Perl scripts) and get confirmation > back (OK! id=1chart=Chart_1), so far so good. The bad news is some commands > seem to work and others do not. 'Setproj equat' seems to do its thing, > whilst 'search m35' finds m35, centres the display on it and then, > eventually times out (tried this a few times). Nothing much is showing up > with Ethereal (network monitor). > > I fully appreciate that using a beta release, overlaid with a snapshot, is > not the most reliable of things to use<g>! Does anyone know what the > current status of TCP/IP communication with CdC is? Is it broken, under > construction or should be working and I'm doing something real dumb? > > Regards > > Robin > [Non-text portions of this message have been removed]
