John Wojnaroski writes: > Appears the command line is being reparsed. This results is the program > failing when a TCP socket is requested for the native-ctrls channel as the > server is created on the first pass and on the next pass trying to create > and bind a "second" server at the same port# fails.
Oops -- I was wondering if reparsing the command line would break anything. The right fix is to have the TCP module read properties and open its socket *after* the command line is parsed, so that the command-line parsing is side-effect free (there may be other side-effects as well). All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
