Declare --props option obsolete and issue a warning message. Rationale:
- props is easy to mix up with the --prop option (for setting properties) - the name is unspecific and inconsistent: other option names describe the protocol -- the way to get the properties. How is, for example, --httpd less about prop(ertie)s? - two identical options easily confuse people, as can be seen in The FlightGear Manual, where --telnet and --props were described differently
This commit is contained in:
parent
ecadeeced4
commit
158e3ebdb4
1 changed files with 7 additions and 4 deletions
|
@ -527,12 +527,15 @@ parse_fov( const string& arg ) {
|
||||||
|
|
||||||
static bool
|
static bool
|
||||||
add_channel( const string& type, const string& channel_str ) {
|
add_channel( const string& type, const string& channel_str ) {
|
||||||
|
if (type == "props")
|
||||||
|
SG_LOG(SG_GENERAL, SG_ALERT, "\n"
|
||||||
|
"****************************************************************\n"
|
||||||
|
"* The --props option is obsolete and will be removed in future *\n"
|
||||||
|
"* releases. Please use --telnet instead with the same syntax. *\n"
|
||||||
|
"****************************************************************");
|
||||||
|
|
||||||
SG_LOG(SG_GENERAL, SG_INFO, "Channel string = " << channel_str );
|
SG_LOG(SG_GENERAL, SG_INFO, "Channel string = " << channel_str );
|
||||||
|
|
||||||
globals->get_channel_options_list()->push_back( type + "," + channel_str );
|
globals->get_channel_options_list()->push_back( type + "," + channel_str );
|
||||||
|
|
||||||
// cout << "here" << endl;
|
|
||||||
|
|
||||||
return true;
|
return true;
|
||||||
}
|
}
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue