Oolite Bulletins

Rese249er wrote:

No kidding. As for keyconfig.plist, I don't think so. It'd be a new key.

I figured that it would be.... I guess I don't understand just why that would be a problem .

CommRLock78 wrote:

Rese249er wrote:

No kidding. As for keyconfig.plist, I don't think so. It'd be a new key.

I figured that it would be.... I guess I don't understand just why that would be a problem .

Because you can't just look at your computer seriously and say "old boy, I want you to accept a new key for Oolite". There's a difference between computer programs and magic.

The developers would have to implement the new key and make it a part of the program. In other words: what you're asking for is a completely new, not yet existing part of the game itself. It's a feature request. And this means that in order for you to get what you want, one of the developers would have to look at it, decide that it's a meaningful and worthy request (possibly consulting with the other developers about it), further decide that it should be implemented at this stage (as opposed to at some later stage in an unknown future), and actually have the resources and the time to do it.

That's basically what's happening each time when somebody requests a functionality that doesn't yet exist in Oolite.

Having said that, feature requests that require a new key to be programmed for some new functionality are especially tricky, because there are only so many keys, and many of them are already taken. Therefore it becomes progressively more difficult (steadily progressing towards "plainly impossible") to find a yet unused key and use it for something completely new. Thus, this type of feature requests would need to be considered really very worthy in order to get implemented.

Commander McLane wrote:

Having said that, feature requests that require a new key to be programmed for some new functionality are especially tricky, because there are only so many keys, and many of them are already taken. Therefore it becomes progressively more difficult (steadily progressing towards "plainly impossible") to find a yet unused key and use it for something completely new. Thus, this type of feature requests would need to be considered really very worthy in order to get implemented.

Yep.. because we're now down to only 11 unassigned 'standard' keys left..

I don't recall using 'W' nor 'S' for anything ('w' and 's' perhaps )

Commander McLane wrote:

<SNIP>There's a difference between computer programs and magic.<SNIP>

Magic, eh? I don't recall asking anyone to perform magic

CommRLock78 wrote:

I don't recall using 'W' nor 'S' for anything ('w' and 's' perhaps )

If the developers wanted to implement "full throttle" and "kill throttle" keys, SHIFT-W and SHIFT-S would be kind of the logical choices, indeed.

Commander McLane wrote:

SHIFT-W and SHIFT-S would be kind of the logical choices, indeed.

Probably not for windows as I read that SHIFT-Q quits Oolite on those platforms. That would be a read full stop when one presses the wrong key .

Eric Walch wrote:

Commander McLane wrote:

SHIFT-W and SHIFT-S would be kind of the logical choices, indeed.

Probably not for windows as I read that SHIFT-Q quits Oolite on those platforms. That would be a read full stop when one presses the wrong key .

That would not be good - however, on the topic of keys that are too close, 'a' and 'd' sometimes get hit instead of 's', as I learned recently trying to dock with a Seedy Space Bar. Caution would definitely need to be exercised for people running under windows.

Eric Walch wrote:

Commander McLane wrote:

SHIFT-W and SHIFT-S would be kind of the logical choices, indeed.

Probably not for windows as I read that SHIFT-Q quits Oolite on those platforms. That would be a read full stop when one presses the wrong key .

It could always be changed to require a double-press, as was done for the Escape key..