* Martin Spott -- Monday 19 February 2007:
Melchior FRANZ wrote:
As a first step I'd change all occurrences of --props in the
documentation to --telnet and add a warning message in the code.
No objections, hence: done!
If you're going ahead, then I'll take care of changing the respective
* Melchior FRANZ -- Saturday 05 May 2007:
Melchior FRANZ wrote:
As a first step I'd change all occurrences of --props in the
documentation to --telnet and add a warning message in the code.
No objections, hence: done!
Hmm ... and while adapting some more documents that I had forgotten,
I suggest to finally phase out the --props option. It's badly named
and has been superseded by the --telnet option, to which it is identical:
- properties (props) can be read/set via other networking options,
too, such as with --httpd, so the name --props is misleading
- there's also the
Melchior FRANZ wrote:
As a first step I'd change all occurrences of --props in the
documentation to --telnet and add a warning message in the code.
I never knew that these two are in fact identical. If this is really
the case, then I'm certainly in favour of the proposed action.
If you're
And while we are at it, we should get rid of this ugliness:
} else if ( tokens[1] == set-sea-level-air-temp-degc ) {
[...]
} else if ( tokens[1] == set-outside-air-temp-degc ) {
[...]
} else if ( tokens[1] == timeofday ) {
[...]
} else if ( tokens[1] == play-audio-message ) {
This
On 2/19/07, Melchior FRANZ [EMAIL PROTECTED] wrote:
And while we are at it, we should get rid of this ugliness:
} else if ( tokens[1] == set-sea-level-air-temp-degc ) {
[...]
} else if ( tokens[1] == set-outside-air-temp-degc ) {
[...]
} else if ( tokens[1] == timeofday ) {
[...]
* Curtis Olson -- Monday 19 February 2007:
On 2/19/07, Melchior FRANZ [EMAIL PROTECTED] wrote:
} else if ( tokens[1] == set-sea-level-air-temp-degc ) {
} else if ( tokens[1] == set-outside-air-temp-degc ) {
} else if ( tokens[1] == timeofday ) {
} else if ( tokens[1] ==
* Melchior FRANZ -- Monday 19 February 2007:
Who said nasal?! I said listener. You know that Nasal listeners
are only wrappers around the real listeners (SGPropertyChangeListener).
I meant such a C++ listener -- they were made exactly for such
purposes.
Err ... and I really meant tied
On 2/19/07, Melchior FRANZ [EMAIL PROTECTED] wrote:
I'm not enthusiastic about ripping this direct procedure call
functionality
out and replacing it with a complicated set of nasal based indirections.
Who said nasal?! I said listener. You know that Nasal listeners
are only wrappers around
* Melchior FRANZ -- Monday 19 February 2007:
And set /sim/screenshot 1?
Or even better: set /sim/screenshot /tmp/crashed-again.tga :-)
m.
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's
On 2/19/07, Melchior FRANZ [EMAIL PROTECTED] wrote:
Well, I don't like secret features that can only be used by one
customer, and are of no use for the majority of users. That
doesn't mean that I would like to see the extra commands in help,
because this is exactly the clutter that doesn't
* Curtis Olson -- Monday 19 February 2007:
I don't think it's fair to characterize these as secret features that can
only be used by one customer.
OK, you are right. The customer gets them set up, not knowing about
them. And everyone else can look at the source code. For more serious
work this
On 2/19/07, Melchior FRANZ [EMAIL PROTECTED] wrote:
OK, you are right. The customer gets them set up, not knowing about
them. And everyone else can look at the source code. For more serious
work this will probably always be necessary. Not that it can't all be
documented, but it's a lot of work,
13 matches
Mail list logo
